"Recent posts
#1
General Discussion / Re: Help with turnserver commu...
Last post by nero355 - Today at 10:08:13 PMQuote from: NoelleAttachedStorage on Today at 07:14:27 PMBump with a picture of my spare parts opnsense build.As a former Thermalright freak I approve this build !!!
- https://tweakers.net/i/mCY0F_YNMut5Ir9Aa-teoFO71zo=/fit-in/4920x3264/filters:max_bytes(3145728):no_upscale():strip_icc():strip_exif()/f/image/YB4h9eBrBWWLV53H8MffQWsN.jpg?f=user_large
- https://tweakers.net/i/QRkJJxvp7gXqCP1fFuFnd3dYaCs=/fit-in/4920x3264/filters:max_bytes(3145728):no_upscale():strip_icc():strip_exif()/f/image/3J1WlWNHDpqFwGQGaQp1FULd.jpg?f=user_large
;)
#2
General Discussion / Re: Upgrade from 24.7.9_1 to l...
Last post by techgirl45 - Today at 10:04:28 PMMany thanks for this. I reconfigured it all in the new server and it's working fine now. The Firewall is upgraded now to the latest version so I'm very happy. I'm trying to get OpenVPN working now, tunnel comes up but routing to it seems to be an issue although NAT rules seem fine. Hopefully I'll have it running soon!
#3
Hardware and Performance / Re: Warning about RealTek adap...
Last post by nero355 - Today at 10:01:24 PMQuote from: Seimus on Today at 05:17:51 PMI have very bad experience with Intel and DDR5, and that doesn't apply only for PCsIs those were ASUS mainboaards then I am not surprised to be honest.
Also some of the Intel N100 (and others) "NUC" like models can be picky about RAM.
Quotethat but as well Server systems.In the Server/Workstation world that's considered normal and I have epxerienced it myself with many HPE models from the E5-2650v1/v2/v3 era in the past :)
#4
26.1 Series / Re: 26.1.2 - crashed and reboo...
Last post by franco - Today at 09:56:18 PMI highly doubt it.
Cheers,
Franco
Cheers,
Franco
#5
26.1 Series / Re: test for future post
Last post by franco - Today at 09:55:52 PMSo was your test successful? ;)
Cheers,
Franco
Cheers,
Franco
#6
General Discussion / Re: AmneziaWG on OPNsense and ...
Last post by franco - Today at 09:54:13 PM> With some modifications, I've compiled a plugin package:
> https://github.com/antspopov/opnsense_amnezia_plugin
I applaud your efforts but I think we have enough WG implementations in the plugin system now.
Cheers,
Franco
> https://github.com/antspopov/opnsense_amnezia_plugin
I applaud your efforts but I think we have enough WG implementations in the plugin system now.
Cheers,
Franco
#7
25.7, 25.10 Series / Re: Unbound on OPNsense 25.7 L...
Last post by SenseX - Today at 09:13:58 PMQuote from: Wrigleys on October 18, 2025, 09:58:26 PMAre there any updates on this case?Hi,
I've experience the same issue when I configure DoT in Unbound with Quad9 Servers even when I only enable 1 Server (ex. 9.9.9.9). Most times, the issue is reproducible (no DNS resolution for any DNS-client; SERVFAIL in Log) after running the following DNS-Checker: https://dnscheck.tools
Thanks for your update.
Got the same error with 26.1.2 also when i run the DNS-Checker.
#8
26.1 Series / Data not reset after reboot bu...
Last post by FredFresh - Today at 08:53:48 PMI have an issue somewhere with a multiwan configuration where I put 3 wireguards to higher priority than the WAN interface.
At a randomic moment (sometime after 1 day sometime after a week) the wireguard connections are note renewed one after another (also in this case with a random delay of days). The VPN log tells me that the handshake is not renewd.
The only way I found to restore the handshake is:
- forcefully change the WAN pubblic address exposed to the opnsense wan interface (restart the modem);
- switch off, wait 30 secs and than switch on the opnsense (just the restart is not effective).
My question is what data/routing/other "resist" the reboot but not the stich off/on. Otherwise everything seems to be properly working and I am not able to find a solution (I have crowdsec and intrusion detection but no alerts are communicated).
I know this is a very weird question, but it would be really helpfull.
Thanks.
At a randomic moment (sometime after 1 day sometime after a week) the wireguard connections are note renewed one after another (also in this case with a random delay of days). The VPN log tells me that the handshake is not renewd.
The only way I found to restore the handshake is:
- forcefully change the WAN pubblic address exposed to the opnsense wan interface (restart the modem);
- switch off, wait 30 secs and than switch on the opnsense (just the restart is not effective).
My question is what data/routing/other "resist" the reboot but not the stich off/on. Otherwise everything seems to be properly working and I am not able to find a solution (I have crowdsec and intrusion detection but no alerts are communicated).
I know this is a very weird question, but it would be really helpfull.
Thanks.
#9
26.1 Series / Re: Multi WAN question/solutio...
Last post by zo0 - Today at 08:19:18 PMOh thanks!
Guess what I want to do is neither weird nor heretical haha
Guess what I want to do is neither weird nor heretical haha
#10
26.1 Series / Multi-wan setup and high laten...
Last post by crustymonkey - Today at 07:56:14 PMThough I recently updated my machine to 26.1, I was seeing this odd behavior on 25.x as well.
I just added another internet connection to my firewall (had xfinity and just added Quantum). I setup multi-wan and I'm using 8.8.8.8 as the monitor IP on my xfinity connection. I setup the quantum connection to use 1.1.1.1 (and I've tried others). The setup all appears to be correct (`netstat -rn` looks correct). However, the problem I'm having is that the web interface is showing that the quantum connection latencies are insane, between 500 and 1200ms. However, if I ssh to the firewall and just `ping 1.1.1.1` from the command-line, I see what I would expect in no packet loss and a latency of 3 to 5ms.
I'm not sure how opnsense is testing these connections, exactly, but it appears there is a flaw in the evaluation or I'm missing some setting somewhere. I'm wondering if anyone else has run into this?
I just added another internet connection to my firewall (had xfinity and just added Quantum). I setup multi-wan and I'm using 8.8.8.8 as the monitor IP on my xfinity connection. I setup the quantum connection to use 1.1.1.1 (and I've tried others). The setup all appears to be correct (`netstat -rn` looks correct). However, the problem I'm having is that the web interface is showing that the quantum connection latencies are insane, between 500 and 1200ms. However, if I ssh to the firewall and just `ping 1.1.1.1` from the command-line, I see what I would expect in no packet loss and a latency of 3 to 5ms.
I'm not sure how opnsense is testing these connections, exactly, but it appears there is a flaw in the evaluation or I'm missing some setting somewhere. I'm wondering if anyone else has run into this?
