LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: VIP on real interface.

To: "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: VIP on real interface.
From: "Dan" <kasper37@xxxxxxxxxxxxx>
Date: Fri, 12 Mar 2004 07:27:57 -0800
Thank you for your response.  Still having some issues though.

> > 1) First, is this possible?
>
> I don't see why not. Its just LVS-DR with packets being forwarded
> to the real servers on the 192.168.0.0 network, right?

That's correct.

> > 2) What should the netmask of x.y.z.2 be on the realserver?
>
> x.y.z.2 should probably be on lo:0, in which case
> its netmask should be 255.255.255.255.
>
> If you really do want it on eth0 (I strongly doubt you do)
> then the netmask would be whatever the netmask for the x.y.z network is,
> presumably 255.255.255.0

Okay, I had that set correctly to 255.255.255.0.  I have no other use for eth0
so I don't mind putting the VIP on it.

> > 3) What should the default gateway be for the realserver?
>
> x.y.z.1

Okay...I had this set correctly.

> > 4) Do I need a routable ip on eth0 other than the VIP?  I'd rather it not
have
> > one.
>
> I can't see why you would need a routable IP on eth0, as long as
> you are routing replies out the interface.
>
> Unfortunately I don't think linux supports IP unnumbered, so you
> probably need some address on eth0.  Logically something from the x.y.z
> network otehr than .1 or .2. But really there is nothing to stop you
> putting any address you like there.

As I said above, hopefully I can get this to work with just the VIP set to eth0.

> > 5) What should /sbin/route output look like on the realserver once this is
> > configured correctly?
>
> I guess something like this.
>
> 192.128.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
> x.y.z.0         0.0.0.0         255.255.255.0   U     0      0        0 eth0
> 0.0.0.0         x.y.x.1         0.0.0.0         UG    0      0        0 eth0

Well...that's exactly what it looks like alright.  I think the only problem I
have left is that eth0 is still answering arps.

# for i in /proc/sys/net/ipv4/conf/*/hidden; do echo $i; cat $i; done
/proc/sys/net/ipv4/conf/all/hidden
1
/proc/sys/net/ipv4/conf/default/hidden
0
/proc/sys/net/ipv4/conf/eth0/hidden
1
/proc/sys/net/ipv4/conf/eth1/hidden
0
/proc/sys/net/ipv4/conf/lo/hidden
0
#

This looks right to me...why is this interface still answering arps?

Dan

P.S.  This is a debian system running the 2.4.25 kernel with the hidden patch.
Nothing I've read indicates that this setup should have a problems, but I'm
mentioning it anyway.

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