Hi WofgangDannert,
we are looking for a description, should be in the description, but seems there is a bug.
Editing the file is allowed, but as it is not the way we suggest there is no description.
In the meantime you can look into reverse engineering by pressing F12 in your browser while creating your rules in the WebUI.
Some first command look like this:
GET Tables
GET https://{{Host}}/firewall/api/v2/families/ip/tables
GET Chains
GET https://{{Host}}/firewall/api/v2/families/ip/tables
GET Rule
https://{{Host}}/firewall/api/v2/families/ip/tables/{{firewalltableid}}/chains/{{firewallchainid}}/rules
POST Create Chain
https://{{Host}}/firewall/api/v2/families/ip/tables/{{firewalltableid}}/chains
Body
{
"hook": "prerouting",
"name": "MyNetmap",
"tableId": "awvLHaxkYan9LqsYiYcuvk",
"id": "id",
"family": "ip",
"priority": 200,
"type": "nat",
"policy": "accept"
}
POST Create Rule
https://{{Host}}/firewall/api/v2/families/ip/tables/{{firewalltableid}}/chains/{{firewallchainid}}/rules
Body
{
"chainId": "{{firewallchainid}}",
"name": "MapIPaddress{{ipoctet}}",
"tableId": "{{firewalltableid}}",
"action": "",
"comment": "MapIPaddressRangebyDNAT",
"handle": 0,
"id": "",
"family": "ip",
"expressions": [
{
"left": {
"field": "daddr",
"protocol": "ip",
"type": "payload"
},
"operation": "==",
"right": "192.168.5.{{ipoctet}}",
"type": "match"
},
{
"addr": "192.168.2.{{ipoctet}}",
"type": "dnat"
}
]
}
... View more
