From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Zebra, Routing ...
Date: Thu, 14 Feb 2002 19:05:22 +0000 [thread overview]
Message-ID: <marc-lartc-101371355401683@msgid-missing> (raw)
Before I start, I don't want to do ECMP or simple bonding ...
I have multiple Internet connections available to multiple boxes on one
of my networks.
Box A connects to ISPs 1, 2 and 3
Box B connects to ISPs 1 and 4
Boxes A and B are both connected to each other and the rest of the
network.
1) I would like to set up some dynamic routing in such a way that any
given outgoing packet from Box A or B would go out over the ISP that had
the "best" path (according to BGP) to the destination. I would like to
be able to assign 'weights' to these routes (based on their available
bandwidth), but it is not necessary.
2) I would like to have any given *nix box on the network pick the right
gateway (A or B) given the destination of its packets.
I understand that I could do 1) easily if I had a BGP AS#, but I don't.
Is it possible to arrange 'private' peering arrangements so I could
download the BGP views each ISP had without needing a public AS# (don't
tell me I should get one -- it probably won't happen).
Am I correct in assuming that OSPF (which I currently have installed) is
the best way to handle route distribution within the network (#2
above)? Is there a 'good' way to configure it with as few rules as
possible?
I'm going to send this to the Zebra list as well once I find my address
book entry for them, but I thought somebody here might have good answers
too.
--
Michael T. Babcock
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next reply other threads:[~2002-02-14 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 19:05 Michael T. Babcock [this message]
2002-02-14 20:31 ` [LARTC] Zebra, Routing Michael T. Babcock
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-101371355401683@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox