diff options
author | Florian Westphal <fw@strlen.de> | 2019-06-17 11:55:42 +0200 |
---|---|---|
committer | Florian Westphal <fw@strlen.de> | 2019-06-17 17:22:15 +0200 |
commit | ca12e455e98fb4247e0aa4c2d361195038debe65 (patch) | |
tree | 5fba8701c290b4edd3123f8b31349e3c496f0c2b /tests/py/ip6/icmpv6.t.payload.ip6 | |
parent | dc5372b6e8448549a770f9d09477fd2a9207d69c (diff) |
datatype: fix print of raw numerical symbol values
The two rules:
arp operation 1-2 accept
arp operation 256-512 accept
are both shown as 256-512:
chain in_public {
arp operation 256-512 accept
arp operation 256-512 accept
meta mark "1"
tcp flags 2,4
}
This is because range expression enforces numeric output,
yet nft_print doesn't respect byte order.
Behave as if we had no symbol in the first place and call
the base type print function instead.
This means we now respect format specifier as well:
chain in_public {
arp operation 1-2 accept
arp operation 256-512 accept
meta mark 0x00000001
tcp flags 0x2,0x4
}
Without fix, added test case will fail:
'add rule arp test-arp input arp operation 1-2': 'arp operation 1-2' mismatches 'arp operation 256-512'
v2: in case of -n, also elide quotation marks, just as if we would not
have found a symbolic name.
Signed-off-by: Florian Westphal <fw@strlen.de>
Acked-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'tests/py/ip6/icmpv6.t.payload.ip6')
0 files changed, 0 insertions, 0 deletions