Re: Oddities with NM 0.7
On 10/12/07, Clark Williams [EMAIL PROTECTED] wrote: I've been having trouble with NetworkManager 0.7 on my rawhide laptop (T60 with iwl3945 wireless part running latest iwlwifi drivers), ever since it came out. The main symptom I'm seeing is the following in syslog: Oct 13 02:30:57 localhost NetworkManager: info Trying to start the supplicant... Oct 13 02:32:03 localhost NetworkManager:last message repeated 11 times NM tries to start wpa_supplicant using dbus-1.1 system service activation and fails. Make sure you have dbus-1.1 installed and running. 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 Tambet Ingo wrote: On 10/12/07, Clark Williams [EMAIL PROTECTED] wrote: I've been having trouble with NetworkManager 0.7 on my rawhide laptop (T60 with iwl3945 wireless part running latest iwlwifi drivers), ever since it came out. The main symptom I'm seeing is the following in syslog: Oct 13 02:30:57 localhost NetworkManager: info Trying to start the supplicant... Oct 13 02:32:03 localhost NetworkManager:last message repeated 11 times NM tries to start wpa_supplicant using dbus-1.1 system service activation and fails. Make sure you have dbus-1.1 installed and running. Tambet Well, I seem to have all the right pieces in place: $ rpm -q dbus dbus-1.1.2-7.fc8 $ sudo /sbin/service messagebus status dbus-daemon (pid 2659 1881) is running... So I started poking around in my /etc dir and I noticed that I have an ldap.conf.rpmnew (the file rpm creates when it doesn't want to replace something it thinks you've modified). And, lo and behold, that unused ldap.conf mentions dbus. Think I'll swap file and restart and see what happens. Thanks, Clark -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHE3HHHyuj/+TTEp0RAqe8AKCu/FKodhBL3LIzN4DR/69O1m/8kACgqpyS /fcsJoOUtCSJ8voDoAVxwYM= =JSz3 -END PGP SIGNATURE- ___ 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
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
Re: Oddities with NM 0.7
On Fri, 2007-10-12 at 15:55 -0500, Clark Williams wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've been having trouble with NetworkManager 0.7 on my rawhide laptop (T60 with iwl3945 wireless part running latest iwlwifi drivers), ever since it came out. The main symptom I'm seeing is the following in syslog: Oct 13 02:30:57 localhost NetworkManager: info Trying to start the supplicant... Oct 13 02:32:03 localhost NetworkManager:last message repeated 11 times No wireless. If I downgrade to the f7 set of packages (NetworkManager*, wireless-tools, dhcdbd, wpa_supplicant, libdhcp4client, and dhclient), NetworkManager works fine. I've also seen the latest rawhide packages cause problems with wired connections (e1000 driver). The wired connection will come up, then NM will take it down and try to start a wireless session. I've had this laptop on rawhide for quite some time, so it's entirely possible that there's some stale config information out there causing one of the components problems. Any suggestions on how to track down what's going wrong? Can you grab /var/log/messages from the machine? It might be the autoconnect thing; up to F8T3 NM didn't have the logic to connect to the last known network, which was added later. If you used NM before you won't have 'autoconnect' set up on that connection. Check GConf in /system/networking/connections, find your auto eth0 connection, and make sure that 'autoconnect' is checked. Dan Thanks, Clark -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHD98nHyuj/+TTEp0RAmipAJ9EY4c8oNYqeNtm99RffK7RpuE+uQCgpBRb IsY6Fjfkf9TtW7N2OqX0o08= =a/6H -END PGP SIGNATURE- ___ 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
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Williams wrote: On Fri, 2007-10-12 at 15:55 -0500, Clark Williams wrote: I've been having trouble with NetworkManager 0.7 on my rawhide laptop (T60 with iwl3945 wireless part running latest iwlwifi drivers), ever since it came out. The main symptom I'm seeing is the following in syslog: Oct 13 02:30:57 localhost NetworkManager: info Trying to start the supplicant... Oct 13 02:32:03 localhost NetworkManager:last message repeated 11 times No wireless. If I downgrade to the f7 set of packages (NetworkManager*, wireless-tools, dhcdbd, wpa_supplicant, libdhcp4client, and dhclient), NetworkManager works fine. I've also seen the latest rawhide packages cause problems with wired connections (e1000 driver). The wired connection will come up, then NM will take it down and try to start a wireless session. I've had this laptop on rawhide for quite some time, so it's entirely possible that there's some stale config information out there causing one of the components problems. Any suggestions on how to track down what's going wrong? Can you grab /var/log/messages from the machine? It might be the autoconnect thing; up to F8T3 NM didn't have the logic to connect to the last known network, which was added later. If you used NM before you won't have 'autoconnect' set up on that connection. Check GConf in /system/networking/connections, find your auto eth0 connection, and make sure that 'autoconnect' is checked. Dan, Thanks, I was running into the autoconnect problem. I ran gconf-editor and checked autoconnect for my eth0 and it now connects just fine. But, I'm still seeing: Oct 15 22:01:15 localhost NetworkManager: info Trying to start the supplicant... Oct 15 22:02:21 localhost NetworkManager:last message repeated 11 times I am running a current rawhide and made a pass through /etc and fixed some out of date configs (bitten by .rpmnew), but I'm still not seeing my iwl3945 wlan connection in the NM applet (and I do on same kernel(s) with f7 NM/wpa_supplicant/et al). Anything I should turn on wrt NM debugging? Clark -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHE4/xHyuj/+TTEp0RAmejAKDGdWcWYOXk0yL32nJF5YHJHHQzUwCg5eN3 0tKW1IWbVUH3Nqoek/+MI7g= =LRVn -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
On Mon, 2007-10-15 at 11:06 -0500, Clark Williams wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Williams wrote: On Fri, 2007-10-12 at 15:55 -0500, Clark Williams wrote: I've been having trouble with NetworkManager 0.7 on my rawhide laptop (T60 with iwl3945 wireless part running latest iwlwifi drivers), ever since it came out. The main symptom I'm seeing is the following in syslog: Oct 13 02:30:57 localhost NetworkManager: info Trying to start the supplicant... Oct 13 02:32:03 localhost NetworkManager:last message repeated 11 times No wireless. If I downgrade to the f7 set of packages (NetworkManager*, wireless-tools, dhcdbd, wpa_supplicant, libdhcp4client, and dhclient), NetworkManager works fine. I've also seen the latest rawhide packages cause problems with wired connections (e1000 driver). The wired connection will come up, then NM will take it down and try to start a wireless session. I've had this laptop on rawhide for quite some time, so it's entirely possible that there's some stale config information out there causing one of the components problems. Any suggestions on how to track down what's going wrong? Can you grab /var/log/messages from the machine? It might be the autoconnect thing; up to F8T3 NM didn't have the logic to connect to the last known network, which was added later. If you used NM before you won't have 'autoconnect' set up on that connection. Check GConf in /system/networking/connections, find your auto eth0 connection, and make sure that 'autoconnect' is checked. Dan, Thanks, I was running into the autoconnect problem. I ran gconf-editor and checked autoconnect for my eth0 and it now connects just fine. But, I'm still seeing: Oct 15 22:01:15 localhost NetworkManager: info Trying to start the supplicant... Oct 15 22:02:21 localhost NetworkManager:last message repeated 11 times I am running a current rawhide and made a pass through /etc and fixed some out of date configs (bitten by .rpmnew), but I'm still not seeing my iwl3945 wlan connection in the NM applet (and I do on same kernel(s) with f7 NM/wpa_supplicant/et al). Do you have /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.conf ? Try running, as root: /usr/sbin/wpa_supplicant -dd -u 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. Dan Anything I should turn on wrt NM debugging? Clark -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHE4/xHyuj/+TTEp0RAmejAKDGdWcWYOXk0yL32nJF5YHJHHQzUwCg5eN3 0tKW1IWbVUH3Nqoek/+MI7g= =LRVn -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: Do you have /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.conf ? Hmmm, almost :). I have: $ ls /usr/share/dbus-1/system-services/ fi.epitest.hostap.WPASupplicant.service Should I rename the above from .service to .conf? Try running, as root: /usr/sbin/wpa_supplicant -dd -u This seems to run fine. 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. Clark -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHE5uMHyuj/+TTEp0RAsInAJ93atu6b1+ot36hGu+WpUIUQ8z1fACeKUWX OVTs90RRNh608pLR754sWV0= =C3G6 -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
On Mon, 2007-10-15 at 11:55 -0500, Clark Williams wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Williams wrote: Do you have /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.conf ? Hmmm, almost :). I have: $ ls /usr/share/dbus-1/system-services/ fi.epitest.hostap.WPASupplicant.service Should I rename the above from .service to .conf? Sorry, .service is the correct extension. My bad, don't change it. Dan Try running, as root: /usr/sbin/wpa_supplicant -dd -u This seems to run fine. 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. Clark -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHE5uMHyuj/+TTEp0RAsInAJ93atu6b1+ot36hGu+WpUIUQ8z1fACeKUWX OVTs90RRNh608pLR754sWV0= =C3G6 -END PGP SIGNATURE- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: iwl3945 fails to associate to open, non-broadcast network
Dan Williams [EMAIL PROTECTED] writes: On Mon, 2007-10-15 at 11:24 -0400, Derek Atkins wrote: Running fedora 7 with kernel-2.6.22.9-91.fc7-i686, trying to connect to a non-broadcasting open network using iwl3945. I see this in dmesg: eth1: Initial auth_alg=0 eth1: authenticate with AP 00:0e:d7:91:94:70 eth1: RX authentication from 00:0e:d7:91:94:70 (alg=0 transaction=2 status=0) eth1: authenticated eth1: associate with AP 00:0e:d7:91:94:70 eth1: RX AssocResp from 00:0e:d7:91:94:70 (capab=0x0 status=45552 aid=0) eth1: AP denied association (code=45552) eth1: associate with AP 00:0e:d7:91:94:70 eth1: RX deauthentication from 00:0e:d7:91:94:70 (reason=2) eth1: deauthenticated what is status code 45552? google says nothing about it. I can try downgrading to an older kernel to test. This happens both with and without NM so it's probably a driver bug but I was hoping that the greater NM community might know. The 45552 sounds bogus; IEEE 802.11 association response codes are 8-bits. Could be some internal status code. Hey, I'm just reporting what it was reporting. I have no idea what it means. I was finally able to cajole it into connecting by stopping NM, unloading my driver, reloading my driver, trying to connect manually, and then (once it connected manually and actually got scan results with visible ESSIDS) restarted NM. Then it connected right away and I've been happy. But it really does seem to dislike hidden networks. :( Dan -derek PS: Any idea why NM stopped using my local caching nameserver? -- 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: Trying to start the supplicant...
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? kad ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: login keyring
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? 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
