This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

API - NAT Creation Returns Success But Rules Not Visible

I'm working with the UTM 9 API and am having success creating Host Definitions and Additional Interfaces, but hit a snag on SNAT and DNAT rules.

The POST request returns successfully and when I do a follow up GET the rules are there. However, looking in the GUI under Network Protection>NAT>NAT, the rules are not visible. Results are the same from the API explorer or from command line.

The URL I'm using is https://[base URL]/api/objects/packetfilter/nat/

I know from creating the Additional Interfaces that the object creation isn't always straight forward. Am I missing some steps or using the wrong URL?

This thread was automatically locked due to age.

0 seroal over 7 years ago

Hi!

The same with me here... Creating Network Definintions was pretty smooth.

But with NAT Rules something is created in CC OBJS, but not visibile in MAIN.

In 127.0.0.1 MAIN nat > rules@ I have 5 entries, while in 127.0.0.1 OBJS packetfilter nat > I have 17 entries, with all that duplicates, when I retried to create the rules. Could somebody please explain, if we are doing anything wrong here? Is there something wrong in restfulapi?

Thanks,

Sebastian
Cancel
Vote Up 0 Vote Down

Cancel
0 sachingurung over 7 years ago

Hi Anthony,

Are you trying your hands with the RESTfulAPI?

seroal using cc > OBJS did you execute a write in the end to save the changes?

Thanks

Sachin Gurung
Team Lead | Sophos Technical Support
Knowledge Base | @SophosSupport | Video tutorials
Remember to like a post. If a post (on a question thread) solves your question use the 'This helped me' link.
Cancel
Vote Up 0 Vote Down

Cancel
0 seroal over 7 years ago in reply to sachingurung

Hi,

Iam only talking about using the Restfulapi.

I used cc only to take a look, if anything was created....!

Thanks
Cancel
Vote Up 0 Vote Down

Cancel
0 sachingurung over 7 years ago in reply to seroal

Thanks, I will recreate this in my Lab and update you further by Monday EOD. Please provide me some time on this.

Cheers and have a good weekend,

Sachin Gurung
Team Lead | Sophos Technical Support
Knowledge Base | @SophosSupport | Video tutorials
Remember to like a post. If a post (on a question thread) solves your question use the 'This helped me' link.
Cancel
Vote Up 0 Vote Down

Cancel
+1 Anthony Hartman over 7 years ago in reply to sachingurung

I actually did get a solution to this. Turns out I was missing a header:

'X-RESTD-INSERT: nat.rules -1'

That determines where in the list the NAT rule is placed, and it won't be active without it. The "-1" meant it would be created at the bottom of the list, but you can change that.

See page 11 of the API document:

www.sophos.com/.../Sophos-UTM-RESTful-API.ashx
Cancel
Vote Up 0 Vote Down

Cancel
0 seroal over 7 years ago in reply to Anthony Hartman

Hi Anthony,

thanks for your comment, thats working like a charme. But you don´t need to add -1 on the end, if you use, 'X-RESTD-INSERT: nat.rules', it is automatically created at the bottom.

That will help a lot in future, cool feature, the rest api.

Thanks,

Sebastian
Cancel
Vote Up 0 Vote Down

Cancel