2010::/16 filtering
Richard Draves
richdr@microsoft.com
Fri, 25 Jun 1999 11:44:32 -0700
This routing loop should be fixed now.
If anyone else can't reach 2010:836b:4179::836b:4179, please let me know.
Thanks,
Rich
> -----Original Message-----
> From: Cyndi Jung [mailto:cmj@3com.com]
> Sent: Thursday, June 24, 1999 3:17 PM
> To: Richard Draves; '6bone'
> Subject: Re: 2010::/16 filtering
>
>
> At 01:53 PM 6/24/99 -0700, Richard Draves wrote:
> >I've started experimenting with connecting a 6to4 relay
> router to the 6bone.
> >(See
> http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-6to4-02.txt.)
> >
> >This means that the 2010::/16 prefix is now being advertised
> in the 6bone.
> >
> >However it appears that many sites are filtering this
> prefix. If you are
> >filtering, could you permit the 2010::/16 prefix?
> >
>
> I don't know about filtering, but I run into a loop attempting to get
> to it:
>
>
> Welcome to the 3Com NETBuilder
> [1]TDC-ipv6 # trr6 2010:836b:4179::836B:4179
> TraceRoute to 2010:836B:4179::836B:4179/128
> TTL Next Hop Address RTTs
> 1 3FFE:1900:5:1:200:81FF:FED5:805A/128 16 ms 16 ms 14 ms
> 2 3FFE:1C00::3/128 86 ms 83 ms 85 ms
> 3 3FFE:1001:1:F004::2/128 313 ms 327
> ms 307 ms
> 4 3FFE:900:0:3::2/128 115 ms 119
> ms 113 ms
> 5 3FFE:1001:1:F004::2/128 356 ms 359
> ms 335 ms
> 6 3FFE:900:0:3::2/128 150 ms 145
> ms 148 ms
> 7 3FFE:1001:1:F004::2/128 377 ms 374
> ms 371 ms
> 8 3FFE:900:0:3::2/128 183 ms 184
> ms 192 ms
> 9 *
> 9 3FFE:1001:1:F004::2/128 403 ms *
> 10 3FFE:900:0:3::2/128 271 ms 228
> ms 249 ms
> 11 3FFE:1001:1:F004::2/128 451 ms
>
> 12 3FFE:900:0:3::2/128 254 ms 250 ms
> 13 3FFE:1001:1:F004::2/128 850 ms *
> 14 3FFE:900:0:3::2/128 284 ms * *
> 15 * * *
> 16 3FFE:900:0:3::2/128
>
> Cyndi
>