Subj : My turn for testing IPv6...
To   : RJ Clay
From : Michiel van der Vlist
Date : Sun Aug 02 2015 15:33:11

Hello RJ,

On Sunday August 02 2015 08:48, you wrote to me:

 MV>> Alas, no IPv6 connect yet:

 RC>   Didn't have the IPv6 default route configured correctly;  that's
 RC> been corrected and I can ping IPv6 addresses from there.  I'd
 RC> appreciate it if you could check again when you have a chance.

As you have seen from my previous message, it works now. It also pings.. ;-)

 MV>> BTW, ftn.rocasa.org does not ping on IPv6 either. Have you
 MV>> blocked ICMP? To operate properly ICMP should not be blocked on
 MV>> IPv6. Especially not the "packet too large"stuff.

 RC>    That also appears to been due to the default route not being set
 RC> correctly; at least, I can now ping and traceroute to it from an IPv6
 RC> capable workstation...

So can I:

D:\FIDO\FMAIL>tracert ftn.rocasa.org

Routenverfolgung zu ftn.rocasa.org [2607:fad0:12:2:0:102:0:24]  ber maximal 30 Abschnitte
:

  1    12 ms    10 ms    12 ms  gw-938.ede-01.nl.sixxs.net [2001:7b8:2ff:3a9::1]
  2    13 ms    11 ms    11 ms  nlede01.sixxs.net [2001:7b8:3:4f:202:b3ff:fe46:bec]
  3    14 ms    11 ms    11 ms  sixxs-gw.jun1.bit-1.network.bit.nl [2001:7b8:3:4f::2]
  4    32 ms    16 ms    75 ms  hurricane-electric.nikhef.nlsix.net
                                 [2001:7f8:13::a500:6939:1]
  5    43 ms    26 ms    25 ms  100ge9-1.core1.lon2.he.net [2001:470:0:2d0::1]
  6    96 ms    84 ms    88 ms  100ge1-1.core1.nyc4.he.net [2001:470:0:2cf::2]
  7   121 ms   103 ms   112 ms  100ge7-2.core1.chi1.he.net [2001:470:0:298::1]
  8     *        *        *     Zeitberschreitung der Anforderung.
  9   108 ms   107 ms   108 ms  lw-border1.rtr.liquidweb.com [2607:fad0:21:2013::1]
 10   109 ms   108 ms   107 ms  2607:fad0:21:2019::2
 11   109 ms   107 ms   107 ms  2607:fad0:12:2:0:102:0:24

Ablaufverfolgung beendet.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
 * Origin: 2001:470:1f15:1117::1 (2:280/5555)

.