freebsd stable - Jul 2006 - ural(4) deassociates if no activity (possible wpa_supplicant problem)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I've noticed something very interesing while using a ural(4) usb wifi
device.

When i plug the usb device, and there is absolutely no network activity, exactly
after five minutes the device deassociates from the access point.

I've put some debug printf's in ural_newstate and when i plug the
device,
i get several IEEE80211_S_SCAN state changes,
then i gets from IEEE80211_S_AUTH to ASSOC and then RUN.
Nothing wrong here, but exactly after five minutes of no activity (measured
with stopwatch) i get a state transition from IEEE80211_S_RUN to
IEEE80211_S_AUTH
and it stays that way, until i remove/insert the device again or send HUP to
wpa_supplicant and restart dhclient.

This looks maybe like wpa_supplicant problem, and i think i've had similar
problems with
ath(4) mini-pci card and card bus ral(3), but as far as i remember the period of
inactivity was much greater with them (i'll try to test this on these cards
too when
i have access to them again)


Regards,
- --niki
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEvLWOHNAJ/fLbfrkRAkSbAJ90SYFCkdtjEw3hckrQ/B2O0geWHgCgoj5j
gF7/O+dMKdNUrvFydNODQrE=piip
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Niki Denev wrote:
> Hello,
> 
> I've noticed something very interesing while using a ural(4) usb wifi
device.
> 
> When i plug the usb device, and there is absolutely no network activity,
exactly
> after five minutes the device deassociates from the access point.
> 
> I've put some debug printf's in ural_newstate and when i plug the
device,
> i get several IEEE80211_S_SCAN state changes,
> then i gets from IEEE80211_S_AUTH to ASSOC and then RUN.
> Nothing wrong here, but exactly after five minutes of no activity (measured
> with stopwatch) i get a state transition from IEEE80211_S_RUN to
IEEE80211_S_AUTH
> and it stays that way, until i remove/insert the device again or send HUP
to
> wpa_supplicant and restart dhclient.
> 
> This looks maybe like wpa_supplicant problem, and i think i've had
similar problems with
> ath(4) mini-pci card and card bus ral(3), but as far as i remember the
period of
> inactivity was much greater with them (i'll try to test this on these
cards too when
> i have access to them again)
> 
> 
> Regards,
> --niki
Well, after a few more moments investigating the problem it seems that dhclient
is to blame.
If i don't start it i don't get disconnected, and also i noticed that
the five minute interval
matches the dhclient renewal period of 300 seconds.

So the logical question is, why dhclient makes my ural(4) adapter deassociate,
and what i can
do to prevent this :)

Thanks!

- --niki
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEvLdOHNAJ/fLbfrkRAnt+AKCnpfDdSucSccRTm4Qmg4ONVWQqzwCgygJp
EE+HPPMAbzIhMOsHO6Q+f6o=NXMO
-----END PGP SIGNATURE-----