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
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:~#
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
er
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.freed
