I guess I should have said that I can force a connection to either server by
simply removing the other one from the ipvsadm hashed routing table.
My ipchains is very big and ugly, I've tried to just pull out this relevant
part:
Chain input (policy DENY):
target prot opt source destination ports
<snip>
- tcp ------ 0.0.0.0/0 200.100.100.31 * ->
80
- tcp ------ 0.0.0.0/0 200.100.100.31 * ->
443
ACCEPT tcp ------ 0.0.0.0/0 200.100.100.31 1024:6553
-> 80
ACCEPT tcp ------ 0.0.0.0/0 200.100.100.31
1024:65535 -> 443
<snip>
(Where "200.100.100.31" would be the VIP I'm using for the FWMARK 3). (This
isn't really my VIP).
The routing table for the director would look like this
Destination Gateway Genmask Flags Metric Ref Use
Iface
0.0.0.0 200.100.100.1 0.0.0.0 UG 0 0 0
eth1
--K
From: Thomas Proell <Thomas.Proell@xxxxxxxxxx>
To: Lorn Kay <lorn_kay@xxxxxxxxxxx>
CC: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: Problem with RR scheduling method?
Date: Tue, 7 Nov 2000 18:49:31 +0100 (MET)
> Making two connections from two different client IPs (after just
reseting
> ipvs with "ipvsadm -C") gives the same (HTTP) server.
Just "ipvsadm -C"? Then you don't have any service at all...
> ipvsadm -L -n confirms this:
O.K. so you seem to have a service running. Show me your "ipchains -L"
and tell me what "deault gateways" you have.
Thomas
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
|