I lose my DHCPv6 on the WAN interface. when I run:
#dhclient igb1
DHCPREQUEST on igb1 to 255.255.255.255 port 67
DHCPACK from x.x.x.1
[fib_algo] inet.0 setup_fd_instance: radix4_lockless algo instance setup failed, failures=61
[fib_algo] inet.0 (radix4_lockless#56) rebuild_fd_flm: table rebuild failed
[fib_algo] inet.0 (radix4_lockless#56) rebuild_fd: sync rebuild failed
[fib_algo] inet.0 setup_fd_instance: radix4_lockless algo instance setup failed, failures=62
[fib_algo] inet.0 (radix4_lockless#56) rebuild_fd_flm: table rebuild failed
[fib_algo] inet.0 (radix4_lockless#56) rebuild_fd: sync rebuild failed
arprequest_internal: cannot find matching address
[fib_algo] inet.0 setup_fd_instance: radix4_lockless algo instance setup failed, failures=63
[fib_algo] inet.0 (radix4_lockless#56) rebuild_fd_flm: table rebuild failed
[fib_algo] inet.0 (radix4_lockless#56) rebuild_fd: sync rebuild failed
[fib_algo] inet.0 setup_fd_instance: radix4_lockless algo instance setup failed, failures=64
[fib_algo] inet.0 (radix4_lockless#56) rebuild_fd_flm: table rebuild failed
[fib_algo] inet.0 (radix4_lockless#56) rebuild_fd: sync rebuild failed
[fib_algo] inet.0 setup_fd_instance: radix4_lockless algo instance setup failed, failures=65
[fib_algo] inet.0 (radix4_lockless#56) rebuild_fd_flm: table rebuild failed
[fib_algo] inet.0 (radix4_lockless#56) rebuild_fd: sync rebuild failed
[fib_algo] inet.0 setup_fd_instance: radix4_lockless algo instance setup failed, failures=66
[fib_algo] inet.0 (radix4_lockless#56) rebuild_fd_flm: table rebuild failed
[fib_algo] inet.0 (radix4_lockless#56) rebuild_fd: sync rebuild failed
bound to x.x.x.y -- renewal in 3600 seconds.
anyone know why this is?
Forgot to disable suricata again?
I don't use suricata or zenarmor.
I have both vlans and DHCPv6 setup (working).
This has been happening since 23.7.
Everything "seems" to work ... excepting openvpn; on reboot I have to run "sudo ps auxww | grep openvpn" and then kill my openvpn connections, they spam on reboot until exhausting all the connections my provider offers, this is due to DHCPv6 (Turn off DHCPv6 and it stop happening), I then have to restart them manually and then apply the gateway configuration to get the monitors to work ... but my logs are constantly spammed.
I was wondering if there is a fix for the radix4_lockless issue as well, but there have consistently been no responses, and google doesn't pull very much up.
I figure this must be an edge case.
Cheers,
So that's not you?
https://forum.opnsense.org/index.php?topic=36429.msg177840#msg177840
Although I am not initiating it with the dhclient command, it seemed similar (the radix4 errors anyways).
This is where it starts on boot and then continues ad ininitum
<13>1 2024-02-10T13:30:10-06:00 dec850.semperubisububi.org opnsense 363 - [meta sequenceId="305"] /usr/local/etc/rc.bootup: plugins_configure dhcp (execute task : dhcpd_dhcp_configure(1)) │
│<13>1 2024-02-10T13:30:10-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="306"] <118>Setting up routes...done. │
│<13>1 2024-02-10T13:30:10-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="307"] <118>Starting DHCPv4 service... │
│<13>1 2024-02-10T13:30:10-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="308"] [fib_algo] inet.0 setup_fd_instance: radix4_lockless algo instance setup failed, failures=1 │
│<13>1 2024-02-10T13:30:10-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="309"] [fib_algo] inet.0 (radix4_lockless#55) rebuild_fd_flm: table rebuild failed │
│<13>1 2024-02-10T13:30:11-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="310"] <118>done.
..........................
<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="195"] [fib_algo] inet.0 setup_fd_instance: radix4_lockless algo instance setup failed, failures=30 │
│<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="196"] [fib_algo] inet.0 (radix4_lockless#55) rebuild_fd_flm: table rebuild failed │
│<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="197"] [fib_algo] inet.0 (radix4_lockless#55) rebuild_fd: sync rebuild failed │
│<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="198"] [fib_algo] inet.0 setup_fd_instance: radix4_lockless algo instance setup failed, failures=31 │
│<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="199"] [fib_algo] inet.0 (radix4_lockless#55) rebuild_fd_flm: table rebuild failed │
│<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="200"] [fib_algo] inet.0 (radix4_lockless#55) rebuild_fd: sync rebuild failed │
│<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="201"] [fib_algo] inet.0 setup_fd_instance: radix4_lockless algo instance setup failed, failures=32 │
│<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="202"] [fib_algo] inet.0 (radix4_lockless#55) rebuild_fd_flm: table rebuild failed │
│<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="203"] [fib_algo] inet.0 (radix4_lockless#55) rebuild_fd: sync rebuild failed
I am not trying to muddy the waters of lilsense's problem (if it is from something different then mine).
I was trying to figure this issue out again, this morning.
I saw his post and I thought it was similar to (though not the same) the problem I was having.
If these radix_lockless errors are something else, I apologize.
lilsense is the only other person who has posted about errors similar to what I have been getting since 23.7, on these forums.
Cheers,
Quote from: Saarbremer on February 10, 2024, 08:07:44 PM
So that's not you?
https://forum.opnsense.org/index.php?topic=36429.msg177840#msg177840
Suricata is working now, but even with Suricata disabled on WAN the DHCPv6 disappears after few hours.
Quote from: Koldnitz on February 10, 2024, 08:49:27 PM
Although I am not initiating it with the dhclient command, it seemed similar (the radix4 errors anyways).
This is where it starts on boot and then continues ad ininitum
<13>1 2024-02-10T13:30:10-06:00 dec850.semperubisububi.org opnsense 363 - [meta sequenceId="305"] /usr/local/etc/rc.bootup: plugins_configure dhcp (execute task : dhcpd_dhcp_configure(1)) │
│<13>1 2024-02-10T13:30:10-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="306"] <118>Setting up routes...done. │
│<13>1 2024-02-10T13:30:10-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="307"] <118>Starting DHCPv4 service... │
│<13>1 2024-02-10T13:30:10-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="308"] [fib_algo] inet.0 setup_fd_instance: radix4_lockless algo instance setup failed, failures=1 │
│<13>1 2024-02-10T13:30:10-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="309"] [fib_algo] inet.0 (radix4_lockless#55) rebuild_fd_flm: table rebuild failed │
│<13>1 2024-02-10T13:30:11-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="310"] <118>done.
..........................
<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="195"] [fib_algo] inet.0 setup_fd_instance: radix4_lockless algo instance setup failed, failures=30 │
│<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="196"] [fib_algo] inet.0 (radix4_lockless#55) rebuild_fd_flm: table rebuild failed │
│<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="197"] [fib_algo] inet.0 (radix4_lockless#55) rebuild_fd: sync rebuild failed │
│<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="198"] [fib_algo] inet.0 setup_fd_instance: radix4_lockless algo instance setup failed, failures=31 │
│<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="199"] [fib_algo] inet.0 (radix4_lockless#55) rebuild_fd_flm: table rebuild failed │
│<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="200"] [fib_algo] inet.0 (radix4_lockless#55) rebuild_fd: sync rebuild failed │
│<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="201"] [fib_algo] inet.0 setup_fd_instance: radix4_lockless algo instance setup failed, failures=32 │
│<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="202"] [fib_algo] inet.0 (radix4_lockless#55) rebuild_fd_flm: table rebuild failed │
│<13>1 2024-02-10T13:32:21-06:00 dec850.don'tworryabouthiswebsite.org kernel - - [meta sequenceId="203"] [fib_algo] inet.0 (radix4_lockless#55) rebuild_fd: sync rebuild failed
I am not trying to muddy the waters of lilsense's problem (if it is from something different then mine).
I was trying to figure this issue out again, this morning.
I saw his post and I thought it was similar to (though not the same) the problem I was having.
If these radix_lockless errors are something else, I apologize.
lilsense is the only other person who has posted about errors similar to what I have been getting since 23.7, on these forums.
Cheers,
I see the same behavior. Thanks for adding the info.
How many routes do you both have?
This indicates some problem initializing some structure in the routing code of BSD. That usually means some configuration (?) is invalid or ... you're running out of heap space.
could this be because of the RFC 6890 configuration in the system:routes:configuration section????
This makes no sense then as this was OK in 23.1.
https://datatracker.ietf.org/doc/html/rfc6890
I have 64 entries in my routes.
I don't know. I just know that my box with the current release doesn't show that behavior. So check your plugins
I have one WAN, 2 OpenVPN connections in a group with failover and a wireguard connection.
There is only one default gateway (WAN) and the VPN connections are used based on IP address.
I did the rfc6890 configuration as well... I have 30 of these configured (2 disabled because they are configured by default).
I have 73 total routes .... from the System: Routes: Status page.
Cheers,
Last summer I stumbled upon the following post:
https://forum.opnsense.org/index.php?topic=34190.0 (https://forum.opnsense.org/index.php?topic=34190.0)
I added the RFC6890 blackhole routes to System > Routes > Configuration and everything seemed to work fine.
This was on 23.1.X.
Fast forward to 23.7.X and 24.1.1 and the radix4_lockless errors were consistently spammed in my logs.
Once I disabled all these blackhole routes all the errors disappeared.
I hope this will help someone.
I plan to see if I can figure out which route is responsible and will update this post if / when I do.
Cheers,
Thanks... This makes perfect sense...