Outdated bogon filtering seems pervasive..

[Iljitsch van Beijnum]

On 3-jun-2006, at 0:17, bmanning at vacation.karoshi.com wrote:

> 	we'll still talk to him... :)

SOMEBODY is still talking to me:

traceroute6 to 2610:78:f::1 (2610:78:f::1) from 3ffe:2500:310:4::1,  
64 hops max, 12 byte packets
1  3ffe:2500:310:4::2  13.751 ms  15.397 ms  15.098 ms
2  2001:1af8:2:6::1  16.076 ms  14.257 ms  16.469 ms
3  2001:1af8:1:195:20e:39ff:fe3c:2aaa  159.392 ms  205.658 ms   
233.981 ms
4  eth0-0-7.6b2.ams7.alter.net  11.956 ms  15.008 ms  16.956 ms
5  tu2.6B1.LND6.ALTER.NET  22.470 ms  24.144 ms  20.593 ms
6  uunet12702.lnd.OCCAID.org  23.220 ms  24.558 ms  24.967 ms
7  52.ge0-0.cr2.lhr1.uk.occaid.net  26.967 ms  24.526 ms  24.717 ms
8  v3323-mpd.cr1.ewr1.us.occaid.net  98.926 ms  100.741 ms  102.171 ms
9  unassigned.ar1.yeg1.ca.occaid.net  155.021 ms  150.584 ms  152.897 ms
10  ipv6.tera-byte.com  151.521 ms  156.950 ms  150.639 ms

I'm glad to see my upstreams don't have broken bogon filters.

I would have hoped that people who are enlightened enough to run IPv6  
would also know that you should either keep your bogon filters up to  
date or don't have any in the first place, but I guess that was too  
much to expect.

You can see what happens with my 6bone connectivity by pinging/ 
tracerouting 6bone.muada.com, by the way. I'll be interested to see  
whether UUNET/MCI/Worldcom/Alter.net makes good on its promise to  
remove 6bone space after 6/6/6.