On Tue, 15 Jun 2021, Bruce Ashfield wrote: > On Tue, Jun 15, 2021 at 6:02 AM Ross Burton <r...@burtonini.com> wrote: > > > > From: Matt Spencer <matt.spen...@arm.com> > > > > We need to prevent systemd-network from managing veth interface when > > using platforms like k3s as they control creation and management of the > > interfaces. > > FWIW, I think this may surprise/break people in other use cases. I had > mentioned this to matt directly as well. > > The situation is not as clear as that commit message implies. networkd > *can* cause issues with veth devices, but not always. > > Not trying to stop the patch, but I wanted my concerns to be archived :D
I second this concern, a default config change like this might bite systemd-nspawn users, as it has its own options to set up private networking with veth interfaces. Maybe adding a drop-in conf file to do this when k3s or the like is installed would be better? Scott > > > > Signed-off-by: Matt Spencer <matt.spen...@arm.com> > > Signed-off-by: Ross Burton <ross.bur...@arm.com> > > --- > > meta/recipes-core/systemd/systemd-conf/wired.network | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/meta/recipes-core/systemd/systemd-conf/wired.network > > b/meta/recipes-core/systemd/systemd-conf/wired.network > > index e7b69970d6..7406287248 100644 > > --- a/meta/recipes-core/systemd/systemd-conf/wired.network > > +++ b/meta/recipes-core/systemd/systemd-conf/wired.network > > @@ -1,5 +1,6 @@ > > [Match] > > Type=ether > > +Name=!veth* > > KernelCommandLine=!nfsroot > > KernelCommandLine=!ip > > > > -- > > 2.25.1 > > > > > > > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#152998): https://lists.openembedded.org/g/openembedded-core/message/152998 Mute This Topic: https://lists.openembedded.org/mt/83552270/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
