Bug#369054: [pkg-wpa-devel] Bug#369054: wpasupplicant: Loosing wifi
with "CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys"
message
Kel Modderman
kelrin at tpg.com.au
Sat May 27 08:15:15 UTC 2006
Mohammed Adnène Trojette wrote:
> Package: wpasupplicant
> Version: 0.4.8-4
> Severity: important
>
>
> Hi,
>
> this is a short time (around two weeks) since I do not manage to have
> wpasupplicant work correctly through my /etc/network/interfaces
> configuration.
>
> Here it is:
>
> | auto eth1
> | iface eth1 inet static
> | address 10.0.4.2
> | netmask 255.0.0.0
> | broadcast 10.255.255.255
> | gateway 10.0.2.2
> | wpa-driver wext
> | wpa-ssid coloc
> | wpa-key-mgmt WPA-PSK
> | wpa-psk "XXXXXXXXXXXXXXXX"
> | wpa-channel 3
>
> But when I suspend to RAM and then wake, or if I get a dhclient
> running for my eth0 (wired) interface, I loose all wireless and
> /etc/init.d/networking restart does not work anymore.
>
> Here is what I get when I launch wpa_cli:
>
> | Selected interface 'eth1'
> |
> | Interactive mode
> |
> | > <2>Trying to associate with 00:0f:66:d3:55:94 (SSID='coloc' freq=0 MHz)
> | <2>Associated with 00:0f:66:d3:55:94
> | <2>Authentication with 00:0f:66:d3:55:94 timed out.
> | <2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> | <2>Trying to associate with 00:0f:66:d3:55:94 (SSID='coloc' freq=0 MHz)
> | <2>Trying to associate with 00:0f:66:d3:55:94 (SSID='coloc' freq=0 MHz)
> | <2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> | <2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> | <2>Trying to associate with 00:0f:66:d3:55:94 (SSID='coloc' freq=0 MHz)
> | <2>Trying to associate with 00:0f:66:d3:55:94 (SSID='coloc' freq=0 MHz)
> | <2>Trying to associate with 00:0f:66:d3:55:94 (SSID='coloc' freq=0 MHz)
> | <2>Trying to associate with 00:0f:66:d3:55:94 (SSID='coloc' freq=0 MHz)
> | <2>Trying to associate with 00:0f:66:d3:55:94 (SSID='coloc' freq=0 MHz)
> | <2>Trying to associate with 00:0f:66:d3:55:94 (SSID='coloc' freq=0 MHz)
> | <2>Associated with 00:0f:66:d3:55:94
>
> And weirdly, the interface gets to associate and work correctly as soon
> as I reboot my access point... And no, there is no problem with my
> access point.
>
> I don't know if this is something directly related to wpasupplicant
> (I've tried applying #365525's patch but in vain) or maybe another soft,
> like udev (one of the only packages that I got upgraded within the last
> two weeks).
>
I do not expect either would improve the situation you describe.
> Please could you have a look and tell me what to try or what to provide
> for debugging?
>
>
Can I please see the output of ifup --verbose eth1 ?
Also, I seem to remember a problem with wpa_supplicant not working on
resume, I'll look into that.
Thanks, Kel.
More information about the Pkg-wpa-devel
mailing list