All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Splitting traffic
Date: Thu, 03 Oct 2002 02:24:43 +0000	[thread overview]
Message-ID: <marc-lartc-103361193402417@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103360390129899@msgid-missing>


Lars,

Curiously, I just wrote a section about this in my document yesterday.  
Though there may be more than one way to do this, I have documented the 
only way I know how to do this.  See

  http://plorf.net/linux-ip/

Visit chapter 7 (Advanced IP Routing), in particular the section on 
multiple connections to the Internet.  I have not written the section on 
fwmark quite yet, but there is an embedded example which shows how to 
split traffic by using fwmark and then routing based on the fwmark.

Good luck,

-Martin

 : Hi
 : 
 : I have the following configuration:
 : 
 :          ________________
 :         |                --- ISP1
 : LAN ----| Linux firewall |
 :         |                |
 :         |________________--- ISP2
 : 
 : I would like to have all http, ssh and UDP traffic routed through ISP1
 : and everything else on ISP2. How can I do this?
 : 
 : Thanks a lot
 : Lars Munch
 : 
 : _______________________________________________
 : LARTC mailing list / LARTC@mailman.ds9a.nl
 : http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
 : 

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com


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

      reply	other threads:[~2002-10-03  2:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03  0:10 [LARTC] Splitting traffic Lars Munch
2002-10-03  2:24 ` Martin A. Brown [this message]

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-103361193402417@msgid-missing \
    --to=mabrown-lartc@securepipe.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.