From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Zebra, Routing ...
Date: Thu, 14 Feb 2002 20:31:05 +0000 [thread overview]
Message-ID: <marc-lartc-101371872116392@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101371355401683@msgid-missing>
On Thu, 2002-02-14 at 15:17, Gregory Maxwell wrote:
> No. OSPF is wrong for inter domain routing. You need to speak BGP.
You misunderstood; OSPF would communicate the routes within my network
to the other boxes on my network. IBGP would be equally productive and
RIP would be workable too if I didn't already have OSPF support.
> I believe you can get zebra to run multiple BGP instances, and dump each
> into a seperate routing table.. you can then use iproute2 to make differnt
> packets use differnt tables.
That seems overly complex considering Zebra should (IMHO) know how to
cull a routing table from multiple BGP4 sessions ... its sort of why
BGP4 exists at all.
I understand the technical side (and packet-side, for that matter) of
how the various routing protocols work; I'm just not familiar with
actually configuring the exterior routing protocols on a box. Maybe I
should tuck a Cisco course feather into my hat ...
--
Michael T. Babcock
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2002-02-14 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 19:05 [LARTC] Zebra, Routing Michael T. Babcock
2002-02-14 20:31 ` 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-101371872116392@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.