iwn(4) link down/up cycling

[Adrian Chadd]

You'll want to enable wpa_supplicant debugging and see what that says.
It's your first hint to figuring out why the interface is flapping.

It may be that the AP is disconnecting you for being idle too long.
Try setting up a background ping.



adrian

On 28 May 2013 04:55, David Wolfskill <david at catwhisker.org> wrote:
> The laptop I've had for some time has an iwn(4) device that has
> generally been working well.
>
> I recently acquired a laptop which I've set up for my spouse to use; its
> wireless NIC is also detected as iwn(4).  However, even when rather
> little is going on (as in, she's not using it, because she's off doing
> Something Else), I find that its IP address (and thus, its hostname) has
> changed.  Here's what "pciconf -lv" has to say about them -- first mine,
> then the "new" one:
>
> iwn0 at pci0:12:0:0:       class=0x028000 card=0x11218086 chip=0x42358086 rev=0x00 hdr=0x00
>     vendor     = 'Intel Corporation'
>     device     = 'Ultimate N WiFi Link 5300'
>     class      = network
>
>
> iwn0 at pci0:3:0:0:        class=0x028000 card=0x12118086 chip=0x42378086 rev=0x00 hdr=0x00
>     vendor     = 'Intel Corporation'
>     device     = 'PRO/Wireless 5100 AGN [Shiloh] Network Connection'
>     class      = network
>
> And here are some representative log entries for the latter:
>
> May 28 00:00:00 g1-241 kernel: wlan0: link state changed to DOWN
> May 28 00:00:03 g1-241 kernel: wlan0: link state changed to UP
>
> May 28 04:31:22 g1-241 kernel: wlan0: link state changed to DOWN
> May 28 04:31:23 g1-241 kernel: wlan0: link state changed to UP
>
>
> Have I done something avoidable to encourage this behavior?
>
> Thanks....
>
> Peace,
> david
> --
> David H. Wolfskill                              david at catwhisker.org
> Taliban: Evil men with guns afraid of truth from a 14-year old girl.
>
> See http://www.catwhisker.org/~david/publickey.gpg for my public key.