sbezverk <sbezverk@xxxxxxxxx> wrote:
> Changed kernel to 5.4.10, and switch to use "inc" instead of "random". Now first curl works and second fails. Whenever second chain is selected to be used, curl connection gets stuck.
>
> chain k8s-nfproxy-svc-M53CN2XYVUHRQ7UB {
> numgen inc mod 2 vmap { 0 : goto k8s-nfproxy-sep-TMVEFT7EX55F4T62, 1 : goto k8s-nfproxy-sep-GTJ7BFLUOQRCGMD5 }
> counter packets 1 bytes 60 comment ""
> }
>
> chain k8s-nfproxy-sep-TMVEFT7EX55F4T62 {
> counter packets 1 bytes 60 comment ""
> ip saddr 57.112.0.41 meta mark set 0x00004000 comment ""
> dnat to 57.112.0.41:8080 fully-random
> }
>
> chain k8s-nfproxy-sep-GTJ7BFLUOQRCGMD5 {
> counter packets 0 bytes 0 comment ""
> ip saddr 57.112.0.52 meta mark set 0x00004000 comment ""
> dnat to 57.112.0.52:8989 fully-random
> }
>
> Any debug I could enable to see where the packet goes?
The counter after numgen should not increment, but it does.
Either numgen does something wrong, or hash alg is broken and doesn't
find a result for "1".
There was such a bug but it was fixed in 5.1...
please show:
uname -a
nft --version
