Summary: | Wrong MAC addresses reported by ndp | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | Serhii (Sergey) Kozlov <skozlov> | ||||||||
Component: | bin | Assignee: | Mark Johnston <markj> | ||||||||
Status: | Closed FIXED | ||||||||||
Severity: | Affects Some People | CC: | allanjude, bz, emaste, gnn, markj, melifaro, sbruno | ||||||||
Priority: | --- | ||||||||||
Version: | CURRENT | ||||||||||
Hardware: | Any | ||||||||||
OS: | Any | ||||||||||
Attachments: |
|
Created attachment 168303 [details]
Log from 10.2-RELEASE
Created attachment 168769 [details]
proposed fix
This looks like a bug in r292978. Could anyone give the attached patch a try?
A commit references this bug: Author: markj Date: Wed Mar 30 00:03:59 UTC 2016 New revision: 297403 URL: https://svnweb.freebsd.org/changeset/base/297403 Log: Fix the lladdr copy in in6_lltable_dump_entry() after r292978. This bug caused "ndp -a" to show the wrong link layer address for neighbour cache entries. PR: 208067 Changes: head/sys/netinet6/in6.c Thanks for the report! (In reply to Mark Johnston from comment #2) Checked the patch - it does fix the problem. Thanks! I am getting a crash that may be related to this fix https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210379 |
Created attachment 168302 [details] Log from 11-CURRENT The ndp utility report wrong MAC addresses on 11-CURRENT snapshot from 2016-03-08. On the same machine: 10.2: root@u0824:~ # ndp -na Neighbor Linklayer Address Netif Expire S Flags fe80::e2db:55ff:fefd:3045%igb0 e0:db:55:fd:30:45 igb0 permanent R 11.0: root@u0824:~ # ndp -an Neighbor Linklayer Address Netif Expire S Flags fe80::e2db:55ff:fefd:3045%igb0 20:f0:66:26:00:f8 igb0 permanent R Full logs are attached. Isolation notes: - Wrong MACs reported for local and remote hosts - Tested on igb and ixl drivers - IPv4 stack (arp utility) is not affected - Despite the wrong MAC addresses are reported, IPv6 traffic is working OK Sponsored by: Intel Corporation