[bdNOG] Fwd: Route leak in Bangladesh

Tue Jun 30 22:04:29 BDT 2015

I don't think I've seen anyone.

How does a NSP end up *originating* other people's prefixes anyway? Is 
that some funky AS-path rewriting gone awry when redistributing from IGP 
into {e}BGP?

I personally would love some information.

Leaks, the traditional ones, usually only reroute by inserting the 
leaker's own ASN in the path.

On 7/1/2015 午前 01:01, Faisal Hasan wrote:
> Hi All,
>
> I see a lot of discussing is going on about the BD Route link at 
> nanog. Did anyone respond about it from BD side?
>
> Thanks
> Faisal
> ---------- Forwarded message ----------
> From: *Graham Beneke* <graham at apolix.co.za <mailto:graham at apolix.co.za>>
> Date: Tue, Jun 30, 2015 at 10:45 AM
> Subject: Re: Route leak in Bangladesh
> To: nanog at nanog.org <mailto:nanog at nanog.org>
>
>
> On 30/06/2015 17:09, Job Snijders wrote:
> > If you were the network causing a leak of this type, prefix filters on
> > inbound facing your customers might not have prevented this.
> >
> > If you are a network providing transit to the leak originator mentioned
> > in the above paragraph, I believe a prefix based filter could have made
> > a big difference.
>
> We seem to be assuming that this leak occurred within the context of a
> customer-provider BGP relationship.
>
> But what if this is not the case?
>
> What if this was a peering session - perhaps via a route server at an
> exchange point. max-pref on a session with a route server is an
> extremely blunt (and potentially ineffective) tool for the job.
>
> In some regions the use to route servers and the lack of clue about
> anything BGP beyond one session to the route server (and one session to
> transit) is scary. We place our faith in the IXP operator, that they
> know best, while there may be no evidence that they do... ;-)
>
> --
> Graham Beneke
>
>
>
> _______________________________________________
> nog mailing list
> nog at bdnog.org
> http://mailman.bdnog.org/mailman/listinfo/nog

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.bdnog.org/pipermail/nog/attachments/20150701/70559be8/attachment.html>