Mailing List Archive

On 11/21/2014 15:09, Thomas Schäfer wrote:
>
> Has anybody an idea? Can somebody confirm this problem by using a different
> isp?
>
> Regards,
> Thomas

I can replicate the issue on one of my servers.

Box is in AS12876.

Relevant mtr:

inari.zombocloud.com | success | rc=0 >>
HOST: inari Loss% Snt Last Avg Best Wrst StDev
1.|-- 2001:bc8:2::1:212:1 20.0% 10 5.5 5.0 0.6 17.3 5.4
2.|-- 2001:bc8:0:1::49 0.0% 10 1.0 1.1 0.9 2.0 0.3
3.|-- prs-b7-link.telia.net 0.0% 10 1.0 0.9 0.9 1.0 0.0
4.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
--
staticsafe
https://staticsafe.ca

It works nicely from NZ (the ping time is typical), but
I'm seeing a different address:

C:\windows\system32>ping www.linkedin.com

Pinging pop-ela4-alpha.www.linkedin.com [2620:109:c00d:100::c765:a381] with 32 bytes of data:
Reply from 2620:109:c00d:100::c765:a381: time=201ms
Reply from 2620:109:c00d:100::c765:a381: time=210ms
Reply from 2620:109:c00d:100::c765:a381: time=200ms
Reply from 2620:109:c00d:100::c765:a381: time=200ms

Ping statistics for 2620:109:c00d:100::c765:a381:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 200ms, Maximum = 210ms, Average = 202ms

Regards
Brian




On 22/11/2014 10:49, staticsafe wrote:
> On 11/21/2014 15:09, Thomas Schäfer wrote:
>> Has anybody an idea? Can somebody confirm this problem by using a different
>> isp?
>>
>> Regards,
>> Thomas
>
> I can replicate the issue on one of my servers.
>
> Box is in AS12876.
>
> Relevant mtr:
>
> inari.zombocloud.com | success | rc=0 >>
> HOST: inari Loss% Snt Last Avg Best Wrst StDev
> 1.|-- 2001:bc8:2::1:212:1 20.0% 10 5.5 5.0 0.6 17.3 5.4
> 2.|-- 2001:bc8:0:1::49 0.0% 10 1.0 1.1 0.9 2.0 0.3
> 3.|-- prs-b7-link.telia.net 0.0% 10 1.0 0.9 0.9 1.0 0.0
> 4.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

Thomas Schäfer wrote:
> but www.linkedin.com has an AAAA-Record.
> from home via DSL (Deutsche Telekom) I get this:
> ping6 www.linkedin.com
> PING www.linkedin.com(2620:109:c007:102::5be1:f881) 56 data bytes
> >From 2003:0:1803:8268::2 icmp_seq=3 Destination unreachable: No route
> >From 2003:0:1803:8268::2 icmp_seq=7 Destination unreachable: No route
> Has anybody an idea? Can somebody confirm this problem by using a different
> isp?

This might be caused by rather strict route filters based on IRR at
AS3320 (DTAG). We also don't see this route via our AS3320 transit.

I see the following pathes:
... 1273 14413 197612
... 1299 14413 197612
... 6939 14413 197612

$ whois -h whois.ra.net AS-LINKEDIN
as-set: AS-LINKEDIN
...
members: AS13443
...

Other IPv6 routes of LinkedIn are visible via AS3320:
2620:109:c006::/48 <neigh> 10 100 0 E
AS_PATH: 3320 2914 14413 55163
2620:109:c00d::/48 <neigh> 10 100 0 E
AS_PATH: 3320 2914 14413 20049

Not feeding IRR DB fires back. You might want to ask LinkedIn to fix
their entries.

Andre
--
Be nice to your kids. They'll choose your nursing home.

Sent off to the right people LinkedIn

-Grant

On Fri, Nov 21, 2014 at 3:34 PM, Andre Grueneberg <
list.ipv6ops@grueneberg.de> wrote:

