|
Hello Joseph,
Joseph Mack wrote:
>
> On Thu, 2 Jul 2009, Olaf Krische wrote:
>> If not using the public IPs, i could not route to the client.
> on the realserver the service is listening on the VIP (as it
> must, because that's where the client sent the packet). The
> realserver replies from the VIP. The packet goes back to the
> client. The RIP is needed so that the director can find its
> MAC address and send a layer 2 packet from MAC_DIP->MAC_RIP.
>
And my problem is "how the packet goes back to the client".
I guess, i have become totally offtopic. Since it is a routing problem,
which has come up with using LVS-DR:
- CIP is "1.2.3.4"
- RIP on realserver is "192.168.1.2", default gw is "192.168.1.1"
- realservers answers to client by sending packet "VIP -> CIP" to gateway
- gateway must be enabled to forward "VIP -> CIP" to the next
gateway, which is responsible for "CIP".
Right now this gateway just does NAT. I have no new rule for this above yet.
The rule for the gateway must be something like:
- When traffic on eth0 and ip-src is "VIP", then forward to "internet
gateway" on eth1
I think thats the result of all the lines. :-)
--
View this message in context:
http://www.nabble.com/ipvs-or-apache-mod_proxy-mod_balancer-tp24184926p24323032.html
Sent from the LVS mailing list archive at Nabble.com.
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
