Re: networkmanager fails to associate (ipw3945)
Dan Williams wrote: Can you connect to that AP with plain wpa_supplicant and the 'wext' driver? using iwlwifi 0.0.16 it works also with networkmanager now :) ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
I tested with ipw3945 1.2.1 and it works too, so it seems that this was a driver bug ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
no it does not work with ipw3945 1.2.1 it only worked once and now it fails to connect ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Rodney Morris [EMAIL PROTECTED] writes: On 2/28/07, Rodney Morris [EMAIL PROTECTED] wrote: On 2/28/07, Derek Atkins [EMAIL PROTECTED] wrote: Rodney Morris [EMAIL PROTECTED] writes: NetworkManager works for me. I can attached to open, WEP, WPA-PSK, and WPA2-PSK access points. The following is the information on my distro, ipw3945 drivers, and IEEE 802.11 stack: 1) Fedora Core 6 2) Kernel 2.6.19-1.2911.fc6, i686 version 3) Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.0d 4) IEEE 802.11 data/management/control stack, git-1.1.13 [snip] I successfully connected to a hidden-SSID, open access point using NetworkManager. Again, my previous offer still stands. I'll test the ability to connect to hidden-SSID access points employing WEP, WPA-PSK, and WPA2-PSK if anyone is interested. COOL! So, where did you get #3 and #4? Are there RPMs available or did you have to pull down from source? (yeah, I realize this is WAY off topic for the NM list. Sorry). Rod -derek, who expects a new laptop with a 3945 in a month. -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Rodney Morris [EMAIL PROTECTED] writes: NetworkManager works for me. I can attached to open, WEP, WPA-PSK, and WPA2-PSK access points. The following is the information on my distro, ipw3945 drivers, and IEEE 802.11 stack: 1) Fedora Core 6 2) Kernel 2.6.19-1.2911.fc6, i686 version 3) Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.0d 4) IEEE 802.11 data/management/control stack, git-1.1.13 Have you tried hidden-SSID, open networks, too? Rod -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
On 2/28/07, Derek Atkins [EMAIL PROTECTED] wrote: Rodney Morris [EMAIL PROTECTED] writes: NetworkManager works for me. I can attached to open, WEP, WPA-PSK, and WPA2-PSK access points. The following is the information on my distro, ipw3945 drivers, and IEEE 802.11 stack: 1) Fedora Core 6 2) Kernel 2.6.19-1.2911.fc6, i686 version 3) Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.0d 4) IEEE 802.11 data/management/control stack, git-1.1.13 Have you tried hidden-SSID, open networks, too? Rod -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available No, I've not tried tried to connect to a hidden-SSID, open networks. Currently, I'm at work and unable to perform such a test. I'll test that set up tonight and report my results. I'll also perform test hidden-SSID with WEP, WPA-PSK, and WPA2-PSK configurations if anyone is interested; however, I won't be able to perform those tests until this weekend. Rod ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Rodney Morris wrote: On Sat, 02/24/2007, Dan Williams wrote: Right; so what we now need to know from everyone is: 1) what distro? 2) what kernel version? 3) what version of ipw3945 drivers? 4) what version of the ieee80211 stack? If someone can point me at where to get (3) and (4), I could answer :-) ///Peter ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Flynn wrote: Rodney Morris wrote: On Sat, 02/24/2007, Dan Williams wrote: Right; so what we now need to know from everyone is: 1) what distro? 2) what kernel version? 3) what version of ipw3945 drivers? 4) what version of the ieee80211 stack? If someone can point me at where to get (3) and (4), I could answer :-) There was a followup message that had instructions. 3 and 4 are both in the output of `dmesg`. - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer III |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF5ho0mb+gadEcsb4RAj8mAKDJ4OKgucuekUlwZuDHryWG7fOMnwCeOY5K ClPVa6RHEoyY/KOWRITi+4k= =001P -END PGP SIGNATURE- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:[EMAIL PROTECTED] title:Systems Programmer III tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
On 2/28/07, Rodney Morris [EMAIL PROTECTED] wrote: On 2/28/07, Derek Atkins [EMAIL PROTECTED] wrote: Rodney Morris [EMAIL PROTECTED] writes: NetworkManager works for me. I can attached to open, WEP, WPA-PSK, and WPA2-PSK access points. The following is the information on my distro, ipw3945 drivers, and IEEE 802.11 stack: 1) Fedora Core 6 2) Kernel 2.6.19-1.2911.fc6, i686 version 3) Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.0d 4) IEEE 802.11 data/management/control stack, git-1.1.13 Have you tried hidden-SSID, open networks, too? Rod -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available No, I've not tried tried to connect to a hidden-SSID, open networks. Currently, I'm at work and unable to perform such a test. I'll test that set up tonight and report my results. I'll also perform test hidden-SSID with WEP, WPA-PSK, and WPA2-PSK configurations if anyone is interested; however, I won't be able to perform those tests until this weekend. Rod I successfully connected to a hidden-SSID, open access point using NetworkManager. Again, my previous offer still stands. I'll test the ability to connect to hidden-SSID access points employing WEP, WPA-PSK, and WPA2-PSK if anyone is interested. Rod ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
On Sat, 02/24/2007, Dan Williams wrote: Right; so what we now need to know from everyone is: 1) what distro? 2) what kernel version? 3) what version of ipw3945 drivers? 4) what version of the ieee80211 stack? NetworkManager works for me. I can attached to open, WEP, WPA-PSK, and WPA2-PSK access points. The following is the information on my distro, ipw3945 drivers, and IEEE 802.11 stack: 1) Fedora Core 6 2) Kernel 2.6.19-1.2911.fc6, i686 version 3) Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.0d 4) IEEE 802.11 data/management/control stack, git-1.1.13 Rod ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Dan Williams wrote: Right; so what we now need to know from everyone is: 1) what distro? FC6 x86_64 2) what kernel version? 2.6.19 ( 2.6.19-1.2911.fc6 ) 3) what version of ipw3945 drivers? 1.2.0 + ucode 1.14.2 + daemon 1.7.22 4) what version of the ieee80211 stack? 1.2.16 (out of tree module + crypt fix patch*), needed else not even wpa_supplicant works for me. if you need any infos feel free to ask I will provide as much as I can. * http://ieee80211.sourceforge.net/patches/ieee80211-1.2.16-crypt-fix2.patch ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Dan Williams escribío: Right; so what we now need to know from everyone is: 1) what distro? 2) what kernel version? 3) what version of ipw3945 drivers? 4) what version of the ieee80211 stack? Works for me. 1) FC6 2) 2.6.19-1.2911.fc6 3) ipw3945-kmdl-2.6.19-1.2911.fc6-1.2.0-18.2.fc6.at Intel(R) PRO/Wireless 3945 Network Connection driver for Linux,1.2.0d 4) ieee80211-kmdl-2.6.19-1.2911.fc6-1.2.16-17.fc6.at 802.11 data/management/control stack, 1.2.16 -- Brian Millett - [ Londo, The Gathering] I suppose there'll be a war now, hmm? All that running around and shooting one another. You would have thought sooner or later it would go out of fashion. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
I seem to face the same problem. Is there some good advice on how to configure the wpa supplicant directly? Any pointer would be highly appreciated. Here are my data: 1) Distro: Ubuntu 6.10 2) Kernel: 2.6.17-11-generic 3) ipw3945 drivers: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.1.0mp 4) ieee80211 stack: git-1.1.13 There are lots of messages in the syslog. That's the beginning: Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): Trying to associate with SSID 'FRITZ!Box Fon WLAN 7170' Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): CTRL_IFACE monitor send - hexdump(len=40): 2f 76 61 72 2f 72 75 6e 2f 4e 65 74 77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 61 5f 63 74 72 6c 5f 34 33 36 32 2d 33 00 Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): Cancelling scan request Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): clearing own WPA/RSN IE Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): Automatic auth_alg selection: 0x1 Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WPA: No WPA/RSN IE available from association info Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WPA: Set cipher suites based on configuration Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WPA: Selected cipher suites: group 30 pairwise 24 key_mgmt 2 Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WPA: clearing AP WPA IE Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WPA: clearing AP RSN IE Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WPA: using GTK CCMP Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WPA: using PTK CCMP Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WPA: using KEY_MGMT WPA-PSK Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 0 4 01 00 00 50 f2 04 01 00 00 50 f2 02 Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): No keys have been configured - skip key clearing Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): wpa_driver_wext_set_drop_unencrypted Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): State: SCANNING - ASSOCIATING Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WEXT: Operstate: linkmode=-1, operstate=5 Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): wpa_driver_wext_associate Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): Setting authentication timeout: 60 sec 0 usec Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): EAPOL: External notification - EAP success=0 Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): EAPOL: External notification - EAP fail=0 Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): EAPOL: External notification - portControl=Auto Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): Wireless event: cmd=0x8b06 len=8 Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): Wireless event: cmd=0x8b1a len=32 Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): Wireless event: cmd=0x8b15 len=20 Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): Wireless event: new AP: 00:15:0c:ed:e6:5f Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): ATING - ASSOCIATED Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WEXT: Operstate: linkmode=-1, operstate=5 Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): Associated to a new BSS: BSSID=00:15:0c:ed:e6:5f Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): No keys have been configured - skip key clearing Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): Network configuration found for the current AP Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WPA: Using WPA IE from AssocReq to set cipher suites Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 2 Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WPA: clearing AP WPA IE Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WPA: clearing AP RSN IE Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WPA: using GTK CCMP Feb 24 23:24:04 osiris NetworkManager: information^Iwpa_supplicant(6443): WPA: using PTK CCMP
Re: networkmanager fails to associate (ipw3945)
Usamah Malik wrote: This is with regards to a thread you started on networkmanager list regarding networkmanager not associating. I have been having the same exact issue was wondering what did you do to resolve it. I am using 2.6.19-2911 kernel + ipw3945 + NetworkManager it fails to establish connection to my WPA enabled wlan. It is however able to show (but not connect) to wlans in the neibourhood. Any pointers are appreciated. as you can see in the thread there seems to be no soultion for it and the discussion stopped :( the only solution that I can tell you is to use wpa_supplicant directly, networkmanager seems not to work with ipw3945 + wpa. it seems to me that in is not working with ipw3945 period. I have the same problem but with an open AP. Would like a resolution though :) Thanks, Sami ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adrian Vasile wrote: Usamah Malik wrote: This is with regards to a thread you started on networkmanager list regarding networkmanager not associating. I have been having the same exact issue was wondering what did you do to resolve it. I am using 2.6.19-2911 kernel + ipw3945 + NetworkManager it fails to establish connection to my WPA enabled wlan. It is however able to show (but not connect) to wlans in the neibourhood. Any pointers are appreciated. as you can see in the thread there seems to be no soultion for it and the discussion stopped :( the only solution that I can tell you is to use wpa_supplicant directly, networkmanager seems not to work with ipw3945 + wpa. it seems to me that in is not working with ipw3945 period. I have the same problem but with an open AP. Not true. Works fine for me. The only thing I'm waiting on is LEAP support. WEP104, which I use at home, works just fine. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF300vmb+gadEcsb4RAge9AJ9Sm+x7FBdDn+TmQh6ozCc8v/IkZgCdGhOB c+FXGrUS9cRUiFkIwDWDyGk= =CleA -END PGP SIGNATURE- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
On Fri, 02/23/2007, dragoran wrote: as you can see in the thread there seems to be no soultion for it and the discussion stopped :( the only solution that I can tell you is to use wpa_supplicant directly, networkmanager seems not to work with ipw3945 + wpa. NM works fine with my ipw3945 + wpa (debian on dell inspiron 6400) same processes running here NM-tool output: NetworkManager Tool State: connected - Device: eth2 NM Path: /org/freedesktop/NetworkManager/Devices/eth2 Type: 802.11 Wireless Driver:ipw3945 Active:yes HW Address:00:13:02:65:97:1E Capabilities: Supported: yes Speed: 54 Mb/s Wireless Settings Scanning:yes WEP Encryption: yes WPA Encryption: yes WPA2 Encryption: yes Wireless Networks (* = Current Network) CLS: Infrastructure Mode, Freq 0.000 MHz, Rate 54 Mb/s, Strength 58%, Encrypted (WEP) *Xenonet:Infrastructure Mode, Freq 0.000 MHz, Rate 62 Mb/s, Strength 93%, Encrypted (WPA) IP Settings: IP Address: 192.168.2.101 Subnet Mask: 255.255.255.0 Broadcast: 192.168.2.255 Gateway: 192.168.2.1 Primary DNS: 192.168.2.1 Secondary DNS: 0.0.0.0 - Device: eth0 NM Path: /org/freedesktop/NetworkManager/Devices/eth0 Type: Wired Driver:b44 Active:no HW Address:00:15:C5:13:51:A5 Capabilities: Supported: yes Carrier Detect: yes Speed: 10 Mb/s Wired Settings Hardware Link: no Did you uncomment your interfaces in /etc/network/interfaces? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
tryed with iwlwifi but no luck either... its even worse (no wpa support) (does not work with wpa_supplicant too) ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Dan Williams wrote: Right; there are cases that I don't understand where the association results between NM and wpa_supplicant are different. We need to find out why. It could be that NM is not passing the right options to wpa_supplicant, or that there are bugs in either NM or wpa_supplicant. We need to find out where the difference is. So in conclusion, maybe we remove the || nm_device_is_activating (dev) from supplicant_status_cb() and just ignore the link timeout while activating. But the real question is, _why_ would the auth/assoc take 20 seconds, and _why_ is the driver sending disconnect events during the attempt, especially if the association doesn't complete within the 20s timeout? What _really_ needs to be fixed here, the driver or NM? the interessting thing is that everything but nm can connect to the app (wpa_supplicant,windows and even the wii) It might be a driver bug I am currently using ipw3945 maybe I will try again this weekend with iwlwifi (if I get it to build) and report. Thanks, Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
On Sun, 2007-02-11 at 03:36 +, Volker Braun wrote: On Sat, 10 Feb 2007 17:17:21 -0500, Dan Williams wrote: This is a really complicated issue. It depends on what disconnect means during the association attempt. During 802.1x handshakes, it's certainly possible that we have associated and authed to the access point, but if our credentials are wrong, the RADIUS server may have kicked us off, and wpa_supplicant returns a DISCONNECT event. With wpa-psk, wpa_supplicant tells you (*) WPA: 4-Way Handshake failed - pre-shared key may be incorrect before disconnecting, that seems to be a better diagnostic. I don't know about WPA enterprise. I know that WEP sucks in that regard as well :-) My point was that if we get an unspecific CTRL-EVENT-DISCONNECTED we shouldn't give up, but try again until the full timeout or until we get an error that makes it clear that we will not be able to authenticate. Right now the disconnect shortens the whole 20sec timeout. In the strict view, if the card or driver sends a DISCONNECT event during the association attempt, there's nothing that NM or the supplicant can do. The card/driver has said it cannot connect. If that's in error, then the _driver_ needs to get fixed. Linux wireless drivers have a history of being crappy. In reality, we walk a tightrope of zero-tolerance and making NM usable for people. One example is the stance on _only_ using the 'wext' driver for wpa_supplicant. This has the happy result of making all major drivers start actually using WEXT and WE-19, including ndiswrapper and madwifi. The airo driver used to send disconnect events during a scan. I fixed that, and was able to remove the disconnect-suppression during scan. Look at this from 10,000 ft. Why on _earth_ should a WEP+SK or WPA handshake take more than 20 seconds? If you're at the margins of the network, then get closer. We're not going to make the experience of NM worse for everyone just to make it better for users who are trying to connect from the margins of a network. I understand that the inherent unreliability of wireless communications makes things more difficult, but if you don't enforce limits, nobody has an incentive to make things better. Maybe NetworkManager could continue to try to associate in the background after the reasonable (like 20sec) timeout passed. That is, after 20 sec show again the password dialog but continue quietly until the user clicks OK/Cancel. If association succeeds after the timeout, just close the password dialog. I disagree. That just complicates internal operations code, and muddles expectations of the user. Seriously, when does an association _really_ take more than ~ 20 seconds? What are you trying to achieve here? Point: Mac OS X connects within 3 seconds in almost all cases, WEP and WPA. Why does NM + wpa_supplicant take so darn long? Part of that time is dhclient being really slow, and part of it is drivers being buggy. Volker (*) Though when I tried right now I couldn't associate with the correct psk on FC6+ipw2200+wpa_supplicant -Dwext, while NetworkManager works fine. Right; there are cases that I don't understand where the association results between NM and wpa_supplicant are different. We need to find out why. It could be that NM is not passing the right options to wpa_supplicant, or that there are bugs in either NM or wpa_supplicant. We need to find out where the difference is. So in conclusion, maybe we remove the || nm_device_is_activating (dev) from supplicant_status_cb() and just ignore the link timeout while activating. But the real question is, _why_ would the auth/assoc take 20 seconds, and _why_ is the driver sending disconnect events during the attempt, especially if the association doesn't complete within the 20s timeout? What _really_ needs to be fixed here, the driver or NM? Thanks, Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Dan Williams wrote: On Fri, 2007-02-09 at 09:16 +0100, dragoran wrote: Volker Braun wrote: I'm having the same problem on FC6 with ipw2200 and WPA-PSK. Compiling STABLE fixes it. so this means whatever it is its a bug in 0.6.4 and that is fixed in the current stable branch? so this means that its time for a 0.6.5 release... Dan? I'd urge people to test what's in the stable branches head, which will be 0.6.5. The quicker people figure out if there are bugs, the quicker we can fix them, and the quicker we can make a release. I posted tarballs of yesterday's SVN, if that helps: http://people.redhat.com/dcbw/NetworkManager/0.6.5/ I downloaded NetworkManager 0.6.5 (only nm, not the applet). build it with --prefix=/opt --distro=redhat then I did servce NetworkManager stop /opt/etc/rc.d/init.d/NetworkManager start then I tryed to connect ... same issue (keeps asking me for a password) Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
In dragoran's wpa_supplicant log there is this suspicious entry somewhere at the beginning: Wireless event: new AP: 00:00:00:00:00:00 Added BSSID 00:00:00:00:00:00 into blacklist State: ASSOCIATING - DISCONNECTED driver bug? wpa_supplicant bug? I don't see the reason for why wpa_supplicant disconnects, but it does. Of course, it immediately tries again and succeeeds. But NetworkManager then ticks differently. The supplicant_timeout_cb() had 20 seconds to complete, but now it has only 8 seconds for the link_timeout_cb. Feb 8 13:48:49 localhost NetworkManager: information SUP: sending command 'ENABLE_NETWORK 0' Feb 8 13:48:49 localhost NetworkManager: information SUP: response was 'OK' Feb 8 13:48:49 localhost NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) complete. Feb 8 13:48:57 localhost kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Comment: doesn't that mean that the link is up now? Feb 8 13:48:59 localhost avahi-daemon[2565]: New relevant interface eth1.IPv6 for mDNS. Feb 8 13:48:59 localhost avahi-daemon[2565]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::218:deff:fe05:f79e. Feb 8 13:48:59 localhost avahi-daemon[2565]: Registering new address record for fe80::218:deff:fe05:f79e on eth1. Comment: it is now 11 seconds past the start of the supplicant_timeout, usually we wouldn't give up yet. Feb 8 13:49:00 localhost NetworkManager: information Activation (eth1/wireless): disconnected during association, asking for new key. Feb 8 13:49:00 localhost NetworkManager: information Activation (eth1) New wireless user key requested for network 'mynet'. I think the heuristic DISCONNECT = need new password is wrong. We should at least try a few times. Either wait until we have a fixed number of disconnects, or wait until the end of the supplicant timeout even if there are initial disconnects. Volker ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
On Sat, 2007-02-10 at 16:46 +, Volker Braun wrote: In dragoran's wpa_supplicant log there is this suspicious entry somewhere at the beginning: Wireless event: new AP: 00:00:00:00:00:00 Added BSSID 00:00:00:00:00:00 into blacklist State: ASSOCIATING - DISCONNECTED driver bug? wpa_supplicant bug? I don't see the reason for why wpa_supplicant disconnects, but it does. Of course, it immediately tries again and succeeeds. This is a driver bug. The driver lost association to the AP, or the AP told the driver to disconnect itself by sending a disassociation or deauthentication frame, or a driver/firmware timer expired, or something like that. It's essentially the card saying I can't connect or I lost the connection, and there's not much that NM or wpa_supplicant can realistically do about it. But NetworkManager then ticks differently. The supplicant_timeout_cb() had 20 seconds to complete, but now it has only 8 seconds for the link_timeout_cb. Feb 8 13:48:49 localhost NetworkManager: information SUP: sending command 'ENABLE_NETWORK 0' Feb 8 13:48:49 localhost NetworkManager: information SUP: response was 'OK' Feb 8 13:48:49 localhost NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) complete. Feb 8 13:48:57 localhost kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Comment: doesn't that mean that the link is up now? Not really; that's the driver calling netif_carrier_on(), which doesn't really mean anything for wireless interfaces. Does it mean that the card associated? Or does it mean that the card has authenticated? Or does it mean the card can actually pass frames to the AP? Or does it mean that you can actually send traffic _beyond_ the AP? netlink carrier detect is essentially useless on wireless links, and nobody (neither NM nor wpa_supplicant) uses wireless carrier notifications for anything because of that. All drivers do netif_carrier_* differently anyway, partially because its useless. Feb 8 13:48:59 localhost avahi-daemon[2565]: New relevant interface eth1.IPv6 for mDNS. Feb 8 13:48:59 localhost avahi-daemon[2565]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::218:deff:fe05:f79e. Feb 8 13:48:59 localhost avahi-daemon[2565]: Registering new address record for fe80::218:deff:fe05:f79e on eth1. Comment: it is now 11 seconds past the start of the supplicant_timeout, usually we wouldn't give up yet. Feb 8 13:49:00 localhost NetworkManager: information Activation (eth1/wireless): disconnected during association, asking for new key. Feb 8 13:49:00 localhost NetworkManager: information Activation (eth1) New wireless user key requested for network 'mynet'. I think the heuristic DISCONNECT = need new password is wrong. We should at least try a few times. Either wait until we have a fixed number of disconnects, or wait until the end of the supplicant timeout even if there are initial disconnects. This is a really complicated issue. It depends on what disconnect means during the association attempt. During 802.1x handshakes, it's certainly possible that we have associated and authed to the access point, but if our credentials are wrong, the RADIUS server may have kicked us off, and wpa_supplicant returns a DISCONNECT event. There was a patch a while ago that normalized the 'new key' requests. It seemed to make sense at the time. Before we change it, I'd urge a review of what exactly it means when wpa_supplicant sends the disconnect event during an association for the different auth methods (including WEP shared key/open system). NetworkManager should probably be trying a little harder before giving up, but definitely not by increasing timeouts. Remember that on WEP Open System connections, you _never_ know if your WEP key is wrong until 45 seconds later when DHCP times out. Trying again would be a connect time of 1:30, and that's just wrong. WPA is a lot better here because there are hard failures when your credentials or keys are wrong, and we should take advantage of that. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
On 2/10/07, Dan Williams [EMAIL PROTECTED] wrote: On Sat, 2007-02-10 at 16:46 +, Volker Braun wrote: In dragoran's wpa_supplicant log there is this suspicious entry somewhere at the beginning: Wireless event: new AP: 00:00:00:00:00:00 Added BSSID 00:00:00:00:00:00 into blacklist State: ASSOCIATING - DISCONNECTED driver bug? wpa_supplicant bug? I don't see the reason for why wpa_supplicant disconnects, but it does. Of course, it immediately tries again and succeeeds. This is a driver bug. The driver lost association to the AP, or the AP told the driver to disconnect itself by sending a disassociation or deauthentication frame, or a driver/firmware timer expired, or something like that. It's essentially the card saying I can't connect or I lost the connection, and there's not much that NM or wpa_supplicant can realistically do about it. But NetworkManager then ticks differently. The supplicant_timeout_cb() had 20 seconds to complete, but now it has only 8 seconds for the link_timeout_cb. Feb 8 13:48:49 localhost NetworkManager: information SUP: sending command 'ENABLE_NETWORK 0' Feb 8 13:48:49 localhost NetworkManager: information SUP: response was 'OK' Feb 8 13:48:49 localhost NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) complete. Feb 8 13:48:57 localhost kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Comment: doesn't that mean that the link is up now? Not really; that's the driver calling netif_carrier_on(), which doesn't really mean anything for wireless interfaces. Does it mean that the card associated? Or does it mean that the card has authenticated? Or does it mean the card can actually pass frames to the AP? Or does it mean that you can actually send traffic _beyond_ the AP? netlink carrier detect is essentially useless on wireless links, and nobody (neither NM nor wpa_supplicant) uses wireless carrier notifications for anything because of that. All drivers do netif_carrier_* differently anyway, partially because its useless. sometimes when this happens the gnome-netstatus -applet shows that the card is associated but nm disconnects it again and ask for a password. Feb 8 13:48:59 localhost avahi-daemon[2565]: New relevant interface eth1.IPv6 for mDNS. Feb 8 13:48:59 localhost avahi-daemon[2565]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::218:deff:fe05:f79e. Feb 8 13:48:59 localhost avahi-daemon[2565]: Registering new address record for fe80::218:deff:fe05:f79e on eth1. Comment: it is now 11 seconds past the start of the supplicant_timeout, usually we wouldn't give up yet. Feb 8 13:49:00 localhost NetworkManager: information Activation (eth1/wireless): disconnected during association, asking for new key. Feb 8 13:49:00 localhost NetworkManager: information Activation (eth1) New wireless user key requested for network 'mynet'. I think the heuristic DISCONNECT = need new password is wrong. We should at least try a few times. Either wait until we have a fixed number of disconnects, or wait until the end of the supplicant timeout even if there are initial disconnects. This is a really complicated issue. It depends on what disconnect means during the association attempt. During 802.1x handshakes, it's certainly possible that we have associated and authed to the access point, but if our credentials are wrong, the RADIUS server may have kicked us off, and wpa_supplicant returns a DISCONNECT event. There was a patch a while ago that normalized the 'new key' requests. It seemed to make sense at the time. Before we change it, I'd urge a review of what exactly it means when wpa_supplicant sends the disconnect event during an association for the different auth methods (including WEP shared key/open system). NetworkManager should probably be trying a little harder before giving up, but definitely not by increasing timeouts. Remember that on WEP Open System connections, you _never_ know if your WEP key is wrong until 45 seconds later when DHCP times out. Trying again would be a connect time of 1:30, and that's just wrong. WPA is a lot better here because there are hard failures when your credentials or keys are wrong, and we should take advantage of that. so whats the solution now? anything that I could test/provide to help here? or is nm useless on this kind of setup? is it possible to make the timeout a gconf-key for each connection? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Volker Braun wrote: I'm having the same problem on FC6 with ipw2200 and WPA-PSK. Compiling STABLE fixes it. so this means whatever it is its a bug in 0.6.4 and that is fixed in the current stable branch? so this means that its time for a 0.6.5 release... Dan? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
On Fri, 2007-02-09 at 09:16 +0100, dragoran wrote: Volker Braun wrote: I'm having the same problem on FC6 with ipw2200 and WPA-PSK. Compiling STABLE fixes it. so this means whatever it is its a bug in 0.6.4 and that is fixed in the current stable branch? so this means that its time for a 0.6.5 release... Dan? I'd urge people to test what's in the stable branches head, which will be 0.6.5. The quicker people figure out if there are bugs, the quicker we can fix them, and the quicker we can make a release. I posted tarballs of yesterday's SVN, if that helps: http://people.redhat.com/dcbw/NetworkManager/0.6.5/ Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Dan, why the split i.e. network manager nm-applet apart? Dan Williams wrote: On Fri, 2007-02-09 at 09:16 +0100, dragoran wrote: Volker Braun wrote: I'm having the same problem on FC6 with ipw2200 and WPA-PSK. Compiling STABLE fixes it. so this means whatever it is its a bug in 0.6.4 and that is fixed in the current stable branch? so this means that its time for a 0.6.5 release... Dan? I'd urge people to test what's in the stable branches head, which will be 0.6.5. The quicker people figure out if there are bugs, the quicker we can fix them, and the quicker we can make a release. I posted tarballs of yesterday's SVN, if that helps: http://people.redhat.com/dcbw/NetworkManager/0.6.5/ Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Grant Williamson wrote: Dan, why the split i.e. network manager nm-applet apart? maybe because gnome-2.18 wants to include nm-applet but not nm? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
On Fri, 2007-02-09 at 14:27 +0100, dragoran wrote: Grant Williamson wrote: Dan, why the split i.e. network manager nm-applet apart? maybe because gnome-2.18 wants to include nm-applet but not nm? Right. Also that the applet is gnome-specific, and NM isn't gnome specific. NM itself works fine with any DE. Eventually the VPN bits should probably get spun out too, but they aren't complex enough to justify it right now. The applet is. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
I recompiled ieee and ipw3945 and it now works with wpa_supplicant without any problems (using the wext driver). but nm keeps asking me for the passphrase and never connects. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Patrick Bureau wrote: dragoran wrote: I recompiled ieee and ipw3945 and it now works with wpa_supplicant without any problems (using the wext driver). but nm keeps asking me for the passphrase and never connects. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list which linux flavor are you running, some releases require settings to be changed around for it to work properly. I am running Fedora Core 6 x86_64 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
On Thu, 2007-02-08 at 10:29 +0100, dragoran wrote: I recompiled ieee and ipw3945 and it now works with wpa_supplicant without any problems (using the wext driver). but nm keeps asking me for the passphrase and never connects. Hmm; can you get some logs of NM during the connection attempt? They should get dumped to /var/log/messages. Basically, it may be the case that NM isn't passing the same options to wpa_supplicant as your testcase is using, but we don't know what those options are. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Dan Williams wrote:
On Thu, 2007-02-08 at 10:29 +0100, dragoran wrote:
I recompiled ieee and ipw3945 and it now works with wpa_supplicant
without any problems (using the wext driver).
but nm keeps asking me for the passphrase and never connects.
Hmm; can you get some logs of NM during the connection attempt? They
should get dumped to /var/log/messages. Basically, it may be the case
that NM isn't passing the same options to wpa_supplicant as your
testcase is using, but we don't know what those options are.
nm output to syslog is attached (note: ignore selinux messages I did run
setenforce 0 before doing this test)
Dan
Feb 8 13:48:35 localhost NetworkManager: information User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / mynet
Feb 8 13:48:35 localhost NetworkManager: information Deactivating device eth1.
Feb 8 13:48:35 localhost kernel: audit(1170938915.752:18): avc: denied { unlink } for pid=2641 comm=NetworkManager name=eth1 dev=sda2 ino=7898869 scontext=system_u:system_r:NetworkManager_t:s0 tcontext=user_u:object_r:var_run_t:s0 tclass=sock_file
Feb 8 13:48:35 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason
Feb 8 13:48:35 localhost NetworkManager: information Device eth1 activation scheduled...
Feb 8 13:48:35 localhost NetworkManager: information Activation (eth1) started...
Feb 8 13:48:35 localhost NetworkManager: information Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Feb 8 13:48:35 localhost NetworkManager: information Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Feb 8 13:48:35 localhost NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Feb 8 13:48:35 localhost NetworkManager: information Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Feb 8 13:48:35 localhost NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Feb 8 13:48:35 localhost NetworkManager: information Activation (eth1/wireless): access point 'mynet' is encrypted, but NO valid key exists. New key needed.
Feb 8 13:48:35 localhost NetworkManager: information Activation (eth1) New wireless user key requested for network 'mynet'.
Feb 8 13:48:35 localhost NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Feb 8 13:48:49 localhost NetworkManager: information Activation (eth1) New wireless user key for network 'mynet' received.
Feb 8 13:48:49 localhost NetworkManager: information Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Feb 8 13:48:49 localhost NetworkManager: information Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Feb 8 13:48:49 localhost NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Feb 8 13:48:49 localhost NetworkManager: information Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Feb 8 13:48:49 localhost NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Feb 8 13:48:49 localhost NetworkManager: information Activation (eth1/wireless): access point 'mynet' is encrypted, and a key exists. No new key needed.
Feb 8 13:48:49 localhost NetworkManager: information SUP: sending command 'INTERFACE_ADD eth1 wext /var/run/wpa_supplicant '
Feb 8 13:48:49 localhost NetworkManager: information SUP: response was 'OK'
Feb 8 13:48:49 localhost NetworkManager: information SUP: sending command 'AP_SCAN 1'
Feb 8 13:48:49 localhost NetworkManager: information SUP: response was 'OK'
Feb 8 13:48:49 localhost NetworkManager: information SUP: sending command 'ADD_NETWORK'
Feb 8 13:48:49 localhost NetworkManager: information SUP: response was '0'
Feb 8 13:48:49 localhost NetworkManager: information SUP: sending command 'SET_NETWORK 0 ssid 6d796e6574'
Feb 8 13:48:49 localhost NetworkManager: information SUP: response was 'OK'
Feb 8 13:48:49 localhost NetworkManager: information SUP: sending command 'SET_NETWORK 0 proto WPA'
Feb 8 13:48:49 localhost NetworkManager: information SUP: response was 'OK'
Feb 8 13:48:49 localhost NetworkManager: information SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
Feb 8 13:48:49 localhost NetworkManager: information SUP: response was 'OK'
Feb 8 13:48:49 localhost NetworkManager: information SUP: sending command 'SET_NETWORK 0 psk key'
Feb 8 13:48:49 localhost NetworkManager: information SUP: response was 'OK'
Feb 8 13:48:49 localhost NetworkManager: information SUP: sending command 'SET_NETWORK 0 pairwise TKIP'
Feb 8 13:48:49 localhost NetworkManager: information SUP: response was 'OK'
Feb 8 13:48:49 localhost NetworkManager: information SUP: sending command 'SET_NETWORK 0 group TKIP'
Feb 8 13:48:49 localhost NetworkManager: information SUP: response was 'OK'
Feb 8 13:48:49 localhost NetworkManager: information SUP: sending command 'ENABLE_NETWORK 0'
Feb 8
Re: networkmanager fails to associate (ipw3945)
On Thu, 2007-02-08 at 13:53 +0100, dragoran wrote:
Dan Williams wrote:
On Thu, 2007-02-08 at 10:29 +0100, dragoran wrote:
I recompiled ieee and ipw3945 and it now works with wpa_supplicant
without any problems (using the wext driver).
but nm keeps asking me for the passphrase and never connects.
Hmm; can you get some logs of NM during the connection attempt? They
should get dumped to /var/log/messages. Basically, it may be the case
that NM isn't passing the same options to wpa_supplicant as your
testcase is using, but we don't know what those options are.
nm output to syslog is attached (note: ignore selinux messages I did run
setenforce 0 before doing this test)
Does this wpa_supplicant config file work for you?
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
ap_scan=1
network={
ssid=mynet
proto=WPA
key_mgmt=WPA-PSK
scan_ssid=1
pairwise=TKIP
group=TKIP
psk=your key
}
If not, we need to figure out why that doesn't work. The config above
is essentially what NM is pushing to wpa_supplicant.
Dan
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
it does I created a file wpax.txt with the contents you posted (only changed
passphrase) and did
wpa_supplicant -D wext -i eth1 -c wpax.txt -dd (to enable debug output to)
and it connects just fine.
I attached the output.
On 2/8/07, Dan Williams [EMAIL PROTECTED] wrote:
On Thu, 2007-02-08 at 13:53 +0100, dragoran wrote:
Dan Williams wrote:
On Thu, 2007-02-08 at 10:29 +0100, dragoran wrote:
I recompiled ieee and ipw3945 and it now works with wpa_supplicant
without any problems (using the wext driver).
but nm keeps asking me for the passphrase and never connects.
Hmm; can you get some logs of NM during the connection attempt? They
should get dumped to /var/log/messages. Basically, it may be the case
that NM isn't passing the same options to wpa_supplicant as your
testcase is using, but we don't know what those options are.
nm output to syslog is attached (note: ignore selinux messages I did run
setenforce 0 before doing this test)
Does this wpa_supplicant config file work for you?
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
ap_scan=1
network={
ssid=mynet
proto=WPA
key_mgmt=WPA-PSK
scan_ssid=1
pairwise=TKIP
group=TKIP
psk=your key
}
If not, we need to figure out why that doesn't work. The config above
is essentially what NM is pushing to wpa_supplicant.
Dan
wpa_supplicant -D wext -i eth1 -c wpax.txt -dd
Initializing interface 'eth1' conf 'wpax.txt' driver 'wext' ctrl_interface 'N/A'
Configuration file 'wpax.txt' - '/home/linux/wpax.txt'
Reading configuration file '/home/linux/wpax.txt'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=10 (from group name 'wheel')
ap_scan=1
Line: 6 - start of a new network block
ssid - hexdump_ascii(len=5):
6d 79 6e 65 74mynet
proto: 0x1
key_mgmt: 0x2
scan_ssid=1 (0x1)
pairwise: 0x8
group: 0x8
PSK (ASCII passphrase) - hexdump_ascii(len=9): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='mynet'
Initializing interface (2) 'eth1'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=21 WE(source)=16 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
Own MAC address: 00:18:de:05:f7:9e
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 10 usec
Added interface eth1
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
State: DISCONNECTED - SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=5):
6d 79 6e 65 74mynet
Scan timeout - try to get results
Received 345 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:0d:0b:c3:bd:c9 ssid='mynet' wpa_ie_len=24 rsn_ie_len=22 caps=0x11
selected based on WPA IE
Trying to associate with 00:0d:0b:c3:bd:c9 (SSID='mynet' freq=0 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 0f ac 02 01 00 00 0f ac 02 0c 00
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING - ASSOCIATING
wpa_driver_wext_associate
Setting authentication timeout: 15 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RSN: Ignored PMKID candidate without preauth flag
Wireless event: cmd=0x8b06 len=12
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: 00:00:00:00:00:00
Added BSSID 00:00:00:00:00:00 into blacklist
State: ASSOCIATING - DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0
Re: networkmanager fails to associate (ipw3945)
On Wed, 2007-02-07 at 11:30 +0100, dragoran wrote: Hello, I am using networkmanager on FC6 with the ipw3945 driver (1.2.0 + ucode 1.14.2). I created a accesspoint with hostapd and a rt2500usb based device. I am using WPA-PSK + TKIP for it. When I try to connect networkmanager ask me for the passphrase, I enter it and it trys to connect, but it never does this. hostapd prints this message: No WPA/RSN IE in association request seems that nm/wpa_supplicant does not send all data which is required by the ap? I tryed windows on the same system and it works. (it ask for passphrase and connects to the ap). I tryed unencrypted but it fails here too (timeout because took longer than 40s). With the unencrypted ap sometimes it *does* associate but nm does not regognice it. (iwconfig shows this) and if I give it a ip I can ping the ap. Whats going on here? I have tryed everything (blamed the ap first, but than tryed windows and it works). Thx in advance for any hints/help. If you need more info feel free to ask. Can you connect to that AP with plain wpa_supplicant and the 'wext' driver? dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Dan Williams wrote: On Wed, 2007-02-07 at 11:30 +0100, dragoran wrote: Hello, I am using networkmanager on FC6 with the ipw3945 driver (1.2.0 + ucode 1.14.2). I created a accesspoint with hostapd and a rt2500usb based device. I am using WPA-PSK + TKIP for it. When I try to connect networkmanager ask me for the passphrase, I enter it and it trys to connect, but it never does this. hostapd prints this message: No WPA/RSN IE in association request seems that nm/wpa_supplicant does not send all data which is required by the ap? I tryed windows on the same system and it works. (it ask for passphrase and connects to the ap). I tryed unencrypted but it fails here too (timeout because took longer than 40s). With the unencrypted ap sometimes it *does* associate but nm does not regognice it. (iwconfig shows this) and if I give it a ip I can ping the ap. Whats going on here? I have tryed everything (blamed the ap first, but than tryed windows and it works). Thx in advance for any hints/help. If you need more info feel free to ask. Can you connect to that AP with plain wpa_supplicant and the 'wext' driver? yes but it keeps connecting/disconnection (disconnect event remove keys) and sometimes it becomes stable and stays connected. while nm never manages to connect. and when using plain wpa_supplicant I do not get No WPA/RSN IE in association request in hostapd output. dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Dan Williams wrote: On Wed, 2007-02-07 at 11:30 +0100, dragoran wrote: Hello, I am using networkmanager on FC6 with the ipw3945 driver (1.2.0 + ucode 1.14.2). I created a accesspoint with hostapd and a rt2500usb based device. I am using WPA-PSK + TKIP for it. When I try to connect networkmanager ask me for the passphrase, I enter it and it trys to connect, but it never does this. hostapd prints this message: No WPA/RSN IE in association request seems that nm/wpa_supplicant does not send all data which is required by the ap? I tryed windows on the same system and it works. (it ask for passphrase and connects to the ap). I tryed unencrypted but it fails here too (timeout because took longer than 40s). With the unencrypted ap sometimes it *does* associate but nm does not regognice it. (iwconfig shows this) and if I give it a ip I can ping the ap. Whats going on here? I have tryed everything (blamed the ap first, but than tryed windows and it works). Thx in advance for any hints/help. If you need more info feel free to ask. Can you connect to that AP with plain wpa_supplicant and the 'wext' driver? wpa_gui dectects the ap as wpa2-psk while nm uses wpa-psk, but chaning the option to wpa2 personal in the ask for key gui does not help. (40s timeout) and wpa_supplicant takes longer than 40 sec to connect (reconnect/disconnect/reconnect etc.) until the connection is up. dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Dan Williams wrote: On Wed, 2007-02-07 at 13:28 +0100, dragoran wrote: Dan Williams wrote: On Wed, 2007-02-07 at 11:30 +0100, dragoran wrote: Hello, I am using networkmanager on FC6 with the ipw3945 driver (1.2.0 + ucode 1.14.2). I created a accesspoint with hostapd and a rt2500usb based device. I am using WPA-PSK + TKIP for it. When I try to connect networkmanager ask me for the passphrase, I enter it and it trys to connect, but it never does this. hostapd prints this message: No WPA/RSN IE in association request seems that nm/wpa_supplicant does not send all data which is required by the ap? I tryed windows on the same system and it works. (it ask for passphrase and connects to the ap). I tryed unencrypted but it fails here too (timeout because took longer than 40s). With the unencrypted ap sometimes it *does* associate but nm does not regognice it. (iwconfig shows this) and if I give it a ip I can ping the ap. Whats going on here? I have tryed everything (blamed the ap first, but than tryed windows and it works). Thx in advance for any hints/help. If you need more info feel free to ask. Can you connect to that AP with plain wpa_supplicant and the 'wext' driver? yes but it keeps connecting/disconnection (disconnect event remove keys) and sometimes it becomes stable and stays connected. while nm never manages to connect. and when using plain wpa_supplicant I do not get No WPA/RSN IE in association request in hostapd output. Are you using ap_scan=1 or ap_scan=2 in your wpa_supplicant config file? What do your pairwise and group cipher options look like? I set the driver to wext in and started wpa_supplicant and connected with wpa_gui, trying with the manuall config now. Thanks, Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
no luck with wpa_supplicant :( it shows trying to associate with correctid (SSID=mynet, freq=*0* Mhz) why 0 ?? and then it fails with Authentification with 00:00:00: .. (only 0) timed out... again why the 00:00 .. ? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
You may have that nasty SSID bug, do a iwconfig a few times, what SSID do u see, any weird characters? dragoran wrote: Dan Williams wrote: On Wed, 2007-02-07 at 13:28 +0100, dragoran wrote: Dan Williams wrote: On Wed, 2007-02-07 at 11:30 +0100, dragoran wrote: Hello, I am using networkmanager on FC6 with the ipw3945 driver (1.2.0 + ucode 1.14.2). I created a accesspoint with hostapd and a rt2500usb based device. I am using WPA-PSK + TKIP for it. When I try to connect networkmanager ask me for the passphrase, I enter it and it trys to connect, but it never does this. hostapd prints this message: No WPA/RSN IE in association request seems that nm/wpa_supplicant does not send all data which is required by the ap? I tryed windows on the same system and it works. (it ask for passphrase and connects to the ap). I tryed unencrypted but it fails here too (timeout because took longer than 40s). With the unencrypted ap sometimes it *does* associate but nm does not regognice it. (iwconfig shows this) and if I give it a ip I can ping the ap. Whats going on here? I have tryed everything (blamed the ap first, but than tryed windows and it works). Thx in advance for any hints/help. If you need more info feel free to ask. Can you connect to that AP with plain wpa_supplicant and the 'wext' driver? yes but it keeps connecting/disconnection (disconnect event remove keys) and sometimes it becomes stable and stays connected. while nm never manages to connect. and when using plain wpa_supplicant I do not get No WPA/RSN IE in association request in hostapd output. Are you using ap_scan=1 or ap_scan=2 in your wpa_supplicant config file? What do your pairwise and group cipher options look like? I set the driver to wext in and started wpa_supplicant and connected with wpa_gui, trying with the manuall config now. Thanks, Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
sorry for the the emails but now I got it working with wpa_supplicant (attached config and output). wpa.tar.bz2 Description: application/bzip ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Grant Williamson wrote: You may have that nasty SSID bug, do a iwconfig a few times, what SSID do u see, any weird characters? not it displays mynet which is correct. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
