{"id":4692,"date":"2019-06-12T05:09:48","date_gmt":"2019-06-12T08:09:48","guid":{"rendered":"https:\/\/blog.clusterweb.com.br\/?p=4692"},"modified":"2019-06-12T05:09:48","modified_gmt":"2019-06-12T08:09:48","slug":"netplan-configuration-examples","status":"publish","type":"post","link":"https:\/\/blog.clusterweb.com.br\/?p=4692","title":{"rendered":"Netplan configuration examples"},"content":{"rendered":"

Below are a collection of example netplan configurations for common scenarios. If you see a scenario missing or have one to contribute, please file a bug against this documentation with the example using the links at the bottom of this page. Thank you!<\/p>\n

Configuration<\/h2>\n

To configure netplan, save configuration files under\u00a0\/etc\/netplan\/<\/code>\u00a0with a\u00a0.yaml<\/code>extension (e.g.\u00a0\/etc\/netplan\/config.yaml<\/code>), then run\u00a0sudo netplan apply<\/code>. This command parses and applies the configuration to the system. Configuration written to disk under\u00a0\/etc\/netplan\/<\/code>\u00a0will persist between reboots.<\/p>\n

Using DHCP and static addressing<\/h2>\n

To let the interface named \u2018enp3s0\u2019 get an address via DHCP, create a YAML file with the following:<\/p>\n

\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  renderer<\/span>:<\/span> networkd<\/span>\r\n  ethernets<\/span>:<\/span>\r\n    enp3s0<\/span>:<\/span>\r\n      dhcp4<\/span>:<\/span> true<\/span>\r\n<\/code><\/pre>\n<\/div>\n
To instead set a static IP address, use the addresses key, which takes a list of (IPv4 or IPv6), addresses along with the subnet prefix length (e.g. \/24). Gateway and DNS information can be provided as well:<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  renderer<\/span>:<\/span> networkd<\/span>\r\n  ethernets<\/span>:<\/span>\r\n    enp3s0<\/span>:<\/span>\r\n      addresses<\/span>:<\/span>\r\n        -<\/span> 10.10.10.2\/24<\/span>\r\n      gateway4<\/span>:<\/span> 10.10.10.1<\/span>\r\n      nameservers<\/span>:<\/span>\r\n          search<\/span>:<\/span> [<\/span>mydomain<\/span>,<\/span> otherdomain<\/span>]<\/span>\r\n          addresses<\/span>:<\/span> [<\/span>10.10.10.1<\/span>,<\/span> 1.1.1.1<\/span>]<\/span>\r\n<\/code><\/pre>\n<\/div>\n
<\/p>\n
Connecting multiple interfaces with DHCP<\/h2>\n
Many systems now include more than one network interface. Servers will commonly need to connect to multiple networks, and may require that traffic to the Internet goes through a specific interface despite all of them providing a valid gateway.<\/p>\n
One can achieve the exact routing desired over DHCP by specifying a metric for the routes retrieved over DHCP, which will ensure some routes are preferred over others. In this example, \u2018enred\u2019 is preferred over \u2018engreen\u2019, as it has a lower route metric:<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  ethernets<\/span>:<\/span>\r\n    enred<\/span>:<\/span>\r\n      dhcp4<\/span>:<\/span> yes<\/span>\r\n      dhcp4-overrides<\/span>:<\/span>\r\n        route-metric<\/span>:<\/span> 100<\/span>\r\n    engreen<\/span>:<\/span>\r\n      dhcp4<\/span>:<\/span> yes<\/span>\r\n      dhcp4-overrides<\/span>:<\/span>\r\n        route-metric<\/span>:<\/span> 200<\/span>\r\n<\/code><\/pre>\n<\/div>\n
Connecting to an open wireless network<\/h2>\n
Netplan easily supports connecting to an open wireless network (one that is not secured by a password), only requiring that the access point is defined:<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  wifis<\/span>:<\/span>\r\n    wl0<\/span>:<\/span>\r\n      access-points<\/span>:<\/span>\r\n        opennetwork<\/span>:<\/span> {}<\/span>\r\n      dhcp4<\/span>:<\/span> yes<\/span>\r\n<\/code><\/pre>\n<\/div>\n
Connecting to a WPA Personal wireless network<\/h2>\n
Wireless devices use the \u2018wifis\u2019 key and share the same configuration options with wired ethernet devices. The wireless access point name and password should also be specified:<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  renderer<\/span>:<\/span> networkd<\/span>\r\n  wifis<\/span>:<\/span>\r\n    wlp2s0b1<\/span>:<\/span>\r\n      dhcp4<\/span>:<\/span> no<\/span>\r\n      dhcp6<\/span>:<\/span> no<\/span>\r\n      addresses<\/span>:<\/span> [<\/span>192.168.0.21\/24<\/span>]<\/span>\r\n      gateway4<\/span>:<\/span> 192.168.0.1<\/span>\r\n      nameservers<\/span>:<\/span>\r\n        addresses<\/span>:<\/span> [<\/span>192.168.0.1<\/span>,<\/span> 8.8.8.8<\/span>]<\/span>\r\n      access-points<\/span>:<\/span>\r\n        \"<\/span>network_ssid_name\"<\/span>:<\/span>\r\n          password<\/span>:<\/span> \"<\/span>**********\"<\/span>\r\n<\/code><\/pre>\n<\/div>\n
Connecting to WPA Enterprise wireless networks<\/h2>\n
It is also common to find wireless networks secured using WPA or WPA2 Enterprise, which requires additional authentication parameters.<\/p>\n
For example, if the network is secured using WPA-EAP and TTLS:<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  wifis<\/span>:<\/span>\r\n    wl0<\/span>:<\/span>\r\n      access-points<\/span>:<\/span>\r\n        workplace<\/span>:<\/span>\r\n          auth<\/span>:<\/span>\r\n            key-management<\/span>:<\/span> eap<\/span>\r\n            method<\/span>:<\/span> ttls<\/span>\r\n            anonymous-identity<\/span>:<\/span> \"<\/span>@internal.example.com\"<\/span>\r\n            identity<\/span>:<\/span> \"<\/span>joe@internal.example.com\"<\/span>\r\n            password<\/span>:<\/span> \"<\/span>v3ryS3kr1t\"<\/span>\r\n      dhcp4<\/span>:<\/span> yes<\/span>\r\n<\/code><\/pre>\n<\/div>\n
Or, if the network is secured using WPA-EAP and TLS:<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  wifis<\/span>:<\/span>\r\n    wl0<\/span>:<\/span>\r\n      access-points<\/span>:<\/span>\r\n        university<\/span>:<\/span>\r\n          auth<\/span>:<\/span>\r\n            key-management<\/span>:<\/span> eap<\/span>\r\n            method<\/span>:<\/span> tls<\/span>\r\n            anonymous-identity<\/span>:<\/span> \"<\/span>@cust.example.com\"<\/span>\r\n            identity<\/span>:<\/span> \"<\/span>cert-joe@cust.example.com\"<\/span>\r\n            ca-certificate<\/span>:<\/span> \/etc\/ssl\/cust-cacrt.pem<\/span>\r\n            client-certificate<\/span>:<\/span> \/etc\/ssl\/cust-crt.pem<\/span>\r\n            client-key<\/span>:<\/span> \/etc\/ssl\/cust-key.pem<\/span>\r\n            client-key-password<\/span>:<\/span> \"<\/span>d3cryptPr1v4t3K3y\"<\/span>\r\n      dhcp4<\/span>:<\/span> yes<\/span>\r\n<\/code><\/pre>\n<\/div>\n
Many different modes of encryption are supported. See the\u00a0Netplan reference<\/a>\u00a0page.<\/p>\n
Using multiple addresses on a single interface<\/h2>\n
The addresses key can take a list of addresses to assign to an interface:<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  renderer<\/span>:<\/span> networkd<\/span>\r\n  ethernets<\/span>:<\/span>\r\n    enp3s0<\/span>:<\/span>\r\n     addresses<\/span>:<\/span>\r\n       -<\/span> 10.100.1.38\/24<\/span>\r\n       -<\/span> 10.100.1.39\/24<\/span>\r\n     gateway4<\/span>:<\/span> 10.100.1.1<\/span>\r\n<\/code><\/pre>\n<\/div>\n
Interface aliases (e.g. eth0:0) are not supported.<\/p>\n
Using multiple addresses with multiple gateways<\/h2>\n
Similar to the example above, interfaces with multiple addresses can be configured with multiple gateways.<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  renderer<\/span>:<\/span> networkd<\/span>\r\n  ethernets<\/span>:<\/span>\r\n    enp3s0<\/span>:<\/span>\r\n     addresses<\/span>:<\/span>\r\n       -<\/span> 9.0.0.9\/24<\/span>\r\n       -<\/span> 10.0.0.10\/24<\/span>\r\n       -<\/span> 11.0.0.11\/24<\/span>\r\n     #gateway4:    # unset, since we configure routes below<\/span>\r\n     routes<\/span>:<\/span>\r\n       -<\/span> to<\/span>:<\/span> 0.0.0.0\/0<\/span>\r\n         via<\/span>:<\/span> 9.0.0.1<\/span>\r\n         metric<\/span>:<\/span> 100<\/span>\r\n       -<\/span> to<\/span>:<\/span> 0.0.0.0\/0<\/span>\r\n         via<\/span>:<\/span> 10.0.0.1<\/span>\r\n         metric<\/span>:<\/span> 100<\/span>\r\n       -<\/span> to<\/span>:<\/span> 0.0.0.0\/0<\/span>\r\n         via<\/span>:<\/span> 11.0.0.1<\/span>\r\n         metric<\/span>:<\/span> 100<\/span>\r\n<\/code><\/pre>\n<\/div>\n
Given that there are multiple addresses, each with their own gateway, we do not specify\u00a0gateway4<\/code>\u00a0here, and instead configure individual routes to 0.0.0.0\/0 (everywhere) using the address of the gateway for the subnet. The\u00a0metric<\/code>\u00a0value should be adjusted so the routing happens as expected.<\/p>\n
DHCP can be used to receive one of the IP addresses for the interface. In this case, the default route for that address will be automatically configured with a\u00a0metric<\/code>value of 100. As a short-hand for an entry under\u00a0routes<\/code>,\u00a0gateway4<\/code>\u00a0can be set to the gateway address for one of the subnets. In that case, the route for that subnet can be omitted from\u00a0routes<\/code>. Its\u00a0metric<\/code>\u00a0will be set to 100.<\/p>\n
Using Network Manager as a renderer<\/h2>\n
Netplan supports both networkd and Network Manager as backends. You can specify which network backend should be used to configure particular devices by using the\u00a0renderer<\/code>\u00a0key. You can also delegate all configuration of the network to Network Manager itself by specifying only the\u00a0renderer<\/code>\u00a0key:<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  renderer<\/span>:<\/span> NetworkManager<\/span>\r\n<\/code><\/pre>\n<\/div>\n
Configuring interface bonding<\/h2>\n
Bonding is configured by declaring a bond interface with a list of physical interfaces and a bonding mode. Below is an example of an active-backup bond that uses DHCP to obtain an address:<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  renderer<\/span>:<\/span> networkd<\/span>\r\n  bonds<\/span>:<\/span>\r\n    bond0<\/span>:<\/span>\r\n      dhcp4<\/span>:<\/span> yes<\/span>\r\n      interfaces<\/span>:<\/span>\r\n        -<\/span> enp3s0<\/span>\r\n        -<\/span> enp4s0<\/span>\r\n      parameters<\/span>:<\/span>\r\n        mode<\/span>:<\/span> active-backup<\/span>\r\n        primary<\/span>:<\/span> enp3s0<\/span>\r\n<\/code><\/pre>\n<\/div>\n
Below is an example of a system acting as a router with various bonded interfaces and different types. Note the \u2018optional: true\u2019 key declarations that allow booting to occur without waiting for those interfaces to activate fully.<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  renderer<\/span>:<\/span> networkd<\/span>\r\n  ethernets<\/span>:<\/span>\r\n    enp1s0<\/span>:<\/span>\r\n      dhcp4<\/span>:<\/span> no<\/span>\r\n    enp2s0<\/span>:<\/span>\r\n      dhcp4<\/span>:<\/span> no<\/span>\r\n    enp3s0<\/span>:<\/span>\r\n      dhcp4<\/span>:<\/span> no<\/span>\r\n      optional<\/span>:<\/span> true<\/span>\r\n    enp4s0<\/span>:<\/span>\r\n      dhcp4<\/span>:<\/span> no<\/span>\r\n      optional<\/span>:<\/span> true<\/span>\r\n    enp5s0<\/span>:<\/span>\r\n      dhcp4<\/span>:<\/span> no<\/span>\r\n      optional<\/span>:<\/span> true<\/span>\r\n    enp6s0<\/span>:<\/span>\r\n      dhcp4<\/span>:<\/span> no<\/span>\r\n      optional<\/span>:<\/span> true<\/span>\r\n  bonds<\/span>:<\/span>\r\n    bond-lan<\/span>:<\/span>\r\n      interfaces<\/span>:<\/span> [<\/span>enp2s0<\/span>,<\/span> enp3s0<\/span>]<\/span>\r\n      addresses<\/span>:<\/span> [<\/span>192.168.93.2\/24<\/span>]<\/span>\r\n      parameters<\/span>:<\/span>\r\n        mode<\/span>:<\/span> 802.3ad<\/span>\r\n        mii-monitor-interval<\/span>:<\/span> 1<\/span>\r\n    bond-wan<\/span>:<\/span>\r\n      interfaces<\/span>:<\/span> [<\/span>enp1s0<\/span>,<\/span> enp4s0<\/span>]<\/span>\r\n      addresses<\/span>:<\/span> [<\/span>192.168.1.252\/24<\/span>]<\/span>\r\n      gateway4<\/span>:<\/span> 192.168.1.1<\/span>\r\n      nameservers<\/span>:<\/span>\r\n        search<\/span>:<\/span> [<\/span>local<\/span>]<\/span>\r\n        addresses<\/span>:<\/span> [<\/span>8.8.8.8<\/span>,<\/span> 8.8.4.4<\/span>]<\/span>\r\n      parameters<\/span>:<\/span>\r\n        mode<\/span>:<\/span> active-backup<\/span>\r\n        mii-monitor-interval<\/span>:<\/span> 1<\/span>\r\n        gratuitious-arp<\/span>:<\/span> 5<\/span>\r\n    bond-conntrack<\/span>:<\/span>\r\n      interfaces<\/span>:<\/span> [<\/span>enp5s0<\/span>,<\/span> enp6s0<\/span>]<\/span>\r\n      addresses<\/span>:<\/span> [<\/span>192.168.254.2\/24<\/span>]<\/span>\r\n      parameters<\/span>:<\/span>\r\n        mode<\/span>:<\/span> balance-rr<\/span>\r\n        mii-monitor-interval<\/span>:<\/span> 1<\/span>\r\n<\/code><\/pre>\n<\/div>\n
Configuring network bridges<\/h2>\n
To create a very simple bridge consisting of a single device that uses DHCP, write:<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  renderer<\/span>:<\/span> networkd<\/span>\r\n  ethernets<\/span>:<\/span>\r\n    enp3s0<\/span>:<\/span>\r\n      dhcp4<\/span>:<\/span> no<\/span>\r\n  bridges<\/span>:<\/span>\r\n    br0<\/span>:<\/span>\r\n      dhcp4<\/span>:<\/span> yes<\/span>\r\n      interfaces<\/span>:<\/span>\r\n        -<\/span> enp3s0<\/span>\r\n<\/code><\/pre>\n<\/div>\n
A more complex example, to get libvirtd to use a specific bridge with a tagged vlan, while continuing to provide an untagged interface as well would involve:<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  renderer<\/span>:<\/span> networkd<\/span>\r\n  ethernets<\/span>:<\/span>\r\n    enp0s25<\/span>:<\/span>\r\n      dhcp4<\/span>:<\/span> true<\/span>\r\n  bridges<\/span>:<\/span>\r\n    br0<\/span>:<\/span>\r\n      addresses<\/span>:<\/span> [<\/span> 10.3.99.25\/24<\/span> ]<\/span>\r\n      interfaces<\/span>:<\/span> [<\/span> vlan15<\/span> ]<\/span>\r\n  vlans<\/span>:<\/span>\r\n    vlan15<\/span>:<\/span>\r\n      accept-ra<\/span>:<\/span> no<\/span>\r\n      id<\/span>:<\/span> 15<\/span>\r\n      link<\/span>:<\/span> enp0s25<\/span>\r\n<\/code><\/pre>\n<\/div>\n
Then libvirtd would be configured to use this bridge by adding the following content to a new XML file under\u00a0\/etc\/libvirtd\/qemu\/networks\/<\/code>. The name of the bridge in the\u00a0tag as well as in\u00a0need to match the name of the bridge device configured using netplan:<\/p>\n
\n
<network><\/span>\r\n  <name><\/span>br0<\/name><\/span>\r\n  <bridge<\/span> name=<\/span>'br0'<\/span>\/><\/span>\r\n  <forward<\/span> mode=<\/span>\"bridge\"<\/span>\/><\/span>\r\n<\/network><\/span>\r\n<\/code><\/pre>\n<\/div>\n
Attaching VLANs to network interfaces<\/h2>\n
To configure multiple VLANs with renamed interfaces:<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  renderer<\/span>:<\/span> networkd<\/span>\r\n  ethernets<\/span>:<\/span>\r\n    mainif<\/span>:<\/span>\r\n      match<\/span>:<\/span>\r\n        macaddress<\/span>:<\/span> \"<\/span>de:ad:be:ef:ca:fe\"<\/span>\r\n      set-name<\/span>:<\/span> mainif<\/span>\r\n      addresses<\/span>:<\/span> [<\/span> \"<\/span>10.3.0.5\/23\"<\/span> ]<\/span>\r\n      gateway4<\/span>:<\/span> 10.3.0.1<\/span>\r\n      nameservers<\/span>:<\/span>\r\n        addresses<\/span>:<\/span> [<\/span> \"<\/span>8.8.8.8\"<\/span>,<\/span> \"<\/span>8.8.4.4\"<\/span> ]<\/span>\r\n        search<\/span>:<\/span> [<\/span> example.com<\/span> ]<\/span>\r\n  vlans<\/span>:<\/span>\r\n    vlan15<\/span>:<\/span>\r\n      id<\/span>:<\/span> 15<\/span>\r\n      link<\/span>:<\/span> mainif<\/span>\r\n      addresses<\/span>:<\/span> [<\/span> \"<\/span>10.3.99.5\/24\"<\/span> ]<\/span>\r\n    vlan10<\/span>:<\/span>\r\n      id<\/span>:<\/span> 10<\/span>\r\n      link<\/span>:<\/span> mainif<\/span>\r\n      addresses<\/span>:<\/span> [<\/span> \"<\/span>10.3.98.5\/24\"<\/span> ]<\/span>\r\n      nameservers<\/span>:<\/span>\r\n        addresses<\/span>:<\/span> [<\/span> \"<\/span>127.0.0.1\"<\/span> ]<\/span>\r\n        search<\/span>:<\/span> [<\/span> domain1.example.com<\/span>,<\/span> domain2.example.com<\/span> ]<\/span>\r\n<\/code><\/pre>\n<\/div>\n
Reaching a directly connected gateway<\/h2>\n
This allows setting up a default route, or any route, using the \u201con-link\u201d keyword where the gateway is an IP address that is directly connected to the network even if the address does not match the subnet configured on the interface.<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  renderer<\/span>:<\/span> networkd<\/span>\r\n  ethernets<\/span>:<\/span>\r\n    addresses<\/span>:<\/span> [<\/span> \"<\/span>10.10.10.1\/24\"<\/span> ]<\/span>\r\n    routes<\/span>:<\/span>\r\n      -<\/span> to<\/span>:<\/span> 0.0.0.0\/0<\/span>\r\n        via<\/span>:<\/span> 9.9.9.9<\/span>\r\n        on-link<\/span>:<\/span> true<\/span>\r\n<\/code><\/pre>\n<\/div>\n
Configuring source routing<\/h2>\n
Route tables can be added to particular interfaces to allow routing between two networks:<\/p>\n
In the example below, ens3 is on the 192.168.3.0\/24 network and ens5 is on the 192.168.5.0\/24 network. This enables clients on either network to connect to the other and allow the response to come from the correct interface.<\/p>\n
Furthermore, the default route is still assigned to ens5 allowing any other traffic to go through it.<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  renderer<\/span>:<\/span> networkd<\/span>\r\n  ethernets<\/span>:<\/span>\r\n    ens3<\/span>:<\/span>\r\n      addresses<\/span>:<\/span>\r\n       -<\/span> 192.168.3.30\/24<\/span>\r\n      dhcp4<\/span>:<\/span> no<\/span>\r\n      routes<\/span>:<\/span>\r\n       -<\/span> to<\/span>:<\/span> 192.168.3.0\/24<\/span>\r\n         via<\/span>:<\/span> 192.168.3.1<\/span>\r\n         table<\/span>:<\/span> 101<\/span>\r\n      routing-policy<\/span>:<\/span>\r\n       -<\/span> from<\/span>:<\/span> 192.168.3.0\/24<\/span>\r\n         table<\/span>:<\/span> 101<\/span>\r\n    ens5<\/span>:<\/span>\r\n      addresses<\/span>:<\/span>\r\n       -<\/span> 192.168.5.24\/24<\/span>\r\n      dhcp4<\/span>:<\/span> no<\/span>\r\n      gateway4<\/span>:<\/span> 192.168.5.1<\/span>\r\n      routes<\/span>:<\/span>\r\n       -<\/span> to<\/span>:<\/span> 192.168.5.0\/24<\/span>\r\n         via<\/span>:<\/span> 192.168.5.1<\/span>\r\n         table<\/span>:<\/span> 102<\/span>\r\n      routing-policy<\/span>:<\/span>\r\n        -<\/span> from<\/span>:<\/span> 192.168.5.0\/24<\/span>\r\n          table<\/span>:<\/span> 102<\/span>\r\n<\/code><\/pre>\n<\/div>\n
Configuring a loopback interface<\/h2>\n
Networkd does not allow creating new loopback devices, but a user can add new addresses to the standard loopback interface, lo, in order to have it considered a valid address on the machine as well as for custom routing:<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  renderer<\/span>:<\/span> networkd<\/span>\r\n  ethernets<\/span>:<\/span>\r\n    lo<\/span>:<\/span>\r\n      match<\/span>:<\/span>\r\n        name<\/span>:<\/span> lo<\/span>\r\n      addresses<\/span>:<\/span> [<\/span> 7.7.7.7\/32<\/span> ]<\/span>\r\n<\/code><\/pre>\n<\/div>\n
Integration with a Windows DHCP Server<\/h2>\n
For networks where DHCP is provided by a Windows Server using the dhcp-identifier key allows for interoperability:<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  ethernets<\/span>:<\/span>\r\n    enp3s0<\/span>:<\/span>\r\n      dhcp4<\/span>:<\/span> yes<\/span>\r\n      dhcp-identifier<\/span>:<\/span> mac<\/span>\r\n<\/code><\/pre>\n<\/div>\n
Connecting an IP tunnel<\/h2>\n
Tunnels allow an administrator to extend networks across the Internet by configuring two endpoints that will connect a special tunnel interface and do the routing required. Netplan supports SIT, GRE, IP-in-IP (ipip, ipip6, ip6ip6), IP6GRE, VTI and VTI6 tunnels.<\/p>\n
A common use of tunnels is to enable IPv6 connectivity on networks that only support IPv4. The example below show how such a tunnel might be configured.<\/p>\n
Here, 1.1.1.1 is the client\u2019s own IP address; 2.2.2.2 is the remote server\u2019s IPv4 address, \u201c2001:dead:beef::2\/64\u201d is the client\u2019s IPv6 address as defined by the tunnel, and \u201c2001:dead:beef::1\u201d is the remote server\u2019s IPv6 address.<\/p>\n
Finally, \u201c2001:cafe:face::1\/64\u201d is an address for the client within the routed IPv6 prefix:<\/p>\n
\n
network<\/span>:<\/span>\r\n  version<\/span>:<\/span> 2<\/span>\r\n  ethernets<\/span>:<\/span>\r\n    eth0<\/span>:<\/span>\r\n      addresses<\/span>:<\/span>\r\n        -<\/span> 1.1.1.1\/24<\/span>\r\n        -<\/span> \"<\/span>2001:cafe:face::1\/64\"<\/span>\r\n      gateway4<\/span>:<\/span> 1.1.1.254<\/span>\r\n  tunnels<\/span>:<\/span>\r\n    he-ipv6<\/span>:<\/span>\r\n      mode<\/span>:<\/span> sit<\/span>\r\n      remote<\/span>:<\/span> 2.2.2.2<\/span>\r\n      local<\/span>:<\/span> 1.1.1.1<\/span>\r\n      addresses<\/span>:<\/span>\r\n        -<\/span> \"<\/span>2001:dead:beef::2\/64\"<\/span>\r\n      gateway6<\/span>:<\/span> \"<\/span>2001:dead:beef::1\"<\/span><\/code><\/pre>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
Below are a collection of example netplan configurations for common scenarios. If you see a scenario missing or have one to contribute, please file a bug against this documentation with the example using the links at the bottom of this page. Thank you! Configuration To configure netplan, save configuration files under\u00a0\/etc\/netplan\/\u00a0with a\u00a0.yamlextension (e.g.\u00a0\/etc\/netplan\/config.yaml), then run\u00a0sudo […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[730,1,830,540,79,42,51,495,68,548],"tags":[761,1338,1283],"class_list":["post-4692","post","type-post","status-publish","format-standard","hentry","category-clusterweb","category-viazap","category-debian","category-dhcp-2","category-firewall","category-leitura-recomendada","category-linux-linuxrs","category-profissional-de-ti","category-redes-2","category-ubuntu-2","tag-configuration","tag-examples","tag-netplan"],"_links":{"self":[{"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/posts\/4692","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4692"}],"version-history":[{"count":1,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/posts\/4692\/revisions"}],"predecessor-version":[{"id":4693,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=\/wp\/v2\/posts\/4692\/revisions\/4693"}],"wp:attachment":[{"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4692"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4692"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.clusterweb.com.br\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4692"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}