Subversion NetworkManager not operational (for me).
Hi All, I am interested in getting the latest Subversion NetworkManager as the one distributed with Ubuntu 7.10 (NM version 0.6.5) does not yet show my WPA AP (CCMP) in the list of available wireless APs. I could connect to it via Other Wireless but I did not want to have to do this step every time. So, while at work today (where I am using wired ethernet), I decided to check out the latest svn sources and compile them. I used the following autogen line: ./autogen.sh --prefix=/usr --with-dbus-sys=/etc/dbus-1/system.d\ --with-wpa_supplicant=/sbin/wpa_supplicant\ --with-dhcdbd=/usr/sbin/dhcdbd --with-distro=debian This built fine and I also built the latest nm-applet. However, when I start NetworkManager is does not see any Wireless access points and cannot get a DHCP lease from the wired ethernet. Any assistance in getting this working will be greatly appreciated. I am suspecting a dbus problem. I will now provide some info: * Hardware - Dell Latitude D610, ipw2200 wireless and tg3 ethernet. * OS - Ubuntu 7.10 (kernel 2.6.22-14-generic) * nm-tool output : NetworkManager Tool State: disconnected - Device: eth0 Type: Wired Driver:tg3 Active:no HW Address:00:11:43:4C:BA:45 Capabilities: Supported: yes Carrier Detect: yes Speed: 100 Mb/s Wired Settings - Device: eth1 Type: 802.11 Wireless Driver:ipw2200 Active:no HW Address:00:12:F0:02:09:FB Capabilities: Supported: yes Wireless Settings WEP Encryption: yes WPA Encryption: yes WPA2 Encryption: yes Wireless Access Points * gconf /system/networking/connections eth0 is using autoconnect * /var/log/syslog: Nov 15 13:48:43 silverado NetworkManager: info SWITCH: no current connection, found better connection 'Auto Ethernet (eth0)'. Nov 15 13:48:43 silverado NetworkManager: info Activating device eth0 Nov 15 13:48:43 silverado NetworkManager: info Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... Nov 15 13:48:43 silverado NetworkManager: info Activation (eth0) Stage 1 of 5 (Device Prepare) started... Nov 15 13:48:43 silverado NetworkManager: info Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... Nov 15 13:48:43 silverado NetworkManager: info Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Nov 15 13:48:43 silverado NetworkManager: info Activation (eth0) Stage 2 of 5 (Device Configure) starting... Nov 15 13:48:43 silverado NetworkManager: info Activation (eth0) Stage 2 of 5 (Device Configure) successful. Nov 15 13:48:43 silverado NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. Nov 15 13:48:43 silverado NetworkManager: info Activation (eth0) Stage 2 of 5 (Device Configure) complete. Nov 15 13:48:43 silverado NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) started... Nov 15 13:48:43 silverado NetworkManager: info Activation (eth0) Beginning DHCP transaction. Nov 15 13:48:43 silverado dhclient: Internet Systems Consortium DHCP Client V3.0.5 Nov 15 13:48:43 silverado NetworkManager: info dhclient started with pid 6249 Nov 15 13:48:43 silverado dhclient: Copyright 2004-2006 Internet Systems Consortium. Nov 15 13:48:43 silverado NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Nov 15 13:48:43 silverado dhclient: All rights reserved. Nov 15 13:48:43 silverado dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Nov 15 13:48:43 silverado dhclient: Nov 15 13:48:43 silverado dhclient: Listening on LPF/eth0/00:11:43:4c:ba:45 Nov 15 13:48:43 silverado dhclient: Sending on LPF/eth0/00:11:43:4c:ba:45 Nov 15 13:48:43 silverado dhclient: Sending on Socket/fallback Nov 15 13:48:44 silverado dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 Nov 15 13:48:44 silverado dhclient: DHCPOFFER from 172.16.153.254 Nov 15 13:48:44 silverado dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Nov 15 13:48:44 silverado dhclient: DHCPACK from 172.16.153.254 Nov 15 13:48:44 silverado dhclient: bound to 172.16.153.34 -- renewal in 10895 seconds. Nov 15 13:48:44 silverado NetworkManager: info Trying to start the supplicant... Nov 15 13:49:14 silverado NetworkManager: info Trying to start the supplicant... Nov 15 13:49:28 silverado NetworkManager: info Device 'eth0' DHCP transaction took too long (45s), stopping it. Nov 15 13:49:28 silverado NetworkManager: info eth0: canceled DHCP transaction, dhclient pid 6249 Nov 15 13:49:28 silverado NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Timeout) scheduled... Nov 15 13:49:28 silverado NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Timeout) started... Nov 15 13:49:28 silverado NetworkManager: info No DHCP reply
Re: Subversion NetworkManager not operational (for me).
On Nov 15, 2007 3:47 PM, Fred Clausen [EMAIL PROTECTED] wrote: So, while at work today (where I am using wired ethernet), I decided to check out the latest svn sources and compile them. I used the following autogen line: ./autogen.sh --prefix=/usr --with-dbus-sys=/etc/dbus-1/system.d\ --with-wpa_supplicant=/sbin/wpa_supplicant\ --with-dhcdbd=/usr/sbin/dhcdbd --with-distro=debian There are no --with-wpa_supplicant and --with-dhcdbd configure flags anymore. This built fine and I also built the latest nm-applet. However, when I start NetworkManager is does not see any Wireless access points and cannot get a DHCP lease from the wired ethernet. You need wpa_supplicant = 0.5.8 built with dbus support (see if wpa_supplicant --help shows '-u' flag). NM doesn't try to start it so you'll either need to start it manually (as root, with -u) before running NM or use dbus 1.1.x which has system service activation. (For that to work, you'll need patches from fedora 8 wpa_supplicant package until Dan gets them upstream). Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Subversion NetworkManager not operational (for me).
Tambet Ingo wrote: Do you have a default script line in /etc/dhclient.conf? Something like: script /sbin/dhclient-script; If so, comment it out. dhclient doesn't let you override configuration values from command line if they are already defined in the configuration file - something that NM needs. Thanks for the tip. I did indeed have a dhclient.conf with some custom supercedes for resolv.conf so I moved away the whole config file but it still displayes the same symptoms (pasted at end). I am also pasting the output of nm-applet which I ran in the foreground. I suspect there may be some odd Ubuntu'ism that I am getting caught on, I have a Fedora 6 machine to test on as well but I will upgrade that to F8 before doing NetworkManager testing on it. Thanks, Fred. * NetworkManager log: Nov 15 16:36:42 silverado NetworkManager: info dhclient started with pid 28270 Nov 15 16:36:42 silverado NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Nov 15 16:36:42 silverado dhclient: Listening on LPF/eth0/00:11:43:4c:ba:45 Nov 15 16:36:42 silverado dhclient: Sending on LPF/eth0/00:11:43:4c:ba:45 Nov 15 16:36:42 silverado dhclient: Sending on Socket/fallback Nov 15 16:36:42 silverado dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 Nov 15 16:36:42 silverado dhclient: DHCPOFFER from 172.16.153.254 Nov 15 16:36:42 silverado dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Nov 15 16:36:42 silverado dhclient: DHCPACK from 172.16.153.254 Nov 15 16:36:42 silverado dhclient: bound to 172.16.153.34 -- renewal in 12167 seconds. Nov 15 16:36:46 silverado NetworkManager: info Trying to start the supplicant... Nov 15 16:36:46 silverado NetworkManager: WARN killswitch_getpower_reply(): Error getting killswitch power: Access type not supported. Nov 15 16:36:51 silverado kernel: [34733.76] eth1: no IPv6 routers present Nov 15 16:36:52 silverado NetworkManager: info Trying to start the supplicant... Nov 15 16:36:53 silverado kernel: [34735.148000] eth0: no IPv6 routers present Nov 15 16:36:58 silverado NetworkManager: info Trying to start the supplicant... Nov 15 16:37:27 silverado NetworkManager: info Device 'eth0' DHCP transaction took too long (45s), stopping it. Nov 15 16:37:27 silverado NetworkManager: info eth0: canceled DHCP transaction, dhclient pid 28270 Nov 15 16:37:27 silverado NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Timeout) scheduled... Nov 15 16:37:27 silverado NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Timeout) started... Nov 15 16:37:27 silverado NetworkManager: info No DHCP reply received. Automatically obtaining IP via Zeroconf. Nov 15 16:37:27 silverado NetworkManager: info autoip: Sending probe #0 for IP address 169.254.30.219. Nov 15 16:37:27 silverado NetworkManager: info autoip: Waiting for reply... Nov 15 16:37:29 silverado NetworkManager: info autoip: Sending probe #1 for IP address 169.254.30.219. Nov 15 16:37:29 silverado NetworkManager: info autoip: Waiting for reply... Nov 15 16:37:31 silverado NetworkManager: info autoip: Sending probe #2 for IP address 169.254.30.219. Nov 15 16:37:31 silverado NetworkManager: info autoip: Waiting for reply... Nov 15 16:37:33 silverado NetworkManager: info autoip: Sending announce #0 for IP address 169.254.30.219. Nov 15 16:37:33 silverado NetworkManager: info autoip: Waiting for reply... Nov 15 16:37:36 silverado NetworkManager: info autoip: Sending announce #1 for IP address 169.254.30.219. Nov 15 16:37:36 silverado NetworkManager: info autoip: Waiting for reply... Nov 15 16:37:39 silverado NetworkManager: info autoip: Sending announce #2 for IP address 169.254.30.219. Nov 15 16:37:39 silverado NetworkManager: info autoip: Waiting for reply... Nov 15 16:37:42 silverado NetworkManager: info Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... Nov 15 16:37:42 silverado NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Timeout) complete. Nov 15 16:37:42 silverado NetworkManager: info Trying to start the supplicant... Nov 15 16:37:42 silverado NetworkManager: info Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... Nov 15 16:37:43 silverado NetworkManager: info Activation (eth0) successful, device activated. Nov 15 16:37:43 silverado NetworkManager: info Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. Nov 15 16:37:48 silverado NetworkManager: info Trying to start the supplicant... Nov 15 16:37:54 silverado kernel: [34795.956000] eth0: no IPv6 routers present Nov 15 16:37:54 silverado NetworkManager: info Trying to start the supplicant... * nm-applet log: Nov 15 16:36:42 silverado NetworkManager: info dhclient started with pid 28270 Nov 15 16:36:42 silverado NetworkManager: info Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Nov 15 16:36:42 silverado dhclient: Listening on LPF/eth0/00:11:43:4c:ba:45 Nov 15 16:36:42 silverado dhclient:
Re: Subversion NetworkManager not operational (for me).
On Nov 15, 2007 5:10 PM, Fred Clausen [EMAIL PROTECTED] wrote: I have dbus 1.1.1 installed and my wpa_supplicant does support the -u flag. However, this still does not explain why the wired tg3 connection is not started. If you look at the logs, it even gets a DHCP lease but NM does not realise this for some reason. Any further suggestions to get wired ethernet working? Then I will work on solving the wireless problem. Do you have a default script line in /etc/dhclient.conf? Something like: script /sbin/dhclient-script; If so, comment it out. dhclient doesn't let you override configuration values from command line if they are already defined in the configuration file - something that NM needs. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Subversion NetworkManager not operational (for me).
Hi, Thanks for your reply. ./autogen.sh --prefix=/usr --with-dbus-sys=/etc/dbus-1/system.d\ --with-wpa_supplicant=/sbin/wpa_supplicant\ --with-dhcdbd=/usr/sbin/dhcdbd --with-distro=debian There are no --with-wpa_supplicant and --with-dhcdbd configure flags anymore. I have recompiled without these options. You need wpa_supplicant = 0.5.8 built with dbus support (see if wpa_supplicant --help shows '-u' flag). NM doesn't try to start it so you'll either need to start it manually (as root, with -u) before running NM or use dbus 1.1.x which has system service activation. (For that to work, you'll need patches from fedora 8 wpa_supplicant package until Dan gets them upstream). I have dbus 1.1.1 installed and my wpa_supplicant does support the -u flag. However, this still does not explain why the wired tg3 connection is not started. If you look at the logs, it even gets a DHCP lease but NM does not realise this for some reason. Any further suggestions to get wired ethernet working? Then I will work on solving the wireless problem. Thanks again, Fred. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
