Use ARP data to detect neighbor

Bug #1441598 reported by Vidar Faltinsen
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Network Administration Visualized
Triaged
Wishlist
Unassigned

Bug Description

Today the algorithm for deciding a L2 neighbor is in this order:

1) LLDP data
2) CDP data
3) CAM (bridge table) data

I suggest a forth level:

4) ARP data

There are circumstances for L3 link networks, i.e. two routers linked back to back, that neighbors are not discovered by NAV.
Typically LLDP and CDP are not supported/enabled in these scenarios. If the ARP data reveal only one other neighbor, this should be a candidate for neighbors

An implementation that supports this will give added value to the IP device info neighbors tab, and the link down alarm.

Changed in nav:
importance: Undecided → Wishlist
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.