Re: How to connect to a WPA network that uses 10 hexadecimal digits as password
Instructions of the hotel are the following SSID: STI WiFi key: a531bc531d PC: Network Key MAC: WPA 10 digits Could you try turning off NM, killing wpa_supplicant, and using 'iwconfig' to association with WEP instead? killall -TERM NetworkManager killall -TERM wpa_supplicant iwconfig wlan0 key a531bc531d essid STI WiFi you might need to try the iwconfig a few times; then if you do an 'iwconfig' on its own, look for the AP: address to be valid, and if it does, try dhclient. If that doesn't work, there are a few things with wpa_supplicant we can try. Dan I tried this but iwconfig says it is not associated with the accesspoint. Jaap ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Novacom GNS-60IU - how to add support
On Thu, Apr 09, 2009 at 02:37:25AM +0400, Alex Williams wrote: What version of NM from 9.04? What driver controls the device? Ubuntu 9.04 Beta 1 - Network Manager 0.7.0.99 Modem is fully 100% functional in GPRS mode when using wvdial software and /dev/ttyUSB0... Please retry with the latest NM available in 9.04. - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] remove dup in configure.in
On Thu, 2009-04-09 at 07:02 +0200, Michael Biebl wrote: Hi, AC_ARG_WITH(crypto,..) is duplicated, most likely a cp error. Trivial patch attached. Committed, thanks! Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.7.0.100 and Slackware
Sasa Ostrouska wrote: Dear Michael, Hi Sasa, please keep the mailing list in CC On Thu, Apr 9, 2009 at 12:26 PM, Michael Biebl bi...@debian.org wrote: Sasa Ostrouska wrote: configure --with-distro=slackware \ --with-docs \ --with-dbus-sys=/etc/dbus-1/system.d \ --with-dhcp-client=dhcdbd \ ^ That doesn't look right, you either want dhclient or dhcpcd here Corrected it to be dhcpcd --with-pppd-plugin-dir=/etc/ppp/plugins \ ^ That is incorrect, too. pppd plugins are usually installed in /usr/lib/ppp/$ppp_version Corrected it to point to /usr/lib/pppd/2.4.4 --with-resolvconf=/etc/resolv.conf \ ^ Here, you should use the path to the resolvconf *binary*. I'm not sure if slackware supports resolvconf, so you probably don't want this configure option. You are wright about that, so I cut of that line. So here is another nm-serial3.txt file attached with the output I got after recompilling it with the right options. ... NetworkManager: info Activation (eth0) Stage 2 of 5 (Device Configure) complete. NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) started... NetworkManager: info (eth0): device state change: 5 - 7 NetworkManager: info Activation (eth0) Beginning DHCP transaction. eth0: dhcpcd 4.0.12 starting NetworkManager: info dhcpcd started with pid 15991 NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection :1.59 is not allowed to own the service org.freedesktop.nm_dhcp_client due to security policies in the configuration file eth0: broadcasting for a lease eth0: offered 192.168.1.104 from 192.168.1.1 eth0: acknowledged 192.168.1.104 from 192.168.1.1 eth0: checking 192.168.1.104 is available on attached networks eth0: leased 192.168.1.104 for 259200 seconds Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection :1.61 is not allowed to own the service org.freedesktop.nm_dhcp_client due to security policies in the configuration file NetworkManager: info Device 'eth0' DHCP transaction took too long (45s), stopping it. eth0: received SIGTERM, stopping Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection :1.62 is not allowed to own the service org.freedesktop.nm_dhcp_client due to security policies in the configuration file NetworkManager: info eth0: canceled DHCP transaction, dhcp client pid 15991 So, this looks much better now. As a next step, please make sure, the NetworkManager dbus policy files are installed in /etc/dbus-1/system.d/ and dbus is reloaded/restarted afterwards. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager issues with password storage on Ubuntu 8.10
On Wed, 2009-04-08 at 17:25 -0700, Harald Rudell wrote: Hello, using the nm-applet 0.7.0 and network manager 0.7, you may end up in a situation where each saved WPA password becomes garbled this can happen when 1. you delete the default key ~/.gnome2/keyrings/login.keyring, and gnome recreates it automatically 2. maybe when changing passwords 3. update Ubuntu to 8.10 symptom is: network manager tries to connect to wpa networks, and an entered password becomes a 64-character string (the password is garbled when nm tries to save it to the keyring) The passphrase gets hashed to the actual hex key, which is what's actually used to connect. However, that should be fine, because NM won't *rehash* it once it's already hashed. verify the issue after it occured: 1. in Gnome start nm-connection-editor from command line or right click nm-applet icon and select Edit connections 2. select Wireless tab, click Add, enter a in SSID field, select Wireless Security tab, select WPA personal security, enter password abcdefgh, click OK 3. select your created connection, click Edit, select Wireless Security tab, check Show Password BUG: the password is a 64 character string EXPECTED: the password abcdefgh Actually, the hashed password is currently expected. Since hashing is one-way, the passphrase is pretty much lost. Yes, I'd like to fix that because it confuses a heck of a lot of people. If the connection fails, is the hashed password shown in the box always the same, or does it keep changing? Dan cause: network manager has incorrect encryption data fix: unknown (it only applies to your login) get-around: edit the created key using: Applications-Accessories-Passwords, select passwords tab, select your connection, click properties, modify the password Could someone help with either how to get on the right side of network manager, or a way to troubleshoot this through pam libraries and what not. perhaps the fix is to reinstall network manager? Thanks in advance for any help H ___ 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: NM 0.7.0.100 and Slackware
On Thu, Apr 9, 2009 at 10:27 PM, Michael Biebl bi...@debian.org wrote: Sasa Ostrouska wrote: Dear Michael, Hi Sasa, please keep the mailing list in CC Hehe, didnt even know that I have mailed you directly :) sorry, will pay more attention on that :) On Thu, Apr 9, 2009 at 12:26 PM, Michael Biebl bi...@debian.org wrote: Sasa Ostrouska wrote: configure --with-distro=slackware \ --with-docs \ --with-dbus-sys=/etc/dbus-1/system.d \ --with-dhcp-client=dhcdbd \ ^ That doesn't look right, you either want dhclient or dhcpcd here Corrected it to be dhcpcd --with-pppd-plugin-dir=/etc/ppp/plugins \ ^ That is incorrect, too. pppd plugins are usually installed in /usr/lib/ppp/$ppp_version Corrected it to point to /usr/lib/pppd/2.4.4 --with-resolvconf=/etc/resolv.conf \ ^ Here, you should use the path to the resolvconf *binary*. I'm not sure if slackware supports resolvconf, so you probably don't want this configure option. You are wright about that, so I cut of that line. So here is another nm-serial3.txt file attached with the output I got after recompilling it with the right options. ... NetworkManager: info Activation (eth0) Stage 2 of 5 (Device Configure) complete. NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) started... NetworkManager: info (eth0): device state change: 5 - 7 NetworkManager: info Activation (eth0) Beginning DHCP transaction. eth0: dhcpcd 4.0.12 starting NetworkManager: info dhcpcd started with pid 15991 NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection :1.59 is not allowed to own the service org.freedesktop.nm_dhcp_client due to security policies in the configuration file eth0: broadcasting for a lease eth0: offered 192.168.1.104 from 192.168.1.1 eth0: acknowledged 192.168.1.104 from 192.168.1.1 eth0: checking 192.168.1.104 is available on attached networks eth0: leased 192.168.1.104 for 259200 seconds Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection :1.61 is not allowed to own the service org.freedesktop.nm_dhcp_client due to security policies in the configuration file NetworkManager: info Device 'eth0' DHCP transaction took too long (45s), stopping it. eth0: received SIGTERM, stopping Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection :1.62 is not allowed to own the service org.freedesktop.nm_dhcp_client due to security policies in the configuration file NetworkManager: info eth0: canceled DHCP transaction, dhcp client pid 15991 So, this looks much better now. Good to hear that. As a next step, please make sure, the NetworkManager dbus policy files are installed in /etc/dbus-1/system.d/ and dbus is reloaded/restarted afterwards. Michael Ok will check all that dbus stuff if it is in, from what I know it should be in, but its better to recheck twice. Another thing it makes me mad, is why every time I start NM it resets my hostname to localhost.localdomain After that is really impossible to do anything on the machine. Rgds Saxa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.7.0.100 and Slackware
On Thu, 2009-04-09 at 22:58 +0200, Sasa Ostrouska wrote: On Thu, Apr 9, 2009 at 10:27 PM, Michael Biebl bi...@debian.org wrote: Sasa Ostrouska wrote: Dear Michael, Hi Sasa, please keep the mailing list in CC Hehe, didnt even know that I have mailed you directly :) sorry, will pay more attention on that :) On Thu, Apr 9, 2009 at 12:26 PM, Michael Biebl bi...@debian.org wrote: Sasa Ostrouska wrote: configure --with-distro=slackware \ --with-docs \ --with-dbus-sys=/etc/dbus-1/system.d \ --with-dhcp-client=dhcdbd \ ^ That doesn't look right, you either want dhclient or dhcpcd here Corrected it to be dhcpcd --with-pppd-plugin-dir=/etc/ppp/plugins \ ^ That is incorrect, too. pppd plugins are usually installed in /usr/lib/ppp/$ppp_version Corrected it to point to /usr/lib/pppd/2.4.4 --with-resolvconf=/etc/resolv.conf \ ^ Here, you should use the path to the resolvconf *binary*. I'm not sure if slackware supports resolvconf, so you probably don't want this configure option. You are wright about that, so I cut of that line. So here is another nm-serial3.txt file attached with the output I got after recompilling it with the right options. ... NetworkManager: info Activation (eth0) Stage 2 of 5 (Device Configure) complete. NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) started... NetworkManager: info (eth0): device state change: 5 - 7 NetworkManager: info Activation (eth0) Beginning DHCP transaction. eth0: dhcpcd 4.0.12 starting NetworkManager: info dhcpcd started with pid 15991 NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection :1.59 is not allowed to own the service org.freedesktop.nm_dhcp_client due to security policies in the configuration file eth0: broadcasting for a lease eth0: offered 192.168.1.104 from 192.168.1.1 eth0: acknowledged 192.168.1.104 from 192.168.1.1 eth0: checking 192.168.1.104 is available on attached networks eth0: leased 192.168.1.104 for 259200 seconds Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection :1.61 is not allowed to own the service org.freedesktop.nm_dhcp_client due to security policies in the configuration file NetworkManager: info Device 'eth0' DHCP transaction took too long (45s), stopping it. eth0: received SIGTERM, stopping Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection :1.62 is not allowed to own the service org.freedesktop.nm_dhcp_client due to security policies in the configuration file NetworkManager: info eth0: canceled DHCP transaction, dhcp client pid 15991 So, this looks much better now. Good to hear that. As a next step, please make sure, the NetworkManager dbus policy files are installed in /etc/dbus-1/system.d/ and dbus is reloaded/restarted afterwards. Michael Ok will check all that dbus stuff if it is in, from what I know it should be in, but its better to recheck twice. Another thing it makes me mad, is why every time I start NM it resets my hostname to localhost.localdomain After that is really impossible to do anything on the machine. The next thing you want to do is write a Slackware system settings plugin that will read wherever Slackware stores the persistent hostname, and provide that hostname to NetworkManager. Then implement reading of the normal slackware network config scripts so NM can transparently use the existing system network config. That will make your problem here go away. The problem is that nothing is telling NM what your intended hostname should be. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.7.0.100 and Slackware
On Thu, Apr 9, 2009 at 11:14 PM, Dan Williams d...@redhat.com wrote: On Thu, 2009-04-09 at 22:58 +0200, Sasa Ostrouska wrote: On Thu, Apr 9, 2009 at 10:27 PM, Michael Biebl bi...@debian.org wrote: Sasa Ostrouska wrote: Dear Michael, Hi Sasa, please keep the mailing list in CC Hehe, didnt even know that I have mailed you directly :) sorry, will pay more attention on that :) On Thu, Apr 9, 2009 at 12:26 PM, Michael Biebl bi...@debian.org wrote: Sasa Ostrouska wrote: configure --with-distro=slackware \ --with-docs \ --with-dbus-sys=/etc/dbus-1/system.d \ --with-dhcp-client=dhcdbd \ ^ That doesn't look right, you either want dhclient or dhcpcd here Corrected it to be dhcpcd --with-pppd-plugin-dir=/etc/ppp/plugins \ ^ That is incorrect, too. pppd plugins are usually installed in /usr/lib/ppp/$ppp_version Corrected it to point to /usr/lib/pppd/2.4.4 --with-resolvconf=/etc/resolv.conf \ ^ Here, you should use the path to the resolvconf *binary*. I'm not sure if slackware supports resolvconf, so you probably don't want this configure option. You are wright about that, so I cut of that line. So here is another nm-serial3.txt file attached with the output I got after recompilling it with the right options. ... NetworkManager: info Activation (eth0) Stage 2 of 5 (Device Configure) complete. NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) started... NetworkManager: info (eth0): device state change: 5 - 7 NetworkManager: info Activation (eth0) Beginning DHCP transaction. eth0: dhcpcd 4.0.12 starting NetworkManager: info dhcpcd started with pid 15991 NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection :1.59 is not allowed to own the service org.freedesktop.nm_dhcp_client due to security policies in the configuration file eth0: broadcasting for a lease eth0: offered 192.168.1.104 from 192.168.1.1 eth0: acknowledged 192.168.1.104 from 192.168.1.1 eth0: checking 192.168.1.104 is available on attached networks eth0: leased 192.168.1.104 for 259200 seconds Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection :1.61 is not allowed to own the service org.freedesktop.nm_dhcp_client due to security policies in the configuration file NetworkManager: info Device 'eth0' DHCP transaction took too long (45s), stopping it. eth0: received SIGTERM, stopping Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection :1.62 is not allowed to own the service org.freedesktop.nm_dhcp_client due to security policies in the configuration file NetworkManager: info eth0: canceled DHCP transaction, dhcp client pid 15991 So, this looks much better now. Good to hear that. As a next step, please make sure, the NetworkManager dbus policy files are installed in /etc/dbus-1/system.d/ and dbus is reloaded/restarted afterwards. Michael Ok will check all that dbus stuff if it is in, from what I know it should be in, but its better to recheck twice. Another thing it makes me mad, is why every time I start NM it resets my hostname to localhost.localdomain After that is really impossible to do anything on the machine. The next thing you want to do is write a Slackware system settings plugin that will read wherever Slackware stores the persistent hostname, and provide that hostname to NetworkManager. Then implement reading of the normal slackware network config scripts so NM can transparently use the existing system network config. That will make your problem here go away. The problem is that nothing is telling NM what your intended hostname should be. Dan Dan ,that sounds great, but can somebody advise on where and how to begin ? Rgds Saxa ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.7.0.100 and Slackware
On Thu, Apr 9, 2009 at 11:21 PM, Sasa Ostrouska cas...@gmail.com wrote: On Thu, Apr 9, 2009 at 11:14 PM, Dan Williams d...@redhat.com wrote: On Thu, 2009-04-09 at 22:58 +0200, Sasa Ostrouska wrote: On Thu, Apr 9, 2009 at 10:27 PM, Michael Biebl bi...@debian.org wrote: Sasa Ostrouska wrote: Dear Michael, Hi Sasa, please keep the mailing list in CC Hehe, didnt even know that I have mailed you directly :) sorry, will pay more attention on that :) On Thu, Apr 9, 2009 at 12:26 PM, Michael Biebl bi...@debian.org wrote: Sasa Ostrouska wrote: configure --with-distro=slackware \ --with-docs \ --with-dbus-sys=/etc/dbus-1/system.d \ --with-dhcp-client=dhcdbd \ ^ That doesn't look right, you either want dhclient or dhcpcd here Corrected it to be dhcpcd --with-pppd-plugin-dir=/etc/ppp/plugins \ ^ That is incorrect, too. pppd plugins are usually installed in /usr/lib/ppp/$ppp_version Corrected it to point to /usr/lib/pppd/2.4.4 --with-resolvconf=/etc/resolv.conf \ ^ Here, you should use the path to the resolvconf *binary*. I'm not sure if slackware supports resolvconf, so you probably don't want this configure option. You are wright about that, so I cut of that line. So here is another nm-serial3.txt file attached with the output I got after recompilling it with the right options. ... NetworkManager: info Activation (eth0) Stage 2 of 5 (Device Configure) complete. NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) started... NetworkManager: info (eth0): device state change: 5 - 7 NetworkManager: info Activation (eth0) Beginning DHCP transaction. eth0: dhcpcd 4.0.12 starting NetworkManager: info dhcpcd started with pid 15991 NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection :1.59 is not allowed to own the service org.freedesktop.nm_dhcp_client due to security policies in the configuration file eth0: broadcasting for a lease eth0: offered 192.168.1.104 from 192.168.1.1 eth0: acknowledged 192.168.1.104 from 192.168.1.1 eth0: checking 192.168.1.104 is available on attached networks eth0: leased 192.168.1.104 for 259200 seconds Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection :1.61 is not allowed to own the service org.freedesktop.nm_dhcp_client due to security policies in the configuration file NetworkManager: info Device 'eth0' DHCP transaction took too long (45s), stopping it. eth0: received SIGTERM, stopping Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection :1.62 is not allowed to own the service org.freedesktop.nm_dhcp_client due to security policies in the configuration file NetworkManager: info eth0: canceled DHCP transaction, dhcp client pid 15991 So, this looks much better now. Good to hear that. As a next step, please make sure, the NetworkManager dbus policy files are installed in /etc/dbus-1/system.d/ and dbus is reloaded/restarted afterwards. Michael Ok will check all that dbus stuff if it is in, from what I know it should be in, but its better to recheck twice. Another thing it makes me mad, is why every time I start NM it resets my hostname to localhost.localdomain After that is really impossible to do anything on the machine. The next thing you want to do is write a Slackware system settings plugin that will read wherever Slackware stores the persistent hostname, and provide that hostname to NetworkManager. Then implement reading of the normal slackware network config scripts so NM can transparently use the existing system network config. That will make your problem here go away. The problem is that nothing is telling NM what your intended hostname should be. Dan Dan ,that sounds great, but can somebody advise on where and how to begin ? Rgds Saxa Ok I did some more testings and thats what I get now with wpa_supplicant started. Thats the contents of my /etc/dbus-1/system.d/ -rw-r--r-- 1 root root 4473 2009-04-03 01:53 /etc/dbus-1/system.d/ConsoleKit.conf -rw-r--r-- 1 root root 1183 2009-04-09 16:50 /etc/dbus-1/system.d/NetworkManager.conf -rw-r--r-- 1 root root 948 2009-03-19 06:40 /etc/dbus-1/system.d/avahi-dbus.conf -rw-r--r-- 1 root root 1131 2008-11-11 23:36 /etc/dbus-1/system.d/bluetooth.conf -rw-r--r-- 1 root root 460 2008-10-22 01:15 /etc/dbus-1/system.d/cups.conf -rw-r--r-- 1 root root 695 2008-04-02 22:25 /etc/dbus-1/system.d/dbus-wpa_supplicant.conf -rw-r--r-- 1 root root 589 2008-09-01 02:38 /etc/dbus-1/system.d/dhcdbd.conf -rw-r--r-- 1 root root 3891 2009-03-21 20:20 /etc/dbus-1/system.d/gdm.conf -rw-r--r-- 1 root root 2091 2008-12-08 02:14 /etc/dbus-1/system.d/hal.conf
Re: Novacom GNS-60IU - how to add support
Is ttyUSB0 the only port the modem provides? Any idea what exact kernel driver the modem uses? Driver is 100% = linux-2.6/drivers/usb/serial/cp210x.c Modem = USB-RS232 converter, it's a simple regular serial port style modem... After connecting modem in /dev I have following new files: drwxr-xr-x 2 root root3200 2009-04-10 01:31 char crw-rw-rw- 1 root tty 5, 2 2009-04-10 01:32 ptmx drwxr-xr-x 4 root root 80 2009-04-10 01:31 serial crw-rw 1 root dialout 188, 0 2009-04-10 01:31 ttyUSB0 crw-rw 1 root root252, 8 2009-04-10 01:31 usbdev2.5_ep00 crw-rw 1 root root252, 7 2009-04-10 01:31 usbdev2.5_ep01 crw-rw 1 root root252, 6 2009-04-10 01:31 usbdev2.5_ep81 And nothing more. Modem is working with /dev/ttyUSB0 100% Please, help me to add this modem to NetworkManager, I know there are many analogical modems (with files at /dev/ttyUSB*) and I can't understand why my modem is not working with NM... ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
policykit and networkmanager
While compiling NetworkManager I receive and error about not having policykit-dbus. when looking at policykit and pkgconfig. I noticed policykit 0.8 offers the correct values, but the latest policykit has changed it definitions: polkit-agent-1.pc polkit-backend-1.pc polkit-gobject-1.pc Is there a fix for this? (I'm concerned about downgrading policykit, since hal, etc.. were built with that version and definitions). regards, -- Justin P. Mattock ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
