Date: Thu, 22 Apr 2021 07:28:01 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 255264] Unable to add default route for fib Message-ID: <bug-255264-7501-Vujwxff5J0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255264-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-255264-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=3D255264 --- Comment #5 from Neal Nelson <ports@nicandneal.net> --- The entry in /usr/src/UPDATING that has been pointed out to me explains the situation a little better than the current message. I'm sure the current message makes sense to those that know the ins and outs, but not those of us not quite so well versed in the intricacies of network routing: Default value of net.add_addr_allfibs has been changed to 0. If you have multi-fib configuration and rely on existence of all interface routes in every fib, you need to set the above sysctl to 1. It's a bit wordy, but more helpful. If it's too wordy, a reference to the e= ntry in UPDATING could be made. As a further suggestion; it might also be useful to add the entries from UPDATING to the release notes. I found the entry there stating the change, = but it was of no use to me whatsoever as it didn't state the consequences of the change. I realise that the release notes are rather long already, but I'm s= ure that some method could be devised to auto include UPDATING entries. --=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-255264-7501-Vujwxff5J0>