[ubuntu 18.04][netplan] Machine network goes down when second gateway is configured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Invalid
|
High
|
Canonical Foundations Team | ||
netplan.io (Ubuntu) |
Invalid
|
High
|
Canonical Foundations Team |
Bug Description
---Problem Description---
Machine network goes down (not sshable/pingable) when gateway is configured for second interface.
---uname output---
Linux ltciofvtr-bostonlc2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = BostonLC bare-metal
---System Hang---
Remove the gateway from second interface and machine is accessible again
---Steps to Reproduce---
I have 2 interfaces configured on my machine,
1. enP2p1s0f0 having public IP 9.40.xx.xx with default gateway 9.40.xx.1
2. second enP2p1s0f2 having private connections IP 40.1.xx.x with out gateway
# cat /etc/netplan/
network:
version: 2
renderer: networkd
ethernets:
enP2p1s0f0:
addresses: [ 9.40.xxx.xx/24 ]
gateway4: 9.xx.xx.1
nameservers:
search: [ xx.xx.ibm.com ]
addresses:
- 9.x.1.x
enP2p1s0f2:
dhcp4: no
dhcp6: no
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 9.40.xx.1 0.0.0.0 UG 0 0 0 enP2p1s0f0
9.40.xx.0 0.0.0.0 255.255.255.0 U 0 0 0 enP2p1s0f0
40.1.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enP2p1s0f2
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
I see both the interfaces are pinging works fine.
But when I add gateway to the second interface i.e
# cat /etc/netplan/
network:
version: 2
renderer: networkd
ethernets:
enP2p1s0f0:
addresses: [ 9.40.xxx.xx/24 ]
gateway4: 9.xx.xx.1
nameservers:
search: [ xx.xx.ibm.com ]
addresses:
- 9.x.1.x
enP2p1s0f2:
dhcp4: no
dhcp6: no
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 40.1.1.1 0.0.0.0 UG 0 0 0 enP2p1s0f2 <<<<<< second gateway
0.0.0.0 9.40.xx.1 0.0.0.0 UG 0 0 0 enP2p1s0f0
9.40.xx.0 0.0.0.0 255.255.255.0 U 0 0 0 enP2p1s0f0
40.1.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enP2p1s0f2
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
run 'netplan apply'
After this I see both the interfaces are not pingable, machine is not sshable.
I see a similar issue and workaround being reported here : https:/
== Comment: #2 - Pradeep Satyanarayana <email address hidden> - 2018-04-23 14:10:46 ==
One requires what is known as "Policy Based Routing" to address this issue. The workaround that is described in the bug that you mention:
https:/
limits your options.
The complete solution to a setup that you have is well illustrated in:
If that does not work, then that would be a Linux Networking bug.
This appears to be a netplan limitation and you should consider mirroring the bug to Ubuntu and asking them to fix it. Googling around it appears that Netplan may not yet support "Policy Based Routing". Hence folks are suggesting workarounds to this problem.
Changed in ubuntu-power-systems: | |
importance: | Undecided → High |
tags: | added: triage-g |
Changed in ubuntu-power-systems: | |
assignee: | nobody → Canonical Foundations Team (canonical-foundations) |
affects: | core-network (Ubuntu) → netplan.io (Ubuntu) |
Changed in ubuntu-power-systems: | |
status: | New → Triaged |
tags: |
added: triage-a removed: triage-g |
tags: | added: id-5afcc9a8a7c2590642681eda |
tags: | added: p9 |
Changed in netplan.io (Ubuntu): | |
assignee: | Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) → Canonical Foundations Team (canonical-foundations) |
no longer affects: | netplan |
tags: | added: ubuntu-18.04.1 |
Changed in netplan.io (Ubuntu): | |
importance: | Undecided → High |
tags: |
added: triage-g removed: triage-a |
Default Comment by Bridge