Bond member unable to be commited

[n443311]

Hi!

Version: VyOS 2025.12.18-0018-rolling

Trying to make bond membership on sub interfaces and have fail.

Configs:

vyos@vyos-2025.12.18-rolling:~$ show configuration commands | match bond1
set interfaces bonding bond1 description ‘Bond-A’
set interfaces bonding bond1 hash-policy ‘encap3+4’
set interfaces bonding bond1 mode ‘xor-hash’

vyos@vyos-2025.12.18-rolling# run show configuration commands | match eth1
set interfaces ethernet eth1 vif 1000
set interfaces ethernet eth1 vif 1001
set interfaces ethernet eth1 vif 1002
set interfaces ethernet eth1 vif 1003

Manual:

Bond / Link Aggregation — VyOS rolling release (current)

Configure | compare

vyos@vyos-2025.12.18-rolling# set interfaces bonding bond1 member interface eth1.1000
[edit]
vyos@vyos-2025.12.18-rolling# compare
[interfaces bonding bond1]

• member {

• interface "eth1.1000"
  

• }

Commit:

vyos@vyos-2025.12.18-rolling# commit
[ interfaces bonding bond1 ]
Can not add interface “eth1.1000” to bond, it has a “” assigned!
[[interfaces bonding bond1]] failed

Commit failed.

Is it possible to make such type of bonding membership?

[L0crian]

Linux does allows you to use a VIF as a bond member, but it’d be an atypical config since many switches won’t allow that on their end. You can make the bond vlan aware though, would that work for you?:

vyos@vyos# set interfaces bonding bond1 member interface eth1
vyos@vyos# set interfaces bonding bond1 vif 1000
vyos@vyos# commit
vyos@vyos# show interfaces bonding bond1
 member {
     interface eth1
 }
 vif 1000 {
 }

If you 100% need to add only sub-interfaces to the bond, then I’m not sure whether to classify that as a bug or a feature request. It’ll depend on how the maintainers view it. If you do need this functionality, can you create a task at https://vyos.dev/

[n443311]

@L0crian Thx for your answer! the situation is clear, topic can be closed.