Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "GoMi" <gomi@perezoso.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Splitting connections between 2 different ADSL lines
Date: Tue, 04 Nov 2003 10:29:08 +0000	[thread overview]
Message-ID: <marc-lartc-106794242521406@msgid-missing> (raw)

 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I was wondering this morning, why unstead of having load balancing, use one ADSL router just for interactive traffic, and a second one just for p2p programs for example? Has anybody ever used this setup. Wouldn't NAT get crazy? Just a thought...

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0

iQA/AwUBP6d/c37diNnrrZKsEQJLWQCeLnArpTnbvMjHwAPN6HCzSVuIAnUAoINR
jU6mHeHMJraHoEriHj0Ll6NY
=AGrK
-----END PGP SIGNATURE-----


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

                 reply	other threads:[~2003-11-04 10:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-106794242521406@msgid-missing \
    --to=gomi@perezoso.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox