Bug#387851: network-manager: DHCP server never called when making wifi-connections
Michael Rasmussen wrote: Hi, I received this email today pointing to a bug which shows similar issues: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=385599 Hi Michael, do you still have problems getting a connection with newer versions of the madwifi driver? 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
Bug#387851: network-manager: DHCP server never called when making wifi-connections
Michael Rasmussen wrote: Forgot to mentione that it also works with D-Link DWL 2000AP+ Doing some research gave this possible solution: All AP which is working does not support WPA2. Could that be the reason? What type of encryption do you have setup on your WLAN routers (wep/wpa/wpa2)? When nm-applet/knetworkmanger prompts you for the key, is the correct encryption selected/available? 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
Bug#387851: network-manager: DHCP server never called when making wifi-connections
Michael Rasmussen wrote: On 2006-09-21 01:00:26, Michael Biebl wrote: 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? The original version was from this site: http://www.marlow.dk/site.php/tech/madwifi I found out the were rather old, and definately was old world. I therefore downloaded the lastest version from Debian Unstable: 0.9.3 (They are from madwifi-ng?). But this did not make any difference. I even tried configuring the AP's to use 802.11b only, but no luck either. I can only find madwifi-source_0.svnr1697 in the Debian archive. This should be the correct driver. Have you tried this one? 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
Bug#387851: network-manager: DHCP server never called when making wifi-connections
On 2006-09-21 01:00:26, Michael Biebl wrote: 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 if it fails for these configurations every time, I would consider it a general problem. 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? The original version was from this site: http://www.marlow.dk/site.php/tech/madwifi I found out the were rather old, and definately was old world. I therefore downloaded the lastest version from Debian Unstable: 0.9.3 (They are from madwifi-ng?). But this did not make any difference. I even tried configuring the AP's to use 802.11b only, but no luck either. AP's from 3COM: no luck: a, b and g - http://www.3com.com/products/en_US/detail.jsp?tab=featurespathtype=purchasesku=3CRWE776075 AP's from Cisco and Lucent: Works. I cannot remember the details. 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. I am also convinced that it is a problem related to wpa_supplicant, but I cannot put my finger on it. Manual configuring with iwconfig and using dhclient3 works for all, including a, b, g and b/g. -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael at rasmussen dot cc http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xD3C9A00E mir at datanom dot net http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xE501F51C mir at miras dot org http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xE3E80917 -- Coach Bear Bryant: Who in the hell is that? High School Coach: That there is Forrest Gump, coach - Just the local idiot pgpnUKkwv9Q9Q.pgp Description: PGP signature
Bug#387851: network-manager: DHCP server never called when making wifi-connections
Forgot to mentione that it also works with D-Link DWL 2000AP+ Doing some research gave this possible solution: All AP which is working does not support WPA2. Could that be the reason? -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael at rasmussen dot cc http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xD3C9A00E mir at datanom dot net http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xE501F51C mir at miras dot org http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xE3E80917 -- When I got up this morning I took two Ex-Lax in addition to my Prozac. I can't get off the john, but I feel good about it. pgperOTKKkzzL.pgp Description: PGP signature
Bug#387851: network-manager: DHCP server never called when making wifi-connections
Michael Biebl wrote: This is not a general problem, so it does not qualify as grave problem. How do you now this? What chipset and driver do you use? Chipset: Atheros AR5212(802.11a/b/g) Driver: Madwifi -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael at rasmussen dot cc http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xD3C9A00E mir at datanom dot net http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xE501F51C mir at miras dot org http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xE3E80917 -- Astrologers do it with heavenly bodies! pgp5EKyAVHWYl.pgp Description: PGP signature
Bug#387851: network-manager: DHCP server never called when making wifi-connections
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
Bug#387851: network-manager: DHCP server never called when making wifi-connections
severity 387851 normal thanks Michael Rasmussen schrieb: Package: network-manager Version: 0.6.4-3+b1 Severity: grave Justification: renders package unusable This is not a general problem, so it does not qualify as grave problem. Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE What chipset and driver do you use? 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
