Trunk port status is never reset on non-Cisco equipment
Bug #1431780 reported by
Morten Brekkevold
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Network Administration Visualized |
Fix Released
|
High
|
Morten Brekkevold | ||
Bug Description
A customer reports that once a port has been a trunk port, NAV never forgets this. I.e., when VLAN tagging is deconfigured for a port, NAV will still report it as a trunk port.
A cursory glance at the code suggest this is true for non-Cisco devices (i.e. any device where Q-BRIDGE-MIB is used as the source of dot1q information). The `dot1q` ipdevpoll plugin only ever sets "interface.trunk = True", never False.
Revision history for this message
| Morten Brekkevold (mbrekkevold) wrote | #1 |
| Changed in nav: | |
| status: | Confirmed → In Progress |
| milestone: | none → 4.2.4 |
| status: | In Progress → Fix Committed |
| Changed in nav: | |
| status: | Fix Committed → Fix Released |
| Changed in nav: | |
| milestone: | 4.2.4 → 4.2.5 |
To post a comment you must log in.
fix here: https:/