On Thursday 14 December 2006 22:19, Thomas Kallenberg wrote: > Could this be a driver issue? I have the same problem and I'm using the > madwifi-svn driver with wpasupplicant driver from unstable and > network-manager from etch.
It is almost 100% likely to be an issue with the madwifi driver. > > I found this bugreport from madwifi driver: http://madwifi.org/ticket/1030 > > The issue can also be temporarily fixed by setting the driver in "g" mode > only: iwpriv $wlan mode 3, > then the network-manager can connect to the unencrypted network. > > If I dont do this, i can see with iwconfig, the "a"-mode is more often > scanned by iwconfig than the "b/g"-mode Interesting observation. and no real surprise to the madwifi people I think. Scanning and mode changing is currently a big pile of mess for those familiar with the internal code of the madwifi driver. Thanks, Kel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
