On Wed, Dec 05, 2007 at 12:47:04PM -0500, Derek Atkins wrote: > Dan Williams <[EMAIL PROTECTED]> writes: > > > Looks like the driver decided that the AP had gone away. It probably > > missed too many beacons or probe responses due to the RF heavy > > environment or something? Could need a driver tweak. > > Maybe. It's the iwl3945. Maybe it was scanning? ;) > The IETF really is a great testbed. Frustrating as a user, > but a great testbed.
That reminds me on a problem I have seen a few weeks ago. Something (maybe NM) triggered a scan every few (1-3) minutes. The iwl3945 driver had (or still has) a bug where no traffic has been transfered while it was scanning. That caused a roaming event. IIRC NM even logged that in /var/log/NetworkManager. The scan also showed up in iwevent. IIRC iwl has been fixed to not interrupt traffic while scanning. -- with kind regards, Christian Deckelmann email: [EMAIL PROTECTED] Department: IS&T EMEA Networking SUSE LINUX GmbH, a Novell business Maxfeldstraße 5 90409 Nürnberg Germany _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
