Before upgrading to 13.0 I used to create a default route in fib 1 so that openvpn could use it to set up a vpn for a jail to use.
This is the setup in rc.conf that worked:
route_vpn="default 10.0.0.1 -fib 1"
After upgrading to 13.0 I get the message "Network is unreachable" and fib 1 contains no default route.
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.
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).
(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?
^Triage: Re-open pending potential messaging improvement, request feedback from reporter
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.