Print

[davygrvy]

tunnel has died.  All communication down.  No changes on my end, but no data ever comes back.  No received bytes at all.  Sends don't result in any errors, just timeouts due to zero replies.

This was before I restarted the tunnel:

Code: [Select]

hurricane Link encap:IPv6-in-IPv4 
          inet6 addr: 2001:470:1f04:ed::2/127 Scope:Global
          inet6 addr: fe80::1807:4e0c/128 Scope:Link
          UP POINTOPOINT RUNNING NOARP  MTU:1480  Metric:1
          RX packets:4892026 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5095999 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3746767686 (3.4 GiB)  TX bytes:3497116541 (3.2 GiB)

Now:

Code: [Select]

hurricane Link encap:IPv6-in-IPv4 
          inet6 addr: 2001:470:1f04:ed::2/127 Scope:Global
          inet6 addr: fe80::1807:4e0c/128 Scope:Link
          UP POINTOPOINT RUNNING NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:326 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:36392 (35.5 KiB)

I expected to see errors, but NOTHING is shown.

[cholzhauer]

Have you tried removing the tunnel interface and re-creating it?

EDIT:

Looks like one of the servers was down for a bit

http://www.tunnelbroker.net/forums/index.php?board=10.0

[davygrvy]

yes, no change.  Works again this morning.  YEA!!

[jimb]

Yeh tserv3.fmt2 went down last night for a while.  Think it was a few hours.

[davygrvy]

My tunnel is dead again!  WTF?!

XChat is in an endless loop:
* Looking up ipv6.chat.us.freenode.net
* Connecting to ipv6.chat.us.freenode.net (2001:19f0:feee::dead:beef:cafe) port 6667...
* Connection failed. Error: Connection timed out
 Cycling to next server in FreeNode...
* Disconnected ().
* Looking up ipv6.chat.us.freenode.net
* Connecting to ipv6.chat.us.freenode.net (2001:19f0:feee::dead:beef:cafe) port 6667...
* Connection failed. Error: Connection timed out
...

All communication is down.  How about this for dead?

Code: [Select]

davygrvy@bigmoma:~$ traceroute6 he.net
traceroute to he.net (2001:470:0:76::2), 30 hops max, 80 byte packets
 1  2001:470:1f05:ed:: (2001:470:1f05:ed::)  0.702 ms  0.956 ms  2.095 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *


[jimb]

Yeah they're having some trouble with that server it looks like.  It was down for a while last night, then again today.  Just started responding to pings again.

They're working on it.

[davygrvy]

Thanks.  Yeah, it's starting to work.  The lag is horrid.  I guess that'll work itself out in a bit

[jimb]

Seems to be up-and-down.  My guess is that they're having hardware issues.

[broquea]

Because it is hard to email ipv6@he.net and ask

Hardware being funky with tserv3.fmt2.ipv6.he.net, working to de-funk it.

[jimb]

Because it is hard to email ipv6@he.net and ask

Hardware being funky, working to de-funk it.

I did actually, although I didn't ask what was actually going on.  I figured hardware.

[broquea]

Because it is hard to email ipv6@he.net and ask

Hardware being funky, working to de-funk it.

I did actually, although I didn't ask what was actually going on.  I figured hardware.

didn't mean you

[davygrvy]

So in the future I should ask ipv6@he.net and let them (you) know I'm having problems?

[jrocha]

So in the future I should ask ipv6@he.net and let them (you) know I'm having problems?

Yes, that's usually the quickest way to get a response and to let us know of an issue.