Show Posts
1
23.7 Legacy Series / API Destination NAT
« on: January 12, 2024, 06:52:28 pm »
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
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