From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: veth0 weirdness
Date: Mon, 4 Dec 2023 16:50:59 -0800 [thread overview]
Message-ID: <20231204165059.089f743c@hermes.local> (raw)
Discovered an anomoly while exploring using veth for some testing scenarios.
The following will always fail with EEXIST:
# ip li add dev veth0 type veth
RTNETLINK answers: File exists
The reason is that name for the peer is always created first via:
"veth%d" and that will return "veth0". Then when the requested device
is created it will conflict with itself.
Not a big problem, but may confuse users. Fixing it would involve some more
complex transactional logic to create the primary device first then
create the peer which could get messy and likely buggy on first versions
for all the cases.
reply other threads:[~2023-12-05 0:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231204165059.089f743c@hermes.local \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).