On 17/05/18(Thu) 21:30, Michael-John Turner wrote: > On Mon, May 14, 2018 at 03:13:12PM +0200, Martin Pieuchot wrote: > > Could you try the diff below and as soon as you see the message in the > > dmesg, get the output of 'route -n show -inet6' and send us both? > > It's happened a few times since applying the patch but I've finally managed > to get the route output at the right moment, as requested. The messages in > dmesg_ndp_issue.txt have been flooding the message buffer for the last ~40 > minutes or so. > > As the text may wrap a bit oddly if posted to the list, I've placed the > files here: > http://dl.rsx11.net/misc/dmesg_ndp_issue.txt > http://dl.rsx11.net/misc/ndp_ndp_issue.txt > http://dl.rsx11.net/misc/netstat_ndp_issue.txt > http://dl.rsx11.net/misc/route_ndp_issue.txt > > Any ideas what could be causing the problem?
No because you didn't send your dmesg. I need the full dmesg, the important part from your original message was: ndp info overwritten for fe80:d::b408:97aa:a658:760e by 40:85:1b:ab:69:d5 on vlan41 ndp info overwritten for fe80:c::b408:97aa:a658:760e by c8:00:44:93:05:62 on vlan40 I need the corresponding information for the output you provided above. I'm guessing the in-kernel state machine tries to overwrite a RTF_LOCAL address and that should not happen.
