gogoNET

IPv6 & Networking the Internet of Things

Seems that montreal.freenet6.com is having some issues again.  

PING montreal.freenet6.net (64.86.88.116) 56(84) bytes of data.From 64.86.88.116 icmp_seq=1 Destination Host Unreachable^CFrom 64.86.88.116 icmp_seq=5 Destination Host Unreachable

 

 

* Starting Gateway6 Client  gw6c                                               Gateway6 Client v6.0-RELEASE build Jan 18 2010-10:28:34  Gateway6 Client v6.0-RELEASE build Jan 18 2010-10:28:34  Built on ///Linux vernadsky 2.6.24-23-server #1 SMP Wed Apr 1 22:22:14 UTC 2009 i686 GNU/Linux///Built on ///Linux vernadsky 2.6.24-23-server #1 SMP Wed Apr 1 22:22:14 UTC 2009 i686 GNU/Linux///Establishing connection to Gateway6 montreal.freenet6.net using reliable UDP.Using TSP protocol version 2.0.1.Retrieving TSP capabilities from Gateway6...RUDP packet 0, RTO 2.000000, sequence 0xf00000f0 timestamp 289.No RUDP reply.RUDP packet 1, RTO 2.000000, sequence 0xf00000f0 timestamp 2290.No RUDP reply.RUDP packet 2, RTO 2.000000, sequence 0xf00000f0 timestamp 4292.No RUDP reply.Failed to contact TSP listener at montreal.freenet6.net.Failed to contact TSP listener at montreal.freenet6.net.Disconnected. Retrying.Disconnected. Retrying.Establishing connection to Gateway6 montreal.freenet6.net using TCP.Failed to connect to Gateway6 montreal.freenet6.net on port 3653.Failed to connect to Gateway6 montreal.freenet6.net on port 3653.Trying to read the Gateway6 redirection list from broker_list file tsp-broker-list.txt.Failed to open broker_list file tsp-broker-list.txt.Disconnected. Retrying in 30 seconds.Disconnected. Retrying in 30 seconds.Establishing connection to Gateway6 montreal.freenet6.net using reliable UDP.Using TSP protocol version 2.0.1.Retrieving TSP capabilities from Gateway6...RUDP packet 0, RTO 2.000000, sequence 0xf00000f0 timestamp 324.No RUDP reply.RUDP packet 1, RTO 2.000000, sequence 0xf00000f0 timestamp 2327.No RUDP reply.RUDP packet 2, RTO 2.000000, sequence 0xf00000f0 timestamp 4329.No RUDP reply.Failed to contact TSP listener at montreal.freenet6.net.Failed to contact TSP listener at montreal.freenet6.net.Disconnected. Retrying.Disconnected. Retrying.

 

 

 

Views: 616

Reply to This

Replies to This Discussion

I am getting the same ping result. I got alert on 07/07/2011 at 2:30pm pacific time (US) that my IPv6 interface went down for my DNS and web servers.

 

I looked at my gogoCLIENT 1.2 (64-bit)'s log:

14:30:44 Keepalive processing stopped: General timeout detected.

After that i see timeouts in the log.

oh and the odd thing is, that it doesn't seem to be listening on UDP 3653 anymore:

Interesting ports on 64.86.88.116:Not shown: 994 filtered ports

PORT      STATE         SERVICE

53/udp    open|filtered domain

68/udp    open|filtered dhcpc

1701/udp  open|filtered L2TP

17184/udp open|filtered unknown

34358/udp open|filtered unknown

49162/udp open|filtered unknown

 

montreal server looks dead to me:

if-2-0-0.mcore3.MTT-Montreal.as6453.net (80.231.153.18)  144.540 ms !H * *

and

if-10-0-0-19.mcore3.MTT-Montreal.as6453.net (216.6.114.13)  0.674 ms !H if-9-0-0-1956.mcore3.MTT-Montreal.as6453.net (216.6.114.45)  0.936 ms *

judging from the status page it stopped working at 17:30 their time, about 10 hours ago.

I've done a reboot. It should be back to normal now.
no, still looks like it's down..
You are correct. Looks like there is an issue with one if the interfaces. No connectivity on the IPv4 side. Debugging...
any update?
Working with the hosting company to restore the v4 connectivity. Not sure when it will be fixed.

OS: Windows Server 2008 R2 Enterprise

 

Here is my Log from today (Pacific Time Zone):

18:04:31 Running Windows version 6.1 Service Pack 1.
18:04:31 Trying last server address montreal.freenet6.net.
18:04:31 Establishing connection to server montreal.freenet6.net using reliable UDP.
18:04:31 Using TSP protocol version 2.0.2.
18:04:31 Retrieving TSP capabilities from Server.
18:04:31 RUDP packet 0, RTO 2.000000, sequence 0xf00000f0 timestamp 732.
18:04:33 No RUDP reply.
18:04:33 RUDP packet 1, RTO 2.000000, sequence 0xf00000f0 timestamp 2744.
18:04:35 No RUDP reply.
18:04:35 RUDP packet 2, RTO 2.000000, sequence 0xf00000f0 timestamp 4757.
18:04:37 No RUDP reply.
18:04:37 Failed to contact TSP listener at montreal.freenet6.net.
18:04:37 Disconnected. Retrying.

 

Here is my ping log:

C:\Users\Administrator>ping montreal.freenet6.net

Pinging montreal.freenet6.net [64.86.88.116] with 32 bytes of data:
Reply from 216.6.98.38: Destination host unreachable.
Reply from 216.6.98.38: Destination host unreachable.
Request timed out.
Request timed out.

Ping statistics for 64.86.88.116:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

 

Part of my trace route (after it leaves Level 3's backbone):
  9     1 ms     1 ms     1 ms  if-0-0-0-889.core1.CT8-Chicago.as6453.net [66.110.27.1]
 10     1 ms     1 ms     1 ms  if-1-0-0-1878.core2.CT8-Chicago.as6453.net [66.110.27.78]
 11    37 ms    27 ms    29 ms  if-4-0-0.mcore3.TTT-Scarborough.as6453.net [216.6.98.17]
 12   202 ms  if-10-0-0-727.mcore3.MTT-Montreal.as6453.net [216.6.98.38]  reports: Destination host unreachable.

Trace complete.

Sad it's not working but glad to see this post - I was afraid it was just me that wasn't able to contact it. Does anyone know of a way to have my prefix routed over another of the servers that is working, or must the routed prefix change if I change servers? I'm thinking that it must change but thought I would ask. I just hate to change my firewall and DNS every time the server goes down :-(
actually, it's quite possible now that RFC 6296 (IPv6 to IPv6 Network Prefix Translation) is out (http://tools.ietf.org/html/rfc6296).  However, I doubt GoGoNet supports it... Or maybe they do?  Mikael?
Hmm, sounds interesting - I'll have to check out that RFC. Thanks!

RSS

Training

IoT & IPv6 Networking Conference

Product Information

Fill out my online form.

© 2014   Created by gogo6.

Badges  |  Report an Issue  |  Terms of Service