Recent posts

#1

Virtual private networks / Re: Wireguard connection not s...

Last post by OPNenthu - Today at 01:48:59 AM

Try testing from a wired PC?  Not only is this a potentially unstable wireless link but you also have the issue of the mobile phone's power optimizations that could mess with the network.

#2

26.1, 26,4 Series / Re: OPNSense not able to re-cl...

Last post by Patrick M. Hausen - Today at 12:33:29 AM

FreeBSD as a "traditional" Unix does not have an explicit OOM killer. But in situations of memory pressure, whenever a process demands swap space while swap space is exhausted, it's killed.

#3

26.1, 26,4 Series / Re: Upgrade from 26.1.4 to 26....

Last post by nero355 - Today at 12:27:50 AM

My guess - it often depends on your browser. Using LibreWolf like me might not be the best idea if you update OPNSense.. *shrug*

Main browsers here are :
- Pale Moon @ Windows + Linux
- LibreWolf @ Linux

I can't remember which I have used the most so I will try to remember to do the next update with LibreWolf because I know the last one was done with Pale Moon :)

But error messages starting with "Danger" - well, that just feels like your forgotten uncle from Nigeria sending you millions of Dollars..

LOL! ^_^

#4

26.1, 26,4 Series / Re: OPNSense not able to re-cl...

Last post by nero355 - Today at 12:24:56 AM

Tbh, I don't know about it. I thought that if every service running, it should be fine.

Since you mentioned hostwatch service have a lot of strange issue, should I disable it?

Considering the fact that you also wrote this :

Also, a bit update from my end. My RAM usage looks stable (within 25-35%), but it starts eating disk space little by little. Previously, it was 3.6GB and now it's already 4.6GB from the total of 32GB (12+ hours since I disabled the Temp RAM and SWAP settings).

Should I be concerned about this?

YES! Absolutely!

#5

26.1, 26,4 Series / Re: Upgrade from 26.1.4 to 26....

Last post by Zeitkind - June 13, 2026, 11:43:24 PM

My guess - it often depends on your browser. Using LibreWolf like me might not be the best idea if you update OPNSense.. *shrug*
But error messages starting with "Danger" - well, that just feels like your forgotten uncle from Nigeria sending you millions of Dollars..

#6

Virtual private networks / [solved] Re: Dual-stack failov...

Last post by OPNenthu - June 13, 2026, 11:37:01 PM

Got it working after re-visting the section on configuring IPv6 in the OPNsense documentation for selective routing.

If you're following other sources, such as a pfSense tutorial on YouTube which uses the same IPs for both the tunnel and gateway, just know that this doesn't work here.  It's not just a preference; it's a requirement for the monitor to work at all.  OPNsense (at least 26.1) I think treats the WG tunnels as routed point-to-point links when configuring gateways even though they really aren't so we have to use those semantics.

Mullvad configs are using /128 so I had to do the trick mentioned in the docs to manually set the config to /127 and use the other matching IP in that range for the IPv6 gateway.  I left the IPv4 tunnel address as /32 but used IP-1 for the IPv4 gateway.  Now both in-tunnel IPs and external (public) IPs can be pinged by the monitor.

This works but it does also produce some noise in the WireGuard logs:

Code Select Expand

Notice
wireguard
/usr/local/opnsense/scripts/wireguard/wg-service-control.php: Chose to bind WAN_VPN2_GW on 10.xx.xxx.198 since we could not find a proper match.

I'm assuming this is expected and safe to ignore since .198 is the interface address.  Maybe it's seeing the gateway address (.197) as well and realizing that it's bogus.  Not sure.

One more observation: the trick of using traceroute to find the next-hop tunnel address to use as a monitor IP doesn't work for all Mullvad peers, or it only turns up the aforementioned gateway (fc00:bbbb:bbbb:bb01::1) that is common to all tunnels.  I switched to using public DNS IPs.  Hopefully Mullvad will some day provide IPv6 versions of their in-tunnel name servers.

#7

French - Français / Re: Débutant : IPv6 derrière f...

Last post by geekpe - June 13, 2026, 10:03:08 PM

Bonjour

Est-ce que cela fonction chez nous sous opnsense 26.1.9 ?

Cordialement

[Running Services:]

#8

26.1, 26,4 Series / Re: OPNSense not able to re-cl...

Last post by Afif - June 13, 2026, 08:37:33 PM

This has been happening since last year

Did you start using

Running Services:

• hostwatch

At the same moment perhaps ?

There have been a lot of strange issues with it since it was introduced !!

Tbh, I don't know about it. I thought that if every service running, it should be fine. Since you mentioned hostwatch service have a lot of strange issue, should I disable it?

Also, a bit update from my end. My RAM usage looks stable (within 25-35%), but it starts eating disk space little by little. Previously, it was 3.6GB and now it's already 4.6GB from the total of 32GB (12+ hours since I disabled the Temp RAM and SWAP settings). Should I be concerned about this?

#9

26.1, 26,4 Series / Re: Upgrade from 26.1.4 to 26....

Last post by nero355 - June 13, 2026, 08:25:13 PM

I lost interest in most error messages during updates.
They appear so often that I now ignore them

Of all the updates that I have done from OPNsense 24 to 25 to 26 and everything in between there were ZERO ERRORS so my guess is you guys are having strange connection or DNS issues :)

[Running Services:]

#10

26.1, 26,4 Series / Re: OPNSense not able to re-cl...

Last post by nero355 - June 13, 2026, 08:20:16 PM

This has been happening since last year

Did you start using

Running Services:

• hostwatch

At the same moment perhaps ?

There have been a lot of strange issues with it since it was introduced !!