Port Forwarding with SonicOS API in GEN7 - using Postman and cURL

05/29/2023 2 People found this article helpful 239,720 Views

Description

SonicOS API provides an alternative to the SonicOS Command Line Interface (CLI) for configuring selected functions.

This article only explains how to add a static route for an internal network to use a specific ISP(WAN). Please follow the below articles for additional assistance:

You are free to choose Swagger, Postman, Git bash, or any application that allows API calls. If you are using a Linux-based operating system, you can execute cURL from the terminal. Please refer to https://sonicos-api.sonicwall.com for the entire list.

Only the first part of this article would change, depending on the SonicWall model you use. Commands are the same for both Gen6 and Gen7 SonicWall devices.

For this article, I'm using Postman App and will be showing the commands to run on cURL for each step.

Resolution

SonicOS API is disabled by default in SonicOS. Any attempt to access SonicOS API while it is disabled results in an HTTP 403 Forbidden error. To use the SonicOS API, you must enable it, either through the SonicOS Management Interface or from the CLI. Please enable the SonicOS API module in the SonicWall UI.

Gen 7: Enable SonicOS API Gen7

Gen 6: Enable SonicOS API Gen6

The above KB also has the steps on how to log in using API Applications

CAUTION: My SonicWall IP address is 192.168.168.168 with user credentials as admin/password. This has to be kept in mind while running the commands from the below screenshots.

Step 1: Login using SonicOS API

The following 3 steps need to be performed for every API request.

NOTE: https://IP-address:port/-- Replace this with your SonicWall's Public or private IP address with the right management port number (If the management port is 443, you can directly use https:// followed by the IP address without the port number too).

a) The HTTP method should be POST and we need to use the URL: https://192.168.168.168/api/sonicos/auth
Under the authorization tab, select Basic Auth and mention the correct admin credentials.

b) Under the settings tab, turn OFF the Enable SSL certificate verification if the firewall is using a self-signed certificate for management.

c) Under the headers tab, include application/JSON as the value for keys Accept and Content-type.

d) The Gen 7 devices are token-driven. Use the {"override" : true} under the body to override any older tokens. This is used only during login.
After this, click on the Send button and then you can see the response on the section below. The response should contain a message: "success".

e) After this, click on the Send button and then you can see the response on the section below. The response should contain a message: "success".

cURL code:

curl --location --request POST 'https://192.168.168.168/api/sonicos/auth' \

--header 'Accept: application/Json' \

--header 'Content-Type: application/Json' \

--header 'Authorization: Basic YWRtaW46cGFzc3dvcmQ=
--data-raw '{"override" : true}'

Step 2: Source and destination network

Portforwarding using GUI is also explained in How can I enable port forwarding and allow access to a server through the SonicWall?

Let us first create the necessary object - Public IP address object getting translated to Private address object, on a custom service port

Add address objects:
This creates 2 objects. As explained in the Summary above, Terminal server will be called using public IP which gets translated to its private IP

cURL command:
curl -L 'https://192.168.168.168/api/sonicos/address-objects/ipv4' \
-H 'Content-Type: application/Json' \
-H 'Accept: application/Json' \
-H 'Authorization: Basic YWRtaW46cGFzc3dvcmQ=' \
-d '{
"address_objects": [
{
"ipv4": {
"name": "Term Server Private",
"zone": "LAN",
"host": {
"ip": "192.168.168.10"
}
}
},
{
"ipv4": {
"name": "Term Server Public",
"zone": "WAN",
"host": {
"ip": "1.1.1.1"
}
}
}
]
}'
Add service object:
This example will be using TCP 3389 port as service.

Step 3: Creating NAT policy

cURL command:

`curl -L 'https://192.168.168.168/api/sonicos/NAT-policies/ipv4' \`
`-H 'Content-Type: application/Json' \`
`-H 'Accept: application/Json' \`
`-H 'Authorization: Basic YWRtaW46cGFzc3dvcmQ=' \`
`-d '{`
`"nat_policies": [`
`{`
`"ipv4": {`
`"name": "Inbound NAT 3389",`
`"enable": true,`
`"comment": "",`
`"inbound": "X1",`
`"outbound": "any",`
`"source": {`
`"any": true`
`},`
`"translated_source": {`
`"original": true`
`},`
`"destination": {`
`"name": "Term Server Public"`
`},`
`"translated_destination": {`
`"name": "Term Server Private"`
`},`
`"service": {`
`"name": "TermServer"`
`},`
`"translated_service": {`
`"original": true`
`}`
`}`
`}`
`]`
`}'`

Step 4: Adding WAN>LAN allow rule

Access Rule WAN>LAN

Step 5: Committing all the above changes made with APIs:

This step is important to save your changes. Usually, this would be the last step. Step 5: is a demonstration to understand adding a new address object to an existing group.

In Postman:

Save Pending config

cURL code:

curl -k -X POST "https://192.168.188.200/api/sonicos/config/pending" -H "accept: application/Json"

CAUTION: If you miss performing the action and log out, you will lose all the configuration changes made in the current session.

Step 6: Log out the SonicWall with API:

It is recommended to log out from the SonicWall via API once the desired configuration is committed.

In Postman:

Log Out

cURL code

curl -k -i -u "admin:password" -X DELETE https://192.168.168.168:443/api/sonicos/auth

“admin:password” – needs to be replaced with the actual admin username and password for your SonicWall.

Not Finding Your Answers?

ASK THE COMMUNITY

Was This Article Helpful?

YES NO

Port Forwarding with SonicOS API in GEN7 - using Postman and cURL

Description

Resolution

Step 1: Login using SonicOS API

Step 2: Source and destination network

Step 3: Creating NAT policy

Step 4: Adding WAN>LAN allow rule

Step 5: Committing all the above changes made with APIs:

Step 6: Log out the SonicWall with API:

Related Articles

Categories

Not Finding Your Answers?

Was This Article Helpful?

Article Helpful Form

Article Not Helpful Form

Follow Us

Subscribe to newsletter

Stay In Touch