> Thomas Schäfer wrote:
> > but www.linkedin.com has an AAAA-Record.
> > from home via DSL (Deutsche Telekom) I get this:
> > ping6 www.linkedin.com
> > PING www.linkedin.com(2620:109:c007:102::5be1:f881) 56 data bytes
> > >From 2003:0:1803:8268::2 icmp_seq=3 Destination unreachable: No route
> > >From 2003:0:1803:8268::2 icmp_seq=7 Destination unreachable: No route
> > Has anybody an idea? Can somebody confirm this problem by using a
> different
> > isp?
>
> This might be caused by rather strict route filters based on IRR at
> AS3320 (DTAG). We also don't see this route via our AS3320 transit.
>
> I see the following pathes:
> ... 1273 14413 197612
> ... 1299 14413 197612
> ... 6939 14413 197612
>
> $ whois -h whois.ra.net AS-LINKEDIN
> as-set: AS-LINKEDIN
> ...
> members: AS13443
> ...
>
> Other IPv6 routes of LinkedIn are visible via AS3320:
> 2620:109:c006::/48 <neigh> 10 100 0 E
> AS_PATH: 3320 2914 14413 55163
> 2620:109:c00d::/48 <neigh> 10 100 0 E
> AS_PATH: 3320 2914 14413 20049
>
> Not feeding IRR DB fires back. You might want to ask LinkedIn to fix
> their entries.
>
> Andre
> --
> Be nice to your kids. They'll choose your nursing home.
>

We lost IPv6 connectivity to www.t-online.de 2:13 am US Central (20-11-2014). I had previously gotten that fixed by working with one of their peering staff, but when I contacted him about it yesterday he said something about engineering not liking his approach. So I suspect some kind of change was made.

Frank

-----Original Message-----
From: ipv6-ops-bounces+frnkblk=iname.com@lists.cluenet.de [mailto:ipv6-ops-bounces+frnkblk=iname.com@lists.cluenet.de] On Behalf Of Thomas Schäfer
Sent: Friday, November 21, 2014 2:10 PM
To: IPv6 Ops list
Subject: Routingproblems - Deutsche Telekom?

Hi,

today the "internetsociety" has anounced that linkedin has joined the World
IPv6 Launch Measurements Project. So far so good (marketing).

But I was confused by using still IPv4.

This company has more than one addresses.

de.linkedin.com has no AAAA-Record. Ok, shit happens.

but www.linkedin.com has an AAAA-Record.


from home via DSL (Deutsche Telekom) I get this:

ping6 www.linkedin.com
PING www.linkedin.com(2620:109:c007:102::5be1:f881) 56 data bytes
>From 2003:0:1803:8268::2 icmp_seq=3 Destination unreachable: No route
>From 2003:0:1803:8268::2 icmp_seq=7 Destination unreachable: No route
^C
--- www.linkedin.com ping statistics ---
8 packets transmitted, 0 received, +2 errors, 100% packet loss, time 16047ms

from work via LRZ/DFN I get this:

ping6 www.linkedin.com
PING www.linkedin.com(2620:109:c007:102::5be1:f881) 56 data bytes
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=1 ttl=47 time=50.4 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=2 ttl=47 time=50.2 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=3 ttl=47 time=50.2 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=4 ttl=47 time=50.2 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=5 ttl=47 time=50.3 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=6 ttl=47 time=50.1 ms
^C
--- www.linkedin.com ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5006ms
rtt min/avg/max/mdev = 50.199/50.293/50.446/0.158 ms

I found also some other problems in 26.... but they are not so prominent.

www.opus1.com
www.ipv6book.ca

Has anybody an idea? Can somebody confirm this problem by using a different
isp?

Regards,
Thomas

www.linkedin.com is an alias for pop-idb2-alpha.www.linkedin.com.
pop-idb2-alpha.www.linkedin.com has address 91.225.248.129
pop-idb2-alpha.www.linkedin.com has IPv6 address
2620:109:c007:102::5be1:f881


NetRange: 2620:109:C000:: - 2620:109:C00F:FFFF:FFFF:FFFF:FFFF:FFFF
CIDR: 2620:109:C000::/44
NetName: LINKEDIN
NetHandle: NET6-2620-109-C000-1
Parent: ARIN-V6-ENDUSER-BLOCK (NET6-2620-1)
NetType: Direct Assignment
OriginAS: AS20049
Organization: LinkedIn Corporation (LINKE-1)
RegDate: 2012-01-12
Updated: 2012-02-08
Ref: http://whois.arin.net/rest/net/NET6-2620-109-C000-1

