On Mon, Aug 04, 2014 at 06:00:07PM +0200, Alvaro Neira Ayuso wrote: > In the evaluation and delinealize steps, we update the protocol > context. The expression must be in host endian byteorder when we update the > context. However, this is not the case because we see them in network > byteorder. > > Fix this by converting to the appropriate byteorder before updating > the protocol context otherwise this doesn't work. > > nft add rule bridge filter input ether type ip > > We have a expression like this: > > [ payload load 2b @ link header + 12 => reg 1 ] > [ cmp eq reg 1 0x00000008 ] > > The byteorder of this expressions is big endian and it's in > host endian, for that when we try to update the context, we > don't find the protocol with this number. This is a output, > example: > > update network layer protocol context: > link layer : ether > network layer : none <- > transport layer : none So after looking into this, the problem seems really simple, the ETH_P_* values are in host byteorder and we incorrectly mark them as being in network byteorder, so they are not converted automatically. Could you please test whether this fixes the problem you're seeing? diff --git a/src/proto.c b/src/proto.c index e5f49cb..050dd90 100644 --- a/src/proto.c +++ b/src/proto.c @@ -772,7 +779,7 @@ const struct datatype ethertype_type = { .type = TYPE_ETHERTYPE, .name = "ether_type", .desc = "Ethernet protocol", - .byteorder = BYTEORDER_BIG_ENDIAN, + .byteorder = BYTEORDER_HOST_ENDIAN, .size = 2 * BITS_PER_BYTE, .basetype = &integer_type, .basefmt = "0x%.4Zx", -- 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