Displaying 1 result from an estimated 1 matches for "xt_u32".
Did you mean:
__u32
2019 Apr 08
0
[Bug 1334] New: invalid example in u32 extension documentation
...y TCP payloads is invalid
-m u32 --u32 '6&0xFF=6&&4&0x3FFF=0&&0>>22&0x3C at 12>>26&0x3C at -3&0xFF=0:255'
never matches, appears to have been a _very_ long time since this was valid (if
it ever was), probably due to the kernel devs rewriting xt_u32.c for slightly
better performance
best that can be managed is
-m u32 --u32 '6&0xFF=6&&4&0x3FFF=0&&0>>22&0x3C at 12>>26&0x3C at 0&0xFF=0:255'
where the test matches packets with >=4 TCP data bytes rather than >0 bytes
negative offset...