-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect ipv6 Termination MAC entries when enslaving port to bridge #351
Comments
Does the port have a IP address assigned? |
It does:
It seems that the flow appears depeding on what happens first between the following two:
If the ipv6 link-local address appears first, then the entry is created. If the port is attached to swbridge BEFORE the ipv6 address appears, the flow is not created. In my example given above, the ipv6 address is generated, and therefore the flow should exist (you can argue about ip addresses on bridged ports...). But what about the case where the port is bridged before the ipv6 address is generated, should it not also generate an entry in the Termination MAC table? |
It should, so absence of one seems like the bug. |
iirc somebody specifically implemented a check a while ago that made sure to consider the "bridge attachement status" before adding flow tables |
Expected Behavior
Enslaving a port to a bridge, then tagging a vlan on the port should not create any Termination MAC entries.
Actual Behavior
Enslaving a port to a bridge, then tagging a vlan on the port does create a Termination MAC entries.
Steps to Reproduce the Problem
Set server side port UP before starting switch side configuration.
On the Switch run the following commands:
Create vlan_filtering bridge swbridge
Set bridge swbridge up
Attach port_left to the swbridge"
Set port_left attached to swbridge up
add vid 10 to port_left
Check termination MAC entries
Gives the output(example given):
Specifications
The text was updated successfully, but these errors were encountered: