-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Missing validation of not assigning several vlans as untagged on the same interface. #6421
Labels
Comments
Bug still exists on SONiC.201911.51-dea38d15 and moved from: |
Not supported today, enhancement for input validation for interface config. |
liat-grozovik
pushed a commit
to sonic-net/sonic-utilities
that referenced
this issue
Jan 27, 2021
…face (#1382) Fix for sonic-net/sonic-buildimage#6421 **- What I did** User was able to add an interface to multiple VLANs as untagged. Added a validation to a single untagged member. **- How I did it** Added a validation when adding a port as untagged to check in DB if is already member as untagged in a different vlan. **- How to verify it** Add vlan, add interface as untagged member in this vlan, add another vlan, try to add the same interface as untagged member in the new vlan. **- Previous command output (if the output of a command-line utility has changed)** Command was successful. **- New command output (if the output of a command-line utility has changed)** Fail in VLAN membership. Error: Ethernet8 is already untagged member!
Bug has been fixed.
|
anand-kumar-subramanian
pushed a commit
to anand-kumar-subramanian/sonic-utilities
that referenced
this issue
Mar 2, 2021
…face (sonic-net#1382) Fix for sonic-net/sonic-buildimage#6421 **- What I did** User was able to add an interface to multiple VLANs as untagged. Added a validation to a single untagged member. **- How I did it** Added a validation when adding a port as untagged to check in DB if is already member as untagged in a different vlan. **- How to verify it** Add vlan, add interface as untagged member in this vlan, add another vlan, try to add the same interface as untagged member in the new vlan. **- Previous command output (if the output of a command-line utility has changed)** Command was successful. **- New command output (if the output of a command-line utility has changed)** Fail in VLAN membership. Error: Ethernet8 is already untagged member!
malletvapid23
added a commit
to malletvapid23/Sonic-Utility
that referenced
this issue
Aug 3, 2023
…face (#1382) Fix for sonic-net/sonic-buildimage#6421 **- What I did** User was able to add an interface to multiple VLANs as untagged. Added a validation to a single untagged member. **- How I did it** Added a validation when adding a port as untagged to check in DB if is already member as untagged in a different vlan. **- How to verify it** Add vlan, add interface as untagged member in this vlan, add another vlan, try to add the same interface as untagged member in the new vlan. **- Previous command output (if the output of a command-line utility has changed)** Command was successful. **- New command output (if the output of a command-line utility has changed)** Fail in VLAN membership. Error: Ethernet8 is already untagged member!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
SONiC does not prevent from assigning several VLANs as untagged on the same interface.
This bug is reproduced on the stable image as well.
Steps to reproduce the issue
Describe the results you received
Two untagged VLANs on the same port.
Describe the results you expected
Config utility should prevent from assigning several VLANs as untagged on the same interface.
The output of show version
The text was updated successfully, but these errors were encountered: