LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: i cannot solve this, is it solvable??

To: Michele Nicosia <michele.network@xxxxxxxxxxxxxxxxxx>
Subject: Re: i cannot solve this, is it solvable??
Cc: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
From: Julian Anastasov <uli@xxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 16 Jun 2000 13:26:04 +0300 (EEST)
        Hello,

On Fri, 16 Jun 2000, Michele Nicosia wrote:

> Hi,
>     this is what i have an the load balancer:
> 
> -A -t loadbalancer:www -s wlc
> -a -t loadbalcner:www -r webintranet1:www -m -w 6
> -a -t loadbalancer:www -r webintranet2:www -m -w 2
> 
> Well , from outside it works, but like i saied, on the local intranet not.
> The routing table is ok, i can ping the real server.

        This is the problem. In normal MASQ situations nobody
can ping the internal host from outside. This breaks the
firewall.

> So if i well understand i have to add:
> -a -t loadbalancer:www -r webintranet1:www -g
> -a -t loadbalancer:www -r webintranet2:www -g
> 
> Is this correct???

        You can't use director as def gw for VS/DR.

        Try the trick with the additional logical private
network (192.168.2). Not tested. One network to talk directly
and one network to masquerade. You don't change the topology,
your LVS/NAT director is still a def gw for the real servers.
If you start to use 192.168.2 as direct (without NAT) route,
you setup rules will not be changed. Later you should ping
192.168.2.real_server but not 192.168.1.real_server. Each
RS will listen on 192.168.2 and 192.168.1 networks. Is that
working?


Regards

--
Julian Anastasov <uli@xxxxxxxxxxxxxxxxxxxxxx>



<Prev in Thread] Current Thread [Next in Thread>