Firewall filters
Edit configuration.firewall.policies[].filters and PUT the complete router definition after a
current GET.
IP and transport-layer schema
Field |
Description |
|---|---|
|
Server-issued rule identifier |
|
Enabled state; set explicitly |
|
|
|
|
|
|
|
LAN UUID for a LAN rule; omit for WAN |
|
|
|
Source/destination IPv4 address or subnet expression |
|
Source/destination port expression |
|
Corresponding address operand enabled |
|
Corresponding port operand enabled |
|
Empty string |
|
Rule logging |
|
Position within the policy |
False operand flags require empty operands and mean no restriction for that operand. Enabled
operands need a valid expression. Port conditions require TCP or UDP; all cannot carry concrete
port matches.
Ports support single values, ranges and comma-separated combinations such as 80,443,8000-8010.
Addresses accept one IPv4 address, one CIDR network, or any. Address
expressions are at most 64 characters; port expressions at most 255. Do not supply hostnames or
invent a policy-routing next hop.
Use the exact returned LAN name and UUID for a LAN rule. For WAN, use WAN or an assigned address
and omit interface_uuid.
Ethernet-layer filtering
Where the appliance supports Ethernet filtering, use layer: "l2" with MAC/EtherType fields
instead of IP/port fields:
{
"layer": "l2",
"active": true,
"action": "deny",
"direction": "in",
"interface": "LAN 1",
"interface_uuid": "22222222-2222-4222-8222-222222222222",
"src_mac": "02:00:00:00:00:10",
"dst_mac": "any",
"ether_type": "ipv4",
"log": false,
"order": 1
}
Replace the LAN UUID. MAC values are any or lowercase colon-separated addresses. This example
matches one source MAC carrying IPv4 frames; use arp to match ARP frames, or any for all
EtherTypes.
Set log false. Do not include protocol, address/port operands or nexthop in an Ethernet
rule. Unsupported appliance capability is rejected.
Editing, deleting and verification
Retain the rule UUID on edit. Remove the row to delete it and keep orders contiguous. Wait for sync, then test matching traffic, a non-matching control and recovery after removal. Use new connections for stateful tests.