|
Hello,
On Thu, 15 Jul 2004, Mark Weaver wrote:
> My idea was to simply add the extra ip addresses in as separate load
> balanced services, and then use something like:
>
> ip rule from backup_ip table backup_route
> ip route add default backup_gw table backup_route
>
> This works fine for non-LVS services (and I can therefore provide a
> straightforward NAT service without redundancy), but with LVS services
> the traffic is pushed straight down the default route. I'm guessing
> that this is because the packets are routed before the NAT happens. A
> few questions:
>
> - Am I right therefore in thinking that this would work with LVS/DR?
> - Can anyone think of another method of using LVS-NAT to get these
> packets to take the right route?
You can check the NFCT support:
http://www.ssi.bg/~ja/nfct/
there is a snat_reroute sysctl var.
> Digging around a little I thought that the old antefacto patches might
> sort this out, and in fact, they do. However, they are unfortunately
> unstable (in testing, they seemed fine, but with real traffic the box
> just drops off the network, presumably with a kernel oops that I can't
> see as it is in some hosting centre miles away). Reading those a bit
> further, there is a particular section that would seem to be just what I
> want:
Regards
--
Julian Anastasov <ja@xxxxxx>
|
