From: c0g <c0g@wp.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems with ICQ etc. on nano-setup
Date: Mon, 15 Dec 2003 12:38:43 +0000 [thread overview]
Message-ID: <marc-lartc-107149274013899@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107145755020004@msgid-missing>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
| Can one "bind" traffic from one LAN-user to the same DSL, effective in
| lets say 10 minutes from the initial connection?
| Can some magic with conntrack be put to use?
You should do Equal Cost Multipath (iproute) + MARK target instead of
state-based loadbalancing for problematic protocols/sites.
Create table with default route thru multiple gateways with equalize
option. Then direct problematic traffic to this table (using routing
rules and mark matching)
Equal Cost Multipath chooses route based on source and destination IP,
so it bounds client to route, no matter how many connections that client
made.
It works for me.
PS: I assume you have separate network interface in your Linux router
for each DSL, so you can do SNAT on each interface. If you have them
connected to one NIC then it not that simple, but may be resolved with
route realms (but not sure for 100%).
- --
c0g@wp.pl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/3atPPqmVt5WhbA8RAo/HAJ9XJ1Fb+/LLDkEQs5aUh9nS7aN8DgCfbuVu
yfQXVOluF+uY7DC5+JZxM4g¤og
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-12-15 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 2:57 [LARTC] Problems with ICQ etc. on nano-setup Steen Suder, privat
2003-12-15 6:25 ` Ben Efros
2003-12-15 10:41 ` Steen Suder, privat
2003-12-15 12:38 ` c0g [this message]
2003-12-15 13:03 ` Steen Suder, privat
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=marc-lartc-107149274013899@msgid-missing \
--to=c0g@wp.pl \
--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.