Bug#1003757: busybox ip ignores peer name on veth pair creation
Package: busybox
Version: 1:1.30.1-7+b2
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
i need to create multiple veth pair interfaces, preferably from busybox...
* What exactly did you do (or not do) that was effective (or
ineffective)?
mc36@noti:~$
mc36@noti:~$ sudo ip link add veth9a type veth peer name veth9b
mc36@noti:~$ ip link show veth9a
9: veth9a@veth9b: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN
mode DEFAULT group default qlen 1000
link/ether 42:65:ad:1b:c4:da brd ff:ff:ff:ff:ff:ff
mc36@noti:~$ sudo ip link del veth9a
mc36@noti:~$ sudo /bin/busybox ip link add veth9a type veth peer name veth9b
mc36@noti:~$ ip link show veth9a
11: veth9a@veth0: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN
mode DEFAULT group default qlen 1000
link/ether 42:65:ad:1b:c4:da brd ff:ff:ff:ff:ff:ff
mc36@noti:~$ sudo ip link del veth9a
mc36@noti:~$
* What was the outcome of this action?
as you can see when i used iproute2 then it freates veth9a-veth9b pair, but
when i used busybox, it created veth9a-veth0 pair
* What outcome did you expect instead?
busybox's ip should honor peer name as iproute2's ip does
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.15.0-2-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages busybox depends on:
ii libc6 2.33-2
busybox recommends no packages.
busybox suggests no packages.
-- no debconf information
Reply to: