Thks for the reply.. here is the capture TCP packet ( i hope it correct )
86 1.531811000 192.168.77.1 192.168.77.50 TCP 60 [TCP ZeroWindow] 37535 > esri-sde [ACK] Seq=1 Ack=1 Win=0 Len=0 87 1.531829000 192.168.77.50 192.168.77.1 TCP 66 [TCP ACKed unseen segment] esri-sde > 37535 [ACK] Seq=1 Ack=2 Win=64887 Len=0 TSval=14742645 TSecr=349169802 259 11.533777000 192.168.77.1 192.168.77.50 TCP 60 [TCP ZeroWindow] 37535 > esri-sde [ACK] Seq=1 Ack=1 Win=0 Len=0
as you can see, 192.168.77.50 is the ip of application server, and 192.168.77.1 is the ip of Haproxy server.. so if the "HAProxy manages buffers and just forward them in both ways (client to server and vice-versa)" ..
it should be passing the tcp ack to the client side/ip ( CMIIW ), which is public ip..
On 4/24/13 12:29 PM, Baptiste wrote:
Hi, Could you take a capture of this check from the server? In TCP mode, HAProxy manages buffers and just forward them in both ways (client to server and vice-versa). Baptiste On Wed, Apr 24, 2013 at 4:59 AM, ZeN <[email protected]> wrote:Hello please bear with because i'm new with haproxy. recently i tried to loadbalance tcp base applications which bind/listen into specific ports. the behavior of the applications ( server side ) is : check time out to the connected client ( 20 seconds), than close/terminated the staled clients connections. but with haproxy, i still cannot manage this behavior to work, because the server send the time out checking to the haproxy server, not directly to the clients. may be some of you who has more expertize with haproxy could point me what is wrong with my setup. i'm running HA-Proxy version 1.4.23 2013/04/03 from FreeBSD ports under FreeBSD 9.1-RELEASE-p2 here is my simple haproxy conf: global log 127.0.0.1 local0 debug maxconn 4096 # ulimit-n 1024 uid 1 gid 1 daemon pidfile /var/run/haproxy.pid listen stats :8081 balance mode http stats enable stats auth blah:blahpass stats refresh 5s listen TEST :5150 ##bind to all interfaces## mode tcp option tcpka option clitcpka option srvtcpka option tcp-smart-accept option tcplog timeout client 320s timeout connect 30s timeout server 30s timeout check 30s option abortonclose option redispatch retries 3 log global balance roundrobin server piglet 192.168.5.18:5150 maxconn 2000 server tigger 192.168.5.30:5150 maxconn 2000 any help will be much appreciated TIA ZeN
