Some leaks in China/Hongkong

Thomas Schmid schmid at dfn.de
Tue Oct 28 17:11:29 CET 2008


Hi all,

Gert Doering wrote:
> Hi,
> 
> On Sun, Oct 26, 2008 at 08:59:38AM -0700, Mike Leber wrote:
>> dfn, geant2, or internet2 don't currently get a decent full view 
>> otherwise they wouldn't send traffic to Hong Kong.
> 
> It's much worse.  At least DFN *has* a full view, but they prefer Geant2
> routes, because "NREN stuff needs to go there".
> 

that's right and this is badly needed today and in the future. We don't want
to send any NREN traffic via unknown peering paths alone because this
affects mutltiple Gigs of traffic and might flood quite some links.

> And since I2 seems to be really unwilling to properly sort out their 
> routing (properly distinguish between "customers", "peers", and "upstream/
> transit", with the proper filters in place to avoid leaking everything
> everywhere) this is causing harm again and again.
> 

here we go ...

> 
> I have some more of these... Egyptian REN more specifics being leaked by 
> I2 all over the place...
> 
> grh.sixxs.net> show bgp ipv6 2001:4300:2001::/48
> BGP routing table entry for 2001:4300:2001::/48
> Paths: (14 available, best #3, table Default-IP-Routing-Table)
>   Not advertised to any peer
>   13645 19151 9304 4635 17579 11537 33789 24863
>     2001:5b8:fffe:: from 2001:5b8:fffe:: (64.135.0.0)
>       Origin IGP, localpref 100, valid, external
>       Community: 13645:3121
>       Last update: Sun Oct 26 10:33:10 2008
> 
>   20932 30781 5511 10764 11537 33789 24863
>     2001:41e0:0:f::1 from 2001:41e0:0:f::1 (217.169.143.20)
>       Origin IGP, metric 0, localpref 100, valid, external
>       Last update: Fri Oct 24 21:43:41 2008
> 
> ...
> 
> (19 /48s in total, only visible via 11537)
> 
> The really bad thing about that is that the /32 in question seems to have
> direct transit via Sprint, which is not used now, since "longest prefix
> wins"...
> 

I don't see an easy solution for the time being. So manual reaction on people
complaining is currently the only way to deal with the problem.

Regards,

  Thomas



More information about the ipv6-ops mailing list