|
Hi Joe,
> I remember finding that the route from the real-servers to the client(s)
> in VS-NAT must have the director as the default gw and not just a route
> for VS-NAT to work.
As Julian mentioned, the DGW is handled first because more bits match
on the route_lookup.
> Say I have a 2 NIC VS-NAT director, with the real-servers on 1 NIC and the
> client on the other NIC, and both NICS on different networks. If on the
> real-server I put the director as the default gw, the LVS works. If
> instead I put a network (or host) route to the client's network through
> the director (but no default gw entry), the LVS doesn't work.
> Why is this?
Should not be. But could you post your example, please?
> (Don't spend a lot of time on this if it doesn't seem right, I'll
> try it out again next week).
Send me your results and test environments.
Best regards,
Roberto Nibali, ratz
--
mailto: `echo NrOatSz@xxxxxxxxx | sed 's/[NOSPAM]//g'`
|
