Recent posts

#1
26.7, 26.10 Series / Re: Https Squid Proxy
Last post by nicholaswkc - Today at 07:07:31 PM
Anyone can share the step by step guide to configure https squid traffic will be nice to have. Thanks.
#2
26.7, 26.10 Series / Re: Feature Request - Gateway ...
Last post by pfry - Today at 07:06:11 PM
Quote from: dmcgough on <strong>Today</strong> at 06:40:45 PM[...]I don't want to suddenly start routing all of my actual traffic to 8.8.8.8 via WAN2[...]

You could include a policy routing rule in your enhancement request. In the mean time you could configure (or more) one manually, or ping an IP you're not using for other purposes (e.g. ping 8.8.4.4 if you use 8.8.8.8 as a resolver). I don't think a policy route for ping from the firewall specifically would be detrimental in any meaningful way. Then again, I'm just assuming configuration of such is a simple matter in pf, as I don't use policy routing.

Aside: It's a bit disappointing that Cloudflare uses 1.0.0.1, but does not name it "SOS". Aside aside: I keep seeing "gateway" as "getaway".
#3
26.7, 26.10 Series / Re: Static-port outbound NAT d...
Last post by anomaly0617 - Today at 06:56:30 PM
Quote from: lmoore on November 17, 2026, 06:59:58 AMIf you have more than one public IP address on your service, you could use One-to-One NAT (BINAT) between your ITSP and your internal PBX and see if that changes the behaviour.

I wish I could dedicate one static IP address to just the PBX, but I don't have that ability in this case. IP addresses are assigned based on whether a port is in use or not on that static IP, and routed to the appropriate internal server. If I did One to One or BiNAT, everything would have to go to the PBX.

Quote from: lmoore on November 17, 2026, 06:59:58 AMI've read various postings about port-forwarding to the internal PBX. I have not encountered a situation where this has been a requirement. Firewall configurations I've used rely upon the connection for the outgoing registration as the channel with which incoming calls will arrive from the ITSP.

In your environment, and prior to 26.7.8_1, what problem does forwarding inbound connections for port range 5060-5063 resolve for you?

Most VoIP carriers try to establish a connection to you in addition to you registering a connection to them. If it doesn't work, they will notify us that one (or more) of their locations cannot reach one (or more) of our locations. This isn't universal - I've seen some VoIP carriers that don't do it, but the good ones seem to do it.

Quote from: lmoore on November 17, 2026, 06:59:58 AM...I may look into this quirk one day and see if changing the Firewall rule setting under advanced mode of the Destination NAT entry from Manual to Register rule.
Perhaps you are seeing something similar with your VoIP traffic.

I have seen this before, and YES, registering the rule has been the solution for me when it has come up. This has happened specifically as we have upgraded from one version of OPNsense to another, and the rule engine on the back end has changed. It's become SOP for us to check all the ports that are supposed to be open on a firewall at a site before we do an upgrade, and then directly after the upgrade we check again. That policy came into existence because of exactly what you are referring to.

Thanks for your response!!
#4
26.7, 26.10 Series / Re: Static-port outbound NAT d...
Last post by anomaly0617 - Today at 06:47:20 PM
First, I appreciate the responses. Let me see if I can provide some answers to some questions...

What we're seeing here happens only when we have multiple static IP addresses AND the static IP address used for the VoIP carrier is not the primary one. So if it is a location with a /30 block (1 static), they don't have a problem. If it's a location with a /29 block (5 statics) or /28 block (13 statics).... as long as the traffic exits the network to the VoIP carrier on the primary IP address of the OPNsense firewall, it's not a problem. It's only when the traffic exits the network to the carrier on a secondary IP address and we have an SNAT rule in place to make sure that traffic leaves on the right IP address that we see the issue.

I have enough instances of OPNsense out there to state that I've checked the issues across multiple firewalls at many sites, and this is the specific environment where I'm seeing it happen.

In this specific case, the primary static IP address (last octet) ends in 146. The VoIP traffic to carriers is supposed to be exiting on 147 per the SNAT rule, but instead it's exiting the network on 146, the primary. The carriers reject that traffic, because we have told them the endpoint is 147. The result is that when you try to make an outbound phone call, you get a 403 error on the handset, and in the VitalPBX logs.

There's an exceptionally easy workaround to this problem - just point the VoIP carrier to your primary static IP, and then when you send traffic out to them, it goes out on the primary IP. Problem solved, right? But it's not really solved, because what we're doing here is working around the problem rather than getting to the root of it.

At the location above, I use two different VoIP carriers based on the phone number - Skyetel and Vitelity. Both are seeing this problem since we upgraded from 25.7 to 26.7.8_1, so it's not the carrier that is the problem.

This setup is co-located in a datacenter. They have 51 (at last count) internet circuits coming into the datacenter, and based on latency, priority, and cost, we can use any one of them as our pipe out to the internet. In the 7 years that I've had gear in that datacenter, the Internet has never dropped due to the upstream internet providers. If one goes down it switches to another seamlessly. If there's a problem with the internet, it's almost 100% because we did something stupid. As an example, years ago when I was setting up high availability (HA) between two OPNsense firewalls, I messed up and gave them both the same advertisement base. Chaos ensued while they fought over which one was the Master and which was the Backup until I could get a guy at the datacenter to wheel over a crash cart with a separate Internet connection to my rack, get in, and fix it. And even then, I had to fight through a parity issue where some interfaces were master on FW 1 and some were master on FW 2.

