Ubuntu 9.04 “Wired Network – device not managed”
by Craig Mayhew on Jun.13, 2009, under Guides/Fixes, Linux/Ubuntu
After upgrading to Ubuntu 9.04 I’ve found the network manager GUI to be far superior to the previous version I was using in Ubuntu 8.04 LTS. Unfortunately when I was using Ubuntu 8.04 I made some custom alterations to my network setup in the “/etc/network/interfaces” file. The Network Manager in 9.04 wasn’t keen on this and so refused to manage it, instead it displayed the message “Wired Network – device not managed”.
As a work around I commented out all of my changes by placing a # at the beginning of each line in my interfaces file:
Open the interfaces file in an editor:
sudo vim /etc/network/interfaces
This is an example of how my file looked before I modified it. Yours will be different:
auto lo iface lo inet loopback iface eth2 inet static address 192.168.0.44 netmask 255.255.255.0 gateway 192.168.0.1 auto eth2
And here’s the same file again, but I’ve added #’s at the beginning of each line so that they are ignored:
#auto lo #iface lo inet loopback #iface eth2 inet static #address 192.168.0.44 #netmask 255.255.255.0 #gateway 192.168.0.1 #auto eth2
In order for the changes to take effect, we need to restart the network manager and the applet by running each of these in the command line:
sudo /etc/init.d/networking restart
And now restart the network manager applet:
pkill nm-applet nm-applet
You should now be able to manage the network connection from within the network manager applet.
17 Comments for this entry
1 Trackback or Pingback for this entry
-
Karmic Koala | Chris Hanretty
November 10th, 2009 on 2:31 pm[...] worked perfectly, my ethernet didn’t autoconnect. I fixed it by following the steps at Craig Mayhew’s blog, but that shouldn’t be necessary: this was a fresh install after [...]
June 29th, 2009 on 3:23 pm
Thank you.It’s very useful.
July 5th, 2009 on 1:19 pm
I have same message “Wired Network – device not managed”, and I can’t manage the network connections.
I’ll try something else.
July 11th, 2009 on 7:22 pm
Yes, this also did not work for me. This isn’t really much of a fix, anyway.
July 12th, 2009 on 12:30 am
Hi Snake, Bondo,
Try changing [ifupdown] managed=false to true in /etc/NetworkManager/nm-system-settings.conf
July 13th, 2009 on 6:11 am
Hey!
Thanks for sharing the info… I had this problem and solved it…
cheers!
July 16th, 2009 on 4:11 am
This worked for me. I wonder if I go back now and uncomment if it will still work.
Note to self:::don’t try wicd because of Network Manager problems and then try to switch back when wicd sucks.
September 27th, 2009 on 10:02 am
It worked for me. But had to restart my pc for the settings to take effect. Restarting the network service didn’t do the job. Thanks buddy..
January 4th, 2010 on 3:25 pm
Thank you! This solution worked for me to (8.04LTS –> 9.04)! Found this post on google, I love finding troubleshooters in old blog posts..
January 4th, 2010 on 6:03 pm
Had the same problem but solved it by changing [ifupdown] managed=false to true in /etc/NetworkManager/nm-system-settings.conf
February 1st, 2010 on 2:39 am
Thank you. It works!
I have been bothered by the question for a long time. After reading your article, I was eagle to try it. It really works on my Ubuntu 9.10. Thanks again!
February 21st, 2010 on 8:19 pm
Thank you so much for this workaround! I’d been unable to connect to anything but my wireless network for the past year or so. This speeds things up tremendously.
February 28th, 2010 on 7:50 pm
Will they ever make the interfaces file and the nm-applet work in harmony? This is ridiculous.
March 29th, 2010 on 4:37 pm
If the above steps don’t work, try restarting the network manager.
sudo /etc/init.d/network-manager restart
May 2nd, 2010 on 2:10 pm
I think I was suffering from this problem because of a switch to wicd (and then back to Network Manager) in a vain attempt to fix a wireless network card problem.
Like Amul, I needed to restart the Network Manager before it worked – now it’s fine. Thanks!
May 24th, 2010 on 9:59 pm
It works but need to restart. Thanks! ;)
May 26th, 2010 on 12:19 pm
Hi, me again.
It works but if you have a server (for example apache). It desapears. Do you know how can i solve that? Thanks:
$ sudo /etc/init.d/apache2 restart
Restarting web server: apache2 … waiting .
$ sudo nmap localhost -PN
Starting Nmap 5.00 ( http://nmap.org ) at 2010-05-26 13:15 UTC
Warning: Hostname localhost resolves to 2 IPs. Using 127.0.0.1.
All 1000 scanned ports on localhost (127.0.0.1) are filtered
Nmap done: 1 IP address (1 host up) scanned in 201.37 seconds
Thanks
May 30th, 2010 on 10:15 pm
Hi, me again.
I’ve solved the previous problem.
Just comment all interfaces except loopback interface. You can also use that to establish the iptables rules. For example, my /etc/network/interfaces file:
auto lo
iface lo inet loopback
pre-up iptables-restore < /etc/iptables.rules
## The primary network interface
#allow-hotplug eth0
#iface eth0 inet dhcp
Now you can do ping to localhost or connect with your own localhost server.
Good luck and thanks!
Carlos