All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Tone <simpletone@mbox.com.au>
To: lartc@vger.kernel.org
Subject: [LARTC] multiple inet links on 1 nix box
Date: Tue, 08 Jan 2002 23:30:59 +0000	[thread overview]
Message-ID: <marc-lartc-101053285509237@msgid-missing> (raw)

I have 2 cable modems with differant providers, connected to a nix box 
 with 1 internal interface and 2 dmz if's..

 to get both cable modems working at once, you simply need to remove the 
 2 default routes that each interface adds to the routing table upon 
 startup..

 however, you will then need to add static routes to each ISP's 
 authentication server / POP server / dhcp server...
 selecting the device (dev ethX)...

 ie: route add -net isp1.pop.server.0/24 gw x.x.x.x dev eth1
 route add -net isp2.pop.server.0/24 gw x.x.x.x dev eth2

 at this point, both cable modems are stable and work, retreive email 
 from each ISP's pop server via fetchmail, reply to ISP's heartbeats 
 etc...

 you can then use netfilter (iptables) to mark packets going out, so, 
 all traffic to tcp:80 (http), route via dev eth1 (faster link takes all 
 outgoing web traffic)..

 however, my problem.. :)
 a web server listening on tcp:443 on eth1 (isp/cablemodem #1), is not 
 contactable from the outside world, UNLESS this dev is set as the 
 DEFAULT route for all traffic...

 can this be fixed with --SNAT ? or mark INCOMING packets with 5 say,
then add route for mark 5 via dev ethX?

 help! :)

---------------------------------------------------------------------
mBox makes you work Smarter, not Harder, from only $0.58 per WEEK!
Visit http://www.mbox.com.au

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

                 reply	other threads:[~2002-01-08 23:30 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-101053285509237@msgid-missing \
    --to=simpletone@mbox.com.au \
    --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.