bgp01.as48972.net# sh ipv6 bgp regexp _20049$
BGP table version is 0, local router ID is 95.130.232.2
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal,
r RIB-failure, S Stale, R Removed
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path
* 2620:109:c00d::/48
2001:1540:800:4000::2:1
90 0 16243 6939
14413 20049 i
* i 2a02:d28:5580:e:1000::221
90 0 5580 3356
14413 20049 i
*> 2a02:d28:5580:e:1000::b5
90 0 5580 3356
14413 20049 i

Total number of prefixes 1

ping6 www.linkedin.com
PING www.linkedin.com(2620:109:c007:102::5be1:f881) 56 data bytes
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=1 ttl=56 time=20.1 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=2 ttl=56 time=20.2 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=3 ttl=56 time=20.0 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=4 ttl=56 time=20.3 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=5 ttl=56 time=20.2 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=6 ttl=56 time=20.1 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=7 ttl=56 time=20.1 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=8 ttl=56 time=20.2 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=9 ttl=56 time=20.2 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=10 ttl=56 time=20.0 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=11 ttl=56 time=20.4 ms
^C
--- www.linkedin.com ping statistics ---
11 packets transmitted, 11 received, 0% packet loss, time 10013ms
rtt min/avg/max/mdev = 20.067/20.215/20.435/0.135 ms


On 11/21/2014 09:09 PM, Thomas Schäfer wrote:
> Hi,
>
> today the "internetsociety" has anounced that linkedin has joined the World
> IPv6 Launch Measurements Project. So far so good (marketing).
>
> But I was confused by using still IPv4.
>
> This company has more than one addresses.
>
> de.linkedin.com has no AAAA-Record. Ok, shit happens.
>
> but www.linkedin.com has an AAAA-Record.
>
>
> from home via DSL (Deutsche Telekom) I get this:
>
> ping6 www.linkedin.com
> PING www.linkedin.com(2620:109:c007:102::5be1:f881) 56 data bytes
> >From 2003:0:1803:8268::2 icmp_seq=3 Destination unreachable: No route
> >From 2003:0:1803:8268::2 icmp_seq=7 Destination unreachable: No route
> ^C
> --- www.linkedin.com ping statistics ---
> 8 packets transmitted, 0 received, +2 errors, 100% packet loss, time 16047ms
>
> from work via LRZ/DFN I get this:
>
> ping6 www.linkedin.com
> PING www.linkedin.com(2620:109:c007:102::5be1:f881) 56 data bytes
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=1 ttl=47 time=50.4 ms
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=2 ttl=47 time=50.2 ms
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=3 ttl=47 time=50.2 ms
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=4 ttl=47 time=50.2 ms
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=5 ttl=47 time=50.3 ms
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=6 ttl=47 time=50.1 ms
> ^C
> --- www.linkedin.com ping statistics ---
> 6 packets transmitted, 6 received, 0% packet loss, time 5006ms
> rtt min/avg/max/mdev = 50.199/50.293/50.446/0.158 ms
>
> I found also some other problems in 26.... but they are not so prominent.
>
> www.opus1.com
> www.ipv6book.ca
>
> Has anybody an idea? Can somebody confirm this problem by using a different
> isp?
>
> Regards,
> Thomas
>
>
>
>
>
>
>
>
>

Issue was already solved.

-Grant

On Sat, Nov 29, 2014 at 7:27 AM, Jan Hugo Prins <jhp@jhprins.org> wrote:

