|
Hey Jospeh, I got to say I really appreciate you taking the time to write
that howto it has helped me a great deal, though I still havn't achieved
success )-: hehe
Is it more difficult to setup LVS to do HTTP, than it is to setup telnet?
What happens is I see this
IP Virtual Server serion 0.9.15 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Wight ActiveConn InActConn
TCP yoggy.vocalcommerce.com:www wlc
-> 192.168.10.101:www Route 1 0 1
The InActConn gets flagged at 1 when I try to connect to the director from a
CIP, yet I'm unable to get anything through the connection...
Ideas?
Anyhow i'm gonna try getting it going with telnet, and see if that works
Thanks in advance for any advice.
----- Original Message -----
From: "Joseph Mack" <mack@xxxxxxxxxxx>
To: "Michael McConnell" <michael@xxxxxxxxxxxxxxxxxxxxxx>
Cc: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Friday, July 28, 2000 3:54 AM
Subject: Re: ipvs 0.9.15 available
> On Thu, 27 Jul 2000, Michael McConnell wrote:
>
> > I've been having a very difficult time getting LVS to work with NAT or
> > Tunneling, I've read the documents on the WebSite many times over.
>
> It isn't easy and there's a lot of things that can go wrong.
>
> Grab my configure script off the website and try setting up VS-NAT with 1
> or 2 real-servers serving telnet. The script will detect most common
> misconfiguration problems. It doesn't do failover, but is simple to use.
>
> If it doesn't work, come back with the conf file and the output of
> ipvsadm just after a failed connect attempt.
>
> Joe
>
> --
> Joseph Mack mack@xxxxxxxxxxx
>
>
>
|
