Bonding done but no internet connection in ubuntu 18.04
We have used the following in the /etc/netplan/
In 01-netcfg.yaml file
network:
version: 2
renderer: networkd
ethernets:
enp1s0:
match:
macaddress: 00:21:85:c7:d5:81
enp5s0:
match:
macaddress: 00:e0:4d:08:1f:7a
In 02-bondings.yaml file
network:
version: 2
renderer: networkd
bonds:
bond0:
interfaces: [enp1s0,enp5s0]
addresses: [192.168.2.100/24]
gateway4: 192.168.2.1
parameters:
mode: active-backup
mii-monitor-interval: 100
lacp-rate: fast
mtu: 1500
nameservers:
addresses: [198.168.0.250]
There is no error in debug of the netplan, but
there is no internet connectivity.
If we give ifconfig -a
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet 192.168.2.100 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::1ccf:81ff:fe56:ba5a prefixlen 64 scopeid 0x20<link>
ether 1e:cf:81:56:ba:5a txqueuelen 1000 (Ethernet)
RX packets 365 bytes 32687 (32.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 551 bytes 38956 (38.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp1s0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether 1e:cf:81:56:ba:5a txqueuelen 1000 (Ethernet)
RX packets 331 bytes 28909 (28.9 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp5s0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether 1e:cf:81:56:ba:5a txqueuelen 1000 (Ethernet)
RX packets 34 bytes 3778 (3.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 551 bytes 38956 (38.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 1101 bytes 89766 (89.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1101 bytes 89766 (89.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
We have also tried this link also, but the same result
https://gist.github.com/PhilipSchmid/54e17f53c15e3bd2c922ec6ff9ee434f
If we give
ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000
link/ether 1e:cf:81:56:ba:5a brd ff:ff:ff:ff:ff:ff
3: enp5s0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bond0 state UNKNOWN group default qlen 1000
link/ether 1e:cf:81:56:ba:5a brd ff:ff:ff:ff:ff:ff
4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 1e:cf:81:56:ba:5a brd ff:ff:ff:ff:ff:ff
inet 192.168.2.100/24 brd 192.168.2.255 scope global bond0
valid_lft forever preferred_lft forever
inet6 fe80::1ccf:81ff:fe56:ba5a/64 scope link
valid_lft forever preferred_lft forever
18.04
|
show 8 more comments
We have used the following in the /etc/netplan/
In 01-netcfg.yaml file
network:
version: 2
renderer: networkd
ethernets:
enp1s0:
match:
macaddress: 00:21:85:c7:d5:81
enp5s0:
match:
macaddress: 00:e0:4d:08:1f:7a
In 02-bondings.yaml file
network:
version: 2
renderer: networkd
bonds:
bond0:
interfaces: [enp1s0,enp5s0]
addresses: [192.168.2.100/24]
gateway4: 192.168.2.1
parameters:
mode: active-backup
mii-monitor-interval: 100
lacp-rate: fast
mtu: 1500
nameservers:
addresses: [198.168.0.250]
There is no error in debug of the netplan, but
there is no internet connectivity.
If we give ifconfig -a
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet 192.168.2.100 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::1ccf:81ff:fe56:ba5a prefixlen 64 scopeid 0x20<link>
ether 1e:cf:81:56:ba:5a txqueuelen 1000 (Ethernet)
RX packets 365 bytes 32687 (32.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 551 bytes 38956 (38.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp1s0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether 1e:cf:81:56:ba:5a txqueuelen 1000 (Ethernet)
RX packets 331 bytes 28909 (28.9 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp5s0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether 1e:cf:81:56:ba:5a txqueuelen 1000 (Ethernet)
RX packets 34 bytes 3778 (3.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 551 bytes 38956 (38.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 1101 bytes 89766 (89.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1101 bytes 89766 (89.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
We have also tried this link also, but the same result
https://gist.github.com/PhilipSchmid/54e17f53c15e3bd2c922ec6ff9ee434f
If we give
ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000
link/ether 1e:cf:81:56:ba:5a brd ff:ff:ff:ff:ff:ff
3: enp5s0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bond0 state UNKNOWN group default qlen 1000
link/ether 1e:cf:81:56:ba:5a brd ff:ff:ff:ff:ff:ff
4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 1e:cf:81:56:ba:5a brd ff:ff:ff:ff:ff:ff
inet 192.168.2.100/24 brd 192.168.2.255 scope global bond0
valid_lft forever preferred_lft forever
inet6 fe80::1ccf:81ff:fe56:ba5a/64 scope link
valid_lft forever preferred_lft forever
18.04
pleas provide also "ip addr show"
– AtomiX84
Jan 4 at 14:32
@AtomiX84: ip addr show added in the question
– Purushothaman
Jan 4 at 14:35
@Purushothman if you try to set enp5s0 link up? "ip link set enp5s0 up"
– AtomiX84
Jan 4 at 14:38
@AtomiX84: RTNETLINK ANSWERS: Operation not permitted. hence sudo ip link set enp5s0 up, still the internet connection is down
– Purushothaman
Jan 4 at 14:44
I find out this bugs on launchpad ( link you to the working config): bugs.launchpad.net/ubuntu/+source/systemd/+bug/1753431/comments/… what seems different in that configuration is that him declare the interfaces also in /etc/network/interface file, then configure it with netplan.
– AtomiX84
Jan 4 at 14:45
|
show 8 more comments
We have used the following in the /etc/netplan/
In 01-netcfg.yaml file
network:
version: 2
renderer: networkd
ethernets:
enp1s0:
match:
macaddress: 00:21:85:c7:d5:81
enp5s0:
match:
macaddress: 00:e0:4d:08:1f:7a
In 02-bondings.yaml file
network:
version: 2
renderer: networkd
bonds:
bond0:
interfaces: [enp1s0,enp5s0]
addresses: [192.168.2.100/24]
gateway4: 192.168.2.1
parameters:
mode: active-backup
mii-monitor-interval: 100
lacp-rate: fast
mtu: 1500
nameservers:
addresses: [198.168.0.250]
There is no error in debug of the netplan, but
there is no internet connectivity.
If we give ifconfig -a
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet 192.168.2.100 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::1ccf:81ff:fe56:ba5a prefixlen 64 scopeid 0x20<link>
ether 1e:cf:81:56:ba:5a txqueuelen 1000 (Ethernet)
RX packets 365 bytes 32687 (32.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 551 bytes 38956 (38.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp1s0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether 1e:cf:81:56:ba:5a txqueuelen 1000 (Ethernet)
RX packets 331 bytes 28909 (28.9 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp5s0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether 1e:cf:81:56:ba:5a txqueuelen 1000 (Ethernet)
RX packets 34 bytes 3778 (3.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 551 bytes 38956 (38.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 1101 bytes 89766 (89.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1101 bytes 89766 (89.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
We have also tried this link also, but the same result
https://gist.github.com/PhilipSchmid/54e17f53c15e3bd2c922ec6ff9ee434f
If we give
ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000
link/ether 1e:cf:81:56:ba:5a brd ff:ff:ff:ff:ff:ff
3: enp5s0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bond0 state UNKNOWN group default qlen 1000
link/ether 1e:cf:81:56:ba:5a brd ff:ff:ff:ff:ff:ff
4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 1e:cf:81:56:ba:5a brd ff:ff:ff:ff:ff:ff
inet 192.168.2.100/24 brd 192.168.2.255 scope global bond0
valid_lft forever preferred_lft forever
inet6 fe80::1ccf:81ff:fe56:ba5a/64 scope link
valid_lft forever preferred_lft forever
18.04
We have used the following in the /etc/netplan/
In 01-netcfg.yaml file
network:
version: 2
renderer: networkd
ethernets:
enp1s0:
match:
macaddress: 00:21:85:c7:d5:81
enp5s0:
match:
macaddress: 00:e0:4d:08:1f:7a
In 02-bondings.yaml file
network:
version: 2
renderer: networkd
bonds:
bond0:
interfaces: [enp1s0,enp5s0]
addresses: [192.168.2.100/24]
gateway4: 192.168.2.1
parameters:
mode: active-backup
mii-monitor-interval: 100
lacp-rate: fast
mtu: 1500
nameservers:
addresses: [198.168.0.250]
There is no error in debug of the netplan, but
there is no internet connectivity.
If we give ifconfig -a
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet 192.168.2.100 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::1ccf:81ff:fe56:ba5a prefixlen 64 scopeid 0x20<link>
ether 1e:cf:81:56:ba:5a txqueuelen 1000 (Ethernet)
RX packets 365 bytes 32687 (32.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 551 bytes 38956 (38.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp1s0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether 1e:cf:81:56:ba:5a txqueuelen 1000 (Ethernet)
RX packets 331 bytes 28909 (28.9 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp5s0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether 1e:cf:81:56:ba:5a txqueuelen 1000 (Ethernet)
RX packets 34 bytes 3778 (3.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 551 bytes 38956 (38.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 1101 bytes 89766 (89.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1101 bytes 89766 (89.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
We have also tried this link also, but the same result
https://gist.github.com/PhilipSchmid/54e17f53c15e3bd2c922ec6ff9ee434f
If we give
ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000
link/ether 1e:cf:81:56:ba:5a brd ff:ff:ff:ff:ff:ff
3: enp5s0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bond0 state UNKNOWN group default qlen 1000
link/ether 1e:cf:81:56:ba:5a brd ff:ff:ff:ff:ff:ff
4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 1e:cf:81:56:ba:5a brd ff:ff:ff:ff:ff:ff
inet 192.168.2.100/24 brd 192.168.2.255 scope global bond0
valid_lft forever preferred_lft forever
inet6 fe80::1ccf:81ff:fe56:ba5a/64 scope link
valid_lft forever preferred_lft forever
18.04
18.04
edited Jan 4 at 14:35
Purushothaman
asked Jan 4 at 14:28
PurushothamanPurushothaman
61112
61112
pleas provide also "ip addr show"
– AtomiX84
Jan 4 at 14:32
@AtomiX84: ip addr show added in the question
– Purushothaman
Jan 4 at 14:35
@Purushothman if you try to set enp5s0 link up? "ip link set enp5s0 up"
– AtomiX84
Jan 4 at 14:38
@AtomiX84: RTNETLINK ANSWERS: Operation not permitted. hence sudo ip link set enp5s0 up, still the internet connection is down
– Purushothaman
Jan 4 at 14:44
I find out this bugs on launchpad ( link you to the working config): bugs.launchpad.net/ubuntu/+source/systemd/+bug/1753431/comments/… what seems different in that configuration is that him declare the interfaces also in /etc/network/interface file, then configure it with netplan.
– AtomiX84
Jan 4 at 14:45
|
show 8 more comments
pleas provide also "ip addr show"
– AtomiX84
Jan 4 at 14:32
@AtomiX84: ip addr show added in the question
– Purushothaman
Jan 4 at 14:35
@Purushothman if you try to set enp5s0 link up? "ip link set enp5s0 up"
– AtomiX84
Jan 4 at 14:38
@AtomiX84: RTNETLINK ANSWERS: Operation not permitted. hence sudo ip link set enp5s0 up, still the internet connection is down
– Purushothaman
Jan 4 at 14:44
I find out this bugs on launchpad ( link you to the working config): bugs.launchpad.net/ubuntu/+source/systemd/+bug/1753431/comments/… what seems different in that configuration is that him declare the interfaces also in /etc/network/interface file, then configure it with netplan.
– AtomiX84
Jan 4 at 14:45
pleas provide also "ip addr show"
– AtomiX84
Jan 4 at 14:32
pleas provide also "ip addr show"
– AtomiX84
Jan 4 at 14:32
@AtomiX84: ip addr show added in the question
– Purushothaman
Jan 4 at 14:35
@AtomiX84: ip addr show added in the question
– Purushothaman
Jan 4 at 14:35
@Purushothman if you try to set enp5s0 link up? "ip link set enp5s0 up"
– AtomiX84
Jan 4 at 14:38
@Purushothman if you try to set enp5s0 link up? "ip link set enp5s0 up"
– AtomiX84
Jan 4 at 14:38
@AtomiX84: RTNETLINK ANSWERS: Operation not permitted. hence sudo ip link set enp5s0 up, still the internet connection is down
– Purushothaman
Jan 4 at 14:44
@AtomiX84: RTNETLINK ANSWERS: Operation not permitted. hence sudo ip link set enp5s0 up, still the internet connection is down
– Purushothaman
Jan 4 at 14:44
I find out this bugs on launchpad ( link you to the working config): bugs.launchpad.net/ubuntu/+source/systemd/+bug/1753431/comments/… what seems different in that configuration is that him declare the interfaces also in /etc/network/interface file, then configure it with netplan.
– AtomiX84
Jan 4 at 14:45
I find out this bugs on launchpad ( link you to the working config): bugs.launchpad.net/ubuntu/+source/systemd/+bug/1753431/comments/… what seems different in that configuration is that him declare the interfaces also in /etc/network/interface file, then configure it with netplan.
– AtomiX84
Jan 4 at 14:45
|
show 8 more comments
0
active
oldest
votes
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%2f1106934%2fbonding-done-but-no-internet-connection-in-ubuntu-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f1106934%2fbonding-done-but-no-internet-connection-in-ubuntu-18-04%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
pleas provide also "ip addr show"
– AtomiX84
Jan 4 at 14:32
@AtomiX84: ip addr show added in the question
– Purushothaman
Jan 4 at 14:35
@Purushothman if you try to set enp5s0 link up? "ip link set enp5s0 up"
– AtomiX84
Jan 4 at 14:38
@AtomiX84: RTNETLINK ANSWERS: Operation not permitted. hence sudo ip link set enp5s0 up, still the internet connection is down
– Purushothaman
Jan 4 at 14:44
I find out this bugs on launchpad ( link you to the working config): bugs.launchpad.net/ubuntu/+source/systemd/+bug/1753431/comments/… what seems different in that configuration is that him declare the interfaces also in /etc/network/interface file, then configure it with netplan.
– AtomiX84
Jan 4 at 14:45