> www.linkedin.com is an alias for pop-idb2-alpha.www.linkedin.com.
> pop-idb2-alpha.www.linkedin.com has address 91.225.248.129
> pop-idb2-alpha.www.linkedin.com has IPv6 address
> 2620:109:c007:102::5be1:f881
>
>
> NetRange: 2620:109:C000:: - 2620:109:C00F:FFFF:FFFF:FFFF:FFFF:FFFF
> CIDR: 2620:109:C000::/44
> NetName: LINKEDIN
> NetHandle: NET6-2620-109-C000-1
> Parent: ARIN-V6-ENDUSER-BLOCK (NET6-2620-1)
> NetType: Direct Assignment
> OriginAS: AS20049
> Organization: LinkedIn Corporation (LINKE-1)
> RegDate: 2012-01-12
> Updated: 2012-02-08
> Ref: http://whois.arin.net/rest/net/NET6-2620-109-C000-1
>
> bgp01.as48972.net# sh ipv6 bgp regexp _20049$
> BGP table version is 0, local router ID is 95.130.232.2
> Status codes: s suppressed, d damped, h history, * valid, > best, i -
> internal,
> r RIB-failure, S Stale, R Removed
> Origin codes: i - IGP, e - EGP, ? - incomplete
>
> Network Next Hop Metric LocPrf Weight Path
> * 2620:109:c00d::/48
> 2001:1540:800:4000::2:1
> 90 0 16243 6939
> 14413 20049 i
> * i 2a02:d28:5580:e:1000::221
> 90 0 5580 3356
> 14413 20049 i
> *> 2a02:d28:5580:e:1000::b5
> 90 0 5580 3356
> 14413 20049 i
>
> Total number of prefixes 1
>
> ping6 www.linkedin.com
> PING www.linkedin.com(2620:109:c007:102::5be1:f881) 56 data bytes
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=1 ttl=56 time=20.1 ms
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=2 ttl=56 time=20.2 ms
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=3 ttl=56 time=20.0 ms
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=4 ttl=56 time=20.3 ms
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=5 ttl=56 time=20.2 ms
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=6 ttl=56 time=20.1 ms
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=7 ttl=56 time=20.1 ms
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=8 ttl=56 time=20.2 ms
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=9 ttl=56 time=20.2 ms
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=10 ttl=56 time=20.0 ms
> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=11 ttl=56 time=20.4 ms
> ^C
> --- www.linkedin.com ping statistics ---
> 11 packets transmitted, 11 received, 0% packet loss, time 10013ms
> rtt min/avg/max/mdev = 20.067/20.215/20.435/0.135 ms
>
>
>
> On 11/21/2014 09:09 PM, Thomas Schäfer wrote:
>
>> Hi,
>>
>> today the "internetsociety" has anounced that linkedin has joined the
>> World
>> IPv6 Launch Measurements Project. So far so good (marketing).
>>
>> But I was confused by using still IPv4.
>>
>> This company has more than one addresses.
>>
>> de.linkedin.com has no AAAA-Record. Ok, shit happens.
>>
>> but www.linkedin.com has an AAAA-Record.
>>
>>
>> from home via DSL (Deutsche Telekom) I get this:
>>
>> ping6 www.linkedin.com
>> PING www.linkedin.com(2620:109:c007:102::5be1:f881) 56 data bytes
>> >From 2003:0:1803:8268::2 icmp_seq=3 Destination unreachable: No route
>> >From 2003:0:1803:8268::2 icmp_seq=7 Destination unreachable: No route
>> ^C
>> --- www.linkedin.com ping statistics ---
>> 8 packets transmitted, 0 received, +2 errors, 100% packet loss, time
>> 16047ms
>>
>> from work via LRZ/DFN I get this:
>>
>> ping6 www.linkedin.com
>> PING www.linkedin.com(2620:109:c007:102::5be1:f881) 56 data bytes
>> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=1 ttl=47 time=50.4 ms
>> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=2 ttl=47 time=50.2 ms
>> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=3 ttl=47 time=50.2 ms
>> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=4 ttl=47 time=50.2 ms
>> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=5 ttl=47 time=50.3 ms
>> 64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=6 ttl=47 time=50.1 ms
>> ^C
>> --- www.linkedin.com ping statistics ---
>> 6 packets transmitted, 6 received, 0% packet loss, time 5006ms
>> rtt min/avg/max/mdev = 50.199/50.293/50.446/0.158 ms
>>
>> I found also some other problems in 26.... but they are not so prominent.
>>
>> www.opus1.com
>> www.ipv6book.ca
>>
>> Has anybody an idea? Can somebody confirm this problem by using a
>> different
>> isp?
>>
>> Regards,
>> Thomas
>>
>>
>>
>>
>>
>>
>>
>>
>>
>