Comment 59 for bug 548992

Revision history for this message
Stefan Hammer (j-4-deactivatedaccount) wrote : Re: [Bug 548992] Re: Wireless connection frequently drops [deauthenticating by local choice (reason=3)]

 I also think, that it is not a problem of network-manager.
I also have this problem, that the connection disassembles again while
trying to establish it (deauthenticating by local choice (reason=3)) But
I only observe this on a specific network. Windows computers and my
Android device can connect to it, only Ubuntu can't. Setting a static IP
address solves this problem and the connection works in my case.
I think, maybe the threshold for getting an IP address from the DHCP
server is set too small. In case you have a slow DHCP server it takes
maybe longer. If one would wait 500 miliseconds longer, you would get an
IP (this is maybe what the other devices do).
This network I speak from was not secured (open network). Uninstalling
network-manager did not solve the problem. I also tried to connect with
the shell tools.

On 19/10/10 10:46, Marc Reichelt wrote:
> Maybe we are looking at the wrong software here. Could it be that this
> is a problem of wpa_supplicant instead? I attached the specific part of
> my syslog when the deauthentication occurs. For the first 6 lines
> everything's ok, though I believe the DHCP lease time of my university
> network is _way_ too small. But then on line 7 wpa_supplicant tells that
> it has started an authentication - which finally leads to a "wlan0:
> deauthenticating from 00:26:99:50:07:dc by local choice (reason=3)" on
> line 15 and the NetworkManager to reauthenticate.
>
> It is actually funny that this bug seems to occur very often in the
> 'eduroam' university network - maybe the DHCP lease time is the trigger.
> I also encounter this problem at home but not so frequently. I will try
> to use a static IP on my university network today and write a comment on
> what happened.
>
> ** Attachment added: "syslog.txt"
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/548992/+attachment/1701222/+files/syslog.txt
>