From cc4e645b15da8e887f465955b9663ebc4c768cc5 Mon Sep 17 00:00:00 2001 From: Liping Zhang Date: Sun, 29 May 2016 18:08:08 +0800 Subject: meta: fix endianness in priority For example, after we add rule to set priority 1:2, it will be displayed in network byte order as 0200:0100, this is wrong: # nft add rule filter test meta priority set 1:2 # nft list chain filter test table ip filter { chain test { meta priority set 0200:0100 } } Signed-off-by: Liping Zhang Signed-off-by: Pablo Neira Ayuso --- src/meta.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/meta.c') diff --git a/src/meta.c b/src/meta.c index b8db0f89..74d2b4cc 100644 --- a/src/meta.c +++ b/src/meta.c @@ -128,7 +128,7 @@ static const struct datatype tchandle_type = { .type = TYPE_TC_HANDLE, .name = "tc_handle", .desc = "TC handle", - .byteorder = BYTEORDER_BIG_ENDIAN, + .byteorder = BYTEORDER_HOST_ENDIAN, .size = 4 * BITS_PER_BYTE, .basetype = &integer_type, .print = tchandle_type_print, -- cgit v1.2.3