[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Consistent routing policy?

Thanks, Mark, that makes sense.

Take care,

On Mon, Sep 16, 2019 at 9:05 AM Mark Tinka <mark.tinka at seacom.mu> wrote:

> On 16/Sep/19 14:47, Ben Logan wrote:
> > Thanks, Mark.  So the discrepancy between what's being advertised (/21
> > vs /22) shouldn't cause any issues?  That's the part I got a bit
> > confused about.  I don't see how it would, but I wanted to make sure.
> Longest match always wins... so provided your /22's are in the global
> table, traffic will follow the path toward them before the /21 is
> preferred.
> So, for example, if the upstream to whom you are sending the /21 doesn't
> do anything about how they learn the /22 from another source, (for their
> network) they will also send traffic back to you via the /22 path. This
> may or may not be preferred by you, or them. I suppose that's the main
> thing to think about.
> Mark.

Ben Logan
Senior Network Engineer | Working Lead
Wilkes Communications | RiverStreet Networks

Address: 1400 River St Wilkesboro, NC 28697
Email: benlogan at myriverstreet.net
Phone: 336-973-9075
Mobile: 336-452-8072
 wilkes.net <https://www.wilkes.net>
 myriverstreet.net <https://www.myriverstreet.net>

This email transmission contains information which may be confidential
and/or privileged. The information is intended to be for the use of the
individual or entity named on this transmission. If you are not the
intended recipient, be aware that any disclosure, copying, distribution or
use of the contents of this email information is prohibited. If you have
received this email in error, please notify the sender to arrange for
retrieval of the original documents. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190916/dc108440/attachment.html>