Date: Thu, 01 Jun 2017 22:44:08 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219699] Issue with IPv6 and neighbor notification Message-ID: <bug-219699-2472-LsEvqh9wRv@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219699-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-219699-2472@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219699 --- Comment #4 from rkoberman@gmail.com --- (In reply to Paul G Webster from comment #3) At the time that you collected this, everything looks good. The default rou= te is pointing to the correct link. (link#1) and all ndp data looks correct. One suggestion is to accept router advertisements. To do this, add "accept_rtadv" to you ifconfig_vtnet0_ipv6 line in rc.conf. This will cause your system to accept router advertisements on your LAN. Unless you have another local system configured to do IPv6 routing, this should be fine. I = also doubt it will help, but it might be worth a try. (If it does not help, I'd remove it.) You might want to monitor the default route and the NDP for 2a07:4580:b0d:27e::1 to see if they are stable. It sure sounds like somethi= ng is flapping when the link is inactive for some period. My guess is NDP, but that is far from certain. N.B. I was very active in working with IPv6 for over 15 years, but I've been retired for six years and I'll admit that I am not as sharp on it as I once was. Worse, Frontier, my ISP about half the year does not yet support IPv6 customer connections. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219699-2472-LsEvqh9wRv>