[ipw2200] NM doesn't connect to one particular network

[William Grant]

Binary package hint: network-manager

All Victorian schools use a 802.11x wireless authentication system. It uses Dynamic WEP, and in order to connect with NM we need to force it to use WPA Enterprise with the various settings by selecting `Connect to Other Wireless Network...' Ideally it would allow selection of WPA Enterprise even if it didn't detect it as a WPA network, but that's another bug.

It works fine when you force it connect and enter all the details, and it saves them all to gconf correctly. However, automatic reconnection fails, with completion of stage 2 followed by an infinite loop of `old_dev has_link? 1' and `old_dev && new_dev!!' every 5 seconds. I guess this is probably because it continues to detect it as a WEP-only network, and gets thoroughly confused when it sees WPA details.

All this is rather inconvenient, as I have to manually enter the details and select certificates every time I wish to connect.

[Alexander Sack (asac)]

On Tue, Jul 24, 2007 at 11:17:58PM -0000, William Grant wrote:
> Public bug reported:
>
> Binary package hint: network-manager
>
> All Victorian schools use a 802.11x wireless authentication system. It
> uses Dynamic WEP, and in order to connect with NM we need to force it to
> use WPA Enterprise with the various settings by selecting `Connect to
> Other Wireless Network...' Ideally it would allow selection of WPA
> Enterprise even if it didn't detect it as a WPA network, but that's
> another bug.
>
> It works fine when you force it connect and enter all the details, and
> it saves them all to gconf correctly. However, automatic reconnection
> fails, with completion of stage 2 followed by an infinite loop of
> `old_dev has_link? 1' and `old_dev && new_dev!!' every 5 seconds. I
> guess this is probably because it continues to detect it as a WEP-only
> network, and gets thoroughly confused when it sees WPA details.
>
> All this is rather inconvenient, as I have to manually enter the details
> and select certificates every time I wish to connect.
>

What kind of network card/chipset are you using? What driver is
loaded? Do you know?

 - Alexander

[William Grant (wgrant)]

On Sun, 2007-07-29 at 22:42 +0000, Alexander Sack wrote:
> [snip]
> What kind of network card/chipset are you using? What driver is
> loaded? Do you know?

It's an ipw2200.

[Alexander Sack (asac)]

On Mon, Jul 30, 2007 at 09:21:41AM -0000, William Grant wrote:
> On Sun, 2007-07-29 at 22:42 +0000, Alexander Sack wrote:
> > [snip]
> > What kind of network card/chipset are you using? What driver is
> > loaded? Do you know?
>
> It's an ipw2200.
>

Do you have some technical skills and would join #ubuntu-mozillateam
channel on irc.freenode.net and ping me (asac)? I am looking for
someone who can test a few things for me on that chipset.

Thanks,

 - Alexander

[Alexander Sack (asac)]

any improvements with latest gutsy network-manager (0.6.5-0ubuntu9) ?

[William Grant (wgrant)]

It is different with the latest network-manager, but still doesn't work.

[Alexander Sack (asac)]

i don't see the successful connection attempt you referred to in your summary in this log. Can you add the full log please?

[Alexander Sack (asac)]

please try to load your ipw2200 driver module with associate=1 parameter

for that you probably have to stop network manager by

 sudo /etc/dbu*/even*/25NetworkManager stop

and remove the module:

 sudo modprobe -r ipw2100

then reload the module:

 sudo modprobe ipw2100 associate=0

...
let me know if that helps.

[Alexander Sack (asac)]

forgot ... finally start networkmanager again :) ...

sudo /etc/dbu*/even*/25NetworkManager start

[William Grant (wgrant)]

When you say:
 sudo modprobe ipw2100 associate=0
... do you mean associate=1?

[Alexander Sack (asac)]

On Fri, Sep 14, 2007 at 08:51:43AM -0000, William Grant wrote:
> When you say:
> sudo modprobe ipw2100 associate=0
> ... do you mean associate=1?
>

no associate=0 is correct ... please try.

 - Alexander

[William Grant (wgrant)]

OK, I'll try it when I'm next at school. I just noticed you said associate=0 in one place, and associate=1 in another.

[Alexander Sack (asac)]

On Fri, Sep 14, 2007 at 11:10:15PM -0000, William Grant wrote:
> OK, I'll try it when I'm next at school. I just noticed you said
> associate=0 in one place, and associate=1 in another.
>

Could you try associate=0 ?

 - Alexander

[Alexander Sack (asac)]

if you can test what i asked for, please reopen this bug.

Thanks,
  - Alexander

[William Grant (wgrant)]

On Sun, 2007-10-07 at 12:47 +0000, Alexander Sack wrote:
> if you can test what i asked for, please reopen this bug.

Sorry, we were just on school holidays. I've tested with associate=0,
and it still won't associate automatically. It no longer print `old_dev
has_link? 1', but still won't associate automatically. It gets to stage
2 and drops back hundred times, eventually stopping.

I'll attach appropriate excerpts of syslog shortly.

  status new

[Basilio Kublik (sourcercito)]

Hi there
do you still experience this issue with the current version of the application?, could you please try to reproduce this using the live environment of the Desktop CD of the development release - Hardy Heron.

Thanks in advance

[Alexander Sack (asac)]

there are a bunch of improvements in network manager 0.6.6-0ubuntu5 package and the drivers in hardy. can you please test?

[Basilio Kublik (sourcercito)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thanks again!