Can't connect to 2wire HomePortal 1000SW wireless network with WEP enabled

Bug #222793 reported by Jayferd
24
Affects Status Importance Assigned to Milestone
Linux
Unknown
High
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I'm using a Toshiba laptop with an internal wireless card, dual-booting Ubuntu 8.04 (Hardy, with latest updates) and Windoaze, and I'm trying to connect to my parent's home wireless network. They have a 2wire HomePortal 1000SW with a 10-digit hex WEP key. Windows connects to the network with no problems.

When I try to connect from Hardy, NetworkManager prompts me to enter the key. I select the Hex option, enter the key and press connect. NetworkManager then hangs for about 15 minutes while saying "Waiting for network key for HomeNet..." before giving up and telling me I can't connect. This was also an issue in Gutsy.

We've now confirmed that a similar problem occurs with Network Manager, wicd and wlassistant.

After further inspection, we've noticed that the HomePortal unit resets whenever a connection is attempted.

Tags: cft-2.6.27
Revision history for this message
markinct (markinct) wrote :

Equipment:

HP Pavilion dv6700 notebook
Intel 4965 agn wireless card
2Wire Homeportal 1000 SW dsl modem/router/access point, running version 3.5.5 of their software.

Kubuntu 8.04, using NetworkManager
(Windows Vista Home Premium works just fine)

---
I have a similar issue. At first I thought it couldn't negotiate the WEP encryption. But when I stood next to the router I could see that every attempt to connect caused the Homeportal unit to reset, just as if I had power cycled the unit. Network manager progresses to "28%" of connection tasks before timing out.

Unlike my Ubuntu installation, Kubuntu sees wireless networks... In fact, I was able to connect to at least two networks in my neighborhood; a netgear and a linksys.

Revision history for this message
Jayferd (jayferd) wrote :

@markinct: Now that you mention it, I have seen the Homeportal unit resetting. Red light blinks, etc. Updating description soon.

description: updated
Revision history for this message
markinct (markinct) wrote :

I have confirmed that the PC in question can connect to another router using all forms of encryption.

Revision history for this message
bolek (bolek-lolek) wrote : Re: Can't connect to 2wire HomePortal 1800HW wireless network with WEP enabled

I confirm the same issue with the Intel Corporation PRO/Wireless 3945ABG and the 2wire homeportal 1800HW running version 3.5.5 of their software. With the modules iwl3945 and iwlwifi_mac80211.

Jayferd (jayferd)
Changed in linux:
status: New → Confirmed
description: updated
Revision history for this message
bbolker (bolker) wrote :

Same issue: trying to connect resets 2WIRE router.
Dell Inspiron 640m: using Broadcom firmware.
Using ssb, b44 -- tried messing around with ndiswrapper
but didn't help (but I may not have gotten everything right).
Worked fine with the same hardware under Gutsy (argh). Can connect to
at least one other wireless network.

  Would be happy to have this resolved ...

Revision history for this message
bbolker (bolker) wrote :

PS -- same behavior under wlassistant, so (?) not a network manager
problem?

Jayferd (jayferd)
description: updated
Revision history for this message
brian21 (briankeithcha) wrote :

I'm connecting to my 2wire 2701ng with WEP enabled using "<default key on 2wire label> enc open" (the whole thing is the key - minus <>)

I have an HP6700z with the Broadcom 4321AG draft n(4328 chipset).
I'm using ndiswrapper and a driver from Dell to get it working.

Downloaded the driver from:
http://ftp.us.dell.com/network/R151517.exe

unzip -a R151517.exe
cd DRIVER
ndiswrapper -i bcmwl5.inf
ndiswrapper -m
modprobe ndiswrapper

I don't know if any of this will help.
Hopefully it will point you in the right direction.

Revision history for this message
Calcaneo (unicandun) wrote :

I can confirm that this is happening with Hardy + 2Wire Home portal 1800. The problem appeared
with the upgrade to hardy (works fine in gutsy) and only on this router.

Is there any further info I should post.

Thanks for Ubuntu! :)

Revision history for this message
bbolker (bolker) wrote :

Has anyone who has this problem with native drivers been able to work around it by using ndiswrapper? As I mentioned above, I have tried to get ndiswrapper going but haven't been sure I've gotten it set up right ...

I too, would be happy to know of any debugging info I can provide.

from lspci:

02:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
0c:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01)

Revision history for this message
mark (mark-m-wilhelm) wrote :

I've been having the same problem, the upgrade to hardy caused wireless connect attempts to reset the 2wire router. I also tried ndiswrapper with no luck. I don't know if this info is helpful, but I have two different machines here with hardy, different wireless cards, one 32 bit and one 64 bit and both cause the router to reset.

Revision history for this message
bbolker (bolker) wrote :

A few questions:

 1. any hope/expectation of resolution of this, or at least classification
