[nft] Byteorder problem still exists in nft

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,
There are still some byteorder prolems in nft.

The first one:
nft> add rule bridge filter input ip saddr 192.168.1.1 counter
nft> list table bridge filter
table bridge filter {
	chain input {
		 type filter hook input priority 0;
		 unknown unknown 0xc0a80101 [invalid type] counter packets 0 bytes 0
	}
}
nft>
I guess this error occurs in payload_gen_dependency() which set the byteorder
host endian but ether type is big endian.

The second one:
nft> add rule ip filter input ip length > 10 counter
BUG: invalid byte order conversion 0 => 2
nft: src/evaluate.c:153: byteorder_conversion_op: Assertion `0' failed.
This is because the datatype of ip length is integer_type whose byteorder is invalid.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Netfitler Users]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux