NetworkManager refuses to manage my WLAN interface
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I'm using Ubuntu 12.10 with Gnome 3.6 on a brand-new Samsung NP900X4C.
The installer detected the wireless adapter, took in the SSID and WPA passphrase, wrote these into /etc/network/interfaces and connected perfectly.
Once installation was finished I wanted to switch to using NetworkManager to manage the wireless adapter, since this is much more convenient than fiddling with /etc/network/interfaces every time I find a new hotspot.
Therefore I edited /etc/NetworkManager/NetworkManager.conf to set:
[ifupdown]
managed=true
When I rebooted NetworkManager, the problems started:
- The NetworkManager tray applet changed from saying device not managed to device not ready
- I lost all internet connectivity as wlan0 would not associate to the Access Point
- if I set managed=false in NetworkManager.conf and restarted both NetworkManager and networking services from the command-line, the Gnome desktop "semi-crashed" and lost all its Window Decorations, the panel, the launcher and basically became unusable.
However if I restart the computer completely after setting managed=false, wlan0 once again works perfectly.
wireless 12.10 network-manager
edited Nov 3 '12 at 14:04
Eliah Kagan
83.5k22229369
asked Nov 3 '12 at 11:27
user104167user104167
164116
add a comment |
I'm using Ubuntu 12.10 with Gnome 3.6 on a brand-new Samsung NP900X4C.
The installer detected the wireless adapter, took in the SSID and WPA passphrase, wrote these into /etc/network/interfaces and connected perfectly.
Once installation was finished I wanted to switch to using NetworkManager to manage the wireless adapter, since this is much more convenient than fiddling with /etc/network/interfaces every time I find a new hotspot.
Therefore I edited /etc/NetworkManager/NetworkManager.conf to set:
[ifupdown]
managed=true
When I rebooted NetworkManager, the problems started:
- The NetworkManager tray applet changed from saying device not managed to device not ready
- I lost all internet connectivity as wlan0 would not associate to the Access Point
- if I set managed=false in NetworkManager.conf and restarted both NetworkManager and networking services from the command-line, the Gnome desktop "semi-crashed" and lost all its Window Decorations, the panel, the launcher and basically became unusable.
However if I restart the computer completely after setting managed=false, wlan0 once again works perfectly.
wireless 12.10 network-manager
edited Nov 3 '12 at 14:04
Eliah Kagan
83.5k22229369
asked Nov 3 '12 at 11:27
user104167user104167
164116
Inmanaged=falsemode, wlan0 works after reboot because ifup configures it at boot time (if /e/n/i containsauto wlan0). Inmanaged=truemode, ifup doesn't bring interfaces up automatically; but then NetworkManager should do so. I don't know why it saiddevice not ready.
– jdthood
Mar 20 '13 at 9:34
add a comment |
I'm using Ubuntu 12.10 with Gnome 3.6 on a brand-new Samsung NP900X4C.
The installer detected the wireless adapter, took in the SSID and WPA passphrase, wrote these into /etc/network/interfaces and connected perfectly.
Once installation was finished I wanted to switch to using NetworkManager to manage the wireless adapter, since this is much more convenient than fiddling with /etc/network/interfaces every time I find a new hotspot.
Therefore I edited /etc/NetworkManager/NetworkManager.conf to set:
[ifupdown]
managed=true
When I rebooted NetworkManager, the problems started:
- The NetworkManager tray applet changed from saying device not managed to device not ready
- I lost all internet connectivity as wlan0 would not associate to the Access Point
- if I set managed=false in NetworkManager.conf and restarted both NetworkManager and networking services from the command-line, the Gnome desktop "semi-crashed" and lost all its Window Decorations, the panel, the launcher and basically became unusable.
However if I restart the computer completely after setting managed=false, wlan0 once again works perfectly.
wireless 12.10 network-manager
edited Nov 3 '12 at 14:04
Eliah Kagan
83.5k22229369
asked Nov 3 '12 at 11:27
user104167user104167
164116
I'm using Ubuntu 12.10 with Gnome 3.6 on a brand-new Samsung NP900X4C.
The installer detected the wireless adapter, took in the SSID and WPA passphrase, wrote these into /etc/network/interfaces and connected perfectly.
Once installation was finished I wanted to switch to using NetworkManager to manage the wireless adapter, since this is much more convenient than fiddling with /etc/network/interfaces every time I find a new hotspot.
Therefore I edited /etc/NetworkManager/NetworkManager.conf to set:
[ifupdown]
managed=true
When I rebooted NetworkManager, the problems started:
- The NetworkManager tray applet changed from saying device not managed to device not ready
- I lost all internet connectivity as wlan0 would not associate to the Access Point
- if I set managed=false in NetworkManager.conf and restarted both NetworkManager and networking services from the command-line, the Gnome desktop "semi-crashed" and lost all its Window Decorations, the panel, the launcher and basically became unusable.
However if I restart the computer completely after setting managed=false, wlan0 once again works perfectly.
wireless 12.10 network-manager
wireless 12.10 network-manager
edited Nov 3 '12 at 14:04
Eliah Kagan
83.5k22229369
asked Nov 3 '12 at 11:27
user104167user104167
164116
edited Nov 3 '12 at 14:04
Eliah Kagan
83.5k22229369
asked Nov 3 '12 at 11:27
user104167user104167
164116
edited Nov 3 '12 at 14:04
Eliah Kagan
83.5k22229369
edited Nov 3 '12 at 14:04
Eliah Kagan
83.5k22229369
edited Nov 3 '12 at 14:04
Eliah Kagan
83.5k22229369
83.5k22229369
asked Nov 3 '12 at 11:27
user104167user104167
164116
asked Nov 3 '12 at 11:27
user104167user104167
164116
asked Nov 3 '12 at 11:27
user104167user104167
164116
164116
Inmanaged=falsemode, wlan0 works after reboot because ifup configures it at boot time (if /e/n/i containsauto wlan0). Inmanaged=truemode, ifup doesn't bring interfaces up automatically; but then NetworkManager should do so. I don't know why it saiddevice not ready.
– jdthood
Mar 20 '13 at 9:34
add a comment |
Inmanaged=falsemode, wlan0 works after reboot because ifup configures it at boot time (if /e/n/i containsauto wlan0). Inmanaged=truemode, ifup doesn't bring interfaces up automatically; but then NetworkManager should do so. I don't know why it saiddevice not ready.
– jdthood
Mar 20 '13 at 9:34
In
managed=false mode, wlan0 works after reboot because ifup configures it at boot time (if /e/n/i contains auto wlan0). In managed=true mode, ifup doesn't bring interfaces up automatically; but then NetworkManager should do so. I don't know why it said device not ready.– jdthood
Mar 20 '13 at 9:34
In
managed=false mode, wlan0 works after reboot because ifup configures it at boot time (if /e/n/i contains auto wlan0). In managed=true mode, ifup doesn't bring interfaces up automatically; but then NetworkManager should do so. I don't know why it said device not ready.– jdthood
Mar 20 '13 at 9:34
add a comment |
2 Answers
2
active
oldest
votes
I ended up fixing this myself, see the exact steps below.
Note that there may be an easier solution but these steps definitely worked.
Make sure
network-manageris the latest version (I have 0.9.6.0-0ubuntu7 ).
You can check this with:sudo dpkg -l | grep network-managerRight-click on Network Manager tray icon -> Edit Connections -> Wireless -> Add
Manually add the parameters for connecting to your WLAN.
Edit
/etc/NetworkManager/NetworkManager.confto set...
[ifupdown]
managed=true
DO NOT restart
network-managerservice.
Edit
/etc/network/interfacesto deactivate the auto-start of your Wireless interface (probably calledwlan0).
For example:
From this:
auto wlan0
.... to this:#auto wlan0
Run
/etc/init.d/network-manager force-reload
edited 13 mins ago
Evan Carroll
4,912113567
answered Nov 9 '12 at 16:51
user104167user104167
164116
1
Interesting. Commenting outauto wlan0should cause NetworkManager not to consider the interface an "autoconnect" interface. Yet you say that NetworkManager does bring it up automatically. Sounds like a bug.
– jdthood
Mar 20 '13 at 9:37
Did you by any chance also define the wireless connection using the NM Connection Editor?
– jdthood
Mar 20 '13 at 9:43
Guy, you are my savior:managed=truewas exactly what I was sought for. My NM refuses to manage all a network connections, and I recalled that it was needed to turn it on in some config, but couldn't remember where.
– Hi-Angel
Sep 6 '14 at 15:53
This doesn't work for me on Ubuntu 14.04. Boot still takes forever with the message "Waiting for network configuration" and afterwards Network Manager and my wifi is still disabled. Nothing works until I manually runnmcli nm wifi on.
– Cerin
Jul 25 '15 at 22:12
@jdthood I guess it is rather an issue with poor NetworkManager documentation by Debian.
– Serge Stroobandt
Oct 8 '17 at 18:03
add a comment |
Uninstall wicd if you intalled it along with network-manager
If both are installed at a time, then there will be a conflict and only one will be able to use the device at a time.
answered Sep 3 '16 at 16:47
Sanjit Singh ChouhanSanjit Singh Chouhan
212
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f211347%2fnetworkmanager-refuses-to-manage-my-wlan-interface%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I ended up fixing this myself, see the exact steps below.
Note that there may be an easier solution but these steps definitely worked.
Make sure
network-manageris the latest version (I have 0.9.6.0-0ubuntu7 ).
You can check this with:sudo dpkg -l | grep network-managerRight-click on Network Manager tray icon -> Edit Connections -> Wireless -> Add
Manually add the parameters for connecting to your WLAN.
Edit
/etc/NetworkManager/NetworkManager.confto set...
[ifupdown]
managed=true
DO NOT restart
network-managerservice.
Edit
/etc/network/interfacesto deactivate the auto-start of your Wireless interface (probably calledwlan0).
For example:
From this:
auto wlan0
.... to this:#auto wlan0
Run
/etc/init.d/network-manager force-reload
edited 13 mins ago
Evan Carroll
4,912113567
answered Nov 9 '12 at 16:51
user104167user104167
164116
1
Interesting. Commenting outauto wlan0should cause NetworkManager not to consider the interface an "autoconnect" interface. Yet you say that NetworkManager does bring it up automatically. Sounds like a bug.
– jdthood
Mar 20 '13 at 9:37
Did you by any chance also define the wireless connection using the NM Connection Editor?
– jdthood
Mar 20 '13 at 9:43
Guy, you are my savior:managed=truewas exactly what I was sought for. My NM refuses to manage all a network connections, and I recalled that it was needed to turn it on in some config, but couldn't remember where.
– Hi-Angel
Sep 6 '14 at 15:53
This doesn't work for me on Ubuntu 14.04. Boot still takes forever with the message "Waiting for network configuration" and afterwards Network Manager and my wifi is still disabled. Nothing works until I manually runnmcli nm wifi on.
– Cerin
Jul 25 '15 at 22:12
@jdthood I guess it is rather an issue with poor NetworkManager documentation by Debian.
– Serge Stroobandt
Oct 8 '17 at 18:03
add a comment |
I ended up fixing this myself, see the exact steps below.
Note that there may be an easier solution but these steps definitely worked.
Make sure
network-manageris the latest version (I have 0.9.6.0-0ubuntu7 ).
You can check this with:sudo dpkg -l | grep network-managerRight-click on Network Manager tray icon -> Edit Connections -> Wireless -> Add
Manually add the parameters for connecting to your WLAN.
Edit
/etc/NetworkManager/NetworkManager.confto set...
[ifupdown]
managed=true
DO NOT restart
network-managerservice.
Edit
/etc/network/interfacesto deactivate the auto-start of your Wireless interface (probably calledwlan0).
For example:
From this:
auto wlan0
.... to this:#auto wlan0
Run
/etc/init.d/network-manager force-reload
edited 13 mins ago
Evan Carroll
4,912113567
answered Nov 9 '12 at 16:51
user104167user104167
164116
1
Interesting. Commenting outauto wlan0should cause NetworkManager not to consider the interface an "autoconnect" interface. Yet you say that NetworkManager does bring it up automatically. Sounds like a bug.
– jdthood
Mar 20 '13 at 9:37
Did you by any chance also define the wireless connection using the NM Connection Editor?
– jdthood
Mar 20 '13 at 9:43
Guy, you are my savior:managed=truewas exactly what I was sought for. My NM refuses to manage all a network connections, and I recalled that it was needed to turn it on in some config, but couldn't remember where.
– Hi-Angel
Sep 6 '14 at 15:53
This doesn't work for me on Ubuntu 14.04. Boot still takes forever with the message "Waiting for network configuration" and afterwards Network Manager and my wifi is still disabled. Nothing works until I manually runnmcli nm wifi on.
– Cerin
Jul 25 '15 at 22:12
@jdthood I guess it is rather an issue with poor NetworkManager documentation by Debian.
– Serge Stroobandt
Oct 8 '17 at 18:03
add a comment |
I ended up fixing this myself, see the exact steps below.
Note that there may be an easier solution but these steps definitely worked.
Make sure
network-manageris the latest version (I have 0.9.6.0-0ubuntu7 ).
You can check this with:sudo dpkg -l | grep network-managerRight-click on Network Manager tray icon -> Edit Connections -> Wireless -> Add
Manually add the parameters for connecting to your WLAN.
Edit
/etc/NetworkManager/NetworkManager.confto set...
[ifupdown]
managed=true
DO NOT restart
network-managerservice.
Edit
/etc/network/interfacesto deactivate the auto-start of your Wireless interface (probably calledwlan0).
For example:
From this:
auto wlan0
.... to this:#auto wlan0
Run
/etc/init.d/network-manager force-reload
edited 13 mins ago
Evan Carroll
4,912113567
answered Nov 9 '12 at 16:51
user104167user104167
164116
I ended up fixing this myself, see the exact steps below.
Note that there may be an easier solution but these steps definitely worked.
Make sure
network-manageris the latest version (I have 0.9.6.0-0ubuntu7 ).
You can check this with:sudo dpkg -l | grep network-managerRight-click on Network Manager tray icon -> Edit Connections -> Wireless -> Add
Manually add the parameters for connecting to your WLAN.
Edit
/etc/NetworkManager/NetworkManager.confto set...
[ifupdown]
managed=true
DO NOT restart
network-managerservice.
Edit
/etc/network/interfacesto deactivate the auto-start of your Wireless interface (probably calledwlan0).
For example:
From this:
auto wlan0
.... to this:#auto wlan0
Run
/etc/init.d/network-manager force-reload
edited 13 mins ago
Evan Carroll
4,912113567
answered Nov 9 '12 at 16:51
user104167user104167
164116
edited 13 mins ago
Evan Carroll
4,912113567
edited 13 mins ago
Evan Carroll
4,912113567
edited 13 mins ago
Evan Carroll
4,912113567
4,912113567
answered Nov 9 '12 at 16:51
user104167user104167
164116
answered Nov 9 '12 at 16:51
user104167user104167
164116
answered Nov 9 '12 at 16:51
user104167user104167
164116
164116
1
Interesting. Commenting outauto wlan0should cause NetworkManager not to consider the interface an "autoconnect" interface. Yet you say that NetworkManager does bring it up automatically. Sounds like a bug.
– jdthood
Mar 20 '13 at 9:37
Did you by any chance also define the wireless connection using the NM Connection Editor?
– jdthood
Mar 20 '13 at 9:43
Guy, you are my savior:managed=truewas exactly what I was sought for. My NM refuses to manage all a network connections, and I recalled that it was needed to turn it on in some config, but couldn't remember where.
– Hi-Angel
Sep 6 '14 at 15:53
This doesn't work for me on Ubuntu 14.04. Boot still takes forever with the message "Waiting for network configuration" and afterwards Network Manager and my wifi is still disabled. Nothing works until I manually runnmcli nm wifi on.
– Cerin
Jul 25 '15 at 22:12
@jdthood I guess it is rather an issue with poor NetworkManager documentation by Debian.
– Serge Stroobandt
Oct 8 '17 at 18:03
add a comment |
1
Interesting. Commenting outauto wlan0should cause NetworkManager not to consider the interface an "autoconnect" interface. Yet you say that NetworkManager does bring it up automatically. Sounds like a bug.
– jdthood
Mar 20 '13 at 9:37
Did you by any chance also define the wireless connection using the NM Connection Editor?
– jdthood
Mar 20 '13 at 9:43
Guy, you are my savior:managed=truewas exactly what I was sought for. My NM refuses to manage all a network connections, and I recalled that it was needed to turn it on in some config, but couldn't remember where.
– Hi-Angel
Sep 6 '14 at 15:53
This doesn't work for me on Ubuntu 14.04. Boot still takes forever with the message "Waiting for network configuration" and afterwards Network Manager and my wifi is still disabled. Nothing works until I manually runnmcli nm wifi on.
– Cerin
Jul 25 '15 at 22:12
@jdthood I guess it is rather an issue with poor NetworkManager documentation by Debian.
– Serge Stroobandt
Oct 8 '17 at 18:03
1
1
Interesting. Commenting out
auto wlan0 should cause NetworkManager not to consider the interface an "autoconnect" interface. Yet you say that NetworkManager does bring it up automatically. Sounds like a bug.– jdthood
Mar 20 '13 at 9:37
Interesting. Commenting out
auto wlan0 should cause NetworkManager not to consider the interface an "autoconnect" interface. Yet you say that NetworkManager does bring it up automatically. Sounds like a bug.– jdthood
Mar 20 '13 at 9:37
Did you by any chance also define the wireless connection using the NM Connection Editor?
– jdthood
Mar 20 '13 at 9:43
Did you by any chance also define the wireless connection using the NM Connection Editor?
– jdthood
Mar 20 '13 at 9:43
Guy, you are my savior:
managed=true was exactly what I was sought for. My NM refuses to manage all a network connections, and I recalled that it was needed to turn it on in some config, but couldn't remember where.– Hi-Angel
Sep 6 '14 at 15:53
Guy, you are my savior:
managed=true was exactly what I was sought for. My NM refuses to manage all a network connections, and I recalled that it was needed to turn it on in some config, but couldn't remember where.– Hi-Angel
Sep 6 '14 at 15:53
This doesn't work for me on Ubuntu 14.04. Boot still takes forever with the message "Waiting for network configuration" and afterwards Network Manager and my wifi is still disabled. Nothing works until I manually run
nmcli nm wifi on.– Cerin
Jul 25 '15 at 22:12
This doesn't work for me on Ubuntu 14.04. Boot still takes forever with the message "Waiting for network configuration" and afterwards Network Manager and my wifi is still disabled. Nothing works until I manually run
nmcli nm wifi on.– Cerin
Jul 25 '15 at 22:12
@jdthood I guess it is rather an issue with poor NetworkManager documentation by Debian.
– Serge Stroobandt
Oct 8 '17 at 18:03
@jdthood I guess it is rather an issue with poor NetworkManager documentation by Debian.
– Serge Stroobandt
Oct 8 '17 at 18:03
add a comment |
Uninstall wicd if you intalled it along with network-manager
If both are installed at a time, then there will be a conflict and only one will be able to use the device at a time.
answered Sep 3 '16 at 16:47
Sanjit Singh ChouhanSanjit Singh Chouhan
212
add a comment |
Uninstall wicd if you intalled it along with network-manager
If both are installed at a time, then there will be a conflict and only one will be able to use the device at a time.
answered Sep 3 '16 at 16:47
Sanjit Singh ChouhanSanjit Singh Chouhan
212
add a comment |
Uninstall wicd if you intalled it along with network-manager
If both are installed at a time, then there will be a conflict and only one will be able to use the device at a time.
answered Sep 3 '16 at 16:47
Sanjit Singh ChouhanSanjit Singh Chouhan
212
Uninstall wicd if you intalled it along with network-manager
If both are installed at a time, then there will be a conflict and only one will be able to use the device at a time.
answered Sep 3 '16 at 16:47
Sanjit Singh ChouhanSanjit Singh Chouhan
212
answered Sep 3 '16 at 16:47
Sanjit Singh ChouhanSanjit Singh Chouhan
212
answered Sep 3 '16 at 16:47
Sanjit Singh ChouhanSanjit Singh Chouhan
212
answered Sep 3 '16 at 16:47
Sanjit Singh ChouhanSanjit Singh Chouhan
212
212
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f211347%2fnetworkmanager-refuses-to-manage-my-wlan-interface%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
In
managed=falsemode, wlan0 works after reboot because ifup configures it at boot time (if /e/n/i containsauto wlan0). Inmanaged=truemode, ifup doesn't bring interfaces up automatically; but then NetworkManager should do so. I don't know why it saiddevice not ready.– jdthood
Mar 20 '13 at 9:34