Route leak in Bangladesh

Sandra Murphy sandy at tislabs.com
Tue Jun 30 14:44:00 UTC 2015


On Jun 30, 2015, at 9:41 AM, Job Snijders <job at instituut.net> wrote:

> 
> In addition to the BGP community scheme, outbound as-path filters could
> help. Most network's list of transit providers is fairly static, it
> would be easiy with as-path filters to prevent announcing upstream
> routes to other upstreams or peering partners.


Except that this was not a route leak per se.  The announced routes AS_PATH shows them as originated by the offending AS, not *propagated* by the offending AS. So the outbound AS_PATH did not retain the upstream portion of the path.

--Sandy


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20150630/d8f89650/attachment.sig>


More information about the NANOG mailing list