Solved [fib_algo] inet.0 (bsearch4#20) rebuild_fd_flm: switching algo to radix4_lockless

Hello.

I've configured a vpn on FreeBSD 14.0 using this config file :

Code:
client
dev tun
proto udp
remote vpn.boston.myvpn.net
resolv-retry infinite
nobind
persist-key
persist-tun
ca /home/marietto/Desktop/Files/OS/FreeBSD/Scripts/VPNPro/ca.crt
cert /home/marietto/Desktop/Files/OS/FreeBSD/Scripts/VPNPro/CN00706276.crt
key /home/marietto/Desktop/Files/OS/FreeBSD/Scripts/VPNPro/CN00706276.key
remote-cert-tls server
cipher AES-256-CBC
verb 3
port 1194
tun-mtu 1500
mssfix 1450
mute 20
pull
comp-lzo
mute-replay-warnings

It works,I'm able to connect to the gateway correctly,but during the boot I see one error :

Code:
# dmesg -a

tun0: link state changed to UP
[fib_algo] inet.0 (bsearch4#20) rebuild_fd_flm: switching algo to radix4_lockless

I would like to know if I can fix or suppress it. The workaround seems to be explained here :


but it can't be because I haven't any tailscaled service on my machine.
 
it's not an error, it's a debug message, the number of inet4 routes you have caused the kernel to select the lockless radix algorithm for route lookups. you might be able to suppress it by changing net.route.algo.debug_level.
 
it's not an error, it's a debug message, the number of inet4 routes you have caused the kernel to select the lockless radix algorithm for route lookups. you might be able to suppress it by changing net.route.algo.debug_level.
Can debug message be critical?
Sometimes I have some message in /var/log/messages on 13.3-RELEASE-p2

│Nov 22 09:08:29 <kern.crit> kernel: [fib_algo] inet.0 (bsearch4#18) rebuild_fd_flm: switching algo to radix4_lockless

P.S. I'm a little sorry for bringing up a closed topic
 
Back
Top