Recent posts

#1
26.7, 26.10 Series / Re: Feature Request - Gateway ...
Last post by dmcgough - Today at 05:15:30 AM
Smart thinking - thanks again for the help!
#2
26.7, 26.10 Series / Re: Feature Request - Gateway ...
Last post by mlenje - Today at 05:12:29 AM
Makes sense. One stopgap until that exists:

Catch the DNS server changing: a small script run from cron or as a Monit "program" check could compare the WAN's current DHCP-provided DNS server with the gateway's configured monitor IP, and alert when they differ. It doesn't fix the monitor automatically, but you'd find out the day the ISP changes it, rather than when the secondary unexpectedly shows down.
#3
26.7, 26.10 Series / Re: Feature Request - Gateway ...
Last post by dmcgough - Today at 05:00:05 AM
Thanks, I was unaware of the "Disable Host Route" option. This will make it easier to pick some example anycast addresses. I may still look into making the FR for monitoring multiple targets and setting down criteria. That way, I can test per-link reachability to multiple remote networks that matter to me. This would help enact a fail over if there are peering problems to a network that matters to me.

I still prefer having the option to monitor an 'internal' address as well, like the WAN-provided DNS server. It's something beyond the ISP gateway but not so far as a foreign network address, and it's something that should be up all the time. It doesn't change often, but it's something that's made available programmatically. If I can say "monitor the DHCP-provided DNS server" vs "monitor this IP that I looked up that, at the time of configuration, was the DHCP-provided DNS server"... it accomplishes the same goal - until it doesn't. Anything where I can configure my intent (that should continue to function after changes are made) vs something explicit is almost always preferable.

The 'defining bad' was more about being able to define failover conditions once I'm able to monitor more than one IP. I was aware of the very granular per-gateway packetloss and latency configurations - just need to extend that concept to multiple members and settings AND / OR conditions. Does one high packetloss to 1 of 3 monitor IPs initiate a failure, or does it need to be 2 of 3? That sort of stuff.
#4
Virtual private networks / Re: Issue with multiple wiregu...
Last post by mlenje - Today at 04:22:45 AM
I run several ProtonVPN and Mullvad WireGuard tunnels at the same time in a failover group, so here's what has worked for me:
/30 vs /32: with a /30, Proton's 10.x.0.1 sits on the tunnel's own subnet, so the firewall treats it as directly connected. That's why it doesn't get a separate route, as Bob.Dig said.

Monitor IP: for the same reason, monitoring 10.x.0.1 only proves the tunnel is up, not that traffic gets past Proton to the internet. I use a different public IP for each tunnel. Each one gets a host route through its own tunnel, so it shouldn't also be one of the DNS servers your clients use.

Handshake vs real traffic: a recent handshake only means the encrypted session is up. dpinger tests the whole path. After any change I test both ICMP and a real TCP connection, because I've seen one work while the other failed.

NAT: +1 to EOC_Jason. One outbound NAT rule per tunnel.

Debugging: Firewall → Log Files → Live View has been far more reliable than tcpdump on the wg interfaces, which can be misleading on FreeBSD.

One Proton-specific thing: some Proton servers reply to the shared 10.2.0.2 address instead of your tunnel address, so dpinger shows 100% loss even though the handshake is fine. Those servers need BINAT; others don't. I wrote this up here: https://forum.opnsense.org/index.php?topic=52712.0 (see reply #3 for the per-server behavior and the Live View check). Since then I've also seen a server's behavior change over time with no change on my side, so if a tunnel suddenly shows down with a fresh handshake, check Live View again before changing anything else.
#5
26.7, 26.10 Series / Re: Feature Request - Gateway ...
Last post by mlenje - Today at 04:11:44 AM
Host route: yes, your suspicion is right. A monitor IP gets a /32 host route via that gateway, so all routed traffic to that IP goes out that WAN, not just the monitoring pings. The fix is the gateway's advanced option "Disable Host Route", or picking monitor IPs you don't otherwise use. That's also why it's a bad idea to monitor the DNS server your clients actually use. A common pattern is a different public anycast IP per WAN (for example 1.1.1.1 on one, 9.9.9.9 on the other), none of them used for DNS.

Monitoring past the gateway: agreed, monitoring the ISP's next hop only proves the link to the ISP is up. A stable public anycast IP tests real internet reachability, and it won't change the way an ISP's DHCP-provided DNS can.

Defining "bad": this already exists. Each gateway has latency and packet loss thresholds under its advanced settings, plus probe interval, time period and loss interval. In the gateway group, the Trigger Level lets you choose whether failover happens on Member Down, Packet Loss, High Latency, or Packet Loss or High Latency.

Multiple monitor targets ("fail only if all 3 fail"): as far as I know there's no native option. dpinger monitors one target per gateway. That would be a good feature request on GitHub (opnsense/core).

Noticing problems on the secondary: dpinger logs every state change, so grep 'Alarm' /var/log/gateways/latest.log shows every drop, including on a link that isn't carrying traffic.
#6
Hi there, i am having a problem with my firewall/opnsense, its making the internet traffic coming through to my home network intermittent and very slow at best. I have spend a ridiculous about of time testing/researching the problem but i cant find anything. Can someone help or point me in the right direction. Is there anyway to set his up basically to just work as a firewall and then add to it. Please go easy i am just amateur here, i know enough to be dangerous. Thanks in advance.
#7
26.7, 26.10 Series / Re: Maltrail Suspicious Traffi...
Last post by nicholaswkc - Today at 03:08:57 AM
Problem solved, I had apply the checked add alias again and it worked. I can created the block in firewall.
#8
26.7, 26.10 Series / Re: [CALL FOR TESTING] Defer P...
Last post by (MARLOO) - Today at 03:07:23 AM
Hi Franco,

I applied commit 39cca4ca785 on OPNsense 26.7.9_3-amd64 with PPPoE, and it works very well.

The patch delays PPPoE startup until the VLAN and interfaces are ready. After rebooting, PPPoE connects successfully, PAP authentication completes, the WAN gets its IPv4 address, and the default route is set on pppoe0. The firewall also boots a bit faster.

This makes the WAN startup much more reliable and predictable. Since my connection had been unstable after the update, I will keep the patch applied.

Yes, you are probably right — I may have just hit a fluke with my ISP, The ONT was also flashing red at the time.

Thanks again for providing such an effective fix
#9
26.7, 26.10 Series / Re: Maltrail Suspicious Traffi...
Last post by nicholaswkc - Today at 02:51:06 AM
I had enable the  Add Blocklist Alias checked but still no alias was created.
#10
26.7, 26.10 Series / Re: Maltrail Suspicious Traffi...
Last post by nicholaswkc - Today at 02:45:06 AM
I found this reddit thread saying is possible to block Maltrail detection traffic using blocklist.  There is no maltril blocklist as created.

https://www.reddit.com/r/opnsense/comments/1gemcxs/maltrail/

Please share some step by step guide to implement it.