network manager says “device not managed”
I used to be able to share my network connection by editing the Auto Eth0 to share with other computers in the Ipv4 section and now I upgraded my laptop to 11.10 .
Now are there no wired connections in the network manager. When I click my connections applet at the top of the tray it also says wired device not managed
!
when I type ifconfig -a
daniella@daniella-1001HA:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 90:e6:ba:83:d6:fc
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:45
eth0:avahi Link encap:Ethernet HWaddr 90:e6:ba:83:d6:fc
inet addr:169.254.13.40 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:45
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wlan0 Link encap:Ethernet HWaddr 00:25:d3:90:43:41
inet addr:192.168.0.6 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::225:d3ff:fe90:4341/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12881 errors:0 dropped:0 overruns:0 frame:0
TX packets:12867 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8851081 (8.8 MB) TX bytes:2343199 (2.3 MB)
network-manager
add a comment |
I used to be able to share my network connection by editing the Auto Eth0 to share with other computers in the Ipv4 section and now I upgraded my laptop to 11.10 .
Now are there no wired connections in the network manager. When I click my connections applet at the top of the tray it also says wired device not managed
!
when I type ifconfig -a
daniella@daniella-1001HA:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 90:e6:ba:83:d6:fc
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:45
eth0:avahi Link encap:Ethernet HWaddr 90:e6:ba:83:d6:fc
inet addr:169.254.13.40 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:45
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wlan0 Link encap:Ethernet HWaddr 00:25:d3:90:43:41
inet addr:192.168.0.6 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::225:d3ff:fe90:4341/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12881 errors:0 dropped:0 overruns:0 frame:0
TX packets:12867 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8851081 (8.8 MB) TX bytes:2343199 (2.3 MB)
network-manager
3
The following answer from a similar question resolved this issue for me: askubuntu.com/a/893614/321971
– Edward Moffett
Apr 21 '17 at 22:56
@EdwardMoffett thanks! Adding the empty file named "10-globally-managed-devices.conf" to the directory "/etc/NetworkManager/conf.d/" fixed it for me!
– dontbyteme
Sep 21 '17 at 8:12
add a comment |
I used to be able to share my network connection by editing the Auto Eth0 to share with other computers in the Ipv4 section and now I upgraded my laptop to 11.10 .
Now are there no wired connections in the network manager. When I click my connections applet at the top of the tray it also says wired device not managed
!
when I type ifconfig -a
daniella@daniella-1001HA:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 90:e6:ba:83:d6:fc
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:45
eth0:avahi Link encap:Ethernet HWaddr 90:e6:ba:83:d6:fc
inet addr:169.254.13.40 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:45
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wlan0 Link encap:Ethernet HWaddr 00:25:d3:90:43:41
inet addr:192.168.0.6 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::225:d3ff:fe90:4341/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12881 errors:0 dropped:0 overruns:0 frame:0
TX packets:12867 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8851081 (8.8 MB) TX bytes:2343199 (2.3 MB)
network-manager
I used to be able to share my network connection by editing the Auto Eth0 to share with other computers in the Ipv4 section and now I upgraded my laptop to 11.10 .
Now are there no wired connections in the network manager. When I click my connections applet at the top of the tray it also says wired device not managed
!
when I type ifconfig -a
daniella@daniella-1001HA:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 90:e6:ba:83:d6:fc
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:45
eth0:avahi Link encap:Ethernet HWaddr 90:e6:ba:83:d6:fc
inet addr:169.254.13.40 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:45
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wlan0 Link encap:Ethernet HWaddr 00:25:d3:90:43:41
inet addr:192.168.0.6 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::225:d3ff:fe90:4341/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12881 errors:0 dropped:0 overruns:0 frame:0
TX packets:12867 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8851081 (8.8 MB) TX bytes:2343199 (2.3 MB)
network-manager
network-manager
edited Apr 26 '14 at 18:26
Braiam
52.3k20137223
52.3k20137223
asked Oct 23 '11 at 20:44
Daniella GloverDaniella Glover
758268
758268
3
The following answer from a similar question resolved this issue for me: askubuntu.com/a/893614/321971
– Edward Moffett
Apr 21 '17 at 22:56
@EdwardMoffett thanks! Adding the empty file named "10-globally-managed-devices.conf" to the directory "/etc/NetworkManager/conf.d/" fixed it for me!
– dontbyteme
Sep 21 '17 at 8:12
add a comment |
3
The following answer from a similar question resolved this issue for me: askubuntu.com/a/893614/321971
– Edward Moffett
Apr 21 '17 at 22:56
@EdwardMoffett thanks! Adding the empty file named "10-globally-managed-devices.conf" to the directory "/etc/NetworkManager/conf.d/" fixed it for me!
– dontbyteme
Sep 21 '17 at 8:12
3
3
The following answer from a similar question resolved this issue for me: askubuntu.com/a/893614/321971
– Edward Moffett
Apr 21 '17 at 22:56
The following answer from a similar question resolved this issue for me: askubuntu.com/a/893614/321971
– Edward Moffett
Apr 21 '17 at 22:56
@EdwardMoffett thanks! Adding the empty file named "10-globally-managed-devices.conf" to the directory "/etc/NetworkManager/conf.d/" fixed it for me!
– dontbyteme
Sep 21 '17 at 8:12
@EdwardMoffett thanks! Adding the empty file named "10-globally-managed-devices.conf" to the directory "/etc/NetworkManager/conf.d/" fixed it for me!
– dontbyteme
Sep 21 '17 at 8:12
add a comment |
11 Answers
11
active
oldest
votes
wired device not managed
Most probably your interface appears in /etc/network/interfaces. By default, NetworkManager does not manage interfaces that appear in /etc/network/interfaces. You can change this behaviour.
To do this - in a terminal:
sudo nano /etc/NetworkManager/NetworkManager.conf
change the line managed=false to managed=true
Save, stop and start network manager:
sudo service network-manager restart
Alternatively, you can remove the interface from /etc/network/interfaces.
backup the current interfaces file:
sudo cp /etc/network/interfaces /etc/network_interfaces_backup
Then open the file:
sudo nano /etc/network/interfaces
Delete everything in that file and copy and paste the following:
auto lo
iface lo inet loopback
Save, stop and start network manager:
sudo service network-manager restart
Double check in network manager (click on the indicator) that you have Enabled Networking ticked and you should also force deletion of old "wired connections" and selecting the new wired connection shown in the network manager indicator.
1
Glad to hear it's working. But you also might check out wicd if you have more network troubles. It's in the repo, but you prolly need to dosudo service network-manager stop
for wicd to work properly
– Matt
Oct 24 '11 at 5:29
2
I like the "alternative" method better because it allows you to later edit the network connection from network manager's UI, to specify additional nameservers, DHCP client ID, and 802.1x security settings, etc...
– Simón
May 23 '14 at 23:56
Thank you! but i needed to execute <code> sudo service networking restart </code> to make your explanation work.
– eifersucht
Nov 22 '16 at 9:19
I tried all this, but the second option in askubuntu.com/a/882812/682596 is what for fixed it for me.
– Roel
Jan 12 '18 at 23:30
NetworkManager also has the option to specifyunmanaged
devices, commenting out that also works
– Wilf
Sep 11 '18 at 20:54
add a comment |
wired device not managed
I had the same problem with a fresh install on my Asus Eee PC 1005HA. The live environment worked with no problems, but once installed I couldn't get the connection to respond or to not read "device not managed". When I changed the text in this configuration file and restarted Network Manager everything worked!
gksudo gedit /etc/NetworkManager/NetworkManager.conf
for lubuntu:
gksudo leafpad /etc/NetworkManager/NetworkManager.conf
Now the text editor will open. Find the line managed=false
and replace false with true and save the file (ctrl+s) and close the file.
Restart your computer or the NetworkManager service (sudo service network-manager restart
).
add a comment |
wireless device not managed
I've also found this issue after installing the Ubuntu 11.10 alternate version.
In my case, the /etc/network/interfaces
was configured during installation to download new packages, and the conflict arose after the NetworkManager was set up during the first session.
The solution I've found was commenting the lines related to the wlan interface in the /etc/network/interfaces
(in console, sudo vim /etc/network/interfaces
or your editor of choice):
# The primary network interface
#auto wlan0
#iface wlan0 inet dhcp
# wpa-ssid [your_ssid]
# wpa-psk [your_wpa_password]
And then, as Joseph VanPelt proposed, set managed=false
in the /etc/NetworkManager/NetworkManager.conf
and running sudo service network-manager restart
.
Excellent! This worked for me on an Eee PC 701.
– oKtosiTe
Dec 10 '11 at 17:00
2
Setting managed= is unnecessary (unless it's meant to revert a prior change).
– Mathieu Trudel-Lapierre
Apr 13 '12 at 17:42
For me, setting managed=true is what solved it eventually. It did not work with managed=false.
– Daniel Hershcovich
Jun 29 '12 at 18:51
add a comment |
wired device not managed
This is a simple command which does the same as the accepted answer non-interactively.
Run this command in a Terminal to use it:
sudo sed -i 's/^managed=false/managed=true/' /etc/NetworkManager/NetworkManager.conf
You may have to restart the network manager afterwards with this command:
sudo service network-manager restart
add a comment |
Situation like this may appear, when one runs pppoeconf
or something similar and the command overwrites the setting saved by NetworkManager. Even though the device seems to be working properly, Network Manager shows device status to be unmanaged.
If this a normal user's pc with simple network configuration like connecting via DHCP and automatic configuration, simply out comment the lines and restart network manager.
$ sudo restart network-manager
If situations other than these, please explain.
add a comment |
I had the same problem, I solved it by commenting the lines where the unmanaged device was mentioned, by mac address, in /etc/NetworkManager/NetworkManager.conf
.
[main]
plugins=ifupdown,keyfile
dns=dnsmasq
[ifupdown]
managed=false
[keyfile]
unmanaged-devices=mac:00:26:2d:fd:5c:e0
changed to
[main]
plugins=ifupdown,keyfile
dns=dnsmasq
[ifupdown]
managed=false
#[keyfile]
#unmanaged-devices=mac:00:26:2d:fd:5c:e0
add a comment |
None of the given solutions worked for me. I was having this problem on an Ubuntu 16.04 machine I hadn't booted in a long time. After some more searching this command is what worked for me.
sudo touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf
Thank you! Your solution worked for me on 18.04.
– Carlos López-Camey
Oct 4 '18 at 19:42
Thank you !!! I spent like two hours on this before finally finding your solution. Works as of 18.10.
– max
Oct 28 '18 at 9:46
add a comment |
There are two ways to manage network connections. You either have to do everything thru the network manager and remove everything Except the Loopback entry in /etc/network/interfaces
auto lo
iface lo inet loopback
or totally remove the network manager thru the package manager or terminal and use the /etc/network/interfaces and /etc/resolve.conf file to control your connections. If not you will see the error you are getting. Even with static IP I've found that the network manager makes things easy and you can configure your IPV4 connections thru the menu.
please put all of that answer into a newbie answer and I dont get any of it :( I just want it to work nothing works!
– Daniella Glover
Oct 23 '11 at 22:59
there is no Auto eth0 in the menu its blank! how can I edit anything if it isnt there! I need a useful answer!
– Daniella Glover
Oct 23 '11 at 23:01
add a comment |
Just to add a non-default answer, this can also happen if your computer has a hardware ON/OFF switch for the Wi-Fi interface. If you have such a "killswitch", ensure that you haven't accidentally turned the interface off
add a comment |
In 11.10 you can go to System Settings and you should see a Network Icon. Run that utility and you should see tabs for your network devices, wired and wireless. Each tab has a slider that allows you to switch the device off. Or in your case switch eth0 or wired connection 1, as it is now called, on. May be. At least check that it not switched to off.
regards.
sorry but its a no go, there is no slider. I suggest you look at my screenshot. no slider there and I repeat there is nothing in the wired connections tab in my network manager. :(
– Daniella Glover
Oct 23 '11 at 21:59
add a comment |
wireless device not managed
This is because the alternate images were for a period of time, configuring the wireless networks in /etc/network/interfaces; which causes NetworkManager to, on purpose, ignore the interface and consider them online.
A good solution if you want to simply use your wireless connection (or wired) with DHCP is to comment out these settings in /etc/network/interfaces for all interfaces except lo, and reboot your system or restart NetworkManager like so:
sudo restart network-manager
Of course, this means you will need to enter your wireless settings into NetworkManager (password, etc) after clicking on the right item from the applet menu.
add a comment |
protected by Community♦ Dec 30 '15 at 5:58
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
11 Answers
11
active
oldest
votes
11 Answers
11
active
oldest
votes
active
oldest
votes
active
oldest
votes
wired device not managed
Most probably your interface appears in /etc/network/interfaces. By default, NetworkManager does not manage interfaces that appear in /etc/network/interfaces. You can change this behaviour.
To do this - in a terminal:
sudo nano /etc/NetworkManager/NetworkManager.conf
change the line managed=false to managed=true
Save, stop and start network manager:
sudo service network-manager restart
Alternatively, you can remove the interface from /etc/network/interfaces.
backup the current interfaces file:
sudo cp /etc/network/interfaces /etc/network_interfaces_backup
Then open the file:
sudo nano /etc/network/interfaces
Delete everything in that file and copy and paste the following:
auto lo
iface lo inet loopback
Save, stop and start network manager:
sudo service network-manager restart
Double check in network manager (click on the indicator) that you have Enabled Networking ticked and you should also force deletion of old "wired connections" and selecting the new wired connection shown in the network manager indicator.
1
Glad to hear it's working. But you also might check out wicd if you have more network troubles. It's in the repo, but you prolly need to dosudo service network-manager stop
for wicd to work properly
– Matt
Oct 24 '11 at 5:29
2
I like the "alternative" method better because it allows you to later edit the network connection from network manager's UI, to specify additional nameservers, DHCP client ID, and 802.1x security settings, etc...
– Simón
May 23 '14 at 23:56
Thank you! but i needed to execute <code> sudo service networking restart </code> to make your explanation work.
– eifersucht
Nov 22 '16 at 9:19
I tried all this, but the second option in askubuntu.com/a/882812/682596 is what for fixed it for me.
– Roel
Jan 12 '18 at 23:30
NetworkManager also has the option to specifyunmanaged
devices, commenting out that also works
– Wilf
Sep 11 '18 at 20:54
add a comment |
wired device not managed
Most probably your interface appears in /etc/network/interfaces. By default, NetworkManager does not manage interfaces that appear in /etc/network/interfaces. You can change this behaviour.
To do this - in a terminal:
sudo nano /etc/NetworkManager/NetworkManager.conf
change the line managed=false to managed=true
Save, stop and start network manager:
sudo service network-manager restart
Alternatively, you can remove the interface from /etc/network/interfaces.
backup the current interfaces file:
sudo cp /etc/network/interfaces /etc/network_interfaces_backup
Then open the file:
sudo nano /etc/network/interfaces
Delete everything in that file and copy and paste the following:
auto lo
iface lo inet loopback
Save, stop and start network manager:
sudo service network-manager restart
Double check in network manager (click on the indicator) that you have Enabled Networking ticked and you should also force deletion of old "wired connections" and selecting the new wired connection shown in the network manager indicator.
1
Glad to hear it's working. But you also might check out wicd if you have more network troubles. It's in the repo, but you prolly need to dosudo service network-manager stop
for wicd to work properly
– Matt
Oct 24 '11 at 5:29
2
I like the "alternative" method better because it allows you to later edit the network connection from network manager's UI, to specify additional nameservers, DHCP client ID, and 802.1x security settings, etc...
– Simón
May 23 '14 at 23:56
Thank you! but i needed to execute <code> sudo service networking restart </code> to make your explanation work.
– eifersucht
Nov 22 '16 at 9:19
I tried all this, but the second option in askubuntu.com/a/882812/682596 is what for fixed it for me.
– Roel
Jan 12 '18 at 23:30
NetworkManager also has the option to specifyunmanaged
devices, commenting out that also works
– Wilf
Sep 11 '18 at 20:54
add a comment |
wired device not managed
Most probably your interface appears in /etc/network/interfaces. By default, NetworkManager does not manage interfaces that appear in /etc/network/interfaces. You can change this behaviour.
To do this - in a terminal:
sudo nano /etc/NetworkManager/NetworkManager.conf
change the line managed=false to managed=true
Save, stop and start network manager:
sudo service network-manager restart
Alternatively, you can remove the interface from /etc/network/interfaces.
backup the current interfaces file:
sudo cp /etc/network/interfaces /etc/network_interfaces_backup
Then open the file:
sudo nano /etc/network/interfaces
Delete everything in that file and copy and paste the following:
auto lo
iface lo inet loopback
Save, stop and start network manager:
sudo service network-manager restart
Double check in network manager (click on the indicator) that you have Enabled Networking ticked and you should also force deletion of old "wired connections" and selecting the new wired connection shown in the network manager indicator.
wired device not managed
Most probably your interface appears in /etc/network/interfaces. By default, NetworkManager does not manage interfaces that appear in /etc/network/interfaces. You can change this behaviour.
To do this - in a terminal:
sudo nano /etc/NetworkManager/NetworkManager.conf
change the line managed=false to managed=true
Save, stop and start network manager:
sudo service network-manager restart
Alternatively, you can remove the interface from /etc/network/interfaces.
backup the current interfaces file:
sudo cp /etc/network/interfaces /etc/network_interfaces_backup
Then open the file:
sudo nano /etc/network/interfaces
Delete everything in that file and copy and paste the following:
auto lo
iface lo inet loopback
Save, stop and start network manager:
sudo service network-manager restart
Double check in network manager (click on the indicator) that you have Enabled Networking ticked and you should also force deletion of old "wired connections" and selecting the new wired connection shown in the network manager indicator.
edited May 20 '12 at 11:18
answered Oct 23 '11 at 23:01
fossfreedom♦fossfreedom
150k37328373
150k37328373
1
Glad to hear it's working. But you also might check out wicd if you have more network troubles. It's in the repo, but you prolly need to dosudo service network-manager stop
for wicd to work properly
– Matt
Oct 24 '11 at 5:29
2
I like the "alternative" method better because it allows you to later edit the network connection from network manager's UI, to specify additional nameservers, DHCP client ID, and 802.1x security settings, etc...
– Simón
May 23 '14 at 23:56
Thank you! but i needed to execute <code> sudo service networking restart </code> to make your explanation work.
– eifersucht
Nov 22 '16 at 9:19
I tried all this, but the second option in askubuntu.com/a/882812/682596 is what for fixed it for me.
– Roel
Jan 12 '18 at 23:30
NetworkManager also has the option to specifyunmanaged
devices, commenting out that also works
– Wilf
Sep 11 '18 at 20:54
add a comment |
1
Glad to hear it's working. But you also might check out wicd if you have more network troubles. It's in the repo, but you prolly need to dosudo service network-manager stop
for wicd to work properly
– Matt
Oct 24 '11 at 5:29
2
I like the "alternative" method better because it allows you to later edit the network connection from network manager's UI, to specify additional nameservers, DHCP client ID, and 802.1x security settings, etc...
– Simón
May 23 '14 at 23:56
Thank you! but i needed to execute <code> sudo service networking restart </code> to make your explanation work.
– eifersucht
Nov 22 '16 at 9:19
I tried all this, but the second option in askubuntu.com/a/882812/682596 is what for fixed it for me.
– Roel
Jan 12 '18 at 23:30
NetworkManager also has the option to specifyunmanaged
devices, commenting out that also works
– Wilf
Sep 11 '18 at 20:54
1
1
Glad to hear it's working. But you also might check out wicd if you have more network troubles. It's in the repo, but you prolly need to do
sudo service network-manager stop
for wicd to work properly– Matt
Oct 24 '11 at 5:29
Glad to hear it's working. But you also might check out wicd if you have more network troubles. It's in the repo, but you prolly need to do
sudo service network-manager stop
for wicd to work properly– Matt
Oct 24 '11 at 5:29
2
2
I like the "alternative" method better because it allows you to later edit the network connection from network manager's UI, to specify additional nameservers, DHCP client ID, and 802.1x security settings, etc...
– Simón
May 23 '14 at 23:56
I like the "alternative" method better because it allows you to later edit the network connection from network manager's UI, to specify additional nameservers, DHCP client ID, and 802.1x security settings, etc...
– Simón
May 23 '14 at 23:56
Thank you! but i needed to execute <code> sudo service networking restart </code> to make your explanation work.
– eifersucht
Nov 22 '16 at 9:19
Thank you! but i needed to execute <code> sudo service networking restart </code> to make your explanation work.
– eifersucht
Nov 22 '16 at 9:19
I tried all this, but the second option in askubuntu.com/a/882812/682596 is what for fixed it for me.
– Roel
Jan 12 '18 at 23:30
I tried all this, but the second option in askubuntu.com/a/882812/682596 is what for fixed it for me.
– Roel
Jan 12 '18 at 23:30
NetworkManager also has the option to specify
unmanaged
devices, commenting out that also works– Wilf
Sep 11 '18 at 20:54
NetworkManager also has the option to specify
unmanaged
devices, commenting out that also works– Wilf
Sep 11 '18 at 20:54
add a comment |
wired device not managed
I had the same problem with a fresh install on my Asus Eee PC 1005HA. The live environment worked with no problems, but once installed I couldn't get the connection to respond or to not read "device not managed". When I changed the text in this configuration file and restarted Network Manager everything worked!
gksudo gedit /etc/NetworkManager/NetworkManager.conf
for lubuntu:
gksudo leafpad /etc/NetworkManager/NetworkManager.conf
Now the text editor will open. Find the line managed=false
and replace false with true and save the file (ctrl+s) and close the file.
Restart your computer or the NetworkManager service (sudo service network-manager restart
).
add a comment |
wired device not managed
I had the same problem with a fresh install on my Asus Eee PC 1005HA. The live environment worked with no problems, but once installed I couldn't get the connection to respond or to not read "device not managed". When I changed the text in this configuration file and restarted Network Manager everything worked!
gksudo gedit /etc/NetworkManager/NetworkManager.conf
for lubuntu:
gksudo leafpad /etc/NetworkManager/NetworkManager.conf
Now the text editor will open. Find the line managed=false
and replace false with true and save the file (ctrl+s) and close the file.
Restart your computer or the NetworkManager service (sudo service network-manager restart
).
add a comment |
wired device not managed
I had the same problem with a fresh install on my Asus Eee PC 1005HA. The live environment worked with no problems, but once installed I couldn't get the connection to respond or to not read "device not managed". When I changed the text in this configuration file and restarted Network Manager everything worked!
gksudo gedit /etc/NetworkManager/NetworkManager.conf
for lubuntu:
gksudo leafpad /etc/NetworkManager/NetworkManager.conf
Now the text editor will open. Find the line managed=false
and replace false with true and save the file (ctrl+s) and close the file.
Restart your computer or the NetworkManager service (sudo service network-manager restart
).
wired device not managed
I had the same problem with a fresh install on my Asus Eee PC 1005HA. The live environment worked with no problems, but once installed I couldn't get the connection to respond or to not read "device not managed". When I changed the text in this configuration file and restarted Network Manager everything worked!
gksudo gedit /etc/NetworkManager/NetworkManager.conf
for lubuntu:
gksudo leafpad /etc/NetworkManager/NetworkManager.conf
Now the text editor will open. Find the line managed=false
and replace false with true and save the file (ctrl+s) and close the file.
Restart your computer or the NetworkManager service (sudo service network-manager restart
).
edited May 20 '12 at 11:18
fossfreedom♦
150k37328373
150k37328373
answered Oct 21 '11 at 21:29
Joseph VanPeltJoseph VanPelt
1412
1412
add a comment |
add a comment |
wireless device not managed
I've also found this issue after installing the Ubuntu 11.10 alternate version.
In my case, the /etc/network/interfaces
was configured during installation to download new packages, and the conflict arose after the NetworkManager was set up during the first session.
The solution I've found was commenting the lines related to the wlan interface in the /etc/network/interfaces
(in console, sudo vim /etc/network/interfaces
or your editor of choice):
# The primary network interface
#auto wlan0
#iface wlan0 inet dhcp
# wpa-ssid [your_ssid]
# wpa-psk [your_wpa_password]
And then, as Joseph VanPelt proposed, set managed=false
in the /etc/NetworkManager/NetworkManager.conf
and running sudo service network-manager restart
.
Excellent! This worked for me on an Eee PC 701.
– oKtosiTe
Dec 10 '11 at 17:00
2
Setting managed= is unnecessary (unless it's meant to revert a prior change).
– Mathieu Trudel-Lapierre
Apr 13 '12 at 17:42
For me, setting managed=true is what solved it eventually. It did not work with managed=false.
– Daniel Hershcovich
Jun 29 '12 at 18:51
add a comment |
wireless device not managed
I've also found this issue after installing the Ubuntu 11.10 alternate version.
In my case, the /etc/network/interfaces
was configured during installation to download new packages, and the conflict arose after the NetworkManager was set up during the first session.
The solution I've found was commenting the lines related to the wlan interface in the /etc/network/interfaces
(in console, sudo vim /etc/network/interfaces
or your editor of choice):
# The primary network interface
#auto wlan0
#iface wlan0 inet dhcp
# wpa-ssid [your_ssid]
# wpa-psk [your_wpa_password]
And then, as Joseph VanPelt proposed, set managed=false
in the /etc/NetworkManager/NetworkManager.conf
and running sudo service network-manager restart
.
Excellent! This worked for me on an Eee PC 701.
– oKtosiTe
Dec 10 '11 at 17:00
2
Setting managed= is unnecessary (unless it's meant to revert a prior change).
– Mathieu Trudel-Lapierre
Apr 13 '12 at 17:42
For me, setting managed=true is what solved it eventually. It did not work with managed=false.
– Daniel Hershcovich
Jun 29 '12 at 18:51
add a comment |
wireless device not managed
I've also found this issue after installing the Ubuntu 11.10 alternate version.
In my case, the /etc/network/interfaces
was configured during installation to download new packages, and the conflict arose after the NetworkManager was set up during the first session.
The solution I've found was commenting the lines related to the wlan interface in the /etc/network/interfaces
(in console, sudo vim /etc/network/interfaces
or your editor of choice):
# The primary network interface
#auto wlan0
#iface wlan0 inet dhcp
# wpa-ssid [your_ssid]
# wpa-psk [your_wpa_password]
And then, as Joseph VanPelt proposed, set managed=false
in the /etc/NetworkManager/NetworkManager.conf
and running sudo service network-manager restart
.
wireless device not managed
I've also found this issue after installing the Ubuntu 11.10 alternate version.
In my case, the /etc/network/interfaces
was configured during installation to download new packages, and the conflict arose after the NetworkManager was set up during the first session.
The solution I've found was commenting the lines related to the wlan interface in the /etc/network/interfaces
(in console, sudo vim /etc/network/interfaces
or your editor of choice):
# The primary network interface
#auto wlan0
#iface wlan0 inet dhcp
# wpa-ssid [your_ssid]
# wpa-psk [your_wpa_password]
And then, as Joseph VanPelt proposed, set managed=false
in the /etc/NetworkManager/NetworkManager.conf
and running sudo service network-manager restart
.
edited May 20 '12 at 11:17
fossfreedom♦
150k37328373
150k37328373
answered Nov 12 '11 at 20:17
el.atomoel.atomo
30638
30638
Excellent! This worked for me on an Eee PC 701.
– oKtosiTe
Dec 10 '11 at 17:00
2
Setting managed= is unnecessary (unless it's meant to revert a prior change).
– Mathieu Trudel-Lapierre
Apr 13 '12 at 17:42
For me, setting managed=true is what solved it eventually. It did not work with managed=false.
– Daniel Hershcovich
Jun 29 '12 at 18:51
add a comment |
Excellent! This worked for me on an Eee PC 701.
– oKtosiTe
Dec 10 '11 at 17:00
2
Setting managed= is unnecessary (unless it's meant to revert a prior change).
– Mathieu Trudel-Lapierre
Apr 13 '12 at 17:42
For me, setting managed=true is what solved it eventually. It did not work with managed=false.
– Daniel Hershcovich
Jun 29 '12 at 18:51
Excellent! This worked for me on an Eee PC 701.
– oKtosiTe
Dec 10 '11 at 17:00
Excellent! This worked for me on an Eee PC 701.
– oKtosiTe
Dec 10 '11 at 17:00
2
2
Setting managed= is unnecessary (unless it's meant to revert a prior change).
– Mathieu Trudel-Lapierre
Apr 13 '12 at 17:42
Setting managed= is unnecessary (unless it's meant to revert a prior change).
– Mathieu Trudel-Lapierre
Apr 13 '12 at 17:42
For me, setting managed=true is what solved it eventually. It did not work with managed=false.
– Daniel Hershcovich
Jun 29 '12 at 18:51
For me, setting managed=true is what solved it eventually. It did not work with managed=false.
– Daniel Hershcovich
Jun 29 '12 at 18:51
add a comment |
wired device not managed
This is a simple command which does the same as the accepted answer non-interactively.
Run this command in a Terminal to use it:
sudo sed -i 's/^managed=false/managed=true/' /etc/NetworkManager/NetworkManager.conf
You may have to restart the network manager afterwards with this command:
sudo service network-manager restart
add a comment |
wired device not managed
This is a simple command which does the same as the accepted answer non-interactively.
Run this command in a Terminal to use it:
sudo sed -i 's/^managed=false/managed=true/' /etc/NetworkManager/NetworkManager.conf
You may have to restart the network manager afterwards with this command:
sudo service network-manager restart
add a comment |
wired device not managed
This is a simple command which does the same as the accepted answer non-interactively.
Run this command in a Terminal to use it:
sudo sed -i 's/^managed=false/managed=true/' /etc/NetworkManager/NetworkManager.conf
You may have to restart the network manager afterwards with this command:
sudo service network-manager restart
wired device not managed
This is a simple command which does the same as the accepted answer non-interactively.
Run this command in a Terminal to use it:
sudo sed -i 's/^managed=false/managed=true/' /etc/NetworkManager/NetworkManager.conf
You may have to restart the network manager afterwards with this command:
sudo service network-manager restart
edited Nov 29 '13 at 21:28
answered Nov 29 '13 at 21:20
kirikiri
19.2k1360106
19.2k1360106
add a comment |
add a comment |
Situation like this may appear, when one runs pppoeconf
or something similar and the command overwrites the setting saved by NetworkManager. Even though the device seems to be working properly, Network Manager shows device status to be unmanaged.
If this a normal user's pc with simple network configuration like connecting via DHCP and automatic configuration, simply out comment the lines and restart network manager.
$ sudo restart network-manager
If situations other than these, please explain.
add a comment |
Situation like this may appear, when one runs pppoeconf
or something similar and the command overwrites the setting saved by NetworkManager. Even though the device seems to be working properly, Network Manager shows device status to be unmanaged.
If this a normal user's pc with simple network configuration like connecting via DHCP and automatic configuration, simply out comment the lines and restart network manager.
$ sudo restart network-manager
If situations other than these, please explain.
add a comment |
Situation like this may appear, when one runs pppoeconf
or something similar and the command overwrites the setting saved by NetworkManager. Even though the device seems to be working properly, Network Manager shows device status to be unmanaged.
If this a normal user's pc with simple network configuration like connecting via DHCP and automatic configuration, simply out comment the lines and restart network manager.
$ sudo restart network-manager
If situations other than these, please explain.
Situation like this may appear, when one runs pppoeconf
or something similar and the command overwrites the setting saved by NetworkManager. Even though the device seems to be working properly, Network Manager shows device status to be unmanaged.
If this a normal user's pc with simple network configuration like connecting via DHCP and automatic configuration, simply out comment the lines and restart network manager.
$ sudo restart network-manager
If situations other than these, please explain.
edited Jun 8 '12 at 2:02
hexafraction
16.4k105486
16.4k105486
answered May 20 '12 at 10:49
Dhruba AdhikariDhruba Adhikari
15115
15115
add a comment |
add a comment |
I had the same problem, I solved it by commenting the lines where the unmanaged device was mentioned, by mac address, in /etc/NetworkManager/NetworkManager.conf
.
[main]
plugins=ifupdown,keyfile
dns=dnsmasq
[ifupdown]
managed=false
[keyfile]
unmanaged-devices=mac:00:26:2d:fd:5c:e0
changed to
[main]
plugins=ifupdown,keyfile
dns=dnsmasq
[ifupdown]
managed=false
#[keyfile]
#unmanaged-devices=mac:00:26:2d:fd:5c:e0
add a comment |
I had the same problem, I solved it by commenting the lines where the unmanaged device was mentioned, by mac address, in /etc/NetworkManager/NetworkManager.conf
.
[main]
plugins=ifupdown,keyfile
dns=dnsmasq
[ifupdown]
managed=false
[keyfile]
unmanaged-devices=mac:00:26:2d:fd:5c:e0
changed to
[main]
plugins=ifupdown,keyfile
dns=dnsmasq
[ifupdown]
managed=false
#[keyfile]
#unmanaged-devices=mac:00:26:2d:fd:5c:e0
add a comment |
I had the same problem, I solved it by commenting the lines where the unmanaged device was mentioned, by mac address, in /etc/NetworkManager/NetworkManager.conf
.
[main]
plugins=ifupdown,keyfile
dns=dnsmasq
[ifupdown]
managed=false
[keyfile]
unmanaged-devices=mac:00:26:2d:fd:5c:e0
changed to
[main]
plugins=ifupdown,keyfile
dns=dnsmasq
[ifupdown]
managed=false
#[keyfile]
#unmanaged-devices=mac:00:26:2d:fd:5c:e0
I had the same problem, I solved it by commenting the lines where the unmanaged device was mentioned, by mac address, in /etc/NetworkManager/NetworkManager.conf
.
[main]
plugins=ifupdown,keyfile
dns=dnsmasq
[ifupdown]
managed=false
[keyfile]
unmanaged-devices=mac:00:26:2d:fd:5c:e0
changed to
[main]
plugins=ifupdown,keyfile
dns=dnsmasq
[ifupdown]
managed=false
#[keyfile]
#unmanaged-devices=mac:00:26:2d:fd:5c:e0
edited Apr 26 '14 at 7:18
Jacob Vlijm
64.9k9129225
64.9k9129225
answered Apr 26 '14 at 6:18
KuldeepKuldeep
311
311
add a comment |
add a comment |
None of the given solutions worked for me. I was having this problem on an Ubuntu 16.04 machine I hadn't booted in a long time. After some more searching this command is what worked for me.
sudo touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf
Thank you! Your solution worked for me on 18.04.
– Carlos López-Camey
Oct 4 '18 at 19:42
Thank you !!! I spent like two hours on this before finally finding your solution. Works as of 18.10.
– max
Oct 28 '18 at 9:46
add a comment |
None of the given solutions worked for me. I was having this problem on an Ubuntu 16.04 machine I hadn't booted in a long time. After some more searching this command is what worked for me.
sudo touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf
Thank you! Your solution worked for me on 18.04.
– Carlos López-Camey
Oct 4 '18 at 19:42
Thank you !!! I spent like two hours on this before finally finding your solution. Works as of 18.10.
– max
Oct 28 '18 at 9:46
add a comment |
None of the given solutions worked for me. I was having this problem on an Ubuntu 16.04 machine I hadn't booted in a long time. After some more searching this command is what worked for me.
sudo touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf
None of the given solutions worked for me. I was having this problem on an Ubuntu 16.04 machine I hadn't booted in a long time. After some more searching this command is what worked for me.
sudo touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf
edited Jan 29 at 23:54
Daniël Knippers
1032
1032
answered Sep 14 '18 at 0:09
David BaucumDavid Baucum
41049
41049
Thank you! Your solution worked for me on 18.04.
– Carlos López-Camey
Oct 4 '18 at 19:42
Thank you !!! I spent like two hours on this before finally finding your solution. Works as of 18.10.
– max
Oct 28 '18 at 9:46
add a comment |
Thank you! Your solution worked for me on 18.04.
– Carlos López-Camey
Oct 4 '18 at 19:42
Thank you !!! I spent like two hours on this before finally finding your solution. Works as of 18.10.
– max
Oct 28 '18 at 9:46
Thank you! Your solution worked for me on 18.04.
– Carlos López-Camey
Oct 4 '18 at 19:42
Thank you! Your solution worked for me on 18.04.
– Carlos López-Camey
Oct 4 '18 at 19:42
Thank you !!! I spent like two hours on this before finally finding your solution. Works as of 18.10.
– max
Oct 28 '18 at 9:46
Thank you !!! I spent like two hours on this before finally finding your solution. Works as of 18.10.
– max
Oct 28 '18 at 9:46
add a comment |
There are two ways to manage network connections. You either have to do everything thru the network manager and remove everything Except the Loopback entry in /etc/network/interfaces
auto lo
iface lo inet loopback
or totally remove the network manager thru the package manager or terminal and use the /etc/network/interfaces and /etc/resolve.conf file to control your connections. If not you will see the error you are getting. Even with static IP I've found that the network manager makes things easy and you can configure your IPV4 connections thru the menu.
please put all of that answer into a newbie answer and I dont get any of it :( I just want it to work nothing works!
– Daniella Glover
Oct 23 '11 at 22:59
there is no Auto eth0 in the menu its blank! how can I edit anything if it isnt there! I need a useful answer!
– Daniella Glover
Oct 23 '11 at 23:01
add a comment |
There are two ways to manage network connections. You either have to do everything thru the network manager and remove everything Except the Loopback entry in /etc/network/interfaces
auto lo
iface lo inet loopback
or totally remove the network manager thru the package manager or terminal and use the /etc/network/interfaces and /etc/resolve.conf file to control your connections. If not you will see the error you are getting. Even with static IP I've found that the network manager makes things easy and you can configure your IPV4 connections thru the menu.
please put all of that answer into a newbie answer and I dont get any of it :( I just want it to work nothing works!
– Daniella Glover
Oct 23 '11 at 22:59
there is no Auto eth0 in the menu its blank! how can I edit anything if it isnt there! I need a useful answer!
– Daniella Glover
Oct 23 '11 at 23:01
add a comment |
There are two ways to manage network connections. You either have to do everything thru the network manager and remove everything Except the Loopback entry in /etc/network/interfaces
auto lo
iface lo inet loopback
or totally remove the network manager thru the package manager or terminal and use the /etc/network/interfaces and /etc/resolve.conf file to control your connections. If not you will see the error you are getting. Even with static IP I've found that the network manager makes things easy and you can configure your IPV4 connections thru the menu.
There are two ways to manage network connections. You either have to do everything thru the network manager and remove everything Except the Loopback entry in /etc/network/interfaces
auto lo
iface lo inet loopback
or totally remove the network manager thru the package manager or terminal and use the /etc/network/interfaces and /etc/resolve.conf file to control your connections. If not you will see the error you are getting. Even with static IP I've found that the network manager makes things easy and you can configure your IPV4 connections thru the menu.
edited Oct 23 '11 at 22:46
answered Oct 23 '11 at 22:36
BobhuberBobhuber
112
112
please put all of that answer into a newbie answer and I dont get any of it :( I just want it to work nothing works!
– Daniella Glover
Oct 23 '11 at 22:59
there is no Auto eth0 in the menu its blank! how can I edit anything if it isnt there! I need a useful answer!
– Daniella Glover
Oct 23 '11 at 23:01
add a comment |
please put all of that answer into a newbie answer and I dont get any of it :( I just want it to work nothing works!
– Daniella Glover
Oct 23 '11 at 22:59
there is no Auto eth0 in the menu its blank! how can I edit anything if it isnt there! I need a useful answer!
– Daniella Glover
Oct 23 '11 at 23:01
please put all of that answer into a newbie answer and I dont get any of it :( I just want it to work nothing works!
– Daniella Glover
Oct 23 '11 at 22:59
please put all of that answer into a newbie answer and I dont get any of it :( I just want it to work nothing works!
– Daniella Glover
Oct 23 '11 at 22:59
there is no Auto eth0 in the menu its blank! how can I edit anything if it isnt there! I need a useful answer!
– Daniella Glover
Oct 23 '11 at 23:01
there is no Auto eth0 in the menu its blank! how can I edit anything if it isnt there! I need a useful answer!
– Daniella Glover
Oct 23 '11 at 23:01
add a comment |
Just to add a non-default answer, this can also happen if your computer has a hardware ON/OFF switch for the Wi-Fi interface. If you have such a "killswitch", ensure that you haven't accidentally turned the interface off
add a comment |
Just to add a non-default answer, this can also happen if your computer has a hardware ON/OFF switch for the Wi-Fi interface. If you have such a "killswitch", ensure that you haven't accidentally turned the interface off
add a comment |
Just to add a non-default answer, this can also happen if your computer has a hardware ON/OFF switch for the Wi-Fi interface. If you have such a "killswitch", ensure that you haven't accidentally turned the interface off
Just to add a non-default answer, this can also happen if your computer has a hardware ON/OFF switch for the Wi-Fi interface. If you have such a "killswitch", ensure that you haven't accidentally turned the interface off
answered Feb 11 '14 at 17:55
HamyHamy
340110
340110
add a comment |
add a comment |
In 11.10 you can go to System Settings and you should see a Network Icon. Run that utility and you should see tabs for your network devices, wired and wireless. Each tab has a slider that allows you to switch the device off. Or in your case switch eth0 or wired connection 1, as it is now called, on. May be. At least check that it not switched to off.
regards.
sorry but its a no go, there is no slider. I suggest you look at my screenshot. no slider there and I repeat there is nothing in the wired connections tab in my network manager. :(
– Daniella Glover
Oct 23 '11 at 21:59
add a comment |
In 11.10 you can go to System Settings and you should see a Network Icon. Run that utility and you should see tabs for your network devices, wired and wireless. Each tab has a slider that allows you to switch the device off. Or in your case switch eth0 or wired connection 1, as it is now called, on. May be. At least check that it not switched to off.
regards.
sorry but its a no go, there is no slider. I suggest you look at my screenshot. no slider there and I repeat there is nothing in the wired connections tab in my network manager. :(
– Daniella Glover
Oct 23 '11 at 21:59
add a comment |
In 11.10 you can go to System Settings and you should see a Network Icon. Run that utility and you should see tabs for your network devices, wired and wireless. Each tab has a slider that allows you to switch the device off. Or in your case switch eth0 or wired connection 1, as it is now called, on. May be. At least check that it not switched to off.
regards.
In 11.10 you can go to System Settings and you should see a Network Icon. Run that utility and you should see tabs for your network devices, wired and wireless. Each tab has a slider that allows you to switch the device off. Or in your case switch eth0 or wired connection 1, as it is now called, on. May be. At least check that it not switched to off.
regards.
answered Oct 23 '11 at 21:47
grahammechanicalgrahammechanical
1,834910
1,834910
sorry but its a no go, there is no slider. I suggest you look at my screenshot. no slider there and I repeat there is nothing in the wired connections tab in my network manager. :(
– Daniella Glover
Oct 23 '11 at 21:59
add a comment |
sorry but its a no go, there is no slider. I suggest you look at my screenshot. no slider there and I repeat there is nothing in the wired connections tab in my network manager. :(
– Daniella Glover
Oct 23 '11 at 21:59
sorry but its a no go, there is no slider. I suggest you look at my screenshot. no slider there and I repeat there is nothing in the wired connections tab in my network manager. :(
– Daniella Glover
Oct 23 '11 at 21:59
sorry but its a no go, there is no slider. I suggest you look at my screenshot. no slider there and I repeat there is nothing in the wired connections tab in my network manager. :(
– Daniella Glover
Oct 23 '11 at 21:59
add a comment |
wireless device not managed
This is because the alternate images were for a period of time, configuring the wireless networks in /etc/network/interfaces; which causes NetworkManager to, on purpose, ignore the interface and consider them online.
A good solution if you want to simply use your wireless connection (or wired) with DHCP is to comment out these settings in /etc/network/interfaces for all interfaces except lo, and reboot your system or restart NetworkManager like so:
sudo restart network-manager
Of course, this means you will need to enter your wireless settings into NetworkManager (password, etc) after clicking on the right item from the applet menu.
add a comment |
wireless device not managed
This is because the alternate images were for a period of time, configuring the wireless networks in /etc/network/interfaces; which causes NetworkManager to, on purpose, ignore the interface and consider them online.
A good solution if you want to simply use your wireless connection (or wired) with DHCP is to comment out these settings in /etc/network/interfaces for all interfaces except lo, and reboot your system or restart NetworkManager like so:
sudo restart network-manager
Of course, this means you will need to enter your wireless settings into NetworkManager (password, etc) after clicking on the right item from the applet menu.
add a comment |
wireless device not managed
This is because the alternate images were for a period of time, configuring the wireless networks in /etc/network/interfaces; which causes NetworkManager to, on purpose, ignore the interface and consider them online.
A good solution if you want to simply use your wireless connection (or wired) with DHCP is to comment out these settings in /etc/network/interfaces for all interfaces except lo, and reboot your system or restart NetworkManager like so:
sudo restart network-manager
Of course, this means you will need to enter your wireless settings into NetworkManager (password, etc) after clicking on the right item from the applet menu.
wireless device not managed
This is because the alternate images were for a period of time, configuring the wireless networks in /etc/network/interfaces; which causes NetworkManager to, on purpose, ignore the interface and consider them online.
A good solution if you want to simply use your wireless connection (or wired) with DHCP is to comment out these settings in /etc/network/interfaces for all interfaces except lo, and reboot your system or restart NetworkManager like so:
sudo restart network-manager
Of course, this means you will need to enter your wireless settings into NetworkManager (password, etc) after clicking on the right item from the applet menu.
edited May 20 '12 at 11:17
fossfreedom♦
150k37328373
150k37328373
answered Apr 13 '12 at 17:41
Mathieu Trudel-LapierreMathieu Trudel-Lapierre
2,0921131
2,0921131
add a comment |
add a comment |
protected by Community♦ Dec 30 '15 at 5:58
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
3
The following answer from a similar question resolved this issue for me: askubuntu.com/a/893614/321971
– Edward Moffett
Apr 21 '17 at 22:56
@EdwardMoffett thanks! Adding the empty file named "10-globally-managed-devices.conf" to the directory "/etc/NetworkManager/conf.d/" fixed it for me!
– dontbyteme
Sep 21 '17 at 8:12