I upgraded from the latest 25.7 version to 26.1 and within an hour my network went down. Sometimes I could get part of the OPNSense Web UI to load but nothing was functional. I went to check the console on the machine and saw that it was filled with an out of swap space error. My only option was to force reset the machine. Upon it rebooting I went into the Web UI and could see the memory usage rising in real-time. I ran the command ps -faxdvvv and got the output, which appears to be full of /usr/local/bin/php /usr/local/etc/rc.newwanipv6 igc0 SOLICIT
I have no idea what is going on but my machine keeps needing to be force reset every hour or so.
Pastebin of full output: https://pastebin.com/WBTCzXgr (https://pastebin.com/WBTCzXgr)
I have had zero issues with OPNsense on this box for around 3 years now.
I don't know if the locations are the same, but this is usually due to using a RAM disk for logging under "System: Settings: Miscellaneous" -> "Disk / Memory Settings (reboot to apply changes)". Not the root cause, but most systems have more storage than RAM, and ZFS compresses logs very effectively. You can then hunt down the root cause without worrying (so much) about crashing.
Quote from: acffordyce973 on February 06, 2026, 10:57:46 PMI ran the command
ps -faxdvvvand got the output, which appears to be full of
/usr/local/bin/php /usr/local/etc/rc.newwanipv6 igc0 SOLICIT
Sounds like : https://forum.opnsense.org/index.php?topic=50505.0 ?!
As we found dhcp6c going haywire is a very old bug in the daemon when it acquires neither NA nor PD and just tries again immediately.
The particular report was fixed during RC testing, but in practice this can always happen when your ISP doesn't return you anything which can point to a latent misconfiguration (either on their end or yours).
Cheers,
Franco
I disabled IPv6 everywhere and that fixed the issue. I then re-enabled IPv6 and tried changing various settings. Turns out "Send rapid commit" was added and got enabled in both my LAN and WAN's DHCPv6 config and was running a script again and again and again until the system ran out of memory. Disabling this option and then rebooting fixed the issue.
It shouldn't get auto enabled and it shouldn't be running a script over and over.