You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some 802.1X specific information per port should be collected by ipdevpoll and presented on the port details page of ipdevinfo.
NAV collects the native VLAN configured on a switch port, but this does not necessarily correspond to the VLAN assigned to the port during an active 802.1X session. MAB (MAC Authentication Bypass)-assigned VLANs should also be supported, but may also have a different information source not yet support by NAV.
Identify which MIB(s) can be used to fetch the 802.1X VLAN. This may be vendor dependent.
Identify whether MAB (MAC Authentication Bypass)-assigned VLANs are collectable through the same 802.1X MIB(s) or in a different MIB. This may be vendor dependent.
Design a data model for storing these kinds of "auxiliary" VLAN values for ports.
Extend ipdevpoll to collect and store these values.
Identify whether these "auxiliary" VLANs need to be considered by the topology detector
And if so, extend navtopology to use the values during detection.
The text was updated successfully, but these errors were encountered:
hmpf
changed the title
Is it possiblle to show more infornation about 802.1X enabled ports?
Is it possible to show more information about 802.1X enabled ports?
May 7, 2019
Some 802.1X specific information per port should be collected by ipdevpoll and presented on the port details page of ipdevinfo.
NAV collects the native VLAN configured on a switch port, but this does not necessarily correspond to the VLAN assigned to the port during an active 802.1X session. MAB (MAC Authentication Bypass)-assigned VLANs should also be supported, but may also have a different information source not yet support by NAV.
The text was updated successfully, but these errors were encountered: