LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: Newbie Problems with NAT RH 6.2, piranha-0.4.14-1, ipvsadm-1.1-2

To: Shaun McCullagh <smccullagh@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Newbie Problems with NAT RH 6.2, piranha-0.4.14-1, ipvsadm-1.1-2
Cc: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
From: Keith Barrett <kbarrett@xxxxxxxxxx>
Date: Mon, 16 Oct 2000 13:50:31 -0400
Shaun McCullagh wrote:
> Pulse starts up fine, and nanny gets the output from uptime on the real
> server. The client browser can ping all the interfaces on both router
> and the real server.
> 
> The problem is the client browser cannot retrieve any data from the
> virtual server.
> 
> Tcpdump shows some data is exchanged, but nothing shows up in the apache
> log on the real server when the client requests a page via the virtual
> server running on the LVS router.
> 
> The client browser can access the real server directly.
> 
>     ________
>    |        |
>    | client | 192.168.31.101/24
>    |________|
>        |
>        |
>        |
>        |
>  vs1 192.168.31.157/24 (eth0:1)
>   192.168.31.148/24 (eth0)
>   __________
>  |          |
>  | lvsmain  | VA Linux 2130, 2.2.14
>  |__________|
>  192.168.100.1(eth1)
>  NAT Router 192.168.100.254 (eth1:1)
>        |
>     (switch)
>        |
>        |
>  s3 = 192.168.100.5 (eth0)
>  ____________
> |            |
> | realserver | VA Linux, 2.2.14.
> |____________| default gw, 192.168.100.254
> 
> ========================== lvs.cf
> ============================================


You are using the 192 address as your public and private network.
192 addresses are not routable. Try changing the address of your client,
and of eth0 and eth0:1 on lvsmain to a normal ip address, and
update your config and ipchains stuff accordingly.

-- 

Keith Barrett
Red Hat Inc. HA Team
kbarrett@xxxxxxxxxx


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