Re: Trying to start the supplicant...
On 10/16/07, krash [EMAIL PROTECTED] wrote: my version of wpa_supplicant is 0.5.7 but don't have -u option. Do i search new version? Yes, it means your wpa_supplicant is compiled without dbus support and won't work with NetworkManager 0.7. If you decide to build wpa_supplicant from sources, it needs a CONFIG_CTRL_IFACE_DBUS=y line in .config file. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Oddities with NM 0.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Williams wrote: On Mon, 2007-10-15 at 11:55 -0500, Clark Williams wrote: Dan Williams wrote: Try running, as root: /usr/sbin/wpa_supplicant -dd -u This seems to run fine. Actually, what happens is that wpa_supplicant runs and scans, but when it sees a network it likes, it pops up a password dialog (rather than invoking gnome-keyring). if that works, then something is going wrong in the dbus service activation of wpa_supplicant. You said SELinux was disabled, or just in permissive? It's worked fine in permissive everywhere I've tried it so far. No, I've actually disabled it in the config file (/me looks sheepish, since I've been meaning to turn it back on...). Maybe I'll try permissive for a bit. I set SELINUX=permissive, waited for the relabel to finish and tried everything again, but saw no change in behavior. I suspect that you are correct, thinking that something is going wrong in dbus's activation of wpa_supplicant. Any thoughts on where to look next? Thanks, Clark -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHFMZeHyuj/+TTEp0RArLYAJ92ZKTYPmWQ6caX6geGJWe1KTEP5ACgnHeB YqkyiYYhXlakU2usc7tc8sE= =Bly3 -END PGP SIGNATURE- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Trying to start the supplicant...
On Mon, 2007-10-15 at 23:53 +0200, krash wrote: 2007/10/15, Dan Williams [EMAIL PROTECTED]: On Mon, 2007-10-15 at 12:25 +0200, krash wrote: 2007/10/14, Dan Williams [EMAIL PROTECTED]: On Sun, 2007-10-14 at 16:08 +0200, krash wrote: Hi friends, I have a trouble with NetworkManager on my Slackware 12.0. I have a notebook with bcm4318 wireless chipset; wireless is powered by ndiswrapper. You need to either: 1) install dbus 1.1.0 or higher with system bus activation capability dbus version is 1.1.2 and process running is: # ps ax |grep dbus 2394 ?Ss 0:01 /usr/bin/dbus-daemon --system 2637 ?Ss 0:00 dbus-daemon --fork --print-address 18 --print-pid 20 --session 2663 ?S 0:00 dbus-daemon --session --print-address --nofork 2) start wpa_supplicant as a service at startup with the -u option I have tried to start wpa_supplicant as service before Networknamager, but nothing. Also I have start wpa_supplicant with debug option: when Networkmanager start i see in log of wpa_supplicant that Networkmanager add a network interface, but in log of Networkmanager i see always Trying to start the supplicant... what is -u option? It tells wpa_supplicant to start its D-Bus control interface, which is how NetworkManager drives wpa_supplicant. This requires wpa_supplicant 0.5.7 or later. Hi, my version of wpa_supplicant is 0.5.7 but don't have -u option. Do i search new version? Did you build wpa_supplicant with CONFIG_CTRL_IFACE_DBUS=y ? kad ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: login keyring
On Tue, 2007-10-16 at 01:50 +0200, Giovanni Lovato wrote: Darren Albers wrote: On Sun, 2007-10-14 at 12:18 +0200, Giovanni Lovato wrote: On a fresh install of Ubuntu Gutsy, I have NM 0.6.5. When I first connect to a wireless network, it stores passphrase on unlocked login keyring, no more on the locked default keyring. It's not a problem for me that, but next time I login NM doesn't connect and syslog: [CUT] info Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... info Activation (eth1) Stage 1 of 5 (Device Prepare) started... info Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... info Activation (eth1) Stage 1 of 5 (Device Prepare) complete. info Activation (eth1) Stage 2 of 5 (Device Configure) starting... info Activation (eth1/wireless): access point 'Telperion' is encrypted, but NO valid key exists. New key needed. info Activation (eth1) New wireless user key requested for network 'Telperion'. info Activation (eth1) Stage 2 of 5 (Device Configure) complete. info Activation (eth1) New wireless user key for network 'Telperion' received. and so on... I have always to unset gconf entries and reconnect manually. Where do you think the problem is? Thank you! G.L. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list It sounds like your keyring isn't being unlocked... I would file a bug on launchpad.net since this seems like a Gutsy specific issue (Though I am running Gutsy without the issue you describe). Reading log files I guess my keyring is being unlocked correctly: gdm[6175]: pam_unix(gdm:session): session opened for user giovanni by (uid=0) gdm[6175]: gkr-pam: unlocked 'login' keyring And it seems also NM is receiving the key: info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... info Activation (wlan0/wireless): access point 'Laurelin' is encrypted, but NO valid key exists. New key needed. info Activation (wlan0) New wireless user key requested for network 'Laurelin'. info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. info Activation (wlan0) New wireless user key for network 'Laurelin' received. info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... info Activation (wlan0/wireless): access point 'Laurelin' is encrypted, but NO valid key exists. New key needed. info Activation (wlan0) New wireless user key requested for network 'Laurelin'. info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. But doesn't bring up the interface and it loops on those stages. The key is correct because if I unset gconf entries and retry to connect all goes fine, it saves the key to the keyring and then connects. The problem appears the next login, so I have to unset gconf entries and always recreate the connection... I have that issue on two different fresh Gutsy installation. Do you think it's a Gutsy related bug, my fault or NM? Can you provide the output of an 'iwlist interface name scan' for the 'Laurelin' access point? Thanks, Dan Thank you! G.L. ___ 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: Oddities with NM 0.7
On Tue, 2007-10-16 at 09:10 -0500, Clark Williams wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Williams wrote: On Mon, 2007-10-15 at 11:55 -0500, Clark Williams wrote: Dan Williams wrote: Try running, as root: /usr/sbin/wpa_supplicant -dd -u This seems to run fine. Actually, what happens is that wpa_supplicant runs and scans, but when it sees a network it likes, it pops up a password dialog (rather than invoking gnome-keyring). Your keyring is probably already unlocked... NM will notice that wpa_supplicant has started, and try to connect to a saved network, prompting your for the wireless key. Dan if that works, then something is going wrong in the dbus service activation of wpa_supplicant. You said SELinux was disabled, or just in permissive? It's worked fine in permissive everywhere I've tried it so far. No, I've actually disabled it in the config file (/me looks sheepish, since I've been meaning to turn it back on...). Maybe I'll try permissive for a bit. I set SELINUX=permissive, waited for the relabel to finish and tried everything again, but saw no change in behavior. I suspect that you are correct, thinking that something is going wrong in dbus's activation of wpa_supplicant. Any thoughts on where to look next? Thanks, Clark -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHFMZeHyuj/+TTEp0RArLYAJ92ZKTYPmWQ6caX6geGJWe1KTEP5ACgnHeB YqkyiYYhXlakU2usc7tc8sE= =Bly3 -END PGP SIGNATURE- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Oddities with NM 0.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Williams wrote: On Tue, 2007-10-16 at 09:10 -0500, Clark Williams wrote: Dan Williams wrote: On Mon, 2007-10-15 at 11:55 -0500, Clark Williams wrote: Dan Williams wrote: Try running, as root: /usr/sbin/wpa_supplicant -dd -u This seems to run fine. Actually, what happens is that wpa_supplicant runs and scans, but when it sees a network it likes, it pops up a password dialog (rather than invoking gnome-keyring). Your keyring is probably already unlocked... NM will notice that wpa_supplicant has started, and try to connect to a saved network, prompting your for the wireless key. No, the keyring isn't unlocked (at least I wasn't prompted to give my passphrase to unlock it). This was a dialog that I've never seen before. And, no matter what I typed into this dialog, I never saw the OK button become active (i.e. it was grayed out). Clark -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHFNLfHyuj/+TTEp0RAv87AKCsVcxx6x8+zPV7kVJQqEydFo6GfgCgp9sf U4VsqORvkiGdRg9QxZapQ3c= =kQd9 -END PGP SIGNATURE- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Trying to start the supplicant...
2007/10/16, Tambet Ingo [EMAIL PROTECTED]: On 10/16/07, krash [EMAIL PROTECTED] wrote: my version of wpa_supplicant is 0.5.7 but don't have -u option. Do i search new version? Yes, it means your wpa_supplicant is compiled without dbus support and won't work with NetworkManager 0.7. If you decide to build wpa_supplicant from sources, it needs a CONFIG_CTRL_IFACE_DBUS=y line in .config file. Tambet Hi no i haven't enabled dbus in config file because i have used a original package. Now i have compiled with options and it works!! If i start wpa_supplicant daemon before NetworkManager, all works, but isn't dbus capable to start wpa_supplicant automatically? In other post i see that there is a file in /usr/share/dbus-1/services. I don't have it. What is the content? Thanks ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: login keyring
Dan Williams wrote: [CUT] Reading log files I guess my keyring is being unlocked correctly: gdm[6175]: pam_unix(gdm:session): session opened for user giovanni by (uid=0) gdm[6175]: gkr-pam: unlocked 'login' keyring And it seems also NM is receiving the key: info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... info Activation (wlan0/wireless): access point 'Laurelin' is encrypted, but NO valid key exists. New key needed. info Activation (wlan0) New wireless user key requested for network 'Laurelin'. info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. info Activation (wlan0) New wireless user key for network 'Laurelin' received. info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... info Activation (wlan0/wireless): access point 'Laurelin' is encrypted, but NO valid key exists. New key needed. info Activation (wlan0) New wireless user key requested for network 'Laurelin'. info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. But doesn't bring up the interface and it loops on those stages. The key is correct because if I unset gconf entries and retry to connect all goes fine, it saves the key to the keyring and then connects. The problem appears the next login, so I have to unset gconf entries and always recreate the connection... I have that issue on two different fresh Gutsy installation. Do you think it's a Gutsy related bug, my fault or NM? Can you provide the output of an 'iwlist interface name scan' for the 'Laurelin' access point? # iwlist wlan0 scan iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: 00:C0:49:D3:F4:0E ESSID:Laurelin Protocol:IEEE 802.11bg Mode:Master Channel:11 Frequency:2.462 GHz (Channel 11) Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Quality=84/100 Signal level=-50 dBm Noise level=-50 dBm IE: WPA Version 1 Group Cipher : WEP-40 Pairwise Ciphers (1) : WEP-40 Authentication Suites (1) : 802.1x Extra: Last beacon: 84ms ago Thank you! G.L. -- mail: [EMAIL PROTECTED] web: http://heruan.my.aldu.net smime.p7s Description: S/MIME Cryptographic Signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Blogpost: Refresh in reactive displays
Hi, For those who haven't seen it, there is a blog-post by Bryan Clark regarding UI principles, arguing against having a Refresh-button in the NetworkManager-applet menu. (Not sure that was ever the intention?) See: http://clarkbw.net/blog/2007/10/16/refresh-in-reactive-displays/ Best regards Hugo Heden -- http://www.fastmail.fm - And now for something completely differentÂ… ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Trying to start the supplicant...
On Tue, 2007-10-16 at 18:20 +0200, krash wrote: 2007/10/16, Tambet Ingo [EMAIL PROTECTED]: On 10/16/07, krash [EMAIL PROTECTED] wrote: my version of wpa_supplicant is 0.5.7 but don't have -u option. Do i search new version? Yes, it means your wpa_supplicant is compiled without dbus support and won't work with NetworkManager 0.7. If you decide to build wpa_supplicant from sources, it needs a CONFIG_CTRL_IFACE_DBUS=y line in .config file. Tambet Hi no i haven't enabled dbus in config file because i have used a original package. Now i have compiled with options and it works!! If i start wpa_supplicant daemon before NetworkManager, all works, but isn't dbus capable to start wpa_supplicant automatically? In other post i see that there is a file in /usr/share/dbus-1/services. I don't have it. Yes, if you have the right .service file in /usr/share/dbus-1/system-services/ then NM will request that dbus automatically start wpa_supplicant. And dbus should be able to do that. Dan What is the content? Thanks ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Blogpost: Refresh in reactive displays
On Tue, 2007-10-16 at 18:59 +0200, Hugo Heden wrote: Hi, For those who haven't seen it, there is a blog-post by Bryan Clark regarding UI principles, arguing against having a Refresh-button in the NetworkManager-applet menu. (Not sure that was ever the intention?) Well, there were requests for a manual refresh button somewhere, and Bryan's argument is that having one anywhere is wrong. Again, I think there are simply bugs in NetworkManager and the applet that would improve the experience for users. That said, I fully admit that I haven't been able to pay 0.6.x the attention it's deserved for the last year or so (due to my working full-time for Red Hat on OLPC). Now, I have been concentrating on getting 0.7 out the door over the last 6 weeks, and once we get a 0.7 release out the door I'll spend some time cleaning up bits in 0.6.x (like auto-scanning behavior and the user-triggered scanning). However, if somebody beats me to the auto-scanning behavior patch (feel free to ask what should happen and I'll gladly say) I won't be crying myself to sleep. Dan See: http://clarkbw.net/blog/2007/10/16/refresh-in-reactive-displays/ Best regards Hugo Heden ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: login keyring
Dan Williams wrote: On Tue, 2007-10-16 at 18:04 +0200, Giovanni Lovato wrote: Dan Williams wrote: [CUT] Reading log files I guess my keyring is being unlocked correctly: gdm[6175]: pam_unix(gdm:session): session opened for user giovanni by (uid=0) gdm[6175]: gkr-pam: unlocked 'login' keyring And it seems also NM is receiving the key: info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... info Activation (wlan0/wireless): access point 'Laurelin' is encrypted, but NO valid key exists. New key needed. info Activation (wlan0) New wireless user key requested for network 'Laurelin'. info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. info Activation (wlan0) New wireless user key for network 'Laurelin' received. info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... info Activation (wlan0/wireless): access point 'Laurelin' is encrypted, but NO valid key exists. New key needed. info Activation (wlan0) New wireless user key requested for network 'Laurelin'. info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. But doesn't bring up the interface and it loops on those stages. The key is correct because if I unset gconf entries and retry to connect all goes fine, it saves the key to the keyring and then connects. The problem appears the next login, so I have to unset gconf entries and always recreate the connection... I have that issue on two different fresh Gutsy installation. Do you think it's a Gutsy related bug, my fault or NM? Can you provide the output of an 'iwlist interface name scan' for the 'Laurelin' access point? # iwlist wlan0 scan iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: 00:C0:49:D3:F4:0E ESSID:Laurelin Protocol:IEEE 802.11bg Mode:Master Channel:11 Frequency:2.462 GHz (Channel 11) Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Quality=84/100 Signal level=-50 dBm Noise level=-50 dBm IE: WPA Version 1 Group Cipher : WEP-40 Pairwise Ciphers (1) : WEP-40 Authentication Suites (1) : 802.1x Extra: Last beacon: 84ms ago Wow. I've never seen an AP advertise in the WPA IE before that it only supports WEP + 802.1x. Usually those APs don't advertise that. Can you tell me the model and vendor of the AP you're using? I think technically, it's illegal to advertise WPA capability with only WEP ciphers. AFAIK WEP is allowed for the Group cipher, but you cannot use WEP as a pairwise cipher with WPA, since WPA requires either TKIP or CCMP or both as pairwise ciphers. This configuration is essentially Dynamic WEP. So it's not surprising that NM will get this config wrong, but it's a bug in NM that should probably get fixed. All that said though, it would be great if all Dynamic WEP access points advertised like this, because then NM can make a better guess as to what type of authentication the AP supports. Seems like a case of a vendor not quite understanding how to go about advertising AP capability... The AP is a USR 9106. The fact is that it always worked (and works) with NM 0.6.4; also notice I have the same problem on another wireless network with the newer DWL-2200AP. So I think my problem isn't related to the APs... G.L. -- mail: [EMAIL PROTECTED] web: http://heruan.my.aldu.net smime.p7s Description: S/MIME Cryptographic Signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: login keyring
On Tue, 2007-10-16 at 23:25 +0200, Giovanni Lovato wrote: Dan Williams wrote: On Tue, 2007-10-16 at 18:04 +0200, Giovanni Lovato wrote: Dan Williams wrote: [CUT] Reading log files I guess my keyring is being unlocked correctly: gdm[6175]: pam_unix(gdm:session): session opened for user giovanni by (uid=0) gdm[6175]: gkr-pam: unlocked 'login' keyring And it seems also NM is receiving the key: info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... info Activation (wlan0/wireless): access point 'Laurelin' is encrypted, but NO valid key exists. New key needed. info Activation (wlan0) New wireless user key requested for network 'Laurelin'. info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. info Activation (wlan0) New wireless user key for network 'Laurelin' received. info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... info Activation (wlan0/wireless): access point 'Laurelin' is encrypted, but NO valid key exists. New key needed. info Activation (wlan0) New wireless user key requested for network 'Laurelin'. info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. But doesn't bring up the interface and it loops on those stages. The key is correct because if I unset gconf entries and retry to connect all goes fine, it saves the key to the keyring and then connects. The problem appears the next login, so I have to unset gconf entries and always recreate the connection... I have that issue on two different fresh Gutsy installation. Do you think it's a Gutsy related bug, my fault or NM? Can you provide the output of an 'iwlist interface name scan' for the 'Laurelin' access point? # iwlist wlan0 scan iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: 00:C0:49:D3:F4:0E ESSID:Laurelin Protocol:IEEE 802.11bg Mode:Master Channel:11 Frequency:2.462 GHz (Channel 11) Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Quality=84/100 Signal level=-50 dBm Noise level=-50 dBm IE: WPA Version 1 Group Cipher : WEP-40 Pairwise Ciphers (1) : WEP-40 Authentication Suites (1) : 802.1x Extra: Last beacon: 84ms ago Wow. I've never seen an AP advertise in the WPA IE before that it only supports WEP + 802.1x. Usually those APs don't advertise that. Can you tell me the model and vendor of the AP you're using? I think technically, it's illegal to advertise WPA capability with only WEP ciphers. AFAIK WEP is allowed for the Group cipher, but you cannot use WEP as a pairwise cipher with WPA, since WPA requires either TKIP or CCMP or both as pairwise ciphers. This configuration is essentially Dynamic WEP. So it's not surprising that NM will get this config wrong, but it's a bug in NM that should probably get fixed. All that said though, it would be great if all Dynamic WEP access points advertised like this, because then NM can make a better guess as to what type of authentication the AP supports. Seems like a case of a vendor not quite understanding how to go about advertising AP capability... The AP is a USR 9106. The fact is that it always worked (and works) with NM 0.6.4; also notice I have the same problem on another wireless network with the newer DWL-2200AP. So I think my problem isn't related to the APs... Does the DWL-2200AP 'iwlist' output look the same? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Cannot connect to any WLAN with NM-Fedora 7-ndiswrapper
I think the problem solved itself. I found an updated package of ndiswrapper
at ATrpms.net, and after I installed that, it started working (for the most
part, it still takes a couple of connection attempts sometimes).
Thanks for your help,
Andrew
On 10/15/07, Dan Williams [EMAIL PROTECTED] wrote:
On Sun, 2007-10-14 at 16:01 -0400, Andrew Pegram wrote:
Sorry I took so long getting back to you. I've attached the iwevent
output as well as the relevant section of the syslog.
So this is because ndiswrapper never actually associates to the access
point that NM has told it to associate to. You'll likely have to enable
ndiswrapper debugging or something to see what's going on there.
Dan
On 10/12/07, Dan Williams [EMAIL PROTECTED] wrote:
On Fri, 2007-10-12 at 00:07 -0400, Andrew Pegram wrote:
Hello all
I don't know if it actually went out the last time I sent
this, so I'm
sending it again (sorry for the repeat, if it is one).
I'm having an issue with connecting to wireless networks
through NM.
It will connect to wired networks just fine, but it refuses
to connect
to any type of wireless network (secured WEP/WPA or
unsecured). I have
checked the syslog and found the following warning
(sensitive
information removed):
Oct 6 23:42:06 Hostname NetworkManager: WARN
nm_device_802_11_wireless_set_essid(): error setting ESSID
to '' for
device wlan0: Invalid argument
I know that the program can read the ESSID from the network
because
earlier in the log, it has:
Oct 6 23:41:44 Hostname NetworkManager: info User
Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / VCU
('VCU' is the ESSID)
I've tried reinstalling everything to do with NetworkManager
and
ndiswrapper, and nothing seems to be working. If I haven't
posted
enough information, I can post everything in the log from
the time I
select the WLAN in the drop-down menu until it stops trying
to
connect.
During an association attempt, can you run the program
iwevent (it
might be in /sbin or /usr/sbin) and reply with it's output?
Thanks!
Dan
Thank you for your time,
Andrew
___
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
