|
On Thu, May 18, 2000 at 12:49:38PM +0000, Szymon Jakub Oterski wrote:
> Internet
> |
> |
> |
> Router (IP: 195.212.95.129) routes 195.212.95.140,
> 195.212.67.138 and 195.212.67.139 into the LAN.
> |
> |
> |
> | ( eth0 = 195.212.95.140 )
> | ( eth0:0 = 195.212.67.138 (LVS 1))
> | ( eth0:1 = 195.212.67.139 (LVS 2))
> Linux host 1
> | ( eth1 = 10.1.1.1 )
> |
> |
> HUB ----------------------------------------------------------->
> local PCs
>
> |
> | |
>
> |
> | |
>
> |
> | |
> (10.1.1.2/24)
> (10.1.1.3/24) (10.1.1.4/24)
> NT-host 1 NT-host
> 2 Linux host 2
> (1. http) (2.
> http) (1. http)
> serves LVS 1 serves LVS
> 2 serves soon LVS 1, too
>
> As you can see, the requests come onto the 195.212.67.x network, but the
> gateway to the internet is on the 195.212.95.x network. The Linux host 1
> shall act as a gateway for the local PCs and as LVS on the two
> 195.212.67.x IPs. for now i'm trying to route al the requests on
> 195.212.67.139:80 to 10.1.1.3:80. I've used the configure.pl script with
> a modified lvs_nat.conf to start the program, but something is wrong and
> I don't know what.. the Linux host 1 is based on SuSE 6.3 Linux with a
> 2.2.15 kernel (from ftp.kernel.org, not suse!) patches with
> lvs-2.2.15-0.9.12 . ehte NICs are all working, routes are set to
> folowing NETs: 10.1.1.0, 195.212.95.0, 195.212.67,0 and default via
> gw195.212.95.129. ipchains allows forwarding from 10.1.1.0 to everywhere
> on all ports over MASQ. so far so good.
>
> Now, when a http request comes from a client on 195.212.67.139:80 iptraf
> says, that a connection is made to 10.1.1.3, and the masq table says,
> that there is traffic from 10.1.1.3 to the client, git the client doesn't
> get a reply. Does anyone know, what configurations i have to do? Does
> anyone got LVS running on a SuSE system?
Can you connect to 10.1.1.3:80 from Linux host 1?
Can you send the out put of the followinc commands on
linux host 1:
ipvsadm -h | head
ipvsadm -L -n
ipchains -L -n
rotue -n
> And finaly, is this program able to handle more than in IP?
IPVS can certainly handle more than one IP, by either setting
up multiple virtual services with the same backend server, or
using the fwmark funtionality, see the ipvsadm man page.
--
Horms
|
