Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: <zen30267@zen.co.uk>
To: lartc@vger.kernel.org
Subject: [LARTC] Problems setting up routing for multiple links
Date: Tue, 30 Sep 2003 13:42:31 +0000	[thread overview]
Message-ID: <marc-lartc-106496085931327@msgid-missing> (raw)

Hi All,

I am trying to setup Routing on my Bering Firewall to allow connections to two providers, as well as maintaining inbound connections to web servers hosted in a dmz.

I have been adding the commands as described on the web site section 4.2.1, but find that the line shown with an * generate a file already exists.

ip route add $P1_NET dev $IF1 src $IP1 table T1
ip route add default via $P1 table T1
ip route add $P2_NET dev $IF2 src $IP2 table T2
ip route add default via $P2 table T2

* ip route add $P1_NET dev $IF1 src $IP1
* ip route add $P2_NET dev $IF2 src $IP2

ip route add default via $P1

ip rule add from $IP1 table T1
ip rule add from $IP2 table T2

ip route add $P0_NET     dev $IF0 table T1
ip route add $P2_NET     dev $IF2 table T1
ip route add 127.0.0.0/8 dev lo   table T1
ip route add $P0_NET     dev $IF0 table T2
ip route add $P1_NET     dev $IF1 table T2
ip route add 127.0.0.0/8 dev lo   table T2 


I am using the up command to add these to the /etc/networks/interface file.

I believe I will need further routes for the dmz, but need to understand the first failure before moving onto this issue. Any help on this would be much appreciated.

Regards,

Simon Chalk.




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

                 reply	other threads:[~2003-09-30 13:42 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-106496085931327@msgid-missing \
    --to=zen30267@zen.co.uk \
    --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