Re: AW: transparent mode -> chksum incorrect

2018-03-22 Thread Willy Tarreau
On Thu, Mar 22, 2018 at 01:15:26PM +, matei marius wrote: > haproxy -vv > HA-Proxy version 1.8.4-1deb90d 2018/02/08 > Copyright 2000-2018 Willy Tarreau > > Build options : >   TARGET  = linux26 >   CPU = generic >   CC  = gcc >   CFLAGS  = -m64 -march=x86-64 -O2 -g -fno-strict-aliasin

Re: AW: transparent mode -> chksum incorrect

2018-03-22 Thread matei marius
haproxy -vv HA-Proxy version 1.8.4-1deb90d 2018/02/08 Copyright 2000-2018 Willy Tarreau Build options :   TARGET  = linux26   CPU = generic   CC  = gcc   CFLAGS  = -m64 -march=x86-64 -O2 -g -fno-strict-aliasing -Wdeclaration-after-statement -fwrapv -Wno-unused-label   OPTIONS = USE_P

AW: transparent mode -> chksum incorrect

2018-03-22 Thread Mathias Weiersmüller
Hi Marius, your NIC is probably doing the TCP checksum calculation (called « TCP offloading»). The TCP/IP stacks therefore sends all outbound TCP packets with the same dummy checksum (in your case: 0x2a21) to the NIC driver. This saves some CPU cycles. Check your TCP offloading settings using: