Messages

Unfortunatelly not. These separators are really a feature, that I like pretty much on my pfSense installation and I miss in OPNsense. Not just for NAT, also in rules.
In OPNsense there is no equivalent for NAT at all and in rules is just a category filter that does not allow this intuitive grouping, like it can be done with separators.

Maybe you should open a feature request on github.

Thanks for the reply, I've actually since moved on from OPNsense. I was getting really poor NAT results from pfSense and OPNsense. Turns out they both use the same, broken, implementation of UPnP so my brother, and I would constantly run into Strict NAT or just not be able to play the same game in general.

I've been running Untangle for a bit now. I will say I do miss OPNSense and it's capabilities and look but until they start using an implementation of UPnP that actually works, I'm kind of forced to look elsewhere.

Hi all,

I've been using OPNsense for about a month now and have really enjoyed it. However, coming from pfSense, there is a specific feature that I've been missing, but can't seem to find an equivalent for on OPNsense. On pfSense, I was able to somewhat group/organize all of my port forwarding rules by service type (RDP, Games, Websites, etc..) using "Separator"s. This just seemed to make reading and working on rules much much easier and helped compartmentalize the port forwards screen. Is there a way to do something similar in OPNsense that I have just missed?

Thanks in advanced.

Here is an example of what I'm talking about: