NetworkManager not managing ethernet device
I have a fresh install of the Ubuntu 18.04 server image, on which I run apt install ubuntu-desktop to get a desktop environment. No matter what I do, NetworkManager refuses to manage the ethernet device. I want this because I want to be able to manage my OpenVPN client from my desktop.
I've tried all the answers in both of these questions to no avail:
- ubuntu 18.04, nm(Network Manager) is not able to manage network devices
- Ethernet device not managed
I've traced the problem to the file /run/NetworkManager/conf.d/netplan.conf which contains the contents:
[keyfile]
# devices managed by networkd
unmanaged-devices+=interface-name:enp0s3,
If I remove the unmanaged-devices line and restart NetworkManager then it works. But since /run/ is a temporary filesystem, as soon as I reboot my changes are discarded.
I have no idea where this file is coming from, and my googlefu has failed me when it comes to figuring out how to get networkd to not take control of my ethernet port.
Any suggestions?
networking 18.04 network-manager ethernet
asked Jan 25 at 14:16
ErikErik
1011
add a comment |
I have a fresh install of the Ubuntu 18.04 server image, on which I run apt install ubuntu-desktop to get a desktop environment. No matter what I do, NetworkManager refuses to manage the ethernet device. I want this because I want to be able to manage my OpenVPN client from my desktop.
I've tried all the answers in both of these questions to no avail:
- ubuntu 18.04, nm(Network Manager) is not able to manage network devices
- Ethernet device not managed
I've traced the problem to the file /run/NetworkManager/conf.d/netplan.conf which contains the contents:
[keyfile]
# devices managed by networkd
unmanaged-devices+=interface-name:enp0s3,
If I remove the unmanaged-devices line and restart NetworkManager then it works. But since /run/ is a temporary filesystem, as soon as I reboot my changes are discarded.
I have no idea where this file is coming from, and my googlefu has failed me when it comes to figuring out how to get networkd to not take control of my ethernet port.
Any suggestions?
networking 18.04 network-manager ethernet
asked Jan 25 at 14:16
ErikErik
1011
Is there a linemanaged=falsein your/etc/NetworkManager/NetworkManager.conf?
– Jos
Jan 25 at 14:26
No I already fixed that to bemanaged=true. But as I understand it, that is only matters if ifupdown is on the system, but Ubuntu Server uses netplan.
– Erik
Jan 25 at 14:27
2
Ah, actually this answer contained the solution for me: askubuntu.com/questions/1031956/…
– Erik
Jan 25 at 14:30
Actually, you should have left /etc/NetworkManager/NetworkManager.conf alone, not changed /etc/netplan/*.yaml to renderer: NetworkManager, and just edited the .yaml file in /etc/netplan and configured enp0s3 there.
– heynnema
Jan 25 at 18:57
@Erik status please
– heynnema
Jan 30 at 16:14
add a comment |
I have a fresh install of the Ubuntu 18.04 server image, on which I run apt install ubuntu-desktop to get a desktop environment. No matter what I do, NetworkManager refuses to manage the ethernet device. I want this because I want to be able to manage my OpenVPN client from my desktop.
I've tried all the answers in both of these questions to no avail:
- ubuntu 18.04, nm(Network Manager) is not able to manage network devices
- Ethernet device not managed
I've traced the problem to the file /run/NetworkManager/conf.d/netplan.conf which contains the contents:
[keyfile]
# devices managed by networkd
unmanaged-devices+=interface-name:enp0s3,
If I remove the unmanaged-devices line and restart NetworkManager then it works. But since /run/ is a temporary filesystem, as soon as I reboot my changes are discarded.
I have no idea where this file is coming from, and my googlefu has failed me when it comes to figuring out how to get networkd to not take control of my ethernet port.
Any suggestions?
networking 18.04 network-manager ethernet
asked Jan 25 at 14:16
ErikErik
1011
I have a fresh install of the Ubuntu 18.04 server image, on which I run apt install ubuntu-desktop to get a desktop environment. No matter what I do, NetworkManager refuses to manage the ethernet device. I want this because I want to be able to manage my OpenVPN client from my desktop.
I've tried all the answers in both of these questions to no avail:
- ubuntu 18.04, nm(Network Manager) is not able to manage network devices
- Ethernet device not managed
I've traced the problem to the file /run/NetworkManager/conf.d/netplan.conf which contains the contents:
[keyfile]
# devices managed by networkd
unmanaged-devices+=interface-name:enp0s3,
If I remove the unmanaged-devices line and restart NetworkManager then it works. But since /run/ is a temporary filesystem, as soon as I reboot my changes are discarded.
I have no idea where this file is coming from, and my googlefu has failed me when it comes to figuring out how to get networkd to not take control of my ethernet port.
Any suggestions?
networking 18.04 network-manager ethernet
networking 18.04 network-manager ethernet
asked Jan 25 at 14:16
ErikErik
1011
asked Jan 25 at 14:16
ErikErik
1011
asked Jan 25 at 14:16
ErikErik
1011
asked Jan 25 at 14:16
ErikErik
1011
asked Jan 25 at 14:16
ErikErik
1011
1011
Is there a linemanaged=falsein your/etc/NetworkManager/NetworkManager.conf?
– Jos
Jan 25 at 14:26
No I already fixed that to bemanaged=true. But as I understand it, that is only matters if ifupdown is on the system, but Ubuntu Server uses netplan.
– Erik
Jan 25 at 14:27
2
Ah, actually this answer contained the solution for me: askubuntu.com/questions/1031956/…
– Erik
Jan 25 at 14:30
Actually, you should have left /etc/NetworkManager/NetworkManager.conf alone, not changed /etc/netplan/*.yaml to renderer: NetworkManager, and just edited the .yaml file in /etc/netplan and configured enp0s3 there.
– heynnema
Jan 25 at 18:57
@Erik status please
– heynnema
Jan 30 at 16:14
add a comment |
Is there a linemanaged=falsein your/etc/NetworkManager/NetworkManager.conf?
– Jos
Jan 25 at 14:26
No I already fixed that to bemanaged=true. But as I understand it, that is only matters if ifupdown is on the system, but Ubuntu Server uses netplan.
– Erik
Jan 25 at 14:27
2
Ah, actually this answer contained the solution for me: askubuntu.com/questions/1031956/…
– Erik
Jan 25 at 14:30
Actually, you should have left /etc/NetworkManager/NetworkManager.conf alone, not changed /etc/netplan/*.yaml to renderer: NetworkManager, and just edited the .yaml file in /etc/netplan and configured enp0s3 there.
– heynnema
Jan 25 at 18:57
@Erik status please
– heynnema
Jan 30 at 16:14
Is there a line
managed=false in your /etc/NetworkManager/NetworkManager.conf?– Jos
Jan 25 at 14:26
Is there a line
managed=false in your /etc/NetworkManager/NetworkManager.conf?– Jos
Jan 25 at 14:26
No I already fixed that to be
managed=true. But as I understand it, that is only matters if ifupdown is on the system, but Ubuntu Server uses netplan.– Erik
Jan 25 at 14:27
No I already fixed that to be
managed=true. But as I understand it, that is only matters if ifupdown is on the system, but Ubuntu Server uses netplan.– Erik
Jan 25 at 14:27
2
2
Ah, actually this answer contained the solution for me: askubuntu.com/questions/1031956/…
– Erik
Jan 25 at 14:30
Ah, actually this answer contained the solution for me: askubuntu.com/questions/1031956/…
– Erik
Jan 25 at 14:30
Actually, you should have left /etc/NetworkManager/NetworkManager.conf alone, not changed /etc/netplan/*.yaml to renderer: NetworkManager, and just edited the .yaml file in /etc/netplan and configured enp0s3 there.
– heynnema
Jan 25 at 18:57
Actually, you should have left /etc/NetworkManager/NetworkManager.conf alone, not changed /etc/netplan/*.yaml to renderer: NetworkManager, and just edited the .yaml file in /etc/netplan and configured enp0s3 there.
– heynnema
Jan 25 at 18:57
@Erik status please
– heynnema
Jan 30 at 16:14
@Erik status please
– heynnema
Jan 30 at 16:14
add a comment |
1 Answer
1
active
oldest
votes
As per my comment...
You should undo your changes to /etc/NetworkManager/NetworkManager.conf...
Your /etc/netplan/*.yaml file should look like this...
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: true
optional: true
followed by...
sudo netplan --debug generate
sudo netplan apply
Update #1:
If you're sticking with NetworkManager... then your /etc/netplan/*.yaml should look like this...
network:
version: 2
renderer: NetworkManager
followed by...
sudo netplan --debug generate
sudo netplan apply
answered Jan 25 at 19:02
heynnemaheynnema
19.7k22158
If renderer is networkd, wouldn't that prevent NetworkManager from managing the connection?
– Erik
Jan 30 at 17:02
@Erik yes, it's EITHER netplan OR NM, but not both. Since you're running a server, probably in a stable and unchanging environment, most servers run with netplan, hence my answer. You're running a server with a GUI added, which is somewhat unusual.
– heynnema
Jan 30 at 17:11
I'm not running a server, I just happened to have the server iso available when I was spinning up the VM and used it.
– Erik
Jan 30 at 19:23
@Erik I updated my answer.
– heynnema
Jan 30 at 20:59
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%2f1112796%2fnetworkmanager-not-managing-ethernet-device%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
As per my comment...
You should undo your changes to /etc/NetworkManager/NetworkManager.conf...
Your /etc/netplan/*.yaml file should look like this...
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: true
optional: true
followed by...
sudo netplan --debug generate
sudo netplan apply
Update #1:
If you're sticking with NetworkManager... then your /etc/netplan/*.yaml should look like this...
network:
version: 2
renderer: NetworkManager
followed by...
sudo netplan --debug generate
sudo netplan apply
answered Jan 25 at 19:02
heynnemaheynnema
19.7k22158
If renderer is networkd, wouldn't that prevent NetworkManager from managing the connection?
– Erik
Jan 30 at 17:02
@Erik yes, it's EITHER netplan OR NM, but not both. Since you're running a server, probably in a stable and unchanging environment, most servers run with netplan, hence my answer. You're running a server with a GUI added, which is somewhat unusual.
– heynnema
Jan 30 at 17:11
I'm not running a server, I just happened to have the server iso available when I was spinning up the VM and used it.
– Erik
Jan 30 at 19:23
@Erik I updated my answer.
– heynnema
Jan 30 at 20:59
add a comment |
As per my comment...
You should undo your changes to /etc/NetworkManager/NetworkManager.conf...
Your /etc/netplan/*.yaml file should look like this...
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: true
optional: true
followed by...
sudo netplan --debug generate
sudo netplan apply
Update #1:
If you're sticking with NetworkManager... then your /etc/netplan/*.yaml should look like this...
network:
version: 2
renderer: NetworkManager
followed by...
sudo netplan --debug generate
sudo netplan apply
answered Jan 25 at 19:02
heynnemaheynnema
19.7k22158
If renderer is networkd, wouldn't that prevent NetworkManager from managing the connection?
– Erik
Jan 30 at 17:02
@Erik yes, it's EITHER netplan OR NM, but not both. Since you're running a server, probably in a stable and unchanging environment, most servers run with netplan, hence my answer. You're running a server with a GUI added, which is somewhat unusual.
– heynnema
Jan 30 at 17:11
I'm not running a server, I just happened to have the server iso available when I was spinning up the VM and used it.
– Erik
Jan 30 at 19:23
@Erik I updated my answer.
– heynnema
Jan 30 at 20:59
add a comment |
As per my comment...
You should undo your changes to /etc/NetworkManager/NetworkManager.conf...
Your /etc/netplan/*.yaml file should look like this...
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: true
optional: true
followed by...
sudo netplan --debug generate
sudo netplan apply
Update #1:
If you're sticking with NetworkManager... then your /etc/netplan/*.yaml should look like this...
network:
version: 2
renderer: NetworkManager
followed by...
sudo netplan --debug generate
sudo netplan apply
answered Jan 25 at 19:02
heynnemaheynnema
19.7k22158
As per my comment...
You should undo your changes to /etc/NetworkManager/NetworkManager.conf...
Your /etc/netplan/*.yaml file should look like this...
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: true
optional: true
followed by...
sudo netplan --debug generate
sudo netplan apply
Update #1:
If you're sticking with NetworkManager... then your /etc/netplan/*.yaml should look like this...
network:
version: 2
renderer: NetworkManager
followed by...
sudo netplan --debug generate
sudo netplan apply
answered Jan 25 at 19:02
heynnemaheynnema
19.7k22158
edited Feb 2 at 4:17
answered Jan 25 at 19:02
heynnemaheynnema
19.7k22158
answered Jan 25 at 19:02
heynnemaheynnema
19.7k22158
answered Jan 25 at 19:02
heynnemaheynnema
19.7k22158
19.7k22158
If renderer is networkd, wouldn't that prevent NetworkManager from managing the connection?
– Erik
Jan 30 at 17:02
@Erik yes, it's EITHER netplan OR NM, but not both. Since you're running a server, probably in a stable and unchanging environment, most servers run with netplan, hence my answer. You're running a server with a GUI added, which is somewhat unusual.
– heynnema
Jan 30 at 17:11
I'm not running a server, I just happened to have the server iso available when I was spinning up the VM and used it.
– Erik
Jan 30 at 19:23
@Erik I updated my answer.
– heynnema
Jan 30 at 20:59
add a comment |
If renderer is networkd, wouldn't that prevent NetworkManager from managing the connection?
– Erik
Jan 30 at 17:02
@Erik yes, it's EITHER netplan OR NM, but not both. Since you're running a server, probably in a stable and unchanging environment, most servers run with netplan, hence my answer. You're running a server with a GUI added, which is somewhat unusual.
– heynnema
Jan 30 at 17:11
I'm not running a server, I just happened to have the server iso available when I was spinning up the VM and used it.
– Erik
Jan 30 at 19:23
@Erik I updated my answer.
– heynnema
Jan 30 at 20:59
If renderer is networkd, wouldn't that prevent NetworkManager from managing the connection?
– Erik
Jan 30 at 17:02
If renderer is networkd, wouldn't that prevent NetworkManager from managing the connection?
– Erik
Jan 30 at 17:02
@Erik yes, it's EITHER netplan OR NM, but not both. Since you're running a server, probably in a stable and unchanging environment, most servers run with netplan, hence my answer. You're running a server with a GUI added, which is somewhat unusual.
– heynnema
Jan 30 at 17:11
@Erik yes, it's EITHER netplan OR NM, but not both. Since you're running a server, probably in a stable and unchanging environment, most servers run with netplan, hence my answer. You're running a server with a GUI added, which is somewhat unusual.
– heynnema
Jan 30 at 17:11
I'm not running a server, I just happened to have the server iso available when I was spinning up the VM and used it.
– Erik
Jan 30 at 19:23
I'm not running a server, I just happened to have the server iso available when I was spinning up the VM and used it.
– Erik
Jan 30 at 19:23
@Erik I updated my answer.
– heynnema
Jan 30 at 20:59
@Erik I updated my answer.
– heynnema
Jan 30 at 20:59
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%2f1112796%2fnetworkmanager-not-managing-ethernet-device%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
Is there a line
managed=falsein your/etc/NetworkManager/NetworkManager.conf?– Jos
Jan 25 at 14:26
No I already fixed that to be
managed=true. But as I understand it, that is only matters if ifupdown is on the system, but Ubuntu Server uses netplan.– Erik
Jan 25 at 14:27
2
Ah, actually this answer contained the solution for me: askubuntu.com/questions/1031956/…
– Erik
Jan 25 at 14:30
Actually, you should have left /etc/NetworkManager/NetworkManager.conf alone, not changed /etc/netplan/*.yaml to renderer: NetworkManager, and just edited the .yaml file in /etc/netplan and configured enp0s3 there.
– heynnema
Jan 25 at 18:57
@Erik status please
– heynnema
Jan 30 at 16:14