Re: Oddities with NM 0.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Williams wrote: On Tue, 2007-10-16 at 10:03 -0500, Clark Williams wrote: 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). Are you trying to use WEP with a passphrase? Current snapshots in Rawhide don't support WEP passphrases, hope to fix that today. All the UI bits are in SVN for this already but not active since there's a bit more code needed to have the dialog pick the right encryption methods for the wireless device (ie, ignore WPA if your card can't do it) and network you're connecting to. Dan Clark Just wanted to thank you for helping me resolve this on IRC. For those that might be interested, I had at one point both the i386 and x86_64 packages for NetworkManager installed on my Fedora rawhide box. When I removed the i386, it left a configuration file (/etc/dbus-1/service.conf) around that specified execing a file out of /lib (rather than /lib64). Changing that path got me going. Thanks Dan! Clark Note to self: be more careful with 'rpm -e' -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHGQzzHyuj/+TTEp0RAqH2AKDeyWNq5t1u+p7ZeZSqD4w5SqgMBgCfcL5Z 0vuHBYRRj3dajUIBmlByisI= =CAi5 -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 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: 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: 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: 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: Oddities with NM 0.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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? Thanks, Clark And of course I forgot to mention that SELinux is currently disabled... Clark -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHD9+SHyuj/+TTEp0RAscvAKCNY3zo1UqYtEWdJexOgUwcWhvWKACgk8FX 1LquSAV8X4hQjqfZcmaFzJs= =s3XH -END PGP SIGNATURE- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Oddities with NM 0.7
-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? 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
