Hey Bruce, I understand that changing things can be difficult once launched.
But looking at the systemd documentation here https://wiki.archlinux.org/title/systemd-networkd and in the note that says 'Devices can also be matched by their type. E.g. Type=ether for Ethernet, Type=wlan for Wi-Fi and Type=wwan for WWAN. Note that Type=ether will also match virtual Ethernet interfaces (veth*), which may be undesirable.' I have created a patch that modifies poky's meta/recipes-core/systemd/systemd-conf/wired.network to add '+Name=!veth*' to the Match clause which the team at Arm are reviewing with a view to upstream. I feel that this should have been the default behaviour anyway? /Matt ________________________________ From: [email protected] <[email protected]> on behalf of Bruce Ashfield via lists.yoctoproject.org <[email protected]> Sent: 14 June 2021 15:24 To: Matt Spencer <[email protected]> Cc: [email protected] <[email protected]> Subject: Re: [meta-virtualization] Networking issue with l3s when using systemd On Mon, Jun 14, 2021 at 6:27 AM Matt Spencer <[email protected]> wrote: > > Hi all > > There seems to be a networking problem with k3s when using systemd. The > problem manifests in that none of the kube-system management containers are > able to communicate with eachother. > > The root cause seems to be that systemd-networking is actively managing veth > interfaces created by k3s/flannel. This happens because of > '/lib/systemd/network/80-wired.network' added by the systemd recipe, which is > matching on Type=ether. > > My fix is to modify the 80-wired.network to add 'Name=eth*'. With this in > place, k3s works as expected. > > I am not sure what the correct upstream solution should be for Yocto? Your > help would be appreciated. > This particular issue is known, in the sense that we have run into it before. At a minimum, I need to warn about it in the k3s README files. I created the cni bbclass to manage potentially conflicting networking configs on that front, but systemd-networking is yet another variable. We don't want to globally make it conflict, since someone might have a working networkd config that they want to use, and exactly how networking is set up, tends to be more of a distro feature. So the recipes need to tread carefully. Which takes me back to the README, and an enhancement to the cni-networking bbclass to be more generic and pick up / warn on configuration issues like this. bruce > /Matt > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#6556): https://lists.yoctoproject.org/g/meta-virtualization/message/6556 Mute This Topic: https://lists.yoctoproject.org/mt/83526656/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
