* veth0 weirdness
@ 2023-12-05 0:50 Stephen Hemminger
0 siblings, 0 replies; only message in thread
From: Stephen Hemminger @ 2023-12-05 0:50 UTC (permalink / raw)
To: netdev
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-12-05 0:51 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-12-05 0:50 veth0 weirdness Stephen Hemminger
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).