I tested netplan.io 0.104-0ubuntu2.1 from jammy-proposed inside a VM and inside an LXD container.
* udev values (i.e. the ".link" file) contains the correct "=false" values.
* ethtool -k show the values have been correctly set to "off" (on "netplan apply" and "reboot")
=> it's noteworthy that some ethtool values are fixed in this setup and thus cannot be changed:
large-receive-offload: off [fixed] # VM & container
rx-checksumming: on [fixed] # VM only, works in container
* The renaming of the interface works as expected inside the VM ("netplan apply" & "reboot")
* The renaming of the interface works inside the container on "netplan apply"
=> it's noteworthy that the interface is not renamed after "reboot" inside the LXD container, this is most probably due to some LXD udev quirks and should not be considered to be a regression, as it happened the same before. I confirmed this using the previous version from -release.
root@jammy-vm:~# cat /run/systemd/network/10-netplan-enp5s0.link | grep Offload
ReceiveChecksumOffload=false
TransmitChecksumOffload=false
TCPSegmentationOffload=false
TCP6SegmentationOffload=false
GenericSegmentationOffload=false
GenericReceiveOffload=false
LargeReceiveOffload=false
root@jammy-vm:~# ethtool -k enp5s0
Features for enp5s0:
rx-checksumming: on [fixed]
tx-checksumming: off
tcp-segmentation-offload: off
tx-tcp6-segmentation: off
generic-segmentation-offload: off
generic-receive-offload: off
large-receive-offload: off [fixed]
root@jj:~# ethtool -k eth0
Features for eth0:
rx-checksumming: off
tx-checksumming: off
tcp-segmentation-offload: off
tx-tcp6-segmentation: off
generic-segmentation-offload: off
generic-receive-offload: off
large-receive-offload: off [fixed]
I tested netplan.io 0.104-0ubuntu2.1 from jammy-proposed inside a VM and inside an LXD container.
* udev values (i.e. the ".link" file) contains the correct "=false" values. receive- offload: off [fixed] # VM & container checksumming: on [fixed] # VM only, works in container
* ethtool -k show the values have been correctly set to "off" (on "netplan apply" and "reboot")
=> it's noteworthy that some ethtool values are fixed in this setup and thus cannot be changed:
large-
rx-
* The renaming of the interface works as expected inside the VM ("netplan apply" & "reboot")
* The renaming of the interface works inside the container on "netplan apply"
=> it's noteworthy that the interface is not renamed after "reboot" inside the LXD container, this is most probably due to some LXD udev quirks and should not be considered to be a regression, as it happened the same before. I confirmed this using the previous version from -release.
root@jammy-vm:~# cat /run/systemd/ network/ 10-netplan- enp5s0. link | grep Offload Offload= false mOffload= false Offload= false nOffload= false tionOffload= false ffload= false load=false n-offload: off segmentation: off segmentation- offload: off receive- offload: off offload: off [fixed]
ReceiveChecksum
TransmitChecksu
TCPSegmentation
TCP6Segmentatio
GenericSegmenta
GenericReceiveO
LargeReceiveOff
root@jammy-vm:~# ethtool -k enp5s0
Features for enp5s0:
rx-checksumming: on [fixed]
tx-checksumming: off
tcp-segmentatio
tx-tcp6-
generic-
generic-
large-receive-
root@jj:~# ethtool -k eth0 n-offload: off segmentation: off segmentation- offload: off receive- offload: off offload: off [fixed]
Features for eth0:
rx-checksumming: off
tx-checksumming: off
tcp-segmentatio
tx-tcp6-
generic-
generic-
large-receive-