Re: transparent mode -> chksum incorrect

Hello, On 22 March 2018 at 11:49, matei marius wrote: > When I try to access the service from the same IP class with haproxy I see > the packets having incorrect checksum. This is most likely due to offloading techniques such as TX checksumming, where tcpdump will not see

Re: transparent mode

Hi Robert, You can develop a netfilter module to change src ipaddr from haproxy's self ip to client ipaddr for backend servers. But this solution maybe decrease the whole performance of haproxy box for about 20%. this is a reference :

Re: transparent mode

Hi James, On Fri, Jun 10, 2011 at 04:20:15PM +0800, ?? wrote: Hi Robert, You can develop a netfilter module to change src ipaddr from haproxy's self ip to client ipaddr for backend servers. But this solution maybe decrease the whole performance of haproxy box for about 20%. There's

RE: transparent mode

If you need to pass the client IP you simply need to enable x-forwarded-for (option forwardfor). If you truly need transparent load balancing then depending on what Linux OS and version you are running you MIGHT very well need to recompile the kernel and iptables. For the one environment that

Re: transparent mode

Hi Robert, On Thu, Jun 09, 2011 at 04:23:46PM -0400, Robert Lassiter wrote: I am sure it's been asked before, I can find some vague references on how to accomplish this but nothing that does not include recompiling the kernel. I think these posts are out of date. So, sorry in advance but