| 2018-04-27 00:54:15 |
Thomas Ward |
bug |
|
|
added bug |
| 2018-04-27 15:50:28 |
Thomas Ward |
description |
Currently, NetPlan either doesn't have documentation on, or doesn't have the ability to, do a single network interface with multiple IP addresses with different gateways.
In the ifupdown days, this could be achieved in /etc/network/interfaces via something like this:
auto ens3
iface ens3 inet static
address 192.184.82.FOO
netmask 255.255.255.0
gateway 192.184.82.1
dns-nameserver 8.8.8.8 8.8.4.4
auto ens3:1
iface ens3:1 inet static
address 107.161.23.BAR
netmask 255.255.255.0
gateway 107.161.23.1
dns-nameserver 8.8.8.8 8.8.4.4
Currently, it is unclear whether NetPlan has this functionality, and if it does it is undocumented.
There are many cases where this type of functionality could be needed, such as with some VPSes, etc. which only have a single NIC that you can utilize on the system, and no ability to add additional NICs bound to the same 'connection'. If this does not exist as a functionality, then the functionality needs included. If the functionality exists, then documentation on *how* to achieve this is necessary. |
Currently, NetPlan either doesn't have documentation on how to configure a single network interface with multiple IP addresses with different gateways.
In the ifupdown days, this could be achieved in /etc/network/interfaces via something like this:
auto ens3
iface ens3 inet static
address 192.184.82.FOO
netmask 255.255.255.0
gateway 192.184.82.1
dns-nameserver 8.8.8.8 8.8.4.4
auto ens3:1
iface ens3:1 inet static
address 107.161.23.BAR
netmask 255.255.255.0
gateway 107.161.23.1
dns-nameserver 8.8.8.8 8.8.4.4
Currently, NetPlan does not have this functionality documented.
There are many cases where this type of setup could be needed, such as with some VPSes, etc. which only have a single NIC that you can utilize on the system, and no ability to add additional NICs bound to the same 'connection'. Therefore, it stands to reason we might need this to be an example in documentation somewhere.
Can we get such documentation and/or examples made available? |
|
| 2018-04-27 15:50:46 |
Thomas Ward |
summary |
No solution for 'multiple IPv4s with different gateways' |
No documentation of solution for 'one NIC with multiple IPv4s with different gateways' |
|
| 2018-04-27 15:53:29 |
Thomas Ward |
description |
Currently, NetPlan either doesn't have documentation on how to configure a single network interface with multiple IP addresses with different gateways.
In the ifupdown days, this could be achieved in /etc/network/interfaces via something like this:
auto ens3
iface ens3 inet static
address 192.184.82.FOO
netmask 255.255.255.0
gateway 192.184.82.1
dns-nameserver 8.8.8.8 8.8.4.4
auto ens3:1
iface ens3:1 inet static
address 107.161.23.BAR
netmask 255.255.255.0
gateway 107.161.23.1
dns-nameserver 8.8.8.8 8.8.4.4
Currently, NetPlan does not have this functionality documented.
There are many cases where this type of setup could be needed, such as with some VPSes, etc. which only have a single NIC that you can utilize on the system, and no ability to add additional NICs bound to the same 'connection'. Therefore, it stands to reason we might need this to be an example in documentation somewhere.
Can we get such documentation and/or examples made available? |
Currently, NetPlan doesn't have documentation on how to configure a single network interface with multiple IP addresses with different gateways.
In the ifupdown days, this could be achieved in /etc/network/interfaces via something like this:
auto ens3
iface ens3 inet static
address 192.184.82.FOO
netmask 255.255.255.0
gateway 192.184.82.1
dns-nameserver 8.8.8.8 8.8.4.4
auto ens3:1
iface ens3:1 inet static
address 107.161.23.BAR
netmask 255.255.255.0
gateway 107.161.23.1
dns-nameserver 8.8.8.8 8.8.4.4
Currently, NetPlan does not have this functionality documented.
There are many cases where this type of setup could be needed, such as with some VPSes, etc. which only have a single NIC that you can utilize on the system, and no ability to add additional NICs bound to the same 'connection'. Therefore, it stands to reason we might need this to be an example in documentation somewhere.
Can we get such documentation and/or examples made available? |
|
| 2018-07-24 07:42:20 |
Daniel Axtens |
netplan: status |
New |
Fix Committed |
|
