Hi again, I've just read that you've already configured the default gw. There is any router between the clients and the ZLB?
BR On Wed, May 29, 2013 at 12:16 PM, Laura Garcia <[email protected]> wrote: > Hi Jose Manuel, maybe you're missing to configure the load balancer ip as > the default gw for your backends. This is mandatory to make dnat works. > > Regards > El 29/05/2013 12:12, "Jose Manuel Blanco" < > [email protected]> escribió: > >> Hi. >> >> I'm trying ZENLB (latest public version: 3.02) as a choice to substitute >> our ancients Alteon balancers but I have a problem: >> >> We want to balance a web application BUT WE NEED that the backend servers >> receive the client connections WITH THE IP OF THE ORIGINAL CLIENT. >> >> First I've created a farm with a HTTP profile and runs BUT the IP of the >> connections is the ZENLB IP, NOT the client IP...so it's useless for us. >> >> So I've tried to create a farm with the L4TNAT profile BUT doesn't run OK: >> >> - the IP the backend servers receive is the client IP...OK >> - the backend servers sends their response (TCP establishment packets) >> trough ZENLB...OK >> - but the client receives NO RESPONSE from ZENLB...FAIL >> >> I've tried several network/gateways configurations but none of them seems >> to run OK, and the online documentation doesn't cover the L4TNAT so...I >> don't know if I've done something wrong, I doesn't have understood the >> L4TNAT operation or ZENLB has some bug/problem with the L4TNAT profile. >> >> The network configuration: >> >> *ZENLB configuration:* >> >> *Netwo**r**k:* >> >> eth0: 10.0.4.XX -> for administration/cluster >> * Gateway: none >> eth1: 192.168.31.100 -> for communicate with backend servers in a private >> network >> * Gateway: none >> eth2: PUBLIC_ADDRESS -> for client access >> * Gateway: "oficial" gateway for the PUBLIC network >> Default gateway: 10.0.4.1 -> "oficial" gateway for the 10.0.4 net >> >> *Farm:* >> >> Profile: L4TNAT >> NAT type: DNAT >> >> *B**ackend server configuration:* >> >> eth0: 192.168.31.YY -> Private IP for service >> Default gateway: 192.168.31.100 -> the ZENLB IP in the 192.168.31.0 >> private network >> >> >> Tcpdump shows: >> - CLIENT_IP initial packet -> ZENLB -> Backend Server >> * the path/NAT of the initial packet seems to be OK >> - Backend Server ansver -> ZENLB -> ???? >> * the "right" packet is received by ZENLB but NOT by he client >> * Perhaps response packet is received by ZENLB but...it comes out >> from ZENLB? >> >> Any idea? >> Thanks >> >> -- >> ------------------------------ >> >> * Jose Manuel Blanco Cortiñas >> Analista de Sistemas - Servicio de las Tecnologias de la Informacion y >> Comunicaciones (STIC) >> Universidad de Valladolid >> Edificio Alfonso VIII, C/Real de Burgos s/n. 47011, Valladolid - ESPAÑA >> Telefono: 983 18-6410, Fax: 983 423271 >> E-mail: [email protected] >> * >> * >> ------------------------------ >> * >> >> >> ------------------------------------------------------------------------------ >> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET >> Get 100% visibility into your production application - at no cost. >> Code-level diagnostics for performance bottlenecks with <2% overhead >> Download for free and get started troubleshooting in minutes. >> http://p.sf.net/sfu/appdyn_d2d_ap1 >> _______________________________________________ >> Zenloadbalancer-support mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support >> >>
<<escudo-uva.gif>>
------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________ Zenloadbalancer-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
