|
I'm using LVS-NAT not LVS-DR as far as I know...
-A -t 198.144.160.53:25 -s wlc
-a -t 198.144.160.53:25 -r 198.144.167.163:25 -m -w 1
-a -t 198.144.160.53:25 -r 198.144.167.162:25 -m -w 1
-A -u 198.144.160.53:53 -s wlc
-a -u 198.144.160.53:53 -r 198.144.167.163:53 -m -w 1
-a -u 198.144.160.53:53 -r 198.144.167.162:53 -m -w 1
-A -t 198.144.160.53:53 -s wlc
-a -t 198.144.160.53:53 -r 198.144.167.163:53 -m -w 1
-a -t 198.144.160.53:53 -r 198.144.167.162:53 -m -w 1
-A -t 198.144.160.53:80 -s wlc
-a -t 198.144.160.53:80 -r 198.144.167.163:80 -m -w 1
-a -t 198.144.160.53:80 -r 198.144.167.162:80 -m -w 1
----- Original Message -----
From: "Peter Mueller" <pmueller@xxxxxxxxxxxx>
To: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, June 20, 2001 4:44 PM
Subject: RE: Problems with LVS, Local machines can't get to Virtual IP.
> > Problem: Our client machine witch is on the same network as
> > the VIP can not
> > get to any services. Machines from other networks CAN get to
> > VIP services.
> > We get a SYNC_RECV when we do a ipvsadm -l -c when a machine from out
> > 198.144.160.x network attemtps to connect to 198.144.160.59...
>
> Looks like you have LVS-DR? In the documentation I seem to recall that
you
> must segregate the client from the LVS setup. Check up on the howto for
> more info.
>
> Is there any possibilty of splitting the 198.144 network into two halves?
> If not, then how about moving the client to a different subnet? At the
very
> least test your setup with a client on another setup.
>
> note : I don't have time to re-check any of this, so please view it as a
> guide rather than as a fact. I could very well be wrong :)
>
> cheers,
>
> Peter
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
