|
On Mon, 26 Sep 2005, Ludo Stellingwerff wrote:
Okay, you're right. The definition of schedular I was using is the
definition used in the source-code: The schedular is the function that
provided the scheduling behaviour: RR, WRR, WLC, etc.
there's lots of schedulers. Yours is another one.
How did you get the director to accept packets for 0.0.0.0/0 as
local?
I don't force the director to accept them as local packets! I modified
the kernel to send forwarded traffic into LVS.
OK
For the HOWTO I would suggest: "Multipath routing through
LVS". This because the kernel term for multiple internet
connections is called multipath routing.
OK will use this name. As an abbreviation can I call it the
"MR" scheduler?
Addition to text:
http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.routing_to_VIP-less_director.html#routing_and_delivery
Another solution for this problem could be the use of the patch by
Ludo Stellingwerff, which modifies the LVS entry path. This patch
provides an iptables target called "LVS" which calls the entry
function of LVS. Thus you can match the traffic to the VIP on the
FORWARD hook of iptables:
#iptables -A FORWARD -t mangle -d <VIP> -m state --state NEW -j MARK
- --set-mark 1
#iptables -A FORWARD -t mangle -m mark --mark 1 -j LVS
This last line mimics the behaviour of packets going to the director
directly, it will call the LVS functions as if the packet was on the
local-delivery path.
no-one has come up with a general solution for this problem,
which is too bad. Thanks for the solution.
Joe
--
Joseph Mack NA3T EME(B,D), FM05lw North Carolina
jmack (at) wm7d (dot) net - azimuthal equidistant map
generator at http://www.wm7d.net/azproj.shtml
Homepage http://www.austintek.com/ It's GNU/Linux!
| 