|
> > success )-: hehe
Let's replace that with progress (-:
> are you from the southern hemisphere too (-: ?
Vancouver, Canada (-:
> > Is it more difficult to setup LVS to do HTTP, than it is to setup
telnet?
> http is the 2nd easiest, after telnet. Since you are starting out, grab my
> configure script (on the documentation page) and set it up for telnet,
> and when that works then try http
dohh!!! don't I feel silly.......
> > 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
>
> you probably have the default gw of the real-server wrong. For VS-DR it
> should not be the director, and for a test setup can be the client.
Well, I'm doing the NAT approach as your recommended this would be the
easiest approach. I have the DF GW set to my DIP, which is allowing TELNET
to go through quite fine, as well as connections to a MySQL db (port 3306)
which seems to functions damn near the same as telnet... but I'm still
getting this funky issue with HTTP... arg.
ohh and yes the HTTP service is running (-:
I'm thinking the issue has to be on the HTTP Daemon, even though it was
running quite fine as a regular old http serving pages to the public in the
past... I'm taking a big guess that is has something to do with CIP to DIP
to RIP translation which you mentioned in your HowTo?
anyhow.... back to it (-:
mike
|
