Closed rr-santos closed 1 year ago
Testing with baseboxd 2.0.8, BISDN Linux 5.0.1, this now seems to be working as expected:
accton-as5835-54x:~$ client_grouptable_dump
groupId = 0x00640036 (L2 Interface, VLAN ID = 100, Port ID = 54): duration: 12, refCount:3
bucketIndex = 0: outputPort = 54 (Physical) popVlanTag = 1 allowVlanTranslation = 0
groupId = 0x20000001 (L3 Unicast, Index = 1): duration: 12, refCount:1
bucketIndex = 0: referenceGroupId = 0x00640036 vlanId = 0x1064 (VLAN 100) srcMac: AE:83:84:68:1A:3D dstMac: 00:00:00:01:00:01
groupId = 0x40640064 (L2 Flood, VLAN ID = 100, Index = 100): duration: 12, refCount:1
bucketIndex = 0: referenceGroupId = 0x00640036
accton-as5835-54x:~$ sudo ip neighbor del 10.1.1.2 lladdr 00:00:00:01:00:01 dev swbridge.100
accton-as5835-54x:~$ client_grouptable_dump
groupId = 0x00640036 (L2 Interface, VLAN ID = 100, Port ID = 54): duration: 103, refCount:2
bucketIndex = 0: outputPort = 54 (Physical) popVlanTag = 1 allowVlanTranslation = 0
groupId = 0x40640064 (L2 Flood, VLAN ID = 100, Index = 100): duration: 103, refCount:1
bucketIndex = 0: referenceGroupId = 0x00640036
Expected Behavior
The L3 group entry should be removed after deleting the neighbor entry.
Actual Behavior
The group entry remains listed when running
client_grouptable_dump
. I suspect this is related to howl3_interface_id
mapping keys are manipulated when deleting L3 egress entries, similar to https://github.com/bisdn/basebox/issues/275Steps to Reproduce the Problem
To configure a switch bridge with a SVI and a neighbor entry:
Deleting the entry afterwards:
client_grouptable_dump
output still shows the group entry:Specifications