diff options
| author | Florian Westphal <fw@strlen.de> | 2018-05-24 17:57:34 +0200 |
|---|---|---|
| committer | Florian Westphal <fw@strlen.de> | 2018-05-25 23:37:55 +0200 |
| commit | 49709e2ac6cf778e8732e9b0ca124da556ed6a91 (patch) | |
| tree | 2791569381bcf135746147894ff42b1b06ebe385 /iptables/xtables.c | |
| parent | 03e1377b38af45292a3a55828ee8e7c7e41ae64c (diff) | |
xtables-compat: remove nft_is_ruleset_compatible
Use nft_is_table_compatible instead as only helper to a 'skip' decision.
Custom tables, tables that have extra base chains that iptables
syntax doesn't allow or rules that have special constructs line nftables
set lookups or verdict maps are not listed, but a message is provided
to show that such table exists.
Signed-off-by: Florian Westphal <fw@strlen.de>
Diffstat (limited to 'iptables/xtables.c')
| -rw-r--r-- | iptables/xtables.c | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/iptables/xtables.c b/iptables/xtables.c index 5410952a..7476c974 100644 --- a/iptables/xtables.c +++ b/iptables/xtables.c @@ -1225,12 +1225,6 @@ int do_commandx(struct nft_handle *h, int argc, char *argv[], char **table, case CMD_LIST: case CMD_LIST|CMD_ZERO: case CMD_LIST|CMD_ZERO_NUM: - ret = nft_is_ruleset_compatible(h); - if (ret) { - printf("ERROR: You're using nft features that cannot be mapped to iptables, please keep using nft.\n"); - exit(EXIT_FAILURE); - } - ret = list_entries(h, p.chain, p.table, p.rulenum, cs.options & OPT_VERBOSE, cs.options & OPT_NUMERIC, |