• SamKnows and IPv6

    From Michiel van der Vlist@2:280/5555 to All on Mon Feb 19 01:37:59 2018
    Hello All,

    My SamKnows probe seems to have been upgraded to IPv6. At least it now has an IPv6 address.

    It should be pingable at 2001:1c02:1100:d700:6666:b3ff:fede:4f52

    The latest report does not show that they do any tests on IPv6, but who knows.

    Anyone else have a SamKnows probe?


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Wilfred van Velzen@2:280/464 to Michiel van der Vlist on Mon Feb 19 08:40:13 2018
    Hi Michiel,

    On 2018-02-19 01:37:59, you wrote to All:

    MvdV> My SamKnows probe seems to have been upgraded to IPv6. At least it
    MvdV> now has an IPv6 address.

    MvdV> It should be pingable at 2001:1c02:1100:d700:6666:b3ff:fede:4f52

    # ping6 2001:1c02:1100:d700:6666:b3ff:fede:4f52
    PING 2001:1c02:1100:d700:6666:b3ff:fede:4f52(2001:1c02:1100:d700:6666:b3ff:fede:4f52) 56 data bytes
    64 bytes from 2001:1c02:1100:d700:6666:b3ff:fede:4f52: icmp_seq=1 ttl=54 time=28.4 ms
    64 bytes from 2001:1c02:1100:d700:6666:b3ff:fede:4f52: icmp_seq=2 ttl=54 time=30.5 ms
    64 bytes from 2001:1c02:1100:d700:6666:b3ff:fede:4f52: icmp_seq=3 ttl=54 time=26.2 ms
    64 bytes from 2001:1c02:1100:d700:6666:b3ff:fede:4f52: icmp_seq=4 ttl=54 time=28.0 ms
    ^C
    -+- 2001:1c02:1100:d700:6666:b3ff:fede:4f52 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3003ms
    rtt min/avg/max/mdev = 26.280/28.337/30.542/1.519 ms

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Richard Menedetter@2:310/31 to Michiel van der Vlist on Mon Feb 19 10:18:56 2018
    Hi Michiel!

    19 Feb 2018 01:37, from Michiel van der Vlist -> All:

    My SamKnows probe seems to have been upgraded to IPv6. At least it now
    has an IPv6 address.
    It should be pingable at 2001:1c02:1100:d700:6666:b3ff:fede:4f52
    The latest report does not show that they do any tests on IPv6, but
    who knows.
    Anyone else have a SamKnows probe?

    Interesting.
    I know that UK Technicolor xDSL CPEs have it built in.
    How did you get it?
    Have you paid for it??

    CU, Ricsi

    Indeed it is pingable:
    fido@odroid:~$ ping6 2001:1c02:1100:d700:6666:b3ff:fede:4f52
    PING 2001:1c02:1100:d700:6666:b3ff:fede:4f52(2001:1c02:1100:d700:6666:b3ff:fede :4f52 ) 56 data bytes
    64 bytes from 2001:1c02:1100:d700:6666:b3ff:fede:4f52: icmp_seq=1 ttl=52 time=115 ms
    64 bytes from 2001:1c02:1100:d700:6666:b3ff:fede:4f52: icmp_seq=2 ttl=52 time=108 ms
    -+- 2001:1c02:1100:d700:6666:b3ff:fede:4f52 ping statistics ---
    2 packets transmitted, 2 received, 0% packet loss, time 1001ms
    rtt min/avg/max/mdev = 108.826/112.219/115.613/3.409 ms

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: He who can analyze his delusions's called a philosopher (2:310/31)
  • From Michiel van der Vlist@2:280/5555 to Richard Menedetter on Mon Feb 19 11:27:50 2018
    Hello Richard,

    On Monday February 19 2018 10:18, you wrote to me:

    My SamKnows probe seems to have been upgraded to IPv6. At least
    it now has an IPv6 address. It should be pingable at
    2001:1c02:1100:d700:6666:b3ff:fede:4f52 The latest report does
    not show that they do any tests on IPv6, but who knows. Anyone
    else have a SamKnows probe?

    Interesting.

    I wrote a FidoNews article about it in Feb 2012.

    I know that UK Technicolor xDSL CPEs have it built in.
    How did you get it?

    I just asked for it. Many, many years ago: https://samknows.com/
    This is my second one. The first box had 100 Mbps ports. I asked for an upgrade when they started issuing boxes with 1000 Mbps ports.

    Have you paid for it??

    No.

    Indeed it is pingable:
    fido@odroid:~$ ping6 2001:1c02:1100:d700:6666:b3ff:fede:4f52
    PING 2001:1c02:1100:d700:6666:b3ff:fede:4f52(2001:1c02:1100:d700:6666: b3ff:fede :4f52 ) 56 data bytes 64 bytes from 2001:1c02:1100:d700:6666:b3ff:fede:4f52: icmp_seq=1 ttl=52 time=115 ms
    64 bytes from 2001:1c02:1100:d700:6666:b3ff:fede:4f52: icmp_seq=2
    ttl=52 time=108 ms -+- 2001:1c02:1100:d700:6666:b3ff:fede:4f52 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 108.826/112.219/115.613/3.409 ms

    Thanks for testing.

    Later:

    I just received an e-mail from them in response to my question if they actually do something with IPv6. This is the answer:

    === <quote> ===

    Ati (SamKnows)

    19 Feb, 10:23 GMT

    Hi Michiel,

    Thanks for getting in touch.

    As of yet, we have not adopted ipv6 tests. We report the ipv6 address if the Whitebox receives it, but we don't really do anything with it.

    Kind regards,

    Ati
    The SamKnows Team

    === </quote> ===


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Alex Shuman@2:463/877 to Michiel van der Vlist on Tue Feb 20 02:06:16 2018

    x) Monday Feb 19, 2018, 01:37. Michiel van der Vlist ÄÄ All.


    MvdV> My SamKnows probe seems to have been upgraded to IPv6. At least it now
    MvdV> has an IPv6 address.
    MvdV> It should be pingable at 2001:1c02:1100:d700:6666:b3ff:fede:4f52

    Well, it works:

    1 <1 ms <1 ms <1 ms 2a01:d0:5:4050::1
    2 <1 ms <1 ms <1 ms 2a01:d0:5:ff04::1
    3 1 ms <1 ms <1 ms 2a01:d0:0:1a::1
    4 <1 ms <1 ms <1 ms 2a01:d0:0:1c::7
    5 1 ms 1 ms 1 ms ae3-299.RT.BMB.KIV.UA.retn.net [2a02:2d8:0:2801:232a::]
    6 42 ms 23 ms 31 ms RT.IRX.VIE.AT.retn.net [2a02:2d8::57f5:e0af]
    7 39 ms 22 ms 22 ms at-vie05b-ri3-xe-9-2-2-0.v6.aorta.net [2001:730:2801:6::d52e:ad21]
    8 100 ms 44 ms 44 ms at-vie01b-rc1-lo0-0.v6.aorta.net [2001:730:2800::5474:80d1]
    9 * * * Request timed out.
    10 45 ms 44 ms 45 ms 2001:b88::1
    11 57 ms 45 ms 45 ms mnd-rc0001-cr101.core.as9143.net [2001:b88::159:74]
    12 * * * Request timed out.
    13 51 ms 52 ms 51 ms ipv6.dynamic.ziggo.nl [2001:1c02:1100:d700:6666:b3ff:fede:4f52]

    --- Neon BBS Line 2, 570-57-80, 20:30-06:30. [bbs.ncc.org.ua]
    * Origin: Neon_#2, Kiev, Ukraine (2:463/877)
  • From Michiel van der Vlist@2:280/5555 to Alex Shuman on Tue Feb 20 01:29:43 2018
    Hello Alex,

    On Tuesday February 20 2018 02:06, you wrote to me:

    Well, it works:

    1 <1 ms <1 ms <1 ms 2a01:d0:5:4050::1
    2 <1 ms <1 ms <1 ms 2a01:d0:5:ff04::1
    3 1 ms <1 ms <1 ms 2a01:d0:0:1a::1
    4 <1 ms <1 ms <1 ms 2a01:d0:0:1c::7
    5 1 ms 1 ms 1 ms ae3-299.RT.BMB.KIV.UA.retn.net
    [2a02:2d8:0:2801:232a::]
    6 42 ms 23 ms 31 ms RT.IRX.VIE.AT.retn.net
    [2a02:2d8::57f5:e0af]
    7 39 ms 22 ms 22 ms at-vie05b-ri3-xe-9-2-2-0.v6.aorta.net
    [2001:730:2801:6::d52e:ad21]
    8 100 ms 44 ms 44 ms at-vie01b-rc1-lo0-0.v6.aorta.net
    [2001:730:2800::5474:80d1]
    9 * * * Request timed out.
    10 45 ms 44 ms 45 ms 2001:b88::1
    11 57 ms 45 ms 45 ms mnd-rc0001-cr101.core.as9143.net
    [2001:b88::159:74]
    12 * * * Request timed out.
    13 51 ms 52 ms 51 ms ipv6.dynamic.ziggo.nl [2001:1c02:
    1100:d700:6666:b3ff:fede:4f52]

    Nice to see the IPv6 internet at work... ;-)

    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Benny Pedersen@1:261/38.20 to Michiel van der Vlist on Sun Feb 25 12:55:48 2018
    Hello Michiel!

    20 Feb 2018 01:29, Michiel van der Vlist wrote to Alex Shuman:

    MvdV> Nice to see the IPv6 internet at work... ;-)

    ----- themultixpoint.junc.eu begins -----
    NS j.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS a.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS f.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS k.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS h.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS l.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS c.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS d.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS g.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS b.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS i.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS m.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS e.root-servers.net. from server 127.0.0.1 in 0 ms.
    RRSIG NS 8 0 518400 20180309170000 20180224160000 41824 . CHH+gFbTVRVSF/Z5sIfML0pazhvDEDQs5RGcCKsI/RuiqIr19KAoDChR yzhpXtfvlNI4sY3R4RVa++AsC5GX6cZYF0LxmHwLAzV8ZSHNdJd+vBP8 gVhdQKHjM5LovVggYYWLO/Y2vINm0PNeFpNk8m6HSXEnx4+nEcp416nU KYw+/QMEh70KCcLtxzT6SMWm7Z2C/fFAw5J8pGwtxJx3+/JJKKd82L6x 3acN+u8mO+RstYt6Et2I8bhGk3lJFT1r1+zX6W9jn6VMKqcOfhjKv4+t rrbtrYOOXuy2c8b6SBboZzpoMRj+AjtmEKDooF3GwFj8q9x/FSnC69kG PqYB1A== from server 127.0.0.1 in 0 ms.
    A 176.58.121.172 from server 149.11.76.234 in 50 ms.
    RRSIG A 5 3 3600 20180320145554 20180218145554 9063 junc.eu. jBo/ZiekgjhFY2XLqc7cH4Ng+lGvQQYZ5chyCZZyeGgmd4SMjOzaTfcd u+63ayUdOJdqZJ8TLW8NwBzPWPslEg== from server 149.11.76.234 in 50 ms.
    ----- themultixpoint.junc.eu ends -----

    ----- themultixpoint.junc.eu begins -----
    NS i.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS k.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS f.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS h.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS c.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS e.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS b.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS g.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS a.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS d.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS j.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS l.root-servers.net. from server 127.0.0.1 in 0 ms.
    NS m.root-servers.net. from server 127.0.0.1 in 0 ms.
    RRSIG NS 8 0 518400 20180309170000 20180224160000 41824 . CHH+gFbTVRVSF/Z5sIfML0pazhvDEDQs5RGcCKsI/RuiqIr19KAoDChR yzhpXtfvlNI4sY3R4RVa++AsC5GX6cZYF0LxmHwLAzV8ZSHNdJd+vBP8 gVhdQKHjM5LovVggYYWLO/Y2vINm0PNeFpNk8m6HSXEnx4+nEcp416nU KYw+/QMEh70KCcLtxzT6SMWm7Z2C/fFAw5J8pGwtxJx3+/JJKKd82L6x 3acN+u8mO+RstYt6Et2I8bhGk3lJFT1r1+zX6W9jn6VMKqcOfhjKv4+t rrbtrYOOXuy2c8b6SBboZzpoMRj+AjtmEKDooF3GwFj8q9x/FSnC69kG PqYB1A== from server 127.0.0.1 in 0 ms.
    AAAA 2a01:7e00:e000:146::2 from server 62.61.159.230 in 25 ms.
    RRSIG AAAA 5 3 3600 20180320145554 20180218145554 9063 junc.eu. XjHFkOnEEDX+m6K/gnEPyFCj57KnHqL+Hai6D8nn5DL+EF/VXh8xXdvn YuFp0YiGbML+mFmXdLNGL143iL4aqA== from server 62.61.159.230 in 25 ms.
    ----- themultixpoint.junc.eu ends -----

    :)

    is 2:292/854 down ?


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.2.0 (Linux/4.9.76-gentoo-r1 (i686))
    * Origin: I will always keep a PC running CPM 3.0 (1:261/38.20)
  • From Kees van Eeten@2:280/5003.4 to Benny Pedersen on Sun Feb 25 14:39:58 2018
    Hello Benny!

    25 Feb 18 12:55, you wrote to Michiel van der Vlist:

    is 2:292/854 down ?

    No, he is alive and kicking.

    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Michiel van der Vlist@2:280/5555 to Benny Pedersen on Sun Feb 25 14:48:34 2018
    Hello Benny,

    On Sunday February 25 2018 12:55, you wrote to me:


    is 2:292/854 down ?

    Looks like there are some DNS problems with dtdns.net. But since it is an IPv4 only problem, it is of no concern to the Fidonet IPv6 club...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Benny Pedersen@1:261/38.20 to Kees van Eeten on Sun Feb 25 18:49:28 2018
    Hello Kees!

    25 Feb 2018 14:39, Kees van Eeten wrote to Benny Pedersen:

    is 2:292/854 down ?
    No, he is alive and kicking.

    snowballs


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.2.0 (Linux/4.9.76-gentoo-r1 (i686))
    * Origin: I will always keep a PC running CPM 3.0 (1:261/38.20)
  • From Benny Pedersen@1:261/38.20 to Michiel van der Vlist on Sun Feb 25 18:50:16 2018
    Hello Michiel!

    25 Feb 2018 14:48, Michiel van der Vlist wrote to Benny Pedersen:

    is 2:292/854 down ?

    MvdV> Looks like there are some DNS problems with dtdns.net. But since it
    MvdV> is an IPv4 only problem, it is of no concern to the Fidonet IPv6
    MvdV> club...

    aslong nodelists contains hostnames its a ipv6 problem aswell


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.2.0 (Linux/4.9.76-gentoo-r1 (i686))
    * Origin: I will always keep a PC running CPM 3.0 (1:261/38.20)