This is the parent task associated with interface configuration errors.
Bridging/ethernet/tunnels etc.
Description
Description
Details
Details
- Difficulty level
- Unknown (require assessment)
- Version
- 1.3
- Why the issue appeared?
- Will be filled on close
- Is it a breaking change?
- Unspecified (possibly destroys the router)
- Issue type
- Internal change (not visible to end users)
Event Timeline
Comment Actions
For all the bridge issues, I wanted to see what was happening on crux, taking T2356 as reference:
conf set interfaces tunnel tun12 encapsulation sit set interfaces tunnel tun12 local-ip 192.0.2.12 set interfaces tunnel tun12 remote-ip 192.0.2.22 set interfaces tunnel tun12 address 2001:db8:bb::2/64 set interfaces bridge br0 member interface tun12 Configuration path: interfaces bridge br0 [member] is not valid Set failed [edit]
Comment Actions
So the commands were not on crux under the tunnel section and trying to use either ip link or brctl is failing:
[email protected]# brctl show bridge name bridge id STP enabled interfaces br0 8000.080027beffc1 no eth1 [email protected]# brctl addif br0 eth2 [email protected]# brctl show bridge name bridge id STP enabled interfaces br0 8000.080027b0d2dc no eth1 eth2 [email protected]# brctl addif br0 tun12 can't add tun12 to bridge br0: Invalid argument [email protected]# ip a s tun12 9: [email protected]: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1476 qdisc noqueue state UNKNOWN group default qlen 1000 link/sit 192.0.2.12 peer 192.0.2.22 inet6 2001:db8:bb::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::c000:20c/64 scope link valid_lft forever preferred_lft forever
Comment Actions
Make sense, because IPIP this is L3, the bridge is L2.
In this case, we should not show L3 as an allowed interface for bridge.
This comment was removed by thomas-mangin.
Comment Actions
https://github.com/vyos/vyos-1x/pull/372 will now not display tunnel (but gre-bridge) as options for bridge. Still not preventing them to be used.