IPv6 | The Internet of Things

I have noticed that the gogo6 web site frequently has extremely poor performance, where it takes minutes for a page to appear.  Apparently, resetting the server "fixes" the problem, only to have it occur again a short time later.  What is it that's causing this problem?  Resetting the server is the same as rebooting Windows to solve a problem.  It's obviously only treating the symptoms and not the root cause of the problem.

Views: 318

Reply to This

Replies to This Discussion

I wish I knew why... Traffic overload at Montreal is one cause of the problem but there is also an issue with the IPv6 proxy failing. As a big part of gogoNET is hosted at Ning, which isn't IPv6, we have our own IPv6 proxy to allow access on IPv6. We have talked to Ning but they hardly know what IPv6 so I don't expect them to offer anything any time soon so we are stuck with the proxy. The proxy is just a a portproxy on a Win 2k8 machine and that works fine as long as it works but for some reason it seems like it just stops working at some point without any error message or anything.

I can well understand that Windows may be the problem.  I certainly saw enough of that when I worked at IBM.  Perhaps a different method would be better.  Why not run the gogo client on that machine, instead of relying on a proxy?  Or perhaps the "IPv6 in 60 Seconds" adapter?


BTW, if you're doing anything on the Internet, Linux & Unix are far better than Windows.  In fact, the Internet became what it is largely because it was run on Unix.  In my own work on computer networks, I find Linux to be far superior to Windows.


The gogonet.gogo6.com site feels very (!) slow today, but only when accessed via IPv6. When I'm on IPv4, the gogo6 website is responding quite well. How comes?

I can tell you that is has nothing to do with the net, or atleast the ICMP side.  I can reach the IP using ping through a tunnel from either the gogo6 client or hurricane electric.  I suspect server hardware or the TCP stack.  For me, the site works great over IPv4, but it times out over IPv6, again, using either tunnel.  This might also be a MTU issue since mine is 1280.  Maybe someone can try a "netsh int ipv6 reset" on the server.


Tracing route to gogonet.gogo6.com [2001:5c0:1000:f::3]
over a maximum of 30 hops:

  1    94 ms   109 ms   109 ms  2001:5c0:1000:a::404
  2    98 ms    97 ms   102 ms  ns2.gogo6.com [2001:5c0:1000:f::3]

Trace complete.


Tracing route to gogonet.gogo6.com [2001:5c0:1000:f::3]
over a maximum of 30 hops:

  1     2 ms     1 ms     2 ms  kaysville.yaritz.net [2001:470:1f05:170b::1]
  2    32 ms    54 ms    34 ms  gnarlymarley-1.tunnel.tserv3.fmt2.ipv6.he.net [2001:470:1f04:170b::1]
  3    42 ms    36 ms    37 ms  gige-g5-19.core1.fmt2.he.net [2001:470:0:45::1]
  4    48 ms    38 ms    34 ms  10gigabitethernet1-1.core1.sjc2.he.net [2001:470:0:31::2]
  5    40 ms    27 ms    34 ms  as6453.gige-g5-16.core1.sjc2.he.net [2001:470:0:196::2]
  6   105 ms   100 ms   108 ms  if-0-0-0.1789.core2.CT8-Chicago.ipv6.as6453.net [2001:5a0:500:100::3e]
  7   115 ms   101 ms   119 ms  POS4-0-0.mcore3.TTT-Scarborough.ipv6.as6453.net [2001:5a0:1000::21]
  8   102 ms    99 ms   100 ms  if-13-0-0.1998.mcore4.MTT-Montreal.ipv6.as6453.net [2001:5a0:300:200::19]
  9   102 ms   109 ms   104 ms  if-3-0-0.6bb1.MTT-Montreal.ipv6.as6453.net [2001:5a0:300:100::22]
 10   107 ms   104 ms   104 ms  2001:5a0:300::6
 11   102 ms   112 ms   114 ms  ns2.gogo6.com [2001:5c0:1000:f::3]

Trace complete.

in our seminar all the facilitators told us that ipv4 will run out on 2014 so we need to learned how to used the ipv6!they said something about ipv6 but the knowledge they gave to us is not enough it is just a basic is there's anyone who can tell me more about ipv6?


An excellent book is "IPv6 Essentials", published by O'Reilly.  It goes into a lot of detail about IPv6.  Also, those facilitators are a bit late.  The last block of IPv4 addresses was handed out almost a year ago to the regions and there are very few left for ISPs.  In fact, some ISPs are now using RFC 1918 addresses and NAT, because they can't get public IP addresses.




IoT Product Information

Fill out my online form.

© 2016   Created by gogo6.   Powered by

Badges  |  Report an Issue  |  Terms of Service