Problems with AS40015 and AS30071 <--> AS3320

Andre Grueneberg list.ipv6ops at grueneberg.de
Thu Nov 26 20:27:28 CET 2015


Thomas Schäfer wrote:
> I am in conflict with the support of Deutsche Telekom (AS3320). They
> check my DSL-connection again and again. And I try to explain that there
> must be a bigger problem.
> 
> The problem itself is very simple:
> 
> bin6.it

$ dig bin6.it AAAA +short
2607:fd50:1:91b0::b146:11
$ whois -h whois.ra.net 2607:fd50:1:91b0::b146:11
%  No entries found for the selected source(s).
 
> v6.testmyipv6.com

$ dig v6.testmyipv6.com AAAA +short
2001:4830:2502:8001::a00:a
$ whois -h whois.ra.net 2001:4830:2502:8001::a00:a
route6:     2001:4830::/32
descr:      Proxy-registered route object
origin:     AS30071
...
source:     ALTDB

> Is somebody here, who could confirm or better fix the problems between
> these AS?

I can confirm that several of our IP transits do not announce these
routes. AS3320 doesn't announce either, AS1299 and AS6461 also don't
carry 2001:4830::/32.

It seems like some Tier1 operators are employing strict filters (I knew
this about AS3320). AS3320 usually updates its filters weekly. 


To sum it up: the problem is not really within AS3320, but at the other
side not maintaining the IRR.

Andre
-- 
I respect faith, but doubt is what gets you an education.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
Url : http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20151126/a1f88edb/attachment.bin 


More information about the ipv6-ops mailing list