|
Ticket ID: SIXXS #4240689 Ticket Status: Resolved PoP: (not applicable)
T58857 Can not ping 2a01:348:6:4aa::1
![[gb]](/s/countries/gb.gif) Shadow Hawkins on Saturday, 16 April 2011 20:44:10
I have read and followed the "Reporting Problems" section on the Contact page.
I am removing these five pre-filled lines to demonstrate that I really read it.
I am providing the full details as requested on the mentioned Contact page.
If I do not remove this, then please ignore this message as I didn't read it anyway.
------------------------------------------------------------------------------>8
I get the following error from a tcpdump:
ICMP gblon02.sixxs.net udp port 5072 unreachable, length 184
I suspect this is due to my server rebooting several times. I have swicthed of aiccu from starting up on a reboot and the server is now stable so if my tunnel has been disabled, can you please re-enable. I can ping the IPv4 tunnel end point and am not dropping any packets due to iptables.
Many thanks
Phil
GLONB tunnels not transfering IPV6 data for me
![[au]](/s/countries/au.gif) Shadow Hawkins on Saturday, 16 April 2011 10:56:07
Hi neither T22965 nor T39369 appear to be passing IPV6 for me.
Both sites can ping 77.75.104.126
IPv6 ping fails from Labertouche site to its point to point partner:
ping6 2a01:348:6:39f::1
PING6(56=40+8+8 bytes) 2a01:348:6:39f::2 --> 2a01:348:6:39f::1
^C
--- 2a01:348:6:39f::1 ping6 statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
From South Yarra site:
atum_29% /sbin/ping6 2a01:348:6:25e::1
PING6(56=40+8+8 bytes) 2a01:348:1fa::2 --> 2a01:348:6:25e::1
^C
--- 2a01:348:6:25e::1 ping6 statistics ---
7 packets transmitted, 0 packets received, 100.0% packet loss
From Labertouche site:
traceroute to 77.75.104.126 (77.75.104.126), 64 hops max, 40 byte packets
1 loop0.core2.smithst.dcsi.net.au (203.27.231.24) 56.003 ms 44.381 ms 28.374 ms
2 gi0-2-1.core1.smithst.dcsi.net.au (203.27.231.17) 45.134 ms 40.088 ms 30.496 ms
3 gi0-1.core1.yarragon2.aussiebb.net (202.142.143.149) 23.013 ms 36.025 ms 23.992 ms
4 gi0-2-37.core1.mel.aussiebb.net (202.142.143.73) 56.137 ms 32.320 ms 63.172 ms
5 vlan7.core1.portmel.aussiebb.net (180.150.0.113) 94.477 ms 216.821 ms 189.921 ms
6 gi5-1.bdr1.portmel.aussiebb.net (180.150.0.65) 292.330 ms 148.011 ms 280.451 ms
7 GigabitEthernet2-11.lon55.Melbourne.telstra.net (165.228.138.149) 169.555 ms 216.567 ms 85.203 ms
8 TenGigabitEthernet0-12-0-2.exi-core1.Melbourne.telstra.net (203.50.80.1) 39.797 ms 48.800 ms 21.565 ms
9 Bundle-Pos3.chw-core2.Sydney.telstra.net (203.50.11.14) 47.070 ms 46.987 ms 39.939 ms
10 Bundle-Ether1.oxf-gw2.Sydney.telstra.net (203.50.6.90) 43.908 ms 41.209 ms 48.610 ms
11 TenGigabitEthernetx-0.syd-core04.Sydney.reach.com (203.50.13.18) 42.107 ms 37.200 ms 101.613 ms
12 i-0-1-2-0.tlot-core01.bx.reach.com (202.84.140.6) 176.951 ms 197.160 ms 184.974 ms
13 i-1-1.eqla01.bi.reach.com (202.84.251.194) 187.916 ms 203.132 ms 239.636 ms
14 gblx-peer.eqla01.pr.reach.com (134.159.63.202) 185.051 ms 228.789 ms 182.934 ms
15 ge-1-1-4.rt0.sov.uk.goscomb.net (64.215.27.102) 326.959 ms 373.617 ms 335.131 ms
16 ge-1-3-1.rt0.the.uk.goscomb.net (93.89.94.153) 337.640 ms 352.059 ms 326.134 ms
17 ge-0-1-3.cs0.thw.uk.goscomb.net (93.89.91.14) 374.552 ms 402.493 ms 313.217 ms
18 gblon02.sixxs.net (77.75.104.126) 315.435 ms 323.546 ms 312.747 ms
From South Yarra site:
atum_30% traceroute 77.75.104.126
traceroute to 77.75.104.126 (77.75.104.126), 64 hops max, 40 byte packets
1 horus (10.100.0.1) 4.719 ms 0.317 ms 0.689 ms
2 nail.apcs.com.au (210.79.16.254) 57.175 ms 50.147 ms 48.502 ms
3 gi0-3-1.cor1.syd1.wip.net.au (210.79.16.82) 49.743 ms 50.707 ms 50.009 ms
4 202.183.118.66 (202.183.118.66) 49.530 ms 49.803 ms 50.484 ms
5 p151-ihsihs-osii-o.syd-core.iseek.com.au (59.154.20.9) 50.979 ms 50.662 ms 49.991 ms
6 67.17.192.141 (67.17.192.141) 208.676 ms 208.137 ms 209.445 ms
7 ge-1-1-4.rt0.sov.uk.goscomb.net (64.215.27.102) 337.234 ms 337.233 ms 342.478 ms
8 ge-1-3-1.rt0.the.uk.goscomb.net (93.89.94.153) 336.264 ms 337.997 ms 336.756 ms
9 ge-0-1-3.cs0.thw.uk.goscomb.net (93.89.91.14) 337.594 ms 337.653 ms 336.527 ms
10 gblon02.sixxs.net (77.75.104.126) 336.324 ms 337.677 ms 338.015 ms
Labertouche config
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1280
tunnel inet 203.147.99.130 --> 77.75.104.126
inet6 fe80::260:b0ff:feb5:a53a%gif0 prefixlen 64 scopeid 0x7
inet6 2a01:348:6:39f::2 --> 2a01:348:6:39f::1 prefixlen 128
Many Thanks for your assistance
Maurice
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Saturday, 16 April 2011 11:27:39
nic handle: JSG4-SIXXS
tunnel: T18377
I appear to be suffering the same problem with gblon2. Tunnel terminates on a cisco router which has seen no changes for several weeks. it appears the tunnel stopped responding at some time between 16/4/11 00:00 BST and 16/4/11 09:00 BST.
tunnel shows as up and the ipv4 endpoint is pingable
LAWGateway#sh ipv6 int
Tunnel0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::5220:5658
No Virtual link-local address(es):
Description: IPv6 tunnel to SixXS
Global unicast address(es):
2A01:348:6:16B::2, subnet is 2A01:348:6:16B::/64
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF00:2
FF02::1:FF20:5658
MTU is 1480 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ICMP unreachables are sent
Input features: Access List
Inbound access list deny-sourcerouted
ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds (using 32416)
Hosts use stateless autoconfig for addresses.
LAWGateway#ping 77.75.104.126
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 77.75.104.126, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/14/16 ms
LAWGateway#trace 77.75.104.126
Type escape sequence to abort.
Tracing the route to 77.75.104.126
1 10.36.0.1 12 msec 8 msec 8 msec
2 195.188.230.225 8 msec 8 msec 8 msec
3 195.188.230.69 8 msec 8 msec 12 msec
4 80.1.241.9 8 msec 8 msec 20 msec
5 213.105.175.157 24 msec 12 msec 8 msec
6 213.105.172.234 16 msec 12 msec 16 msec
7 213.105.159.50 12 msec 16 msec 12 msec
8 62.253.185.74 16 msec 12 msec 12 msec
9 195.66.226.226 16 msec 20 msec 16 msec
10 93.89.94.153 16 msec 16 msec 20 msec
11 93.89.91.14 16 msec 16 msec 16 msec
12 77.75.104.126 16 msec 16 msec 20 msec
LAWGateway#
however I cannot ping the ipv6 endpoint or route beyond it
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2A01:348:6:16B::1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
LAWGateway#sh ipv6 route
IPv6 Routing Table - Default - 8 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, M - MIPv6, R - RIP, D - EIGRP
EX - EIGRP external
O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
S 2000::/3 [1/0]
via 2A01:348:6:16B::1
C 2A01:348:6:16B::/64 [0/0]
via Tunnel0, directly connected
L 2A01:348:6:16B::2/128 [0/0]
via Tunnel0, receive
C 2A01:348:19E:2::/64 [0/0]
via Vlan2, directly connected
L 2A01:348:19E:2::1/128 [0/0]
via Vlan2, receive
C 2A01:348:19E:42::/64 [0/0]
via Vlan1, directly connected
L 2A01:348:19E:42::1/128 [0/0]
via Vlan1, receive
L FF00::/8 [0/0]
via Null0, receive
getting someone to do a traceroute from out on the net inwards shows the traffic getting to goscombe.net but going no furthur.
traceroute to 2A01:348:6:16B::2 (2a01:348:6:16b::2) from 2001:470:1f08:17fe::2, 30 hops max, 16 byte packets
1 2001:470:1f08:17fe::1 (2001:470:1f08:17fe::1) 9.27 ms 8.938 ms 8.478 ms
2 gige-g4-6.core1.lon1.he.net (2001:470:0:67::1) 5.917 ms 9.054 ms 1.461 ms
3 ae1.rt0.the.uk.goscomb.net (2001:7f8:4::999e:1) 1.157 ms 1.411 ms 1.233 ms
4 ge-0-1-3.cs0.thw.uk.goscomb.net (2a01:348::27:1:1) 2.202 ms 1.916 ms 1.413 ms
5 * * *
running a debug ipv6 packet shows the traffic being forwarded out of the tunnel but no response
<191>2566: Apr 16 09:23:19.481: IPv6: Looking up 2A01:348:6:16B::1 [Source ::] in FIB192.168.42.116/04 10:22:02.074
<191>2567: Apr 16 09:23:19.481: IPv6: FIB lookup for 2A01:348:6:16B::1 succeeded. if=Tunnel0, nexthop 2A01:348:6:16B::1192.168.42.116/04 10:22:02.074
<191>2568: Apr 16 09:23:19.481: IPv6-Sas: SAS picked source 2A01:348:6:16B::2 for 2A01:348:6:16B::1 (Tunnel0)192.168.42.116/04 10:22:02.074
<191>2569: Apr 16 09:23:19.481: IPV6: source 2A01:348:6:16B::2 (local)192.168.42.116/04 10:22:02.074
<191>2570: Apr 16 09:23:19.481: dest 2A01:348:6:16B::1 (Tunnel0)192.168.42.116/04 10:22:02.074
<191>2571: Apr 16 09:23:19.481: traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, originating192.168.42.116/04 10:22:02.074
<191>2572: Apr 16 09:23:19.481: IPv6-Fwd: Sending on Tunnel0192.168.42.116/04 10:22:02.074
There is no firewalling for protocol 41 or for the pop endpoint address.
Thanks for any insight you can offer
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Saturday, 16 April 2011 11:48:42
My tunnel is up, but there is no IPv6 routing going on. (Tunnel T40057).
I can ping my local endpoint (2a01:348:6:3a9::1 but I can't ping my remote endpoint 2a01:348:6:3a9::2)
I can't even ping the remote endpoint via another server (I have a hosted server on Goscomb's network, but it can't ping either end of my tunnel either!). So it appears to be a network issue at Goscomb.
Looking at my tunnel stats, my tunnel went from 0% packet loss to 100% packet loss at around 7am BST.
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Saturday, 16 April 2011 11:52:01
Sorry, brain freeze - got those the wrong way around - my local end is ::2, which I can ping from my internal network, but not from outside.
PoP end is ::2, which I can't ping from my internal network even though the tunnel is up, and I can't ping the ::2 end from a remote server also on Goscomb's network.
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Saturday, 16 April 2011 12:09:21
Hi,
I have the same problem since 7AM BST on 16/04/2011, setup details as follows:
Tunnel - T50825
Subnet - R22685
This is a static setup ending on a Cisco router with no untested config changes
BRM-DMZ#trace 2A01:348:6:431::1
Type escape sequence to abort.
Tracing the route to gw-1074.lon-02.gb.sixxs.net (2A01:348:6:431::1)
1 * * *
2 * * *
...
29 * * *
30 * * *
BRM-DMZ#
BRM-DMZ#trace 77.75.104.126
Type escape sequence to abort.
Tracing the route to gblon02.sixxs.net (77.75.104.126)
1 10.42.64.1 8 msec 8 msec 24 msec
2 sand-geam-1a-v15.network.virginmedia.net (62.30.254.161) 16 msec 32 msec 12 msec
3 wolv-core-1a-tenge94-487.network.virginmedia.net (62.30.254.57) 16 msec 16 msec 16 msec
4 manc-bb-1a-ae7-0.network.virginmedia.net (212.43.163.241) 16 msec 24 msec 16 msec
5 brnt-bb-1b-ae1-0.network.virginmedia.net (212.43.163.86) 32 msec 16 msec 20 msec
6 brnt-tmr-1-ae5-0.network.virginmedia.net (213.105.159.50) 16 msec 24 msec 20 msec
7 telc-ic-1-as0-0.network.virginmedia.net (62.253.185.74) 28 msec 16 msec 20 msec
8 ae1.rt0.sov.uk.goscomb.net (195.66.226.226) 24 msec 20 msec 28 msec
9 ge-1-3-1.rt0.the.uk.goscomb.net (93.89.94.153) 40 msec 60 msec 36 msec
10 ge-0-1-3.cs0.thw.uk.goscomb.net (93.89.91.14) 28 msec 24 msec 28 msec
11 gblon02.sixxs.net (77.75.104.126) 20 msec 20 msec 24 msec
BRM-DMZ#
BRM-DMZ#sho ip int tun 0
Tunnel0 is up, line protocol is up
Internet protocol processing disabled
BRM-DMZ#
BRM-DMZ#sho ipv6 route
IPv6 Routing Table - 12 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
S ::/0 [1/0]
via 2A01:348:6:431::1
C 2A01:348:6:431::/64 [0/0]
via ::, Tunnel0
L 2A01:348:6:431::2/128 [0/0]
via ::, Tunnel0
C 2A01:348:287:201::/64 [0/0]
via ::, Loopback201
L 2A01:348:287:201::1/128 [0/0]
via ::, Loopback201
C 2A01:348:287:202::/64 [0/0]
via ::, Loopback202
L 2A01:348:287:202::1/128 [0/0]
via ::, Loopback202
C 2A01:348:287:203::/64 [0/0]
via ::, Vlan30
L 2A01:348:287:203::1/128 [0/0]
via ::, Vlan30
LC FC00::1/128 [0/0]
via ::, Loopback0
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0
BRM-DMZ#
BRM-DMZ#sho ipv6 int tun 0
Tunnel0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::5225:6967
Description: The Dark Passage
Global unicast address(es):
2A01:348:6:431::2, subnet is 2A01:348:6:431::/64
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF00:2
FF02::1:FF25:6967
MTU is 1280 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
Input features: ACL
Output features: ACL
Inbound access list TUNNEL_V6_IN
Outgoing access list TUNNEL_V6_OUT
ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds
Hosts use stateless autoconfig for addresses.
BRM-DMZ#
BRM-DMZ#sho ipv6 acc
IPv6 access list TUNNEL_V6_IN
permit icmp any host 2A01:348:6:431::2 (590 matches) sequence 10
permit icmp host 2A01:348:6:431::1 any sequence 20
evaluate TUNNEL_V6_RETURNING sequence 40
IPv6 access list TUNNEL_V6_OUT
permit ipv6 any any reflect TUNNEL_V6_RETURNING (13277 matches) sequence 50
IPv6 access list TUNNEL_V6_RETURNING (reflexive) (per-user)
permit udp host 2001:0:4137:9E76:2098:FBE7:AABE:D828 eq 52070 host 2A01:348:287:203:534:F14A:9A25:9F7B eq 22299 timeout 300 (time left 244) sequence 574
permit tcp host 2001:0:4137:9E76:2098:FBE7:AABE:D828 eq 52070 host 2A01:348:287:203:534:F14A:9A25:9F7B eq 1722 timeout 300 (time left 250) sequence 679
BRM-DMZ#
BRM-DMZ#sho run int tun 0
Building configuration...
Current configuration : 311 bytes
!
interface Tunnel0
description The Dark Passage
no ip address
ipv6 address 2A01:348:6:431::2/64
ipv6 enable
ipv6 traffic-filter TUNNEL_V6_IN in
ipv6 traffic-filter TUNNEL_V6_OUT out
ipv6 mtu 1280
ipv6 router isis
tunnel source 82.37.105.103
tunnel destination 77.75.104.126
tunnel mode ipv6ip
end
BRM-DMZ#
You can contact me on: ebay_noob(at)yahoo.com
Thanks for all help.
Chris.
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Saturday, 16 April 2011 16:52:38
Confirm also for tunnel T47821
Packet loss went to (almost) 80% at 7am then at 9am to 100%
Can't ping other end of link.
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Saturday, 16 April 2011 21:14:53
FWIW, I'm also seeing this on tunnel T24006.
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Saturday, 16 April 2011 21:51:57
Same problem here unfortunately (T54901), graphs show packet loss of 80% starting at 7am, with 100% from 8am. No traffic is routable over the tunnel, and
This is a static tunnel ending on a Cisco 877 running IOS 15.0(1)XA5 with no recent changes being made (other than a reload earlier today [approx 4:25pm]).
As others have reported, the IPv4 endpoint is pingable, IPv6 endpoint is not
Traceroute:
tachyon#traceroute 77.75.104.126
Type escape sequence to abort.
Tracing the route to gblon02.sixxs.net (77.75.104.126)
1 losubs.subs.dsl1.wh-man.zen.net.uk (62.3.87.145) 36 msec 32 msec 36 msec
2 ge-2-1-0-160.cr1.wh-man.zen.co.uk (62.3.87.161) 36 msec 32 msec 36 msec
3 ge-3-0-0-0.cr2.th-lon.zen.net.uk (62.3.80.45) 40 msec 40 msec 40 msec
4 ae1.rt0.the.uk.goscomb.net (195.66.224.226) 36 msec 40 msec 44 msec
5 ge-0-1-3.cs0.thw.uk.goscomb.net (93.89.91.14) 40 msec 40 msec 36 msec
6 gblon02.sixxs.net (77.75.104.126) 40 msec 40 msec 40 msec
IPv6 Traceroute (to PoP):
tachyon#traceroute 2a01:348:6:47c::1
Type escape sequence to abort.
Tracing the route to gw-1149.lon-02.gb.sixxs.net (2A01:348:6:47C::1)
1 * * *
2 * *
Traceroute to the PoP from an external server (running on HE IPv6):
mde@reid:~$ traceroute6 -n 2a01:348:6:47c::1
traceroute to 2a01:348:6:47c::2 (2a01:348:6:47c::2), 30 hops max, 80 byte packets
1 2001:470:1f08:92a::1 7.238 ms 12.942 ms 18.302 ms
2 2001:470:0:67::1 28.273 ms 28.254 ms 28.225 ms
3 2001:7f8:4::999e:1 19.334 ms 19.316 ms 19.293 ms
4 2a01:348::27:1:1 19.641 ms 19.607 ms 19.710 ms
5 * * *
6 * * *
tachyon#sh ipv6 int tun0
Tunnel0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::D99B:FB86
No Virtual link-local address(es):
Description: IPv6 uplink to SixXS
Global unicast address(es):
2A01:348:6:47C::2, subnet is 2A01:348:6:47C::/64
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF00:2
FF02::1:FF9B:FB86
MTU is 1280 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ICMP unreachables are sent
Input features: Common pak subblock Access List
Output features: Firewall Inspection
Inbound access list firewallv6
Outbound Inspection Rule firewallv6
ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds (using 30000)
Hosts use stateless autoconfig for addresses.
tachyon#sh ipv6 route
IPv6 Routing Table - default - 7 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, M - MIPv6, R - RIP, D - EIGRP
EX - EIGRP external, ND - Neighbor Discovery
O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
S ::/0 [1/0]
via Tunnel0, directly connected
S 2000::/3 [1/0]
via 2A01:348:6:47C::1
C 2A01:348:6:47C::/64 [0/0]
via Tunnel0, directly connected
L 2A01:348:6:47C::2/128 [0/0]
via Tunnel0, receive
C 2A01:348:2A5:666::/64 [0/0]
via Vlan1, directly connected
L 2A01:348:2A5:666:21D:A2FF:FEC2:428A/128 [0/0]
via Vlan1, receive
L FF00::/8 [0/0]
via Null0, receive
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Saturday, 16 April 2011 22:21:04
IPv6 outage on tunnel T40625 too.
gblon02 endpoint pings OK via IPv4, "address unreachable" via IPv6.
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Saturday, 16 April 2011 23:01:39
I am also experiencing a lack of IPv6 routing on tunnel T57913.
When trying to ping the remote endpoint (2a01:348:6:49f::1) tcpdump shows:
21:00:39.584078 IP 88.208.247.57 > 77.75.104.126: IP6 2a01:348:6:49f::2 > 2a01:348:6:49f::1: ICMP6, echo request, seq 1, length 64
21:00:39.589422 IP 77.75.104.126 > 88.208.247.57: ICMP 77.75.104.126 protocol 41 unreachable, length 132
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Sunday, 17 April 2011 00:11:03
Can also confirm that I can't reach the IPv6 Internet via my tunnel but tunnel creates fine and I can ping both the tic server and the PoP IPv4 address.
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Sunday, 17 April 2011 00:17:02
root@casper:~# ifconfig sixxs
sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: 2a01:348:6:48a::2/64 Scope:Global
inet6 addr: fe80::48:6:48a:2/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1428 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
root@casper:~# traceroute 77.75.104.126
traceroute to 77.75.104.126 (77.75.104.126), 30 hops max, 60 byte packets
1 192.168.2.1 (192.168.2.1) 1.833 ms 2.503 ms 2.842 ms
2 192.168.0.1 (192.168.0.1) 6.961 ms 7.192 ms 7.353 ms
3 cr1.nsnth.uk.easynet.net (87.87.254.95) 87.398 ms 87.873 ms 87.854 ms
4 ip-87-87-169-1.easynet.co.uk (87.87.169.1) 85.841 ms 85.680 ms 84.317 ms
5 89.200.131.191 (89.200.131.191) 105.323 ms 106.117 ms 106.609 ms
6 ae1.rt0.the.uk.goscomb.net (195.66.224.226) 106.823 ms 104.557 ms 105.788 ms
7 ge-0-1-3.cs0.thw.uk.goscomb.net (93.89.91.14) 105.695 ms 248.676 ms 269.272 ms
8 gblon02.sixxs.net (77.75.104.126) 266.792 ms * *
root@casper:~# traceroute tic.sixxs.net
traceroute to tic.sixxs.net (213.204.193.2), 30 hops max, 60 byte packets
1 192.168.2.1 (192.168.2.1) 2.505 ms 2.355 ms 2.248 ms
2 192.168.0.1 (192.168.0.1) 6.920 ms 7.308 ms 7.211 ms
3 cr1.nsnth.uk.easynet.net (87.87.254.95) 173.242 ms 173.172 ms 174.800 ms
4 ip-87-87-169-1.easynet.co.uk (87.87.169.1) 170.008 ms 170.885 ms 171.932 ms
5 89.200.131.187 (89.200.131.187) 191.875 ms 192.155 ms 192.343 ms
6 bu4.gr10.telon.uk.easynet.net (89.200.135.145) 192.517 ms 44.860 ms 45.134 ms
7 te1-0-0.gr10.saams.nl.easynet.net (87.86.77.60) 52.241 ms 109.330 ms 109.675 ms
8 amsix.pe01.gs.network.scarlet.nl (195.69.144.105) 112.133 ms 111.989 ms 112.678 ms
9 ge-1-3-0.pe01.intx.network.scarlet.nl (213.204.226.130) 113.494 ms 114.127 ms 114.923 ms
10 broker04.ams.nl.sixxs.net (213.204.193.2) 115.750 ms 118.577 ms 114.584 ms
root@casper:~# ping6 2a01:348:6:48a::1 -c 3
PING 2a01:348:6:48a::1(2a01:348:6:48a::1) 56 data bytes
--- 2a01:348:6:48a::1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2007ms
This is for tunnel T55781.
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Sunday, 17 April 2011 00:44:11
Hi guys,
There are already numerous other detailed reports demonstrating that gblon2 PoP is having serious problems. This report is intended more as a "+1" to indicate another person experiencing what appears to be the same issue.
I will provide the full troubleshooting checklist data if really necessary, but given the number of detailed reports already made, it would seem to be unjustfied to go to the trouble of doing that at this point.
Instead, here is a brief summary of the symptoms I am seeing.
I have two tunnels to gblon2, one AYIYA to a laptop (T60457), one static to a co-lo Xen VPS (TT60489).
Just noticed the AYIYA one not working on the laptop. Checked the static one and that is not working either.
In both cases the configuration has not been changed on my end.
In both cases I can ping the remote IPv4 endpoint (77.75.104.126) successfully.
In both cases I can ping my local IPv6 endpoint, but cannot get a ping reply from the remote IPv6 endpoint.
Regards,
Bill
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Sunday, 17 April 2011 01:16:13
Perhaps some further diagnostically helpful information, the endpoint at 77.75.104.126 is returning ICMP type 3, code 2: protocol unreachable for tunnelled packets.
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Sunday, 17 April 2011 08:51:08
I'm also seeing this problem (not providing all the diagnostics as it looks like that's been done enough). I wonder based on other posters comments as to the time this started happening if it is in some way related to http://www.goscomb.net/support/status/228 ?
GLONB tunnels not transfering IPV6 data for me
![[us]](/s/countries/us.gif) Shadow Hawkins on Sunday, 17 April 2011 09:10:03
I have read and followed the "Reporting Problems" section on the Contact page.
I am removing these five pre-filled lines to demonstrate that I really read it.
I am providing the full details as requested on the mentioned Contact page.
If I do not remove this, then please ignore this message as I didn't read it anyway.
------------------------------------------------------------------------------>8
Same issues here for both my tunnels using gblon2.
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Sunday, 17 April 2011 10:01:09
I have read and followed the "Reporting Problems" section on the Contact page.
I am removing these five pre-filled lines to demonstrate that I really read it.
I am providing the full details as requested on the mentioned Contact page.
If I do not remove this, then please ignore this message as I didn't read it anyway.
------------------------------------------------------------------------------>8
My tunnel is up, but has not passed any traffic since some time on the 16th April according to the sixxs graphs. Also 100% packet loss for the keep alive ping.
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Sunday, 17 April 2011 09:52:16
Same issue 2a01:348:6:4c::2 [me] <=> 2a01:348:6:4c::1 [gblon02] (T13202), traced problem at 17-Apr-2011 08:12 BST but there were IPv6 issues present yesterday.
David
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Sunday, 17 April 2011 11:31:17
Confirmed also for tunnel T24146. IPv6 router reporting next hop on 2a01:348:6:29a::2 --> 2a01:348:6:29a::1 not available.
traceroute to 77.75.104.126 (77.75.104.126), 30 hops max, 60 byte packets
1 gateway.home.cheeky-chimps.net (192.168.16.254) 0.278 ms 0.164 ms 0.145 ms
2 * * *
3 * * *
4 ae1.rt0.the.uk.goscomb.net (195.66.224.226) 11.924 ms 11.884 ms 12.961 ms
5 ge-0-1-3.cs0.thw.uk.goscomb.net (93.89.91.14) 13.260 ms 13.411 ms 14.334 ms
6 gblon02.sixxs.net (77.75.104.126) 14.315 ms 11.240 ms 11.908 ms
traceroute to ping0.ja.net (2001:630::44), 30 hops max, 80 byte packets
1 gateway.home.cheeky-chimps.net (2a01:348:11b:beef::fe) 0.212 ms 0.091 ms 0.092 ms
2 gateway.home.cheeky-chimps.net (2a01:348:11b:beef::fe) 0.143 ms !H 0.147 ms !H 0.130 ms !H
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Sunday, 17 April 2011 14:44:29
I have just spoken with Goscomb, and they have no outages that would result in this happening. I can confirm that at this time, after restarting AICCU once again, I still have no IPv6 connectivity to the IPv6 Internet. Apparently problem is with SiXXS, but http://www.sixxs.net/pops/status/ shows it as up and http://www.sixxs.net/misc/latency/ shows that whilst some of the PoPs have made a jump up in the latency for pinging gblon2, it's still reachable via IPv6.
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Sunday, 17 April 2011 21:17:05
I have just tried again, and now IPv6 routing via gblon02 is now working for me.
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Sunday, 17 April 2011 22:04:23
Confirmed working here too:
traceroute to ping0.ja.net (2001:630::44), 30 hops max, 80 byte packets
1 gateway.home.cheeky-chimps.net (2a01:348:11b:beef::fe) 0.214 ms 0.099 ms 0.091 ms
2 gw-667.lon-02.gb.sixxs.net (2a01:348:6:29a::1) 9.138 ms 9.268 ms 10.391 ms
3 ge-0-0-5-20.cs0.thw.uk.goscomb.net (2a01:348:0:4:0:3:0:1) 12.278 ms 12.456 ms 13.605 ms
4 ge-0-0-20.cs0.the.uk.goscomb.net (2a01:348::27:0:1) 19.530 ms 19.973 ms 19.952 ms
5 linx-gw1.ja.net (2001:7f8:4::312:1) 17.784 ms 17.892 ms 19.870 ms
6 ae1.lond-sbr4.ja.net (2001:630:0:10::151) 19.850 ms 9.603 ms 10.135 ms
7 as1.read-sbr1.ja.net (2001:630:0:10::91) 12.010 ms 84.087 ms 83.999 ms
8 2001:630:0:10::10e (2001:630:0:10::10e) 13.428 ms 14.470 ms 15.842 ms
9 2001:630::44 (2001:630::44) 16.484 ms 17.626 ms 18.268 ms
Thanks.
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Sunday, 17 April 2011 23:47:45
I have just tested again and it all seems to be working now for me too.
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Sunday, 17 April 2011 23:49:42
Would anyone like to provide what happened and what was done to fix it being it was down for 24 hours more?
GLONB tunnels not transfering IPV6 data for me
Shadow Hawkins on Monday, 18 April 2011 02:16:53
Back up for me as well.
I would be interested in knowing what the problem was.
[and why it never changed to confirmed]
T58857 Can not ping 2a01:348:6:4aa::1
Shadow Hawkins on Saturday, 16 April 2011 22:38:01
Hi Phil,
Your issues it being seen by others on the Goscomb POP - see ticket 4230821.
Mathew
T58857 Can not ping 2a01:348:6:4aa::1
Shadow Hawkins on Saturday, 16 April 2011 23:50:16
I have read and followed the "Reporting Problems" section on the Contact page.
I am removing these five pre-filled lines to demonstrate that I really read it.
I am providing the full details as requested on the mentioned Contact page.
If I do not remove this, then please ignore this message as I didn't read it anyway.
------------------------------------------------------------------------------>8
many thanks for your feedback.
Loss of IPv6 connectivity
Shadow Hawkins on Sunday, 17 April 2011 10:48:00
Tunnel: T60681
I no longer have IPv6 connectivity through the above mentioned tunnel. It disappeared at 06:27 on 16th April and has not yet returned.
Thanks,
Tim.
Loss of IPv6 connectivity
Shadow Hawkins on Sunday, 17 April 2011 11:01:26
This is a duplicate of ticket #4230821
Loss of IPv6 connectivity
Shadow Hawkins on Monday, 18 April 2011 07:48:30
Connectivity returned 19:22 17th April.
State change: resolved
The state of this ticket has been changed to resolved
|
![[ch]](/s/countries/ch.gif)
on Monday, 18 April 2011 20:17:19
Posting is only allowed when you are