<div dir="ltr">Sent off to the right people LinkedIn<div><br></div><div>-Grant</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 21, 2014 at 3:34 PM, Andre Grueneberg <span dir="ltr"><<a href="mailto:list.ipv6ops@grueneberg.de" target="_blank">list.ipv6ops@grueneberg.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Thomas Schäfer wrote:<br>
> but <a href="http://www.linkedin.com" target="_blank">www.linkedin.com</a> has an AAAA-Record.<br>
> from home via DSL (Deutsche Telekom) I get this:<br>
> ping6 <a href="http://www.linkedin.com" target="_blank">www.linkedin.com</a><br>
> PING <a href="http://www.linkedin.com" target="_blank">www.linkedin.com</a>(2620:109:c007:102::5be1:f881) 56 data bytes<br>
> >From 2003:0:1803:8268::2 icmp_seq=3 Destination unreachable: No route<br>
> >From 2003:0:1803:8268::2 icmp_seq=7 Destination unreachable: No route<br>
</span><span class="">> Has anybody an idea? Can somebody confirm this problem by using a different<br>
> isp?<br>
<br>
</span>This might be caused by rather strict route filters based on IRR at<br>
AS3320 (DTAG). We also don't see this route via our AS3320 transit.<br>
<br>
I see the following pathes:<br>
... 1273 14413 197612<br>
... 1299 14413 197612<br>
... 6939 14413 197612<br>
<br>
$ whois -h <a href="http://whois.ra.net" target="_blank">whois.ra.net</a> AS-LINKEDIN<br>
as-set: AS-LINKEDIN<br>
...<br>
members: AS13443<br>
...<br>
<br>
Other IPv6 routes of LinkedIn are visible via AS3320:<br>
2620:109:c006::/48 <neigh> 10 100 0 E<br>
AS_PATH: 3320 2914 14413 55163<br>
2620:109:c00d::/48 <neigh> 10 100 0 E<br>
AS_PATH: 3320 2914 14413 20049<br>
<br>
Not feeding IRR DB fires back. You might want to ask LinkedIn to fix<br>
their entries.<br>
<span class="HOEnZb"><font color="#888888"><br>
Andre<br>
--<br>
Be nice to your kids. They'll choose your nursing home.<br>
</font></span></blockquote></div><br></div>