Ilia Ross 2fe57dd456 Fix to validate nftables set usage in rules ...

* Note: Prevent incompatible nftables sets from being used in rule fields. The rule editor now only offers address sets for address matches and port/service sets for port matches, while save and apply paths validate existing set references before writing or loading rules. This avoids nft datatype mismatch errors such as using inet_proto sets with tcp dport.

2026-05-03 00:44:54 +02:00

..

action.html

…

chain_hook.html

…

chain_name.html

…

chain_policy.html

…

chain_priority.html

…

chain_type.html

…

comment.html

…

counter_1.html

…

counter.html

…

ct_state.html

…

daddr.html

…

dport.html

…

edit_direct_1.html

…

edit_direct.html

…

goto.html

…

icmp_type.html

…

iif.html

…

intro.html

…

jump.html

…

limit_burst.html

…

limit_rate.html

…

log_1.html

…

log_level.html

…

log_prefix.html

…

log.html

…

oif.html

…

proto.html

…

raw_rule.html

…

saddr.html

…

set_elements.html

…

set_flags.html

…

set_name.html

…

set_type.html

…

sport.html

…

tcp_flags_mask.html

…

tcp_flags.html

…