Mailing List Archive

Hi,

> 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
>
> v6.testmyipv6.com
>
> are not reachable from the network of Deutsche Telekom ( DSL, LTE, - no
> route to host)
Not only from there:

AS24940:
$ ping6 -c 1 v6.testmyipv6.com
PING v6.testmyipv6.com(2001:4830:2502:8001::a00:a) 56 data bytes
From ibr01-ve26.lndn01.occaid.net icmp_seq=1 Destination unreachable: No
route

--- v6.testmyipv6.com ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss

AS3209:
$ ping6 -c 1 v6.testmyipv6.com
PING v6.testmyipv6.com(2001:4830:2502:8001::a00:a) 56 data bytes
From ibr01-ve26.lndn01.occaid.net icmp_seq=1 Destination unreachable: No
route

--- v6.testmyipv6.com ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time

>>From some other hosts e.g. my workplace at DFN/LRZ it works, at least
> ping, at the moment port 80 seems to be down.
>
> Also http://ipv6-test.com/validate.php indicates that at least
> v6.testmyipv6.com is alive.
>
> Is somebody here, who could confirm or better fix the problems between
> these AS?
>
> Regards,
> Thomas
>
> PS: traceroutes from Deutsche Telekom (not ok) and DFN (ok) can be found
> here:
>
> https://telekomhilft.telekom.de/t5/Telefonie-Internet/Destination-unreachable-No-route/td-p/1523108/page/2

My traceroute stops always at

ibr01-ve26.lndn01.occaid.net (2001:7f8:4::7577:1)

Best regards
Holger

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.