Why there is difference of time to hold the neighbour table entries in cache for IPv4 versus IPv6 ?
Issue
- RHEL behaves differently for
IPv4vsIPv6when it comes to storing neigh table entries in cache. - When there are more than one
ARPreply for anIPv4address, details in first reply gets stored in neighbour cache and is used by the system for further communication but in case ofIPv6the lastNeighbor Advertisementgets stored in cache and is used by system. Why there is such a difference ?
Environment
- Red Hat Enterprise Linux 6 (All minor versions)
- Neighbour table cache (
# ip neigh show) - IPv6
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
