Re: wlan0 going UP/DOWN problem

On Sunday 05 December 2010 07:21:03 Steve Kargl wrote:
> It seems some recent change (as in the last 7-10 days)
> has caused an instability in wlan0.  Just a small
> excerpt from /var/log/messages,
> 
> Dec  4 18:54:16 laptop kernel: wlan0: link state changed to UP
> Dec  4 19:11:16 laptop kernel: wlan0: link state changed to DOWN
> Dec  4 19:11:16 laptop kernel: wlan0: link state changed to UP
> Dec  4 19:19:46 laptop kernel: wlan0: link state changed to DOWN
> Dec  4 19:19:46 laptop kernel: wlan0: link state changed to UP
> Dec  4 19:37:01 laptop kernel: wlan0: link state changed to DOWN
> Dec  4 19:37:01 laptop kernel: wlan0: link state changed to UP
> Dec  4 19:45:31 laptop kernel: wlan0: link state changed to DOWN
> Dec  4 19:45:31 laptop kernel: wlan0: link state changed to UP
> Dec  4 19:54:01 laptop kernel: wlan0: link state changed to DOWN
> Dec  4 19:54:01 laptop kernel: wlan0: link state changed to UP
> Dec  4 20:11:16 laptop kernel: wlan0: link state changed to DOWN
> Dec  4 20:11:16 laptop kernel: wlan0: link state changed to UP
> Dec  4 20:19:46 laptop kernel: wlan0: link state changed to DOWN
> Dec  4 20:19:46 laptop kernel: wlan0: link state changed to UP
> Dec  4 20:36:46 laptop kernel: wlan0: link state changed to DOWN
> Dec  4 20:36:46 laptop kernel: wlan0: link state changed to UP
> Dec  4 20:45:16 laptop kernel: wlan0: link state changed to DOWN
> Dec  4 20:45:16 laptop kernel: wlan0: link state changed to UP
> Dec  4 20:53:46 laptop kernel: wlan0: link state changed to DOWN
> Dec  4 20:53:46 laptop kernel: wlan0: link state changed to UP
> 
> So, every 18 minutes the devices is going DOWN/UP. :-/

More details please. Which driver? How is that stuff configured? 
wpa_supplicant involved? Try running it with debug messages enabled.

We need to figure out what entity is causing the device to go down/up, this 
can either be wpa_supplicant or net80211 (or a cronjob calling ifconfig 
down/up every 18 minutes ;). The appropriate debug options enabled (wlandebug 
0xffffffff or wpa_supplicant with -dd) should reveal that.

-- 
Bernhard