Running nplan 0.30 on Ubuntu 17.10. From what I can tell, the ethernets/interface/mtu field isn't applied when testing against a private ethernet adapter.
Using a netplan yaml file (/etc/netplan/10-ens7.yaml):
---
network: version: 2 renderer: networkd ethernets: ens7: mtu: 1450 dhcp4: no addresses: [10.99.0.13/16]
Then running "netplan apply" (or rebooting), yields the following:
6: ens7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:2a:19:bc brd ff:ff:ff:ff:ff:ff inet 10.99.0.13/16 brd 10.99.255.255 scope global ens7 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe2a:19bc/64 scope link valid_lft forever preferred_lft forever
Is this a bug in netplan, or am I misunderstanding the YAML syntax?
Best, Andrew
Running nplan 0.30 on Ubuntu 17.10. From what I can tell, the ethernets/ interface/ mtu field isn't applied when testing against a private ethernet adapter.
Using a netplan yaml file (/etc/netplan/ 10-ens7. yaml):
---
network:
version: 2
renderer: networkd
ethernets:
ens7:
mtu: 1450
dhcp4: no
addresses: [10.99.0.13/16]
---
Then running "netplan apply" (or rebooting), yields the following:
---
6: ens7: <BROADCAST, MULTICAST, UP,LOWER_ UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 ff:fe2a: 19bc/64 scope link
link/ether 52:54:00:2a:19:bc brd ff:ff:ff:ff:ff:ff
inet 10.99.0.13/16 brd 10.99.255.255 scope global ens7
valid_lft forever preferred_lft forever
inet6 fe80::5054:
valid_lft forever preferred_lft forever
---
Is this a bug in netplan, or am I misunderstanding the YAML syntax?
Best,
Andrew