summaryrefslogtreecommitdiffstats
path: root/extensions/libipt_realm.t
diff options
context:
space:
mode:
authorFlorian Westphal <fw@strlen.de>2018-11-02 14:36:54 +0100
committerFlorian Westphal <fw@strlen.de>2018-11-03 20:35:22 +0100
commitfd95f1f0223f8e2ecf91aa8d1a4ba84576861082 (patch)
tree3f3d5eccdd114000afa0a81de80dd2a492286cda /extensions/libipt_realm.t
parentfb747f8ae01bdcbb197f5f9fc1085416ad636d38 (diff)
ebtables: fix -j CONTINUE handling for add/delete
-j CONTINUE can be added, but it can't be removed: extensions/libebt_standard.t: ERROR: line 5 (cannot find: ebtables -I INPUT -d de:ad:be:ef:00:00 -j CONTINUE) This problem stems from silly ambiguity in ebtables-nft vs. iptables. In iptables, you can do iptables -A INPUT (no -j) in ebtables, you can do either ebtables -A INPUT or ebtables -A INPUT -j CONTINUE both are *supposed* to be the same (and they do the same even in ebtables-nft on netlink side). However, the temprary binary representation within ebtables-nft is not the same: when parsing -j CONTINUE, we add a standard target, then omit it later in _add_target(). When translating netlink representation to ebt binary one, we do not add a standard target and instead just print '-j CONTINUE' when listing rules. So when doing -I INPUT -j CONTINUE -D INPUT -j CONTINUE the -D operation fails because it has a standard target in the binary representation, whereas the rule we obtained from translating nftables netlink back to ebtables' binary represenation doesn't. Fix it by ignoring 'CONTINUE' on parser side. Signed-off-by: Florian Westphal <fw@strlen.de>
Diffstat (limited to 'extensions/libipt_realm.t')
0 files changed, 0 insertions, 0 deletions