feedI was finally able to get NetworkManager working in KDE. I had to emerge hal, dbus, and friends, re-emerge pam w/ the pam_console use flag, and use the Gentopia overlay for the NetworkManager ebuilds. Once I had the application up and running I had to use gtk-update-icon-cache command before the applet would start. Once that worked I had to start and stop gnome-keyring-daemon and set the environment variables in my kde env and shutdown directories:
spencer@jtfc ~ $ cat /usr/kde/3.5/env/gnome-keyring.sh
#!/bin/sh
eval `gnome-keyring-daemon`
export GNOME_KEYRING_PID GNOME_KEYRING_SOCKET
set | grep GNOME
spencer@jtfc ~ $ cat /usr/kde/3.5/shutdown/gnome-keyring.sh
#!/bin/sh
if [ -n "$GNOME_KEYRING_PID" ]; then
echo killing gnome-keyring-daemon $GNOME_KEYRING_PID
kill $GNOME_KEYRING_PID fi spencer@jtfc ~ $
gnome-keyring is used to store WEP/WPA keys and passwords and such. Without running it you can still use NetworkManager, you will just have to enter the encryption keys for any secure networks by hand each time.
Now that it’s all installed I must say it’s pretty damn cool. I installed the pptp and vpnc “plugins” but haven’t had a chance to play much with those. I like being able to plugin a wire and have it switch to the wired network automatically, and then when I unplug it the lappy goes wireless again. Nice work guys!
I’m also using a gtk2-ssh-askpass now. I uncommented the “ssh-agent” lines in /usr/kde/3.5/env/ and /usr/kde/3.5/shutdown/ agent files(and gpg-agent lines for other reasons). Then I run “ssh-add” from ~/.kde3.5/Autostart/ssh-add.sh. Now I only have to type my passphrases for my dsa and rsa keys once when I login. The agents are terminated at the end of my session automatically. Pretty neat trick.
Comment by Benjamin
6 Thursday, April 27, 2006, 8:55 pm o'clock |
i have
Comment by spencer
7 Saturday, May 6, 2006, 9:37 am o'clock |
Last time I checked there were only a few wifi drivers that were officially supported… my ipw2200 was one of them. I know that the more recent version of Network Manager utilize wpa_supplicant to manage the actual devices. It passes the wext module to wpa_supplicant (is this a build time option?) so if your Cisco card doesn’t support wext you might be out of luck. You could also try modifying the Network Manager source to pass different parameters to wpa_supplicant.
Comment by Doug
8 Monday, September 11, 2006, 2:51 pm o'clock |
I recently worked though a similar problem with my SuSE 10.1 / Gnome setup. Note: NetworkManager and the rest of this should comfortably sit below either KDE or Gnome.
The main issue in my case was the flakey DHCP clients — at least in SuSE. I long ago set up my router to provide static leases, allowing DNS settings to automaticaly update without losing easy access to my other machines. Some routers turn static leases into infinite leases and Linux DHCP clients start complaining!
You might be able to find a /var/log/localmessages line such as “dhcpcd[7824]: infinite IP address lease time. Exiting” but “dhcpcd[7824]: dhcpIPaddrLeaseTime=4294967295 in DHCP server response.” was all I could find at first. In any case, NetworkManager was waiting for a DBUS message from a process that had died.
Reconfigured my DHCP server and I was on my way…
BTW: Other routers, such as my older default DHCP server, honour the DHCP lease request a client sends — providing an easier work-around in /etc/sysconfig/network/dhcp.