Ubuntu 9.04 Network manager won't re-enable eth0 if router restarted
 

I have a problem with Network manager in ubuntu 9.04

If the router restarted for any reason Network manager won't enable eth0 automatically after the router is up again. I have to click on the Network manager icon and enable eth0 manually each time that happens. Is there a way to fix this??

Remove Network-Manager and replace it with wicd.

sudo apt-get remove network-manager network-manager-gnome
sudo apt-get install wicd

in wicd check the box in the interface config for automatically reconnect.

Isn't there anyway to get gnome Network manager re-enable it rather than using wicd instead?

Thanks anyway. I will use that if i didn't find any other way.

Not that I've ever found.. network-manager is junk imho.. it doesn't play well with anything and only manages the basics.
wicd is more functional, but that's just my opinion.

Auto reconnect is a simple check box in wicd, I helped someone with this exact same issue a week or so ago, and he was ecstatic about it working exactly like he wanted. After switching to wicd, his router rebooted and the NIC reconnected automatically

It's not like you couldn't switch back easy enough if it doesn't work out for you.

I have removed Network manager and stucked with no connection for half an hour. LoL
I used dhcpclient to get it back. I tried manually setting it up using ifconfig and route but failed. Now I will install wicd. Hope it goes well. :)

Ok. I installed it. What should I do now??

Of course, you can remove network-manager completely and just edit /etc/network/interfaces.

But how can I use wicd??

I thought it was rather intuitive, and self explanatory.. maybe not... heres a couple articles that briefly explain how to use it..

http://ubuntulinuxhelp.com/is-your-l...k-wicd-wicked/

http://www.linux.com/archive/feature/118224

http://www.linuxplanet.com/linuxplan...orials/6527/1/

and of course the home page.. http://wicd.sourceforge.net/

Sorry, I have checked the links and searched a bit as well. I still have a problem. One of the links said to log out and log back in and it should be started but didn't happen. When i try to open the wcid-client from a terminal that's what I get:

Traceback (most recent call last):
File "/usr/share/wicd/wicd-client.py", line 50, in <module>
import wicd.gui as gui
File "/usr/share/wicd/wicd/gui.py", line 2005, in <module>
setup_dbus()
File "/usr/share/wicd/wicd/gui.py", line 177, in setup_dbus
proxy_obj = bus.get_object("org.wicd.daemon", '/org/wicd/daemon')
File "/var/lib/python-support/python2.6/dbus/bus.py", line 244, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/var/lib/python-support/python2.6/dbus/proxies.py", line 241, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/var/lib/python-support/python2.6/dbus/bus.py", line 183, in activate_name_er
self.start_service_by_name(bus_name)
File "/var/lib/python-support/python2.6/dbus/bus.py", line 281, in start_service_by_name
'su', (bus_name, flags)))
File "/var/lib/python-support/python2.6/dbus/connection.py", line 622, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.wicd.daemon was not provided by any .service files

On my search some ppl said to make sure wcid deamon is started. I started it by /etc/init.d/wcid start. And it started fine. but still the same problem.

Also someone else said to delete /var/log/wcid/ folder and restart the wcid daemon. And i did that but still stuck with the same error. Any help would be appreciated. Thanks farslayer for ur help. :)

wow all I had tro do to install it on Debian was

aptitude remove network-manager network-manager-gnome
aptitude install wicd

and I was done... the daemon was started, Fired up the Gui and configured it.. I have a hard time believing it's more difficult on Ubuntu :(

Nope Nope. I found it. I only had to restart. I read that logging out and logging back in is enough in some other thread. !! but it wasn't LoL

btw wicd is great. I love it. Thanks a lot man. :)

Ahh, so you probably could have started the daemon manually then...

sudo /etc/init.d/wicd start

just for future reference. Glad to hear you are up and running.

Nope. I tried to start it manually and even logged out and came back on. but didn't work till I restarted. It's weird cause usually u don't have to restart linux to run any daemons. :s

Yes, but I guess you need to modprobe some module first. On a system that is already running, that would have to be done manually.