Well, this is all it gave when it switched: -- messages.0:Jul 9 17:18:07 storage kernel: ral0: sta_roam_check: currssi 21 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:18:22 storage kernel: ral0: sta_roam_check: currssi 21 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:18:37 storage kernel: ral0: sta_roam_check: currssi 21 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:18:52 storage kernel: ral0: sta_roam_check: currssi 21 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:19:07 storage kernel: ral0: sta_roam_check: currssi 19 currate 72 roamrssi 14 roamrate 10 messages.0:Jul 9 17:19:22 storage kernel: ral0: sta_roam_check: currssi 21 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:19:37 storage kernel: ral0: sta_roam_check: currssi 21 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:19:52 storage kernel: ral0: sta_roam_check: currssi 21 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:20:07 storage kernel: ral0: sta_roam_check: currssi 23 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:20:22 storage kernel: ral0: sta_roam_check: currssi 21 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:20:37 storage kernel: ral0: sta_roam_check: currssi 21 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:20:52 storage kernel: ral0: sta_roam_check: currssi 21 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:21:07 storage kernel: ral0: sta_roam_check: currssi 21 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:21:22 storage kernel: ral0: sta_roam_check: currssi 23 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:21:37 storage kernel: ral0: link state changed to DOWN messages.0:Jul 9 17:21:39 storage kernel: ral0: link state changed to UP messages.0:Jul 9 17:21:54 storage kernel: ral0: sta_roam_check: currssi 45 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:22:09 storage kernel: ral0: sta_roam_check: currssi 45 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:22:24 storage kernel: ral0: sta_roam_check: currssi 45 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:22:40 storage kernel: ral0: sta_roam_check: currssi 45 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:22:55 storage kernel: ral0: sta_roam_check: currssi 45 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:23:10 storage kernel: ral0: sta_roam_check: currssi 45 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:23:25 storage kernel: ral0: sta_roam_check: currssi 43 currate 108 roamrssi 14 roamrate 10 messages.0:Jul 9 17:23:39 storage kernel: ral0: sta_roam_check: currssi 45 currate 108 roamrssi 14 roamrate 10 -- Any ideas? Or, any other commands you'd like me to try to give any more verbose logging? On 7/7/07, Sepherosa Ziehau <sepherosa_at_gmail.com> wrote: > > On 7/5/07, Kevin Gerry <sfpoof_at_gmail.com> wrote: > > Weird, one of the issues it appears I'm having is that when it's set to > > -bgscan and roaming device, the device will just get stuck on "no > carrier" > > Please leave bgscan and roaming on and run following command: > wlandebug -i ral0 +roam > wlandebug -i ath0 +roam > > Post the log, when the AP switching happened. > > Best Regards, > sephe > > -- > Live Free or Die >Received on Tue Jul 10 2007 - 00:03:10 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:14 UTC