|
Are you sure you've handled the ARP problem on x.232 ?
In Director, two packet perl-Parse-RecDescent-1.80-1.rh.el.um.1.noarch.rpm
and perl-XML-NamespaceSupport-1.08-1.rh.el.um.1.noarch.rpm have been
installed, and i have command
echo 1 > /proc/sys/net/ipv4/ip_forward also .
In the two realserver, i install these two packet and with Command
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/ipv4/conf/all/hidden
echo 1 > /proc/sys/net/ipv4/conf/lo/hidden
does it enough to handled ARP problem?
> the Structure is as below:
>
> Prot LocalAddress:Port Scheduler Flags
> -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> TCP 10.0.58.136:443 rr
> -> 10.0.58.232:443 Route 1 0 2
> TCP 10.0.58.136:80 rr
> -> 10.0.58.230:80 Route 1 1 8
> -> 10.0.58.232:80 Route 1 0 7
All those inactive connections on both HTTP and HTTPS imply that you
haven't.
What method did you use?
I use the Direct Routing with Round Roubin scheduling
The Director is ES3.0 with the Ultramonkey kernel-2.4.21-27.0.2.EL.um.1.i686.rpm
and the HTTPS server is RH8.0 with kernel-bigmem-2.4.20-31.9.um.3.i686.rpm
Please Help
Thank You
Regards,
Louis.
______________________________________________
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
|
