Comment 3 for bug 1398382

Revision history for this message
Morten Brekkevold (mbrekkevold) wrote :

The bug appears to still be present in NAV 4.2.2, but due to another data problem:

The code does not allow for multiple ELINKs to the same peer node if the ELINK vlans have not been assigned a proper net_ident value. An empty net_ident causes a sysname and interface name for the ELINK peer to be generated, but the interface name is always the same, causing hashing/keying errors in the graph.

The remote "fictional" interface should at least be unique per detected link.