From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Loadbalancing and failover using TC and Iptables
Date: Tue, 09 Aug 2005 01:59:37 +0000 [thread overview]
Message-ID: <42F80E09.2F083F6C@iswest.com> (raw)
In-Reply-To: <018701c59bda$5f42db40$0903a8c0@southern>
:: L i n u XK i D :: wrote:
>
> I've read next link:
>
> -> I'm not sure this is still a good link
> -> http://selab.edu.ms/twiki/bin/view/Networking/MultihomedLinuxNetworking
>
> is really neccessary mark pakets on this way ?
From the machine on which the 2 ISPs are connected to two different
NICs, no. It will send and receive packets without marking. Where I
have a problem is with NATted users; they are tied to one or the other
ISP (even though I run 'ip route flush cache') unless I mark.
Maybe Julian will give us some hints <grin>?
--
gypsy
> [... snip ...]
>
> # iptables -A POSTROUTING -t mangle -j MARK --set-mark 1 \
> -m state --state NEW -o ppp0
> # iptables -A POSTROUTING -t mangle -j MARK --set-mark 2 \
> -m state --state NEW -o ppp1
> # iptables -A POSTROUTING -t mangle -j CONNMARK --save-mark \
> -m state --state NEW
>
> [... snip ...]
>
> # iptables -A POSTROUTING -t nat -m mark --mark 1 \
> -j SNAT --to-source 11.1.1.1
> # iptables -A POSTROUTING -t nat -m mark --mark 2 \
> -j SNAT --to-source 22.2.2.2
>
> -> hareram wrote:
> -> >
> -> > Hi all
> -> >
> -> > iam trying to deploy loadbalance and failover
> -> >
> -> > My setup description
> -> > --Fedora Core 4
> -> > --Linux 2.6.12.3 #1 SMP Mon Jul 25 22:37:34 IST 2005 i686 i686 i386
> -> > GNU/Linux
> -> > --tc utility, iproute2-ss050314
> -> > --ip utility, iproute2-ss050314
> -> > --iptables v1.3.0
> ->
> -> You say nothing about Julian's patch, so I assume you did not patch your
> -> kernel. You must do that.
> -> http://www.ssi.bg/~ja/
> ->
> -> http://www.geocities.com/mctiew/ffw/dual.htm
> ->
> -> I'm not sure this is still a good link
> -> http://selab.edu.ms/twiki/bin/view/Networking/MultihomedLinuxNetworking
> -> so here is an old copy
> -> http://yesican.chsoft.biz/lartc/MultihomedLinuxNetworking.html
> -> --
> -> gypsy
> -> _______________________________________________
> -> LARTC mailing list
> -> LARTC@mailman.ds9a.nl
> -> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-08-09 1:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 5:43 [LARTC] Loadbalancing and failover using TC and Iptables hareram
2005-08-08 13:46 ` gypsy
2005-08-08 17:26 ` hareram
2005-08-08 17:35 ` :: L i n u XK i D ::
2005-08-08 17:59 ` hareram
2005-08-09 1:59 ` gypsy [this message]
2005-08-09 14:21 ` LinuXKiD
2005-08-09 20:42 ` LinuXKiD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42F80E09.2F083F6C@iswest.com \
--to=gypsy@iswest.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.