Ubuntu 18.04 desktop: netplan.io+NetworkManager: wrong default route mask (0.0.0.0/24)
My yaml file is:
network:
version: 2
renderer: NetworkManager
ethernets:
enp2s0:
dhcp4: no
dhcp6: no
enp3s0:
dhcp4: no
dhcp6: no
addresses: [192.168.245.50/24]
bridges:
br0:
interfaces: [enp2s0]
dhcp4: no
dhcp6: no
addresses: [192.168.204.35/24]
nameservers:
addresses: [192.168.1.4,192.168.1.5]
search: [mydomain.xyz]
routes:
- to: 0.0.0.0/0
via: 192.168.204.1
metric: 200
type: unicast
After 'netplan apply' command i get the wrong route mask (0.0.0.0/24):
$ sudo ip route
0.0.0.0/24 via 192.168.204.1 dev br0 proto static metric 200 linkdown
169.254.0.0/16 dev enp3s0 scope link metric 1000
192.168.204.0/24 dev br0 proto kernel scope link src 192.168.204.35 metric 425 linkdown
192.168.245.0/24 dev enp3s0 proto kernel scope link src 192.168.245.50 metric 100
$ sudo ip route del 0.0.0.0/24
$ sudo ip route add 0.0.0.0/0 via 192.168.204.1 dev br0 proto static metric 200
$ sudo ip route
default via 192.168.204.1 dev br0 proto static metric 200
....
When I specify the correct route (see above), the interface goes up and the network becomes available. After reboot the wrong route appears again.
What to do?
networking network-manager network-bridge netplan
asked Oct 26 '18 at 14:26
Yuri FedkinYuri Fedkin
1
add a comment |
My yaml file is:
network:
version: 2
renderer: NetworkManager
ethernets:
enp2s0:
dhcp4: no
dhcp6: no
enp3s0:
dhcp4: no
dhcp6: no
addresses: [192.168.245.50/24]
bridges:
br0:
interfaces: [enp2s0]
dhcp4: no
dhcp6: no
addresses: [192.168.204.35/24]
nameservers:
addresses: [192.168.1.4,192.168.1.5]
search: [mydomain.xyz]
routes:
- to: 0.0.0.0/0
via: 192.168.204.1
metric: 200
type: unicast
After 'netplan apply' command i get the wrong route mask (0.0.0.0/24):
$ sudo ip route
0.0.0.0/24 via 192.168.204.1 dev br0 proto static metric 200 linkdown
169.254.0.0/16 dev enp3s0 scope link metric 1000
192.168.204.0/24 dev br0 proto kernel scope link src 192.168.204.35 metric 425 linkdown
192.168.245.0/24 dev enp3s0 proto kernel scope link src 192.168.245.50 metric 100
$ sudo ip route del 0.0.0.0/24
$ sudo ip route add 0.0.0.0/0 via 192.168.204.1 dev br0 proto static metric 200
$ sudo ip route
default via 192.168.204.1 dev br0 proto static metric 200
....
When I specify the correct route (see above), the interface goes up and the network becomes available. After reboot the wrong route appears again.
What to do?
networking network-manager network-bridge netplan
asked Oct 26 '18 at 14:26
Yuri FedkinYuri Fedkin
1
You have to do asudo netplan --debug generatebefore thesudo netplan apply. But you probably should be using networkd instead of NetworkManager. Is this a server? Report back to @heynnema
– heynnema
Oct 26 '18 at 15:15
Hi, @heynnema! I use desktop version. Execution ofsudo netplan --debug generatebefore thesudo netplan applydon't take effect. @Yuri Fedkin
– Yuri Fedkin
Oct 29 '18 at 7:19
add a comment |
My yaml file is:
network:
version: 2
renderer: NetworkManager
ethernets:
enp2s0:
dhcp4: no
dhcp6: no
enp3s0:
dhcp4: no
dhcp6: no
addresses: [192.168.245.50/24]
bridges:
br0:
interfaces: [enp2s0]
dhcp4: no
dhcp6: no
addresses: [192.168.204.35/24]
nameservers:
addresses: [192.168.1.4,192.168.1.5]
search: [mydomain.xyz]
routes:
- to: 0.0.0.0/0
via: 192.168.204.1
metric: 200
type: unicast
After 'netplan apply' command i get the wrong route mask (0.0.0.0/24):
$ sudo ip route
0.0.0.0/24 via 192.168.204.1 dev br0 proto static metric 200 linkdown
169.254.0.0/16 dev enp3s0 scope link metric 1000
192.168.204.0/24 dev br0 proto kernel scope link src 192.168.204.35 metric 425 linkdown
192.168.245.0/24 dev enp3s0 proto kernel scope link src 192.168.245.50 metric 100
$ sudo ip route del 0.0.0.0/24
$ sudo ip route add 0.0.0.0/0 via 192.168.204.1 dev br0 proto static metric 200
$ sudo ip route
default via 192.168.204.1 dev br0 proto static metric 200
....
When I specify the correct route (see above), the interface goes up and the network becomes available. After reboot the wrong route appears again.
What to do?
networking network-manager network-bridge netplan
asked Oct 26 '18 at 14:26
Yuri FedkinYuri Fedkin
1
My yaml file is:
network:
version: 2
renderer: NetworkManager
ethernets:
enp2s0:
dhcp4: no
dhcp6: no
enp3s0:
dhcp4: no
dhcp6: no
addresses: [192.168.245.50/24]
bridges:
br0:
interfaces: [enp2s0]
dhcp4: no
dhcp6: no
addresses: [192.168.204.35/24]
nameservers:
addresses: [192.168.1.4,192.168.1.5]
search: [mydomain.xyz]
routes:
- to: 0.0.0.0/0
via: 192.168.204.1
metric: 200
type: unicast
After 'netplan apply' command i get the wrong route mask (0.0.0.0/24):
$ sudo ip route
0.0.0.0/24 via 192.168.204.1 dev br0 proto static metric 200 linkdown
169.254.0.0/16 dev enp3s0 scope link metric 1000
192.168.204.0/24 dev br0 proto kernel scope link src 192.168.204.35 metric 425 linkdown
192.168.245.0/24 dev enp3s0 proto kernel scope link src 192.168.245.50 metric 100
$ sudo ip route del 0.0.0.0/24
$ sudo ip route add 0.0.0.0/0 via 192.168.204.1 dev br0 proto static metric 200
$ sudo ip route
default via 192.168.204.1 dev br0 proto static metric 200
....
When I specify the correct route (see above), the interface goes up and the network becomes available. After reboot the wrong route appears again.
What to do?
networking network-manager network-bridge netplan
networking network-manager network-bridge netplan
asked Oct 26 '18 at 14:26
Yuri FedkinYuri Fedkin
1
asked Oct 26 '18 at 14:26
Yuri FedkinYuri Fedkin
1
asked Oct 26 '18 at 14:26
Yuri FedkinYuri Fedkin
1
asked Oct 26 '18 at 14:26
Yuri FedkinYuri Fedkin
1
asked Oct 26 '18 at 14:26
Yuri FedkinYuri Fedkin
1
1
You have to do asudo netplan --debug generatebefore thesudo netplan apply. But you probably should be using networkd instead of NetworkManager. Is this a server? Report back to @heynnema
– heynnema
Oct 26 '18 at 15:15
Hi, @heynnema! I use desktop version. Execution ofsudo netplan --debug generatebefore thesudo netplan applydon't take effect. @Yuri Fedkin
– Yuri Fedkin
Oct 29 '18 at 7:19
add a comment |
You have to do asudo netplan --debug generatebefore thesudo netplan apply. But you probably should be using networkd instead of NetworkManager. Is this a server? Report back to @heynnema
– heynnema
Oct 26 '18 at 15:15
Hi, @heynnema! I use desktop version. Execution ofsudo netplan --debug generatebefore thesudo netplan applydon't take effect. @Yuri Fedkin
– Yuri Fedkin
Oct 29 '18 at 7:19
You have to do a
sudo netplan --debug generate before the sudo netplan apply. But you probably should be using networkd instead of NetworkManager. Is this a server? Report back to @heynnema– heynnema
Oct 26 '18 at 15:15
You have to do a
sudo netplan --debug generate before the sudo netplan apply. But you probably should be using networkd instead of NetworkManager. Is this a server? Report back to @heynnema– heynnema
Oct 26 '18 at 15:15
Hi, @heynnema! I use desktop version. Execution of
sudo netplan --debug generate before the sudo netplan apply don't take effect. @Yuri Fedkin– Yuri Fedkin
Oct 29 '18 at 7:19
Hi, @heynnema! I use desktop version. Execution of
sudo netplan --debug generate before the sudo netplan apply don't take effect. @Yuri Fedkin– Yuri Fedkin
Oct 29 '18 at 7:19
add a comment |
1 Answer
1
active
oldest
votes
Notes:
Check the gateway4 address and DNS nameserver/search values that I used. I'm not sure if having them on different subnets from the main IP addresses will cause DNS resolution errors.
If you don't need the bridge, you can move the addresses: and routes: stanza's directly into enp2s0 (under dhcp6), and remove the bridges: section. Be mindful of the indentation.
If you copy/paste the script, you may need to remove the leading 4 spaces from each line. This is because when I use the {} code sample to make the script readable, it adds 4 spaces to the beginning of each line. Keep the indentation the same.
If you don't have any wireless interfaces, you may need to change NetworkManager to networkd.
Use https://netplan.io/examples for more examples.
After installing the script (as the only .yaml file) into /etc/netplan do:
sudo netplan --debug generate
sudo netplan apply
reboot
network:
version: 2
renderer: networkd
ethernets:
enp2s0:
dhcp4: no
dhcp6: no
nameservers:
addresses: [192.168.1.4,192.168.1.5]
search: [mydomain.xyz]
optional: true
enp3s0:
dhcp4: no
dhcp6: no
addresses: [192.168.245.50/24]
gateway4: 192.168.245.1
nameservers:
addresses: [192.168.1.4,192.168.1.5]
search: [mydomain.xyz]
optional: true
bridges:
br0:
interfaces: [enp2s0]
addresses: [192.168.204.35/24]
routes:
- to: 0.0.0.0/0
via: 192.168.204.1
metric: 200
type: unicast
answered Oct 29 '18 at 13:56
heynnemaheynnema
18.7k22155
Hi, @heynnema! When I apply your yaml script and reboot PC I've got linkdown state forbr0interface and0.0.0.0/24as default route.
– Yuri Fedkin
Oct 30 '18 at 13:37
Do you have wireless networks on this machine? Did you remove the leading 4 spaces from each line, if that was required? Did you keep the indentation the same? Did the generate command issue any errors?
– heynnema
Oct 30 '18 at 13:43
I think that this problem lies in NetworkManager area. Wheh I runnm-connection-editorchoosebr0interface and click on routes button on IPv4-tab I see error on route. The cell with address 0.0.0.0 is marked with red color and mask is set to 255.255.255.0. When i try to correct mask to 0.0.0.0 the cell becames red, too.
– Yuri Fedkin
Oct 30 '18 at 13:48
I haven't any wi-fi interface. As you see above I follow to indent recomendations.
– Yuri Fedkin
Oct 30 '18 at 13:50
@YuriFedkin first, try changing NetworkManager to networkd, redo the two netplan commands, and see if that helps. Second, if that doesn't help, you can try moving the addresses and routes from br0 to enp2s0, right under the dhcp6 line. Report back, and I can edit the answer if either change works.
– heynnema
Oct 30 '18 at 13:54
|
show 5 more comments
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%2f1087473%2fubuntu-18-04-desktop-netplan-ionetworkmanager-wrong-default-route-mask-0-0-0%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
Notes:
Check the gateway4 address and DNS nameserver/search values that I used. I'm not sure if having them on different subnets from the main IP addresses will cause DNS resolution errors.
If you don't need the bridge, you can move the addresses: and routes: stanza's directly into enp2s0 (under dhcp6), and remove the bridges: section. Be mindful of the indentation.
If you copy/paste the script, you may need to remove the leading 4 spaces from each line. This is because when I use the {} code sample to make the script readable, it adds 4 spaces to the beginning of each line. Keep the indentation the same.
If you don't have any wireless interfaces, you may need to change NetworkManager to networkd.
Use https://netplan.io/examples for more examples.
After installing the script (as the only .yaml file) into /etc/netplan do:
sudo netplan --debug generate
sudo netplan apply
reboot
network:
version: 2
renderer: networkd
ethernets:
enp2s0:
dhcp4: no
dhcp6: no
nameservers:
addresses: [192.168.1.4,192.168.1.5]
search: [mydomain.xyz]
optional: true
enp3s0:
dhcp4: no
dhcp6: no
addresses: [192.168.245.50/24]
gateway4: 192.168.245.1
nameservers:
addresses: [192.168.1.4,192.168.1.5]
search: [mydomain.xyz]
optional: true
bridges:
br0:
interfaces: [enp2s0]
addresses: [192.168.204.35/24]
routes:
- to: 0.0.0.0/0
via: 192.168.204.1
metric: 200
type: unicast
answered Oct 29 '18 at 13:56
heynnemaheynnema
18.7k22155
Hi, @heynnema! When I apply your yaml script and reboot PC I've got linkdown state forbr0interface and0.0.0.0/24as default route.
– Yuri Fedkin
Oct 30 '18 at 13:37
Do you have wireless networks on this machine? Did you remove the leading 4 spaces from each line, if that was required? Did you keep the indentation the same? Did the generate command issue any errors?
– heynnema
Oct 30 '18 at 13:43
I think that this problem lies in NetworkManager area. Wheh I runnm-connection-editorchoosebr0interface and click on routes button on IPv4-tab I see error on route. The cell with address 0.0.0.0 is marked with red color and mask is set to 255.255.255.0. When i try to correct mask to 0.0.0.0 the cell becames red, too.
– Yuri Fedkin
Oct 30 '18 at 13:48
I haven't any wi-fi interface. As you see above I follow to indent recomendations.
– Yuri Fedkin
Oct 30 '18 at 13:50
@YuriFedkin first, try changing NetworkManager to networkd, redo the two netplan commands, and see if that helps. Second, if that doesn't help, you can try moving the addresses and routes from br0 to enp2s0, right under the dhcp6 line. Report back, and I can edit the answer if either change works.
– heynnema
Oct 30 '18 at 13:54
|
show 5 more comments
Notes:
Check the gateway4 address and DNS nameserver/search values that I used. I'm not sure if having them on different subnets from the main IP addresses will cause DNS resolution errors.
If you don't need the bridge, you can move the addresses: and routes: stanza's directly into enp2s0 (under dhcp6), and remove the bridges: section. Be mindful of the indentation.
If you copy/paste the script, you may need to remove the leading 4 spaces from each line. This is because when I use the {} code sample to make the script readable, it adds 4 spaces to the beginning of each line. Keep the indentation the same.
If you don't have any wireless interfaces, you may need to change NetworkManager to networkd.
Use https://netplan.io/examples for more examples.
After installing the script (as the only .yaml file) into /etc/netplan do:
sudo netplan --debug generate
sudo netplan apply
reboot
network:
version: 2
renderer: networkd
ethernets:
enp2s0:
dhcp4: no
dhcp6: no
nameservers:
addresses: [192.168.1.4,192.168.1.5]
search: [mydomain.xyz]
optional: true
enp3s0:
dhcp4: no
dhcp6: no
addresses: [192.168.245.50/24]
gateway4: 192.168.245.1
nameservers:
addresses: [192.168.1.4,192.168.1.5]
search: [mydomain.xyz]
optional: true
bridges:
br0:
interfaces: [enp2s0]
addresses: [192.168.204.35/24]
routes:
- to: 0.0.0.0/0
via: 192.168.204.1
metric: 200
type: unicast
answered Oct 29 '18 at 13:56
heynnemaheynnema
18.7k22155
Hi, @heynnema! When I apply your yaml script and reboot PC I've got linkdown state forbr0interface and0.0.0.0/24as default route.
– Yuri Fedkin
Oct 30 '18 at 13:37
Do you have wireless networks on this machine? Did you remove the leading 4 spaces from each line, if that was required? Did you keep the indentation the same? Did the generate command issue any errors?
– heynnema
Oct 30 '18 at 13:43
I think that this problem lies in NetworkManager area. Wheh I runnm-connection-editorchoosebr0interface and click on routes button on IPv4-tab I see error on route. The cell with address 0.0.0.0 is marked with red color and mask is set to 255.255.255.0. When i try to correct mask to 0.0.0.0 the cell becames red, too.
– Yuri Fedkin
Oct 30 '18 at 13:48
I haven't any wi-fi interface. As you see above I follow to indent recomendations.
– Yuri Fedkin
Oct 30 '18 at 13:50
@YuriFedkin first, try changing NetworkManager to networkd, redo the two netplan commands, and see if that helps. Second, if that doesn't help, you can try moving the addresses and routes from br0 to enp2s0, right under the dhcp6 line. Report back, and I can edit the answer if either change works.
– heynnema
Oct 30 '18 at 13:54
|
show 5 more comments
Notes:
Check the gateway4 address and DNS nameserver/search values that I used. I'm not sure if having them on different subnets from the main IP addresses will cause DNS resolution errors.
If you don't need the bridge, you can move the addresses: and routes: stanza's directly into enp2s0 (under dhcp6), and remove the bridges: section. Be mindful of the indentation.
If you copy/paste the script, you may need to remove the leading 4 spaces from each line. This is because when I use the {} code sample to make the script readable, it adds 4 spaces to the beginning of each line. Keep the indentation the same.
If you don't have any wireless interfaces, you may need to change NetworkManager to networkd.
Use https://netplan.io/examples for more examples.
After installing the script (as the only .yaml file) into /etc/netplan do:
sudo netplan --debug generate
sudo netplan apply
reboot
network:
version: 2
renderer: networkd
ethernets:
enp2s0:
dhcp4: no
dhcp6: no
nameservers:
addresses: [192.168.1.4,192.168.1.5]
search: [mydomain.xyz]
optional: true
enp3s0:
dhcp4: no
dhcp6: no
addresses: [192.168.245.50/24]
gateway4: 192.168.245.1
nameservers:
addresses: [192.168.1.4,192.168.1.5]
search: [mydomain.xyz]
optional: true
bridges:
br0:
interfaces: [enp2s0]
addresses: [192.168.204.35/24]
routes:
- to: 0.0.0.0/0
via: 192.168.204.1
metric: 200
type: unicast
answered Oct 29 '18 at 13:56
heynnemaheynnema
18.7k22155
Notes:
Check the gateway4 address and DNS nameserver/search values that I used. I'm not sure if having them on different subnets from the main IP addresses will cause DNS resolution errors.
If you don't need the bridge, you can move the addresses: and routes: stanza's directly into enp2s0 (under dhcp6), and remove the bridges: section. Be mindful of the indentation.
If you copy/paste the script, you may need to remove the leading 4 spaces from each line. This is because when I use the {} code sample to make the script readable, it adds 4 spaces to the beginning of each line. Keep the indentation the same.
If you don't have any wireless interfaces, you may need to change NetworkManager to networkd.
Use https://netplan.io/examples for more examples.
After installing the script (as the only .yaml file) into /etc/netplan do:
sudo netplan --debug generate
sudo netplan apply
reboot
network:
version: 2
renderer: networkd
ethernets:
enp2s0:
dhcp4: no
dhcp6: no
nameservers:
addresses: [192.168.1.4,192.168.1.5]
search: [mydomain.xyz]
optional: true
enp3s0:
dhcp4: no
dhcp6: no
addresses: [192.168.245.50/24]
gateway4: 192.168.245.1
nameservers:
addresses: [192.168.1.4,192.168.1.5]
search: [mydomain.xyz]
optional: true
bridges:
br0:
interfaces: [enp2s0]
addresses: [192.168.204.35/24]
routes:
- to: 0.0.0.0/0
via: 192.168.204.1
metric: 200
type: unicast
answered Oct 29 '18 at 13:56
heynnemaheynnema
18.7k22155
edited 22 mins ago
answered Oct 29 '18 at 13:56
heynnemaheynnema
18.7k22155
answered Oct 29 '18 at 13:56
heynnemaheynnema
18.7k22155
answered Oct 29 '18 at 13:56
heynnemaheynnema
18.7k22155
18.7k22155
Hi, @heynnema! When I apply your yaml script and reboot PC I've got linkdown state forbr0interface and0.0.0.0/24as default route.
– Yuri Fedkin
Oct 30 '18 at 13:37
Do you have wireless networks on this machine? Did you remove the leading 4 spaces from each line, if that was required? Did you keep the indentation the same? Did the generate command issue any errors?
– heynnema
Oct 30 '18 at 13:43
I think that this problem lies in NetworkManager area. Wheh I runnm-connection-editorchoosebr0interface and click on routes button on IPv4-tab I see error on route. The cell with address 0.0.0.0 is marked with red color and mask is set to 255.255.255.0. When i try to correct mask to 0.0.0.0 the cell becames red, too.
– Yuri Fedkin
Oct 30 '18 at 13:48
I haven't any wi-fi interface. As you see above I follow to indent recomendations.
– Yuri Fedkin
Oct 30 '18 at 13:50
@YuriFedkin first, try changing NetworkManager to networkd, redo the two netplan commands, and see if that helps. Second, if that doesn't help, you can try moving the addresses and routes from br0 to enp2s0, right under the dhcp6 line. Report back, and I can edit the answer if either change works.
– heynnema
Oct 30 '18 at 13:54
|
show 5 more comments
Hi, @heynnema! When I apply your yaml script and reboot PC I've got linkdown state forbr0interface and0.0.0.0/24as default route.
– Yuri Fedkin
Oct 30 '18 at 13:37
Do you have wireless networks on this machine? Did you remove the leading 4 spaces from each line, if that was required? Did you keep the indentation the same? Did the generate command issue any errors?
– heynnema
Oct 30 '18 at 13:43
I think that this problem lies in NetworkManager area. Wheh I runnm-connection-editorchoosebr0interface and click on routes button on IPv4-tab I see error on route. The cell with address 0.0.0.0 is marked with red color and mask is set to 255.255.255.0. When i try to correct mask to 0.0.0.0 the cell becames red, too.
– Yuri Fedkin
Oct 30 '18 at 13:48
I haven't any wi-fi interface. As you see above I follow to indent recomendations.
– Yuri Fedkin
Oct 30 '18 at 13:50
@YuriFedkin first, try changing NetworkManager to networkd, redo the two netplan commands, and see if that helps. Second, if that doesn't help, you can try moving the addresses and routes from br0 to enp2s0, right under the dhcp6 line. Report back, and I can edit the answer if either change works.
– heynnema
Oct 30 '18 at 13:54
Hi, @heynnema! When I apply your yaml script and reboot PC I've got linkdown state for
br0 interface and 0.0.0.0/24 as default route.– Yuri Fedkin
Oct 30 '18 at 13:37
Hi, @heynnema! When I apply your yaml script and reboot PC I've got linkdown state for
br0 interface and 0.0.0.0/24 as default route.– Yuri Fedkin
Oct 30 '18 at 13:37
Do you have wireless networks on this machine? Did you remove the leading 4 spaces from each line, if that was required? Did you keep the indentation the same? Did the generate command issue any errors?
– heynnema
Oct 30 '18 at 13:43
Do you have wireless networks on this machine? Did you remove the leading 4 spaces from each line, if that was required? Did you keep the indentation the same? Did the generate command issue any errors?
– heynnema
Oct 30 '18 at 13:43
I think that this problem lies in NetworkManager area. Wheh I run
nm-connection-editor choose br0 interface and click on routes button on IPv4-tab I see error on route. The cell with address 0.0.0.0 is marked with red color and mask is set to 255.255.255.0. When i try to correct mask to 0.0.0.0 the cell becames red, too.– Yuri Fedkin
Oct 30 '18 at 13:48
I think that this problem lies in NetworkManager area. Wheh I run
nm-connection-editor choose br0 interface and click on routes button on IPv4-tab I see error on route. The cell with address 0.0.0.0 is marked with red color and mask is set to 255.255.255.0. When i try to correct mask to 0.0.0.0 the cell becames red, too.– Yuri Fedkin
Oct 30 '18 at 13:48
I haven't any wi-fi interface. As you see above I follow to indent recomendations.
– Yuri Fedkin
Oct 30 '18 at 13:50
I haven't any wi-fi interface. As you see above I follow to indent recomendations.
– Yuri Fedkin
Oct 30 '18 at 13:50
@YuriFedkin first, try changing NetworkManager to networkd, redo the two netplan commands, and see if that helps. Second, if that doesn't help, you can try moving the addresses and routes from br0 to enp2s0, right under the dhcp6 line. Report back, and I can edit the answer if either change works.
– heynnema
Oct 30 '18 at 13:54
@YuriFedkin first, try changing NetworkManager to networkd, redo the two netplan commands, and see if that helps. Second, if that doesn't help, you can try moving the addresses and routes from br0 to enp2s0, right under the dhcp6 line. Report back, and I can edit the answer if either change works.
– heynnema
Oct 30 '18 at 13:54
|
show 5 more comments
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%2f1087473%2fubuntu-18-04-desktop-netplan-ionetworkmanager-wrong-default-route-mask-0-0-0%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
You have to do a
sudo netplan --debug generatebefore thesudo netplan apply. But you probably should be using networkd instead of NetworkManager. Is this a server? Report back to @heynnema– heynnema
Oct 26 '18 at 15:15
Hi, @heynnema! I use desktop version. Execution of
sudo netplan --debug generatebefore thesudo netplan applydon't take effect. @Yuri Fedkin– Yuri Fedkin
Oct 29 '18 at 7:19