David Wolfskill wrote:
> On Wed, May 29, 2013 at 06:54:40PM +0200, Julian H. Stacey wrote:
> > David Wolfskill wrote:
> > ...
> > > Have I done something avoidable to encourage this behavior?
> >=20
> > Might this be a USB device coming & going ? ie might it be USB bus at fau=
> lt ?
> > ...
>
> I
On Wed, May 29, 2013 at 06:54:40PM +0200, Julian H. Stacey wrote:
> David Wolfskill wrote:
> ...
> > Have I done something avoidable to encourage this behavior?
>
> Might this be a USB device coming & going ? ie might it be USB bus at fault ?
> ...
I admit that hardware is not one of my stronger
David Wolfskill wrote:
> 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
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 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
