|
Ticket ID: SIXXS #4902393 Ticket Status: User PoP: nlhaa01 - Leaseweb B.V. (Haarlem)
'local' routing problems
Shadow Hawkins on Thursday, 09 June 2011 03:13:06
There is an issue with "internal" routing on this location.
We have a few servers in Evoswitch with Leaseweb running on our own IPv6 range: 2a02:cc8::/32 (Leaseweb provides all routing).
There is no traffic flowing to this IPv6 range, all traffic stops on a router, all other traffic works without any problems.
All went dead around 11:30 08-jun-2011..
Kind regards,
Robin Waarts
# ping6 www.internettoday.nl
PING www.internettoday.nl(2a02:cc8::99:16) 56 data bytes
From te9-2.sr8.evo.leaseweb.net icmp_seq=1 Destination unreachable: Address unreachable
From be25.crs.tc2.leaseweb.net icmp_seq=5 Destination unreachable: Address unreachable
From be25.crs.tc2.leaseweb.net icmp_seq=6 Destination unreachable: Address unreachable
From be25.crs.tc2.leaseweb.net icmp_seq=7 Destination unreachable: Address unreachable
From be25.crs.tc2.leaseweb.net icmp_seq=8 Destination unreachable: Address unreachable
From be25.crs.tc2.leaseweb.net icmp_seq=9 Destination unreachable: Address unreachable
From te9-2.sr8.evo.leaseweb.net icmp_seq=14 Destination unreachable: Address unreachable
traceroute to www.internettoday.nl (2a02:cc8::99:16), 30 hops max, 80 byte packets
1 2001:1af8:febb:1234::1 (2001:1af8:febb:1234::1) 0.335 ms 0.604 ms 0.597 ms
2 gw-644.haa-01.nl.sixxs.net (2001:1af8:fe00:283::1) 16.740 ms 17.766 ms 17.944 ms
3 2001:1af8:4050::1 (2001:1af8:4050::1) 18.127 ms 18.305 ms 18.687 ms
4 be25.crs.tc2.leaseweb.net (2001:1af8::3d) 18.865 ms 19.048 ms 23.475 ms
5 te9-2.sr8.evo.leaseweb.net (2001:1af8::4e) 25.252 ms 26.234 ms *
6 te9-2.sr8.evo.leaseweb.net (2001:1af8::4e) 3023.681 ms !H * *
traceroute to www.internettoday.nl (2a02:cc8::99:16), 30 hops max, 80 byte packets
1 2001:1af8:febb:1234::1 (2001:1af8:febb:1234::1) 0.328 ms 0.544 ms 0.537 ms
2 gw-644.haa-01.nl.sixxs.net (2001:1af8:fe00:283::1) 20.226 ms 21.391 ms 21.580 ms
3 2001:1af8:4050::1 (2001:1af8:4050::1) 162.773 ms 163.858 ms 164.031 ms
4 be25.crs.tc2.leaseweb.net (2001:1af8::3d) 23.443 ms 24.825 ms 25.201 ms
5 te9-2.sr8.evo.leaseweb.net (2001:1af8::4e) 40.811 ms 41.842 ms 42.168 ms
6 * * *
traceroute to www.internettoday.nl (2a02:cc8::99:16), 30 hops max, 80 byte packets
1 2001:1af8:febb:1234::1 (2001:1af8:febb:1234::1) 0.302 ms 0.415 ms 1.104 ms
2 gw-644.haa-01.nl.sixxs.net (2001:1af8:fe00:283::1) 11.855 ms 16.431 ms 17.407 ms
3 2001:1af8:4050::1 (2001:1af8:4050::1) 18.444 ms 18.626 ms 18.806 ms
4 * * *
PING ns4.satserver.nl(2001:470:937a::2) 56 data bytes
64 bytes from 2001:470:937a::2: icmp_seq=1 ttl=58 time=40.9 ms
64 bytes from 2001:470:937a::2: icmp_seq=2 ttl=58 time=39.5 ms
64 bytes from 2001:470:937a::2: icmp_seq=3 ttl=58 time=39.3 ms
64 bytes from 2001:470:937a::2: icmp_seq=4 ttl=58 time=40.3 ms
PING ipv6.google.com(2a00:1450:8001::68) 56 data bytes
64 bytes from 2a00:1450:8001::68: icmp_seq=1 ttl=55 time=37.0 ms
64 bytes from 2a00:1450:8001::68: icmp_seq=2 ttl=55 time=35.9 ms
64 bytes from 2a00:1450:8001::68: icmp_seq=3 ttl=55 time=37.1 ms
64 bytes from 2a00:1450:8001::68: icmp_seq=4 ttl=55 time=39.7 ms
Other location running over a HE tunnel:
ns4:~# traceroute6 www.internettoday.nl
traceroute to www.internettoday.nl (2a02:cc8::99:16), 30 hops max, 80 byte packets
1 robinw-4.tunnel.tserv5.lon1.ipv6.he.net (2001:470:1f08:1bb::1) 23.096 ms 28.161 ms 22.462 ms
2 gige-g4-6.core1.lon1.he.net (2001:470:0:67::1) 29.046 ms 29.270 ms 29.307 ms
3 2001:7f8:4::3f89:1 (2001:7f8:4::3f89:1) 42.475 ms 41.619 ms 42.454 ms
4 te9-2.sr7.evo.leaseweb.net (2001:1af8::12) 41.627 ms 41.865 ms 41.859 ms
5 today.satserver.nl (2a02:cc8::99:16) 41.849 ms 40.927 ms 41.826 ms
State change: user
![]()
The state of this ticket has been changed to user
'local' routing problems
SixXS has nothing to do with those prefixes, please contact the relevant ISPs directly.
'local' routing problems
Shadow Hawkins on Thursday, 09 June 2011 03:34:39
Thanks,
Problem again reported to Leaseweb..
'local' routing problems
Shadow Hawkins on Friday, 10 June 2011 14:06:05
Status update..
There where some routing issues at Leaseweb, this dropped all traffic from SixXS to the "inside" the network..
Solved..
|