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 ***

Actually, busybox's `ip link' ignores everything it doesn't recognize:

  busybox ip link add veth9a type veth foo bar baz  -- this works.

it just skips unrecognized arguments, that's all.

And it's the case in 1.38 in 2026 still.

Thanks,

/mjt