Date: Tue, 20 Nov 2018 08:30:48 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 233283] IPv6 routing problem when using FreeBSD as a VPS at a cloud provider Message-ID: <bug-233283-7501-j2BxpBiVju@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-233283-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-233283-7501@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=3D233283 --- Comment #6 from peos42 <peo_s@incedo.org> --- Maybe there is a reason why DragonflyBSD fixed it.=20 The cloud provider in the same support case I started this thread with said: --snip-- Additionally, if BSD followed RFC compliance for neighbour table discovery (https://tools.ietf.org/html/rfc4861) it would not be an issue, but they do not. This has been know and unfortunately has affected *BSD all the back to 2012. It's actually BSD that is not RFC compliant in this case. --snip-- I have not looked that deep. But is the case that FreeBSD does not follow t= he RFC4861 regarding Neighbour Discovery? IF it is not... Then I suggest this will be added to the future ToDo list f= or fixing. --=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-233283-7501-j2BxpBiVju>