https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
--- Comment #6 from peos42 <pe...@incedo.org> --- Maybe there is a reason why DragonflyBSD fixed it. 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 the RFC4861 regarding Neighbour Discovery? IF it is not... Then I suggest this will be added to the future ToDo list for fixing. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