as something other than "Importance=undecided"? (Sorry to be a jerk,
but I really hate to use the cable or boot into Windows in order to work
at home ...)

 2. this seems pretty generic (independent of card, 32/64bit, network-manager
vs wlassistant -- something in the kernel???

 3. is there any debugging info that would be useful? I'm not sure
whether I can get a log from the router after it resets, but maybe
I could give it a shot ...

Revision history for this message
twocows (hockeypuck360) wrote :

Confirmed here as well. When I attempt to connect to my network, the router goes into an infinite loop of resetting (as though I had turned it off) and starting back up.

Setup:
Asus F8Sn notebook PC + 2wire HomePortal 1800HW + Ubuntu 8.04

Revision history for this message
mark (mark-m-wilhelm) wrote :

I have been wondering if this problem has something to do with the wireless driver module. My current module (with Hardy) is "b43.ko" but I recall that it used to be "bcm43xx.ko" - could it be that this change lead to the problem? I really don't know much about these things, but I did try unsuccessfully to revert my driver back to the old one. I used rmmod and insmod and the module loaded, but the wifi led did NOT turn on, so I was unable to test this hypothesis. I'm curious though, if:

(a) anybody else is using b43.ko?
(b) anybody has an idea about how to make bcm43xx work again?

In case you are like me circa a few days ago, and don't know how to check if you are using b43, you can type "lsmod | grep b43" in a terminal - if nothing shows up, you're not.

Revision history for this message
Mike Kusold (kusold) wrote :

I can confirm that this doesn't work. I'm using a HP dv6500t. I don't know how to look up the exact chipset, but mine has draft-n capabilities.
lsmod | grep b43 resulted in nothing showing up.

Revision history for this message
twocows (hockeypuck360) wrote :

I've not been able to duplicate this problem on my other laptop. I'm able to connect just fine with it, even using 8.04. The one that connect is slightly older, and this one's pretty new. I don't know if that's helpful.

Revision history for this message
Mike Kusold (kusold) wrote :

To Add to my previous post. I'm using a Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)

Also, did anyone check to see if this: http://www.intellinuxwireless.org/?p=iwlwifi&n=howto-iwlwifi fixes? That's where intel told me to go for drivers for my wireless.

Revision history for this message
bolek (bolek-lolek) wrote :

I have been using 2wire homeportal 1800HW with the Intel Corporation PRO/Wireless 3945ABG and about 2 weeks a go i upgrade the 2wire model and the problem go out!!! so i thing that the problem is a combination between the 2wire firmware and the iwl3945 and iwlwifi_mac80211 modules.

Revision history for this message
Birkir Brimdal (birkir) wrote :

I have the same problem when I try to connect to a 2wire router. The model is HomePortal 1000SW with WEP-64 (a 10 digit hex). I am trying to connect with a Sony Vaio VGN-C140G that connected fine when it had XP and later Vista (please don't make me go back...). My wife's MacBook connects fine. When I try to connect, everyone gets disconnected including the wired connection (saying "network cable has been unplugged"). The normally 3 green LEDs turn off and the top (power) LED turns red like I just plugged the router in. I am running Ubuntu 8.04.

Revision history for this message
bbolker (bolker) wrote :

any news on this issue? still booting into Windows at home to get a network connection :-( . Should I just go out and buy a different router ... ?

  Ben Bolker

Revision history for this message
Mike Kusold (kusold) wrote : Re: [Bug 222793] Re: Can't connect to 2wire HomePortal 1000SW wireless network with WEP enabled

IntelLinuxWireless has a bug repot that is assigned, but it's been assigned
for a few months...
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1505
I also filed a complaint with the BBB because 2wire would not respond to my
requests for the newer firmware. If anyone is interested I'll let them know
what happens with that.

On Tue, Jul 29, 2008 at 10:06 AM, bbolker <email address hidden> wrote:

> any news on this issue? still booting into Windows at home to get a
> network connection :-( . Should I just go out and buy a different router
> ... ?
>
> Ben Bolker
>
> --
> Can't connect to 2wire HomePortal 1000SW wireless network with WEP enabled
> https://bugs.launchpad.net/bugs/222793
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "linux" source package in Ubuntu: Confirmed
>
> Bug description:
> I'm using a Toshiba laptop with an internal wireless card, dual-booting
> Ubuntu 8.04 (Hardy, with latest updates) and Windoaze, and I'm trying to
> connect to my parent's home wireless network. They have a 2wire HomePortal
> 1000SW with a 10-digit hex WEP key. Windows connects to the network with no
> problems.
>
> When I try to connect from Hardy, NetworkManager prompts me to enter the
> key. I select the Hex option, enter the key and press connect.
> NetworkManager then hangs for about 15 minutes while saying "Waiting for
> network key for HomeNet..." before giving up and telling me I can't connect.
> This was also an issue in Gutsy.
>
> We've now confirmed that a similar problem occurs with Network Manager,
> wicd and wlassistant.
>
> After further inspection, we've noticed that the HomePortal unit resets
> whenever a connection is attempted.
>

Changed in linux:
status: Unknown → In Progress
Revision history for this message
mark (mark-m-wilhelm) wrote :

Aha! It works again! So after installing the kernel updates that came through the normal system update thing which popped up for me on August 26, '08 - I have been able to get my card working again using the ndiswrapper approach. On my system at least, the bug is fixed, the 2wire router is now doing just fine - and what a relief! (for reference, using 2wire home portal + bcm4312 rev 01 wifi card on 64 bit hardy).

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
bbolker (bolker) wrote :

  Where is the package available?
  I'm on hardy with security, updates, backports, proposed repositories
enabled and don't see anything above 2.6.24 ... ? (Sorry if I'm missing
something obvious ...)
  [Looking forward to a fix! Unfortunately the upgrade-fix described by
mark above doesn't work for me (but I'm not using ndiswrapper, don't
have time to hack it up right now ...]

  Ben Bolker

Revision history for this message
mark (mark-m-wilhelm) wrote :

Sorry I can't find 2.6.27 either. Is it a package I can get to with synaptic? I googled for what repository to add but couldn't find anything that looked relevant.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Guys,

Sorry for any confusion, you'll need to enable the Intrepid repository in order to install the 2.6.27 Intrepid kernel. If you are unfamiliar with how to enable Intrepid, I'd suggest waiting for the the Alpha5 release to test. Thanks.

Revision history for this message
mark (mark-m-wilhelm) wrote :

I think I'd better wait for the Alpha5 then, I'll probably just end up breaking my system if I try this otherwise.

Revision history for this message
bbolker (bolker) wrote :

In intrepid alpha5, with the workaround cited in another bug report (which itself
was recently fixed) of copying the /lib/firmware/b43 directory from its location
in the previous install to the same place, and restarting network manager,
this appears fixed. Yay! Provided the other bug is really fixed, alpha 6 should
(??) work seamlessly ...

Changed in linux:
status: In Progress → Invalid
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Can anyone else confirm this specific issue is fixed for them with Intrepid's final release? Thanks.

Changed in linux:
status: Confirmed → Incomplete
Revision history for this message
jmunroe (jmmunroe) wrote :

This issue is fixed for me with the final release.

----- Original Message ----
From: Leann Ogasawara <email address hidden>
To: <email address hidden>
Sent: Friday, November 7, 2008 9:42:59 PM
Subject: [Bug 222793] Re: Can't connect to 2wire HomePortal 1000SW wireless network with WEP enabled

Can anyone else confirm this specific issue is fixed for them with
Intrepid's final release?  Thanks.

** Changed in: linux (Ubuntu)
      Status: Confirmed => Incomplete

--
Can't connect to 2wire HomePortal 1000SW wireless network with WEP enabled
https://bugs.launchpad.net/bugs/222793
You received this bug notification because you are a direct subscriber
of the bug.

Status in The Linux Kernel: Invalid
Status in “linux” source package in Ubuntu: Incomplete

Bug description:
I'm using a Toshiba laptop with an internal wireless card, dual-booting Ubuntu 8.04 (Hardy, with latest updates) and Windoaze, and I'm trying to connect to my parent's home wireless network.  They have a 2wire HomePortal 1000SW with a 10-digit hex WEP key.  Windows connects to the network with no problems.

When I try to connect from Hardy, NetworkManager prompts me to enter the key.  I select the Hex option, enter the key and press connect.  NetworkManager then hangs for about 15 minutes while saying "Waiting for network key for HomeNet..." before giving up and telling me I can't connect.  This was also an issue in Gutsy.

We've now confirmed that a similar problem occurs with Network Manager, wicd and wlassistant.

After further inspection, we've noticed that the HomePortal unit resets whenever a connection is attempted.

Revision history for this message
Calcaneo (unicandun) wrote :

I can confirm that with the intrepid release the bug was fixed !!

Thanks!
Carlos

On 11/7/08, Leann Ogasawara <email address hidden> wrote:
>
> Can anyone else confirm this specific issue is fixed for them with
> Intrepid's final release? Thanks.
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> Can't connect to 2wire HomePortal 1000SW wireless network with WEP enabled
> https://bugs.launchpad.net/bugs/222793
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Linux Kernel: Invalid
> Status in "linux" source package in Ubuntu: Incomplete
>
> Bug description:
> I'm using a Toshiba laptop with an internal wireless card, dual-booting
> Ubuntu 8.04 (Hardy, with latest updates) and Windoaze, and I'm trying to
> connect to my parent's home wireless network. They have a 2wire HomePortal
> 1000SW with a 10-digit hex WEP key. Windows connects to the network with no
> problems.
>
> When I try to connect from Hardy, NetworkManager prompts me to enter the
> key. I select the Hex option, enter the key and press
> connect. NetworkManager then hangs for about 15 minutes while saying
> "Waiting for network key for HomeNet..." before giving up and telling me I
> can't connect. This was also an issue in Gutsy.
>
> We've now confirmed that a similar problem occurs with Network Manager,
> wicd and wlassistant.
>
> After further inspection, we've noticed that the HomePortal unit resets
> whenever a connection is attempted.
>

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Setting status to "Fix Released" per the last few comments. Thanks.

Changed in linux:
status: Incomplete → Fix Released
Changed in linux:
importance: Unknown → High
status: Invalid → Unknown
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.