All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Why multiple NICs in a multiple route situation?
Date: Tue, 06 Aug 2002 16:30:47 +0000	[thread overview]
Message-ID: <marc-lartc-102865150010208@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102827313732464@msgid-missing>

Greg Scott wrote:

>So why a NIC per T1?  Why not just give a single NIC an 
>IP address in all the networks for each T1?  Or am I missing
>something important?
>  
>
I don't like the fact that one ISP can 'see' the other ISP if they 
decide to actually 'look'.
-- 
Michael T. Babcock


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

      parent reply	other threads:[~2002-08-06 16:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-02  7:46 [LARTC] Why multiple NICs in a multiple route situation? Greg Scott
2002-08-02  7:57 ` William L. Thomson Jr.
2002-08-06 16:30 ` Michael T. Babcock [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-102865150010208@msgid-missing \
    --to=mbabcock@fibrespeed.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 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.