Re: [systemd-devel] TCPSegmentationOffload seem to be ignored in link-file
On 08.08.23 15:47, basti wrote: Hello, I move my network config from if-up to systemd and create a link file as follows: root@s920:~# cat /etc/systemd/network/10-enp1s0f1.link [Match] MACAddress=00:19:99:b7:e0:99 [Link] GenericSegmentationOffload=false GenericReceiveOffload=false TCPSegmentationOffload=false root@s920:~# The file seems to be used: root@s920:~# networkctl status enp1s0f1 ● 3: enp1s0f1 Link File: /etc/systemd/network/10-enp1s0f1.link Network File: /etc/systemd/network/enp1s0f1.network State: routable (configured) Online state: online Type: ether Path: pci-:01:00.1 Driver: igb Vendor: Intel Corporation Model: 82580 Gigabit Network Connection Hardware Address: 00:19:99:b7:e0:99 (Fujitsu Technology Solutions GmbH) MTU: 1500 (min: 68, max: 9216) QDisc: mq IPv6 Address Generation Mode: eui64 Number of Queues (Tx/Rx): 8/8 Auto negotiation: yes Speed: 1Gbps Duplex: full Port: tp Address: 192.168.1.10 fe80::219:99ff:feb7:e099 Activation Policy: up Required For Online: yes DHCP6 Client DUID: DUID-EN/Vendor:ab117b7b45fb726da9a5 Aug 07 21:37:52 s920 systemd-networkd[831]: enp1s0f1: Configuring with /etc/systemd/network/enp1s0f1.network. Aug 07 21:37:52 s920 systemd-networkd[831]: enp1s0f1: Link UP Aug 07 21:37:55 s920 systemd-networkd[831]: enp1s0f1: Gained carrier Aug 07 21:37:56 s920 systemd-networkd[831]: enp1s0f1: Gained IPv6LL root@s920:~# root@s920:~# ethtool -k enp1s0f1 | grep offload tcp-segmentation-offload: on generic-segmentation-offload: off generic-receive-offload: off large-receive-offload: off [fixed] rx-vlan-offload: on tx-vlan-offload: on l2-fwd-offload: off [fixed] hw-tc-offload: off [fixed] esp-hw-offload: off [fixed] esp-tx-csum-hw-offload: off [fixed] rx-udp_tunnel-port-offload: off [fixed] tls-hw-tx-offload: off [fixed] tls-hw-rx-offload: off [fixed] macsec-hw-offload: off [fixed] hsr-tag-ins-offload: off [fixed] hsr-tag-rm-offload: off [fixed] hsr-fwd-offload: off [fixed] hsr-dup-offload: off [fixed] root@s920:~# But tcp-segmentation-offload is still on or re-enabled by someone? any ideas? systemd is 252.12-1 (debian12) Best regards FYI: Add TCP6SegmentationOffload=false fix it. We found this bug https://github.com/systemd/systemd/issues/6854#issuecomment-353603816 Best Regards,
[systemd-devel] TCPSegmentationOffload seem to be ignored in link-file
Hello, I move my network config from if-up to systemd and create a link file as follows: root@s920:~# cat /etc/systemd/network/10-enp1s0f1.link [Match] MACAddress=00:19:99:b7:e0:99 [Link] GenericSegmentationOffload=false GenericReceiveOffload=false TCPSegmentationOffload=false root@s920:~# The file seems to be used: root@s920:~# networkctl status enp1s0f1 ● 3: enp1s0f1 Link File: /etc/systemd/network/10-enp1s0f1.link Network File: /etc/systemd/network/enp1s0f1.network State: routable (configured) Online state: online Type: ether Path: pci-:01:00.1 Driver: igb Vendor: Intel Corporation Model: 82580 Gigabit Network Connection Hardware Address: 00:19:99:b7:e0:99 (Fujitsu Technology Solutions GmbH) MTU: 1500 (min: 68, max: 9216) QDisc: mq IPv6 Address Generation Mode: eui64 Number of Queues (Tx/Rx): 8/8 Auto negotiation: yes Speed: 1Gbps Duplex: full Port: tp Address: 192.168.1.10 fe80::219:99ff:feb7:e099 Activation Policy: up Required For Online: yes DHCP6 Client DUID: DUID-EN/Vendor:ab117b7b45fb726da9a5 Aug 07 21:37:52 s920 systemd-networkd[831]: enp1s0f1: Configuring with /etc/systemd/network/enp1s0f1.network. Aug 07 21:37:52 s920 systemd-networkd[831]: enp1s0f1: Link UP Aug 07 21:37:55 s920 systemd-networkd[831]: enp1s0f1: Gained carrier Aug 07 21:37:56 s920 systemd-networkd[831]: enp1s0f1: Gained IPv6LL root@s920:~# root@s920:~# ethtool -k enp1s0f1 | grep offload tcp-segmentation-offload: on generic-segmentation-offload: off generic-receive-offload: off large-receive-offload: off [fixed] rx-vlan-offload: on tx-vlan-offload: on l2-fwd-offload: off [fixed] hw-tc-offload: off [fixed] esp-hw-offload: off [fixed] esp-tx-csum-hw-offload: off [fixed] rx-udp_tunnel-port-offload: off [fixed] tls-hw-tx-offload: off [fixed] tls-hw-rx-offload: off [fixed] macsec-hw-offload: off [fixed] hsr-tag-ins-offload: off [fixed] hsr-tag-rm-offload: off [fixed] hsr-fwd-offload: off [fixed] hsr-dup-offload: off [fixed] root@s920:~# But tcp-segmentation-offload is still on or re-enabled by someone? any ideas? systemd is 252.12-1 (debian12) Best regards
[systemd-devel] multiple systemd-nspawn container name resolution
Hello, i have setup multiple systemd-nspawn container with virtualEthernet=yes. Inside the container systemd-networkd and systemd-resolved are enabled. So far so good. Is there a way to disable the 169.254... networking for systemd? The problem is as followed: ip r 169.254.0.0/16 dev ve-test3 proto kernel scope link src 169.254.144.44 169.254.0.0/16 dev ve-test2 proto kernel scope link src 169.254.38.46 169.254.0.0/16 dev ve-test proto kernel scope link src 169.254.80.104 So I only can ping test3. The same problem is with name resolution. best regards
[systemd-devel] systemd-nspawn map UID/GID between cointainer and host
Hello, I have some users inside container hat had the same uid/GID on host. The files are bind to container and has rights "700" on host. I can't access files inside container (permission denied). so far so good. Is there a way to map uid/gid from host to container or from container to host, that user with uid 1004 on container can access files owned by user with uid 1004 on host? there are multiple uid so that --private-users option is not usable I think. Best regards, basti ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
