Date: Tue, 14 Jun 2022 07:44:12 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 261129] IPv6 default route vanishes with rtadvd/rtsold Message-ID: <bug-261129-7501-m6KRHbvte9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261129-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-261129-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=3D261129 --- Comment #16 from Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> --- After taking some measures and test, so far I came to following conclusions: 1. The default route gets _silently_ corrupted irregardless of deployed route.algo, with no traces observable neither with route(8) monitor nor with increased net.route.algo.debug_level due to unknown reason (overflow ?). 2. Setting net.inet6.ip6.no_radr=3D1 net.inet6.ip6.accept_rtadv=3D0 and respectively disabling these options on the interfaces doesn't prevent the default route from being corrupted. Changing the value of net.add_addr_allf= ibs doesn't help either.=20 3. Restarting "routing" service fixes the issue for some time. 4.FreeBSD routing stack at current state doesn't allow to use in production= two different IPv6 GUA subsets on the same interface neither on 13-STABLE nor CURRENT (tested on amd64 and arm64 archs). 5. PF(4) supports rtable, route-to and reply-to for IPv6 traffic allowing deployment of more advanced network scenarios. 6. IPv6 on FreeBSD still needs more testing, especially in muiltihomed scenarios where multiple FIBs are involved. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-261129-7501-m6KRHbvte9>