Hi Florent, you're already talking with a ZLB team member and L4 farm
developer.
The L4 farms don't bind any socket and they won't, as this is the reason of
the high performance of such farms. If you think that binding a socket will
solve your problem, you could use a L7 farm...
By the way, I do not totally agree with you. The output packet has already
a source IP address in the IP packet header, which is the address
"10.108.240.164", as you already said:
"I can see with tcpdump that packets originating from 10.108.240.164 are
sent to the mac address of 10.111.0.254 "
So, in that case you would never see the packets...
I'll investigate further this case in the lab, but I'm almost sure that
it's related about routing virtual IPs.
Kind Regards and happy new year! :)
On Sat, Dec 27, 2014 at 10:44 AM, Florent B <flor...@coppint.com> wrote:
> I had an answer from Miguel Bernabé on la...@vger.kernel.org mailing
> list :
>
> If your server does not use the bind call to bind the socket to the IP
> address 10.108.240.164 then the rule above will not match the packet. This
> is, if your server does not bind the socket to a given IP address, the source
> IP address of the packet for the IP header will be INADDR_ANY and the kernel
> will fill it at the time the route is choosen using the route table regarding
> the destination IP address so this source IP address will be the address of
> the device that match the route.
>
>
> So it seems to be the case here, ZLB never bind a socket in l4xnat mode,
> so the gateway per interface can't work...
>
> I can't believe to be the only one having this problem :)
>
> Of course, it should work in TCP/UDP mode, and it works I think.
>
> ZLB team : any idea to improve this ? Because l4xnat is very interesting,
> for example there is no farmguardian in UDP mode :(
>
> On 12/22/2014 11:05 PM, Florent B wrote:
>
> Hi all,
>
> In a complex network with a lot of DNAT/SNAT, I have a ZLB configured
> with a NAT farm.
>
> eth0 interface is the one to join my backends
> eth1 interface is the one with a LB IP.
>
> ZLB is configured with a default gateway on eth0.
>
> But eth1 as also a gateway, which is valid for the LB IP.
>
> Why ZLB does not send replies of NAT (from LB IP) to the gateway of eth1
> ?? It always send replies to the default gateway of the system.
> Of course it works if I put gateway of eth1 as the default one for the
> system, but the problem is that I also have and eth2, eth3... which
> needs to work too with others gateways. :D
>
> I don't understand this behaviour.
>
> Is it expected ?
>
> All is running fine except the choice of the gateway depending of the
> source IP.
>
> Can someone help me with that please ?
>
> Thank you a lot :)
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Zenloadbalancer-support mailing
> listZenloadbalancer-support@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Zenloadbalancer-support mailing list
> Zenloadbalancer-support@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Zenloadbalancer-support mailing list
Zenloadbalancer-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
