From: "Scott Murray" <scott.murray@konsulko.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Ross Burton <ross@burtonini.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] systemd-conf: Prevent systemd-network from managing veth interfaces
Date: Tue, 15 Jun 2021 14:35:15 -0400 (EDT) [thread overview]
Message-ID: <aaedf6cc-3c45-5a92-5fac-c5edde1d1327@spiteful.org> (raw)
In-Reply-To: <CADkTA4N_y-LcJj3+FbFgkdYtPZmPExj8qf-FrQ8pzeQy8t0F9g@mail.gmail.com>
On Tue, 15 Jun 2021, Bruce Ashfield wrote:
> On Tue, Jun 15, 2021 at 6:02 AM Ross Burton <ross@burtonini.com> wrote:
> >
> > From: Matt Spencer <matt.spencer@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.spencer@arm.com>
> > Signed-off-by: Ross Burton <ross.burton@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
> >
> >
> >
> >
>
>
>
next prev parent reply other threads:[~2021-06-15 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 10:02 [PATCH] systemd-conf: Prevent systemd-network from managing veth interfaces Ross Burton
2021-06-15 12:28 ` [OE-core] " Bruce Ashfield
2021-06-15 18:35 ` Scott Murray [this message]
2021-06-15 17:57 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aaedf6cc-3c45-5a92-5fac-c5edde1d1327@spiteful.org \
--to=scott.murray@konsulko.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross@burtonini.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.