850b982f2a
The handling of BVI is awkward, with the autoderived interface name "bviXX" based on the bridgedomain bd_id. Lots of special casing happens on account of this decision, and to make matters worse there is poor interaction (leading to VPP crashes) when BVIs and Loopbacks are used at the same time: https://lists.fd.io/g/vpp-dev/message/21116 This is step one of a refactor of the logic. In this commit, I'm removing all of the BVI logic from the codebase, rendering bridgedomains unable to have IP interfaces. In the next commit, I will introduce new behavior in the schema, allowing for 'bvi' to be a loopback interfacename which will be used as BVI for a bridgedomain, restoring the ability to use bridgedomains with IP interfaces (using a loop).
54 lines
1.6 KiB
YAML
54 lines
1.6 KiB
YAML
test:
|
|
description: "IP interfaces cannot be more- or less-specific of any other interface"
|
|
errors:
|
|
expected:
|
|
- "interface .* IP address .* conflicts with another"
|
|
- "sub-interface .* IP address .* conflicts with another"
|
|
- "loopback .* IP address .* conflicts with another"
|
|
count: 14
|
|
---
|
|
interfaces:
|
|
GigabitEthernet1/0/0:
|
|
lcp: e1-0-0
|
|
description: "The 2nd/3rd addresses all are more/less specifics of the first"
|
|
addresses: [ 172.16.12.1/29, 172.16.12.2/30, 172.16.12.3/28 ]
|
|
|
|
GigabitEthernet1/0/1:
|
|
lcp: e1-0-1
|
|
addresses: [ 192.0.2.1/29, 2001:db8:1::1/64 ]
|
|
sub-interfaces:
|
|
100:
|
|
description: "These addresses overlap with Gi1/0/1"
|
|
addresses: [ 192.0.2.2/29, 2001:db8:1::2/64 ]
|
|
101:
|
|
description: "These addresses overlap with loop0"
|
|
addresses: [ 192.0.2.10/29, 2001:db8:2::2/64 ]
|
|
|
|
GigabitEthernet1/0/2:
|
|
lcp: e0-2
|
|
|
|
GigabitEthernet1/0/3:
|
|
lcp: e0-3
|
|
description: "These addresses are more-specific to Gi1/0/4"
|
|
addresses: [ 10.0.0.1/24, 2001:db8:3::1/64 ]
|
|
|
|
GigabitEthernet1/0/4:
|
|
lcp: e0-4
|
|
description: "These addresses are less-specific to Gi1/0/3"
|
|
addresses: [ 10.0.0.2/23, 2001:db8:3::2/60 ]
|
|
|
|
GigabitEthernet1/0/5:
|
|
lcp: e0-5
|
|
description: "These addresses are more-specific to Gi1/0/3"
|
|
addresses: [ 10.0.0.3/25, 2001:db8:3::3/112 ]
|
|
|
|
GigabitEthernet3/0/0:
|
|
description: "Bridge Domain bd1, member #1"
|
|
mtu: 2000
|
|
|
|
loopbacks:
|
|
loop0:
|
|
description: "These addresses overlap with Gi1/0/1.101"
|
|
lcp: "loop0"
|
|
addresses: [ 192.0.2.9/29, 2001:db8:2::1/64 ]
|