Hi Florent, the only weird thing in your configuration is that you've set
up 2 network interfaces with the same subnet.
10.108.0.0/16 dev eth1 proto kernel scope link src 10.108.13.111
10.108.0.0/16 dev eth2 proto kernel scope link src 10.108.13.121
These destination routes are duplicated. Could you remove the eth2 route
and see what happens?
Regards.
On Tue, Dec 23, 2014 at 7:37 PM, Florent B <flor...@coppint.com> wrote:
> To the client IP (client = the who made the request). Public IP on
> 212.xx.xx.xx
>
>
> On 12/23/2014 07:35 PM, Laura Garcia wrote:
>
> Hi, you're trying to go from 10.108.240.164 to which destination?
>
> regards.
>
>
>
> On Tue, Dec 23, 2014 at 7:23 PM, Florent B <flor...@coppint.com> wrote:
>
>> Hi Laura,
>>
>> Here are the outputs of commands :
>>
>> root@lb04-1:~# ifconfig
>> eth0 Link encap:Ethernet HWaddr 46:bd:c5:53:54:73
>> inet addr:10.111.13.41 Bcast:10.111.255.255 Mask:255.255.0.0
>> inet6 addr: fe80::44bd:c5ff:fe53:5473/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:13644 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:10634 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:1023305 (999.3 KiB) TX bytes:894445 (873.4 KiB)
>>
>> eth1 Link encap:Ethernet HWaddr 32:02:c0:a9:5c:da
>> inet addr:10.108.13.111 Bcast:10.108.255.255 Mask:255.255.0.0
>> inet6 addr: fe80::3002:c0ff:fea9:5cda/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:716 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:371 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:46409 (45.3 KiB) TX bytes:21838 (21.3 KiB)
>>
>> eth2 Link encap:Ethernet HWaddr e6:11:03:68:a5:b1
>> inet addr:10.108.13.121 Bcast:10.108.255.255 Mask:255.255.0.0
>> inet6 addr: fe80::e411:3ff:fe68:a5b1/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:8400 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:8471 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:537180 (524.5 KiB) TX bytes:505048 (493.2 KiB)
>>
>> eth0:vip Link encap:Ethernet HWaddr 46:bd:c5:53:54:73
>> inet addr:10.111.13.40 Bcast:0.0.0.0 Mask:255.255.0.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>
>> eth1:sina1-1 Link encap:Ethernet HWaddr 32:02:c0:a9:5c:da
>> inet addr:10.108.240.164 Bcast:10.108.255.255 Mask:255.255.0.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>
>> eth1:sina1-2 Link encap:Ethernet HWaddr 32:02:c0:a9:5c:da
>> inet addr:10.108.240.165 Bcast:10.108.255.255 Mask:255.255.0.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>
>> eth1:sina1-3 Link encap:Ethernet HWaddr 32:02:c0:a9:5c:da
>> inet addr:10.108.240.166 Bcast:10.108.255.255 Mask:255.255.0.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>
>> eth1:sina1-4 Link encap:Ethernet HWaddr 32:02:c0:a9:5c:da
>> inet addr:10.108.240.167 Bcast:10.108.255.255 Mask:255.255.0.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>
>> eth1:sina1-5 Link encap:Ethernet HWaddr 32:02:c0:a9:5c:da
>> inet addr:10.108.240.168 Bcast:10.108.255.255 Mask:255.255.0.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>
>> eth2:qhoster1-1 Link encap:Ethernet HWaddr e6:11:03:68:a5:b1
>> inet addr:10.108.24.114 Bcast:10.108.255.255 Mask:255.255.0.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>
>> eth2:qhoster1-2 Link encap:Ethernet HWaddr e6:11:03:68:a5:b1
>> inet addr:10.108.24.115 Bcast:10.108.255.255 Mask:255.255.0.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>
>> eth2:qhoster1-3 Link encap:Ethernet HWaddr e6:11:03:68:a5:b1
>> inet addr:10.108.24.116 Bcast:10.108.255.255 Mask:255.255.0.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>
>> eth2:qhoster1-4 Link encap:Ethernet HWaddr e6:11:03:68:a5:b1
>> inet addr:10.108.44.23 Bcast:10.108.255.255 Mask:255.255.0.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>
>> lo Link encap:Local Loopback
>> inet addr:127.0.0.1 Mask:255.0.0.0
>> inet6 addr: ::1/128 Scope:Host
>> UP LOOPBACK RUNNING MTU:16436 Metric:1
>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:0
>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>>
>> root@lb04-1:~# ip rule list
>> 0: from all lookup local
>> 32753: from 10.108.240.164 lookup table_eth1
>> 32754: from 10.108.240.167 lookup table_eth1
>> 32755: from 10.108.240.166 lookup table_eth1
>> 32756: from 10.108.44.23 lookup table_eth2
>> 32757: from 10.108.24.114 lookup table_eth2
>> 32758: from 10.108.240.165 lookup table_eth1
>> 32759: from 10.108.24.116 lookup table_eth2
>> 32760: from 10.108.24.115 lookup table_eth2
>> 32761: from 10.108.240.168 lookup table_eth1
>> 32762: from 10.111.13.40 lookup table_eth0
>> 32763: from 10.108.13.121 lookup table_eth2
>> 32764: from 10.108.13.111 lookup table_eth1
>> 32765: from 10.111.13.41 lookup table_eth0
>> 32766: from all lookup main
>> 32767: from all lookup default
>>
>> root@lb04-1:~# ip route list
>> 10.108.0.0/16 dev eth1 proto kernel scope link src 10.108.13.111
>> 10.108.0.0/16 dev eth2 proto kernel scope link src 10.108.13.121
>> 10.111.0.0/16 dev eth0 proto kernel scope link src 10.111.13.41
>> default via 10.111.0.254 dev eth0
>>
>> root@lb04-1:~# ip route list table table_eth1
>> 10.108.0.0/16 dev eth1 scope link src 10.108.13.111
>> default via 10.108.0.111 dev eth1
>>
>> root@lb04-1:~# ip route list table table_eth0
>> 10.111.0.0/16 dev eth0 scope link src 10.111.13.41
>>
>>
>> The config seems fine, but I can see with tcpdump that packets
>> originating from 10.108.240.164 are sent to the mac address of 10.111.0.254
>> (global gateway), and not to 10.108.0.111 as expected :(
>>
>>
>>
>> On 12/23/2014 07:13 PM, Laura Garcia wrote:
>>
>> Hi, could you send some real configuration?
>>
>> Exec the following commands please and paste the output:
>>
>> ifconfig
>> ip rule list
>> ip route list
>> ip route list table table_eth1
>> ip route list table table_eth0
>>
>> regards
>>
>>
>>
>>
>> On Tue, Dec 23, 2014 at 5:16 PM, Florent B <flor...@coppint.com> wrote:
>>
>>> It seems to be the "ip rule from" that does not work for me. Can someone
>>> confirm this ?
>>>
>>> I can provide some packets capture that show packets going to global
>>> gateway and not to interface gateway..
>>>
>>> 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 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
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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
> 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
