Re: netowork manager doesn't know it has connected
Does your system actually use DHCP or static IP?If DHCP, something isnot getting to NetworkManager.Be sure you have the correct 'dbus-send' magic at the top of the dhclient script (possiblyin /sbin/dhclient-script).The fact that NM is attempting to do autoiphere means that DHCP is clearly not succeeding, and that NM is told thatthe interface requires static IP configuration. Ah, great!This was the pointer I needed! Located dhclient-script in /etc/dhclient3 and tracked the problem down to a rogue whereami exit-hook script that broke the dhclient exit... Now works like a charm! Thanks! anze ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netowork manager doesn't know it has connected
On Sun, 2006-09-17 at 22:41 +0200, Anze Slosar wrote: Hi, I am using ubuntu dapper. On a fresh install I used network manager for a while, but since it didn't have a static IP, I went back to a home-cooked solution using whereami, ifplugd, etc. Now I wanted to go back to the network manager, and now it doesn't work any more... I just use a normal package, nothing fancy, no wpa, nothing just eth0 and ath0. Asked for help on ubuntu forums and no luck. Specifically, my problem is as follows: Below is what happens when I plug in the cable (i.e. not a wireless problem and not a hardware problem, the same thing happens with ath0). At the point where I added WORKING to the log, the eth0 network is up and running, I can connect to various sites, etc. Looks like system configured succesfully via DHCP. However, network manager still thinks it is down, the dots keep rotating in the applet, and after a while it times out and then it sets eth0 to some stupid default IP at which point I (of course) loose connectivity. Any ideas for debugging? I am really desperate... Does your system actually use DHCP or static IP? If DHCP, something is not getting to NetworkManager. Be sure you have the correct 'dbus-send' magic at the top of the dhclient script (possibly in /sbin/dhclient-script). The fact that NM is attempting to do autoip here means that DHCP is clearly not succeeding, and that NM is told that the interface requires static IP configuration. Dan [EMAIL PROTECTED]:/home/anze# NetworkManager --no-daemon NetworkManager: information starting... NetworkManager: WARNING main (): nm_data_new: Setting up dbus filter NetworkManager: information eth0: Device is fully-supported using driver 'e1000'. NetworkManager: information nm_device_init(): waiting for device's worker thread to start NetworkManager: information nm_device_init(): device's worker thread started, continuing. NetworkManager: information Now managing wired Ethernet (802.3) device 'eth0'. NetworkManager: information ath0: Device is fully-supported using driver 'ath_pci'. NetworkManager: information nm_device_init(): waiting for device's worker thread to start NetworkManager: information nm_device_init(): device's worker thread started, continuing. NetworkManager: information Now managing wireless (802.11) device 'ath0'. NetworkManager: information Updating allowed wireless network lists. NetworkManager: information match NetworkManager: information match NetworkManager: WARNING nm_dbus_get_networks_cb (): nm-dbus-nmi.c:522 (nm_dbus_get_networks_cb): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored.. NetworkManager: information match NetworkManager: information match NetworkManager: information match NetworkManager: information match NetworkManager: information match NetworkManager: information match NetworkManager: information Will activate wired connection 'eth0' because it now has a link. NetworkManager: information match NetworkManager: information match NetworkManager: information SWITCH: no current connection, found better connection 'eth0'. NetworkManager: information Will activate connection 'eth0'. NetworkManager: information Device eth0 activation scheduled... NetworkManager: information Activation (eth0) started... NetworkManager: information Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: information Activation (eth0) Stage 1 of 5 (Device Prepare) started... NetworkManager: information match NetworkManager: information Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: information Activation (eth0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: information Activation (eth0) Stage 2 of 5 (Device Configure) starting... NetworkManager: information Activation (eth0) Stage 2 of 5 (Device Configure) successful. NetworkManager: information Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. NetworkManager: information Activation (eth0) Stage 2 of 5 (Device Configure) complete. NetworkManager: information Activation (eth0) Stage 3 of 5 (IP Configure Start) started... NetworkManager: information match NetworkManager: information match NetworkManager: information Activation (eth0) Beginning DHCP transaction. NetworkManager: information Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. NetworkManager: information DHCP daemon state is now 12 (successfully started) for interface eth0 NetworkManager: information Old device 'eth0' activating, won't change. NetworkManager: information match NetworkManager: information Old device 'eth0' activating, won't change. **WORKING NetworkManager: information Device 'eth0' DHCP transaction took too long (45s), stopping it. NetworkManager: information Activation (eth0) Stage 4 of 5 (IP Configure Timeout) scheduled... NetworkManager: information DHCP daemon
netowork manager doesn't know it has connected
Hi, I am using ubuntu dapper. On a fresh install I used network manager for a while, but since it didn't have a static IP, I went back to a home-cooked solution using whereami, ifplugd, etc. Now I wanted to go back to the network manager, and now it doesn't work any more... I just use a normal package, nothing fancy, no wpa, nothing just eth0 and ath0. Asked for help on ubuntu forums and no luck. Specifically, my problem is as follows: Below is what happens when I plug in the cable (i.e. not a wireless problem and not a hardware problem, the same thing happens with ath0). At the point where I added WORKING to the log, the eth0 network is up and running, I can connect to various sites, etc. Looks like system configured succesfully via DHCP. However, network manager still thinks it is down, the dots keep rotating in the applet, and after a while it times out and then it sets eth0 to some stupid default IP at which point I (of course) loose connectivity. Any ideas for debugging? I am really desperate... [EMAIL PROTECTED]:/home/anze# NetworkManager --no-daemon NetworkManager: information starting... NetworkManager: WARNINGmain (): nm_data_new: Setting up dbus filter NetworkManager: information eth0: Device is fully-supported using driver 'e1000'. NetworkManager: information nm_device_init(): waiting for device's worker thread to start NetworkManager: information nm_device_init(): device's worker thread started, continuing. NetworkManager: information Now managing wired Ethernet (802.3) device 'eth0'. NetworkManager: information ath0: Device is fully-supported using driver 'ath_pci'. NetworkManager: information nm_device_init(): waiting for device's worker thread to start NetworkManager: information nm_device_init(): device's worker thread started, continuing. NetworkManager: information Now managing wireless (802.11) device 'ath0'. NetworkManager: information Updating allowed wireless network lists. NetworkManager: information match NetworkManager: information match NetworkManager: WARNING nm_dbus_get_networks_cb (): nm-dbus-nmi.c:522 (nm_dbus_get_networks_cb): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored.. NetworkManager: information match NetworkManager: information match NetworkManager: information match NetworkManager: information match NetworkManager: information match NetworkManager: information match NetworkManager: information Will activate wired connection 'eth0' because it now has a link. NetworkManager: information match NetworkManager: information match NetworkManager: information SWITCH: no current connection, found better connection 'eth0'. NetworkManager: information Will activate connection 'eth0'. NetworkManager: information Device eth0 activation scheduled... NetworkManager: information Activation (eth0) started... NetworkManager: information Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: information Activation (eth0) Stage 1 of 5 (Device Prepare) started... NetworkManager: information match NetworkManager: information Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: information Activation (eth0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: information Activation (eth0) Stage 2 of 5 (Device Configure) starting... NetworkManager: information Activation (eth0) Stage 2 of 5 (Device Configure) successful. NetworkManager: information Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. NetworkManager: information Activation (eth0) Stage 2 of 5 (Device Configure) complete. NetworkManager: information Activation (eth0) Stage 3 of 5 (IP Configure Start) started... NetworkManager: information match NetworkManager: information match NetworkManager: information Activation (eth0) Beginning DHCP transaction. NetworkManager: information Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. NetworkManager: information DHCP daemon state is now 12 (successfully started) for interface eth0 NetworkManager: information Old device 'eth0' activating, won't change. NetworkManager: information match NetworkManager: information Old device 'eth0' activating, won't change. **WORKING NetworkManager: information Device 'eth0' DHCP transaction took too long (45s), stopping it. NetworkManager: information Activation (eth0) Stage 4 of 5 (IP Configure Timeout) scheduled... NetworkManager: information DHCP daemon state is now 14 (normal exit) for interface eth0 NetworkManager: information DHCP daemon state is now 14 (normal exit) for interface eth0 NetworkManager: information Activation (eth0) Stage 4 of 5 (IP Configure Timeout) started... NetworkManager: information No DHCP reply received. Automatically obtaining IP via Zeroconf. NetworkManager: information autoip: Sending probe #0 for IP address 169.254.223.103. NetworkManager: information autoip:
Re: netowork manager doesn't know it has connected
Il giorno dom, 17/09/2006 alle 22.41 +0200, Anze Slosar ha scritto: just use a normal package, nothing fancy, no wpa, nothing just eth0 and ath0. Asked for help on ubuntu forums and no luck. Specifically, my problem is as follows: [snip...] The nm version in dapper doesn't work well if there are interfaces defined in the /etc/network/interfaces file. Can you check it and be sure that it contains just these lines? # The loopback network interface auto lo iface lo inet loopback If there are references to eth0 or other interfaces it won't work. That should work, just try it. Cheers, Alessandro ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netowork manager doesn't know it has connected
Hi, Thanks for you help, Alessandro, I should have mentioned that: yes, I did remove both eth0 and ath0 from /etc/network/interfaces - if you don't do that, Network manager simply ignores all these interfaces and does nothing (i think ubuntu has a patched version of network manager that takes all interfaces bar lo bar ones listed in etc/network/interfaces)... So, this is not the problem. anzeOn 9/17/06, Alessandro Gervaso [EMAIL PROTECTED] wrote: Il giorno dom, 17/09/2006 alle 22.41 +0200, Anze Slosar ha scritto:just use a normal package, nothing fancy, no wpa, nothing just eth0 and ath0. Asked for help on ubuntu forums and no luck. Specifically, my problem is as follows:[snip...]The nm version in dapper doesn't work well if there are interfacesdefined in the /etc/network/interfaces file.Can you check it and be sure that it contains just these lines? # The loopback network interfaceauto loiface lo inet loopbackIf there are references to eth0 or other interfaces it won't work.That should work, just try it.Cheers,Alessandro ___NetworkManager-list mailing listNetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list-- -- ... somebody would have remembered that rock beats scissors, scissorsbeats paper, and a few HK MP5A3s full of 9mm Hydroshok ammo and laser designators beats a bunch of punks with baseball bats. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