Also, our setup there runs on bare metal hardware - two Dell PowerEdge R330's with redundant drives, redundant power supplies, and redundant network connections. The network card in each server is a 10GB Intel quad port card.

I tell you all of this because I want to emphasize that this is not a "home-modded chinese POS single board computer" on "a flimsy coax or DSL connection." This is happening in a redundant, high availability environment with cooling at a constant 56 degrees, multiple power providers with a massive generator for failover, and a pretty rock solid internet connection.

If a dev wants to examine logs, packets, or whatever for themselves - PM me. I'll set you up with temporary access so you can see it happening. If I can provide logs or something else useful, let me know. But I'd rather fix the problem than work around it, because as I said, I can work around it, but that does not make OPNsense better for everyone.

Thanks, all!
Paul
#5
26.7, 26.10 Series / Re: Feature Request - Gateway ...
Last post by dmcgough - Today at 06:40:45 PM
I want to know if the source IP address of my WAN interface can reach a certain IP / set of IPs. But on my WAN2 interface, if I test 8.8.8.8 because it's a great universal testing point, I don't want to suddenly start routing all of my actual traffic to 8.8.8.8 via WAN2. In routing terms, it would be a VRF. A separate routing table, just for a subset of communications. A process for monitoring that IP would use this routing table, would generate the monitor packets from the WAN2 interface, but my inside systems wouldn't send traffic out WAN2 unless I specified it (or unless it failed over).

Because I want to test reachability doesn't mean I want to affect actual traffic routing decisions. I can imagine that if a site saw a session that was supposed to be from one client start coming at them from two (wildly) different source IP addresses, that would likely start triggering some security rules. One session should only come from one source IP, but if my 'testing' also starts splitting active traffic between links, this sort of situation could happen. Unlikely, but possible.
#6
General Discussion / Re: Internet only vlan with IP...
Last post by Maurice - Today at 06:36:52 PM
Quote from: nero355 on <strong>Today</strong> at 05:14:46 PMI forgot to ask : Can the 'NULL Route configuration' mentioned some time ago prevent that ?

Prevent what?

For packets handled by policy routing, a null route does nothing since the routing table is ignored.

And a null route by itself cannot prevent access from one LAN to another. It just blackholes packets to destinations which don't exist.
#7
26.7, 26.10 Series / Re: https://nginx2root.com/ Is...
Last post by franco - Today at 06:09:52 PM
Quote from: bimbar on <strong>Today</strong> at 04:33:41 PMI hope it will get better when the bugs are mostly found.

It's a possibility, although things will never be quite the same again.


Cheers,
Franco
#8
Tutorials and FAQs / Re: OPNsense aarch64 firmware ...
Last post by nero355 - Today at 05:56:20 PM
Quote from: Carcharoth on <strong>Today</strong> at 05:54:38 PMYes, of course! Thank you for the idea!
https://github.com/Tellyke892/opnsense-netgate-1100
AWESOME!!! :)
#9
Tutorials and FAQs / Re: OPNsense aarch64 firmware ...
Last post by Carcharoth - Today at 05:54:38 PM
Quote from: nero355 on <strong>Today</strong> at 04:44:38 PM
Quote from: Carcharoth on November 19, 2026, 04:36:54 PMThanks to the awesome work Maurice has done I was able to install Opnsense into a Netgate 1100, and it's working. If anyone is curious I'll link a full guide.

https://drive.google.com/file/d/1jy6wmW2TumZvh1PlwcIhep5jogcSxo15/view?usp=sharing
May I suggest converting this guide to GitHUB/GitLAB/whatever you like the most... for easier access and readability ? :)

Yes, of course! Thank you for the idea!
https://github.com/Tellyke892/opnsense-netgate-1100

Quote from: Maurice on November 19, 2026, 05:58:50 PMThanks for the success story and the tutorial. Interesting to hear that bootefi works on this hardware and with this U-Boot build. That's not always the case...

If you use a ufs-serial-vm-aarch64 image (which defaults to a serial console), you'll have console access from the start. I create these specifically for devices without a video console.

If you erase the eMMC before you write the OPNsense image to it, you don't have to manually repair the backup GPT header.

You don't have to change anything in System / Firmware / Settings. In my aarch64 VM images, the "(default)" mirror already points to my repo.

Cheers
Maurice
Thank you for the corrections, I addressed them in the github repo!
#10
26.7, 26.10 Series / Port 1194 wrongly displayed as...
Last post by viragomann - Today at 05:46:57 PM
This is OPNsense 26.10.0p1.

In the rule set view port 1194 is shown up as "OpenVPN (Group) network" instead of "OPENVPN (1194)".

You cannot view this attachment.

When editing the rule, the the port is shown correctly.

You cannot view this attachment.