|
Hello,
On Wed, 19 Jan 2000 nissim@xxxxxxxxxxxxx wrote:
> Hi, I set up LVS as follows:
>
> Director:
> eth0: 166.84.192.35 (this is the VIP, and an Internet address)
> eth1: 192.168.1.1
>
> ipchains -A forward -s 192.168.1.0/24 -j MASQ
> ipvsadm -A -t 166.84.192.35:80 -s
> ipvsadm -a -t 166.84.192.35:80 -r 192.168.1.80 -g wlc
>
> This machine has is the default gateway for both of the other machines.
>
> Real Server:
> eth0: 192.168.1.80
> dummy0: 166.84.192.35 (with arp hidden using proc fs)
>
> Client:
> eth0: 192.168.1.10
>
> Now if I do
> telnet 166.84.192.35 80
> from my shell account on a machine on the internet it connects
> successfully to the Web Server on 192.168.1.80,
>
> But if I do the same from the client listed above, it waits and never
> connects.
>
> Is there a solution to this?
>
Yes. I assume this is a test configuration. So, for the test you
must put the client in the external logical network. By this way the
client, the director and the real server(s) are on same physical network
but the client can't be on the masqueraded logical network. So, change the
client from 192.168.1.80 to 166.84.192.80 (or something else). Don't add
interface 192.168.1.0/24 in the client. The path to 192.168.1.0/24 must be
through DIP (I don't see such IP for the Director). Why in your setup
DIP==VIP ? If you add DIP (166.84.192.33 for example) in the director you
can later add path for 192.168.1.0/24 through 166.84.192.33. There is no
need to use masquerading with 2 NICs. Just remove the client from the
internal logical network used by the LVS cluster. Is it working :)
Regards,
Julian Anastasov
----------------------------------------------------------------------
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
To unsubscribe, e-mail: lvs-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: lvs-users-help@xxxxxxxxxxxxxxxxxxxxxx
|
