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
VLAN checks could just be via a config entry for allowed VLAN ids and then run arp-scan with the --vlan tag for each and every vlan specified. Outside of that it would be a matter of watching for traffic on any vlans not allowed and alert that there's an unknown vlan in use. Since adding VLANs is not a common occurrence in any network there should be no need for a UI component, only a config file entry.
The text was updated successfully, but these errors were encountered:
To confirm, this would be making a list of devices on the allowed vlans and then any device not on them you'd get the alert but what would the UI show, only the allowed or everything?
In the UI there would be no change to how it is now e.g., you would see everything and have the ability to mark it as known or see it as unknown and receive alerts.
VLAN checks could just be via a config entry for allowed VLAN ids and then run arp-scan with the --vlan tag for each and every vlan specified. Outside of that it would be a matter of watching for traffic on any vlans not allowed and alert that there's an unknown vlan in use. Since adding VLANs is not a common occurrence in any network there should be no need for a UI component, only a config file entry.
The text was updated successfully, but these errors were encountered: