Re: periodic_update(): Roamed ...

[Howard Chu <hyc symas com>]

Alexander Sack wrote:
> On Mon, Apr 20, 2009 at 06:24:33PM -0700, Howard Chu wrote:
> > Since killing NM prevents the problem from showing up, I don't see how
> > this can be a wpa_supplicant bug. ??  Should I add another comment to the
> > bug report?
>
> To verify that its really the scan making your driver behave badly you
> could do the kill -9 trick you mentioned above and then check whether
> you can make your network stuck by calling the "scan" dbus method of
> wpa supplicant.
>
> Probably an "iwlist scan" would also trigger it while you are in that
> state. Maybe check that too.

I tried "iwlist scan" but it didn't seem to break anything. It still had a 
noticeable effect though, as seen by ping:

64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.57 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.56 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=4607 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=3604 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=2604 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=1604 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=604 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=1.54 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=1.54 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=1.54 ms

Obviously the usual ping time is ~1.5ms; "iwlist scan" slows that down quite a 
lot.

I didn't see any obvious way to send the right command to wpa_supplicant using 
dbus so I didn't try that yet.
--
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/