Michael Rasmussen schrieb: > > Michael Biebl wrote: >> This is not a general problem, so it does not qualify as grave problem. > How do you now this?
You said it yourself, that it worked for certain configurations, but only failed for: AP using 802.11g: Did not receive IP AP using 802.11b+g: Did not receive IP >> What chipset and driver do you use? > Chipset: Atheros AR5212(802.11a/b/g) > Driver: Madwifi The madwifi driver is known to have problems. Which version do you have (where did you get it from)? Is this driver version the one based on the madwifi-ng branch? My guess is, that it is a driver issue. NM is very picky in that regard. The driver has to properly support the Wireless Extensions (wext) api otherwise it will not work properly in combination with NM. Packages like wpa_supplicant have many workarounds for broken drivers, which is a bad thing imho, because it caused many badly written drivers which did not standardize on one central API. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
