Ticket ID: SIXXS #1289281 Ticket Status: User PoP: gblon02 - Goscomb Technologies (London)
Connectivity issues via gblon02
Shadow Hawkins on Monday, 07 December 2009 11:52:37
Hi,
I seem to be experiencing intermittent issues via gblon02.
I received an email from the tunnel robot saying my tunnel had been down for a number of days. Bouncing the tunnel a few times allowed me to ping out again, but it seems that traceroutes are being blocked at the first hop:-
mordor:~# traceroute6 noc.sixxs.net
traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c), 30 hops max, 80 byte packets
1 cl-10.lon-02.gb.sixxs.net (2a01:348:6:9::2) 0.084 ms !H 0.029 ms !H 0.028 ms !H
mordor:~# traceroute6 ipv6.google.com
traceroute to ipv6.google.com (2001:4860:a003::68), 30 hops max, 80 byte packets
1 cl-10.lon-02.gb.sixxs.net (2a01:348:6:9::2) 0.088 ms !H 0.028 ms !H 0.027 ms !H
I'm not sure if this is intentional, but it has worked previously.
Andy Smith.
State change: user
Jeroen Massar on Monday, 07 December 2009 12:12:03
The state of this ticket has been changed to user
Connectivity issues via gblon02
Jeroen Massar on Monday, 07 December 2009 12:14:52 Bouncing the tunnel a few times allowed me to ping out again,
What do you mean with this?
1 cl-10.lon-02.gb.sixxs.net (2a01:348:6:9::2) 0.084 ms !H 0.029 ms !H 0.028 ms !H
Wellps, that is a cl-X / <tunnel>::2 in other words your side of the tunnel, so that problem seems to be on your side.
Can you please read that big orange box and read the instructions as mentioned there and in a lot of other places? Without those details there is not much we can do at all.
Connectivity issues via gblon02
Shadow Hawkins on Tuesday, 08 December 2009 02:53:26
Sigh.
After typing out a long message here I realised whilst doing a tcpdump that my gateway is responding on a different IPv4 address now.
I've updated the endpoint, and although it's not working yet I'm 99% certain it's user error. Sorry.
Feel free to close the ticket.
Posting is only allowed when you are logged in. |