Discussion:
[Bug 255264] Unable to add default route for fib
b***@freebsd.org
2021-04-20 14:36:08 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255264

Li-Wen Hsu <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@FreeBSD.org,
| |***@FreeBSD.org
Assignee|***@FreeBSD.org |***@FreeBSD.org
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2021-04-20 15:09:55 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255264

Marek Zarychta <***@plan-b.pwste.edu.pl> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@plan-b.pwste.edu.
| |pl

--- Comment #1 from Marek Zarychta <***@plan-b.pwste.edu.pl> ---
The default behaviour has changed. Now in dmesg we get:
"WARNING: Adding ifaddrs to all fibs has been turned off by default. Consider
tuning net.add_addr_allfibs if needed"

Please add globally the sysctl net.add_addr_allfibs=1 to revert to the old
behaviour. You can also solve this by assigning fib 1 to the interface which is
supposed to carry this route or by installing the network route for this
interface in fib 1.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2021-04-20 15:42:51 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255264

Neal Nelson <***@nicandneal.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|New |Closed
Resolution|--- |Works As Intended

--- Comment #2 from Neal Nelson <***@nicandneal.net> ---
Thanks for the information. I saw the message upon boot, but it looks to be a
large sweeping setting which made me nervous. Also I wasn't sure if it referred
to this situation precisely as frankly I don't really understand what it's
saying.

After setting this sysctl, all seems to be working as it was before.

Thanks for the very rapid response (unlike on the forum).
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2021-04-20 20:28:04 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255264

--- Comment #3 from Alexander V. Chernikov <***@FreeBSD.org> ---
(In reply to Neal Nelson from comment #2)
Hi Neal, you mentioned that the message wasn't helpful.

Do you by any chance have any suggestions/comments on how can the message be
improved to provide more context?

Thank you!
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2021-04-21 03:57:58 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255264

Kubilay Kocak <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Flags| |maintainer-feedback?(ports@
| |nicandneal.net)
CC| |***@nicandneal.net
Status|Closed |Open
Resolution|Works As Intended |---

--- Comment #4 from Kubilay Kocak <***@FreeBSD.org> ---
^Triage: Re-open pending potential messaging improvement, request feedback from
reporter
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2021-04-22 07:28:01 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255264

--- Comment #5 from Neal Nelson <***@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 entry
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 sure
that some method could be devised to auto include UPDATING entries.
--
You are receiving this mail because:
You are the assignee for the bug.
Loading...