All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carol Anne Ogdin <caogdin@deepwoods.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Split Access Detail Question
Date: Fri, 09 May 2003 03:53:43 +0000	[thread overview]
Message-ID: <marc-lartc-105245249201101@msgid-missing> (raw)

In LARTC (v1.32), under 4.2.1 Split access, the following note appears:

>Reader Rod Roark notes: 'If $P0_NET is the local network and $IF0 is
>its interface, the following additional entries are desirable:
>
>       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've market two particular lines for my question:  Wouldn't these two lines
(marked with ***) explicitly permit traffic arriving on $IF1 ($P1_NET) to
be routed back out on $IF2 ($P2_NET), and vice versa?  Under what
conditions would I want traffic arriving at my router from ISP #1 to be
sent back out to ISP #2, or vice versa?  Have I overlooked something
important here?

--Carol Anne
                                                                                    
 Carol Anne Ogdin            http://www.net-working.com                530/295-3657 
                                                                                    
 Deep Woods Technology, Inc.  http://www.deepwoods.com        CAOgdin@deepwoods.com 
                                                                                    
  Leveraging technology to                                                          
   restore the soul of the                                                          
        organization                                                                
                                                                                    




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

             reply	other threads:[~2003-05-09  3:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09  3:53 Carol Anne Ogdin [this message]
2003-05-09  5:19 ` [LARTC] Split Access Detail Question Martin A. Brown
2003-05-09 13:36 ` Carol Anne Ogdin
2003-05-09 14:29 ` William L. Thomson Jr.

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-105245249201101@msgid-missing \
    --to=caogdin@deepwoods.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.