|
Ok, nevermind. Another false alarm. I restarted the machine without adding
the modules and it worked ok.
Sorry...
Thanks again!
----- Original Message -----
From: <bhilkert@xxxxxx>
To: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, November 18, 2008 12:10 PM
Subject: [lvs-users] Ldirectord won't forward
> I'm using Debian Etch and installed Ldirectord using:
>
> aptitude install ldirectord-2
>
> My cf file is:
>
> # Global Directives
> checktimeout=5
> checkinterval=20
> autoreload=no
> logfile="/var/log/ldirectord.log"
> quiescent=yes
>
> # Virtual Server for HTTP
> virtual=10.10.5.1:80
> fallback=10.10.5.3:80
> real=10.10.5.2:80 masq
> service=http
> request="index.htm"
> receive="10.10.5.2"
> scheduler=rr
> protocol=tcp
> checktype=negotiate
>
> I start is using: ldirectord -d start
>
> and the page is proper checked for the keyword and found successful.
>
> IP Virtual Server version 1.2.1 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
> -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> TCP 10.10.5.1:80 rr
> -> 10.10.5.2:80 Masq 1 0 2
>
> Each time i refresh the broswer, the InActConn increases
>
>
> ntop:/# tcpdump -n -i any port 80
> 11:31:37.797723 IP 10.10.10.101.4813 > 10.10.5.1.80: S
> 3075972850:3075972850(0)
> win 65535 <mss 1460,nop,nop,sackOK>
> 11:31:37.797736 IP 10.10.10.101.4813 > 10.10.5.2.80: S
> 3075972850:3075972850(0)
> win 65535 <mss 1460,nop,nop,sackOK>
>
> So it forwards it to the right place, but the browser never sees the
> connection.
> I can go straight to 10.10.5.2 and the page loads fine.
>
> So why does the broswer not see the forwarded connection?
>
>
>
|
