API Destination NAT

[theGinger]

Hi folks!

I'm new to OPNSense and the forum here.  I'm a recent convert from pfSense and was thrilled to see there was an API and a few Terraform providers around even if none of them are complete.

Working on a project where I would like to treat some OPNSense virtual appliances like cattle (its my home setup but its complicated for many reasons) and I was reading through the documentation and I don't see a way to create a DNAT rule (Port Forward) in the core API or in the os-firewall extension plugin.

My questions: is this intentional?  Are there technical hurdles to implementing DNAT rules in the API?

Someone else had asked a similar question a few years back https://forum.opnsense.org/index.php?topic=30356.0 but this was all I could find on the forum simmilar to my question here.

Thanks in Advance!
-The Ginger

[cookiemonster]

note: not speaking for devs nor the project. Sure I'll be corrected if I got this wrong.
The api is not feature-complete ie. not everything done via the UI and config files can be done via the api.
It might take a while, see https://docs.opnsense.org/development/guidelines/basics.html

[Monviech (Cedrik)]

Right now it seems like they incrementally working on making the os-firewall plugin more feature rich so that one day it can supersede the legacy firewall implementation. It also looks like from the commits that theyre working on implementing the plugin into the core.

https://github.com/opnsense/core/issues/6390