• List of IPv6 nodes

    From Michiel van der Vlist@2:280/5555 to All on Thu Aug 19 20:34:30 2021
    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555

    Updated 15 August 2021


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen Native Xs4All f
    2 2:280/5003 Kees van Eeten Native Xs4All f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
    4 2:280/5555 Michiel van der Vlist Native Ziggo f
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula Native Hetzner f
    7 2:221/6 Tommi Koivula Native OVH
    8 2:5053/54 Denis Mikhlevich Native TTK-Volga
    9 2:5030/257 Vova Uralsky Native PCextreme
    10 1:154/10 Nicholas Bol Native Spectrum f
    11 2:203/0 Bjrn Felten T-6in4 he.net
    12 2:280/5006 Kees van Eeten Native Xs4All f INO4
    13 3:712/848 Scott Little T-6in4 he.net f
    14 2:5020/545 Alexey Vissarionov Native Hetzner f
    15 1:103/17 Stephen Hurd T-6in4 he.net
    16 2:5020/9696 Alexander Skovpen T-6in4 TUNNELBROKER-0
    17 2:421/790 Viktor Cizek T-6in4 he.net
    18 2:222/2 Kim Heino Native TeliaSonera
    19 3:633/280 Stephen Walsh Native AusNetServers f
    20 2:463/877 Alex Shuman Native Nline f IO
    21 1:19/10 Matt Bedynek T-6in4 he.net
    22 3:770/1 Paul Hayton T-6in4 he.net
    23 2:5053/58 Alexander Kruglikov Native TTK-Volga f
    24 1:103/1 Stephen Hurd Native Choopa
    25 3:633/281 Stephen Walsh Native Internode
    26 2:310/31 Richard Menedetter Native DE-NETCUP f
    27 3:633/410 Tony Langdon Native IINET
    28 2:5020/329 Oleg Lukashin Native Comfortel f
    29 2:246/1305 Emil Schuster Native TAL.DE
    30 2:2448/4000 Tobias Burchhardt Native DTAG IO
    31 2:331/51 Marco d'Itri Native BOFH-IT
    32 1:154/30 Mike Miller Native LINODE
    33 2:5001/100 Dmitry Protasoff Native OVH
    34 2:5059/38 Andrey Mundirov T-6in4 he.net
    35 2:240/5853 Philipp Giebel Native Hetzner
    36 2:5083/444 Peter Khanin Native OVH
    37 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
    38 1:123/10 Wayne Smith T-6in4 he.net
    39 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    40 1:135/300 Eric Renfro Native Amazon.com
    41 1:103/13 Stephen Hurd Native Choopa
    42 2:5020/1042 Michael Dukelsky Native FORPSI Ktis f
    43 2:5095/0 Sergey V. Efimoff T-6in4 he.net
    44 2:5095/20 Sergey V. Efimoff T-6in4 he.net
    45 2:5019/400 Konstantin Kuzov Native LT-LT
    46 2:467/239 Mykhailo Kapitanov Native Vultr f
    47 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    48 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
    49 2:280/2000 Michael Trip Native Xs4All
    50 2:230/38 Benny Pedersen Native Linode
    51 2:460/58 Stas Mishchenkov T-6in4 he.net f
    52 1:135/367 Antonio Rivera Native RRSW-V6
    53 2:5020/2123 Anton Samsonov T-6in4 he.net
    54 2:5020/2332 Andrey Ignatov Native ru.rtk
    55 2:5005/49 Victor Sudakov T-6in4 he.net f
    56 2:5005/77 Valery Lutoshkin T-6in4 NTS f
    57 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    58 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    59 2:5010/352 Dmitriy Smirnov Native EkranTV f
    60 2:292/854 Ward Dossche Native Proximus
    61 2:469/122 Sergey Zabolotny T-6in4 he.net f
    62 2:5053/400 Denis Mikhlevich Native TTK-Volga
    63 1:135/371 Eric Renfro Native Cox Cmmunctns
    64 2:421/21 Stepan Gabriel Native NETDATACOMM
    65 2:5030/1997 Alexey Fayans T-6in4 he.net
    66 1:220/70 Joseph Werle T-6in4 he.net
    67 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    68 2:2452/502 Ludwig Bernhartzeder Native DTAG
    69 2:423/39 Karel Kral Native WEDOS
    70 2:5080/102 Stas Degteff T-6to4 NOVATOR
    71 2:280/1049 Simon Voortman Native Solcon
    72 1:102/127 Bradley Thornton Native Hetzner
    73 2:335/364 Fabio Bizzi Native IT-ALBACOM
    74 1:124/5016 Nigel Reed Native DAL1-US f
    75 2:5020/843 Peter Antonov Native BelCloud
    76 2:5075/37 Andrew Komardin Native IHC-NET
    77 1:153/146 Erich Bublitz Native LINODE-US
    78 1:106/633 William Williams Native LINODE-US PM *1
    79 2:263/5 Martin List-Petersen Native TuxBox
    80 2:5030/1520 Andrey Geyko T-6in4 he.net f
    81 1:229/664 Jay Harris Native Rogers
    82 1:142/103 Brian Rogers T-6in4 he.net
    83 1:134/101 Kostie Muirhead T-6in4 he.net f
    84 2:280/2030 Martien Korenblom Native Transip
    85 3:633/509 Deon George Native Telstra
    86 2:5020/4441 Yuri Myakotin Native SOVINTEL
    87 1:320/319 Andrew Leary Native Comcast f
    88 2:240/5824 Anna Christina Nass T-6in4 he.net f
    89 2:460/5858 Stas Mishchenkov T-6in4 he.net f
    90 1:105/5 Michael Pierce Native Comcast
    91 1:218/401 James Downs Native ORG-TT1
    92 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
    93 2:301/812 Benoit Panizon Native WOODYV6
    94 1:229/616 Vasily Losev Native GIGEPORT
    95 2:301/113 Alisha Manuela Stutz T-6in4 he.net
    96 2:5035/63 Vladimir Goncharov Native RFEIV6NET 6DWN
    97 1:134/100 Kostie Muirhead T-6in4 he.net f
    98 1:134/102 Shelley Petersen T-6in4 he.net f INO4
    99 1:134/103 Gordon Muirhead T-6in4 he.net f
    100 1:134/302 Adam Park T-6in4 he.net f
    101 1:134/301 Brandon Moore T-6in4 he.net f INO4
    102 1:153/7715 Dallas Hinton Native Shaw Comms.
    103 1:218/840 Morgan Collins Native Linode
    104 2:5020/921 Andrew Savin T-6in4 he.net


    T-6in4 Static 6in4
    T-AYIY Dynamic AYIYA
    T-6to4 6to4
    T-6RD 6RD

    Remarks:

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    (zone, net, node in decimal notation)
    IO Incoming only (Node can not make outgoing IPv6 calls)
    OO Outgoing only (Node can not accept incoming IPv6 calls).
    INO4 No IPv4 (Node can not accept incoming IPv4 calls).
    PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
    but is configured to try IPv4 first)
    6DWN The IPv6 connectivity of this node is temporarely down.
    NO6 The node no longer presents an IPv6 address in the nodelist
    and will soon be removed from this list.
    HOLD The node is temporarely off-line. Mail may be routed.
    DOWN This node is Down for both IPv4 and IPv6 and will be
    removed from this list if the condition pertains.
    PM Prospective Member. The node has demonstrated IPv6
    capability but is not listed or does not advertise an
    IPv6 address in the Fidonet nodelist yet.

    PM *1 [2600:3c01::f03c:91ff:fe2b:c319]


    Notes:

    To make an IPv6 connection to a node connected via 6to4 tunneling
    one may have to force the mailer into IPv6 (-6 option in binkd's
    node config for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
    and up when compiled with AF_FORCE=1). If the destination address
    is a 6to4 tunnel address (2002::/16) many OSs default to IPv4 if
    an IPv4 address is present.


    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to All on Fri Sep 3 23:33:30 2021
    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555

    Updated 3 September 2021


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen Native Xs4All f
    2 2:280/5003 Kees van Eeten Native Xs4All f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
    4 2:280/5555 Michiel van der Vlist Native Ziggo f
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula Native Hetzner f
    7 2:221/6 Tommi Koivula Native OVH
    8 2:5053/54 Denis Mikhlevich Native TTK-Volga
    9 2:5030/257 Vova Uralsky Native PCextreme
    10 1:154/10 Nicholas Bol Native Spectrum f
    11 2:203/0 Bjrn Felten T-6in4 he.net
    12 2:280/5006 Kees van Eeten Native Xs4All f INO4
    13 3:712/848 Scott Little T-6in4 he.net f
    14 2:5020/545 Alexey Vissarionov Native Hetzner f
    15 1:103/17 Stephen Hurd T-6in4 he.net
    16 2:5020/9696 Alexander Skovpen T-6in4 TUNNELBROKER-0
    17 2:421/790 Viktor Cizek T-6in4 he.net
    18 2:222/2 Kim Heino Native TeliaSonera
    19 3:633/280 Stephen Walsh Native AusNetServers f
    20 2:463/877 Alex Shuman Native Nline f IO
    21 1:19/10 Matt Bedynek T-6in4 he.net
    22 3:770/1 Paul Hayton T-6in4 he.net
    23 2:5053/58 Alexander Kruglikov Native TTK-Volga f
    24 1:103/1 Stephen Hurd Native Choopa
    25 3:633/281 Stephen Walsh Native Internode
    26 2:310/31 Richard Menedetter Native DE-NETCUP f
    27 3:633/410 Tony Langdon Native IINET
    28 2:5020/329 Oleg Lukashin Native Comfortel f
    29 2:246/1305 Emil Schuster Native TAL.DE
    30 2:2448/4000 Tobias Burchhardt Native DTAG IO
    31 2:331/51 Marco d'Itri Native BOFH-IT
    32 1:154/30 Mike Miller Native LINODE
    33 2:5001/100 Dmitry Protasoff Native OVH
    34 2:5059/38 Andrey Mundirov T-6in4 he.net
    35 2:240/5853 Philipp Giebel Native Hetzner
    36 2:5083/444 Peter Khanin Native OVH
    37 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
    38 1:123/10 Wayne Smith T-6in4 he.net
    39 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    40 1:135/300 Eric Renfro Native Amazon.com
    41 1:103/13 Stephen Hurd Native Choopa
    42 2:5020/1042 Michael Dukelsky Native FORPSI Ktis f
    43 2:5095/0 Sergey V. Efimoff T-6in4 he.net
    44 2:5095/20 Sergey V. Efimoff T-6in4 he.net
    45 2:5019/400 Konstantin Kuzov Native LT-LT
    46 2:467/239 Mykhailo Kapitanov Native Vultr f
    47 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    48 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
    49 2:280/2000 Michael Trip Native Xs4All
    50 2:230/38 Benny Pedersen Native Linode
    51 2:460/58 Stas Mishchenkov T-6in4 he.net f
    52 1:135/367 Antonio Rivera Native RRSW-V6
    53 2:5020/2123 Anton Samsonov T-6in4 he.net
    54 2:5020/2332 Andrey Ignatov Native ru.rtk
    55 2:5005/49 Victor Sudakov T-6in4 he.net f
    56 2:5005/77 Valery Lutoshkin T-6in4 NTS f
    57 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    58 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    59 2:5010/352 Dmitriy Smirnov Native EkranTV f
    60 2:292/854 Ward Dossche Native Proximus
    61 2:469/122 Sergey Zabolotny T-6in4 he.net f
    62 2:5053/400 Denis Mikhlevich Native TTK-Volga
    63 1:135/371 Eric Renfro Native Cox Cmmunctns
    64 2:421/21 Stepan Gabriel Native NETDATACOMM
    65 2:5030/1997 Alexey Fayans T-6in4 he.net
    66 1:220/70 Joseph Werle T-6in4 he.net
    67 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    68 2:2452/502 Ludwig Bernhartzeder Native DTAG
    69 2:423/39 Karel Kral Native WEDOS
    70 2:5080/102 Stas Degteff T-6to4 NOVATOR
    71 2:280/1049 Simon Voortman Native Solcon
    72 1:102/127 Bradley Thornton Native Hetzner
    73 2:335/364 Fabio Bizzi Native IT-ALBACOM
    74 1:124/5016 Nigel Reed Native DAL1-US f
    75 2:5020/843 Peter Antonov Native BelCloud
    76 2:5075/37 Andrew Komardin Native IHC-NET
    77 1:153/146 Erich Bublitz Native LINODE-US
    78 1:106/633 William Williams Native LINODE-US PM *1
    79 2:263/5 Martin List-Petersen Native TuxBox
    80 2:5030/1520 Andrey Geyko T-6in4 he.net f
    81 1:229/664 Jay Harris Native Rogers
    82 1:142/103 Brian Rogers T-6in4 he.net
    83 1:134/101 Kostie Muirhead T-6in4 he.net f
    84 2:280/2030 Martien Korenblom Native Transip
    85 3:633/509 Deon George Native Telstra
    86 2:5020/4441 Yuri Myakotin Native SOVINTEL
    87 1:320/319 Andrew Leary Native Comcast f
    88 2:240/5824 Anna Christina Nass T-6in4 he.net f
    89 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
    90 1:105/5 Michael Pierce Native Comcast
    91 1:218/401 James Downs Native ORG-TT1
    92 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
    93 2:301/812 Benoit Panizon Native WOODYV6
    94 1:229/616 Vasily Losev Native GIGEPORT
    95 2:301/113 Alisha Manuela Stutz T-6in4 he.net
    96 2:5035/63 Vladimir Goncharov Native RFEIV6NET
    97 1:134/100 Kostie Muirhead T-6in4 he.net f
    98 1:134/102 Shelley Petersen T-6in4 he.net f INO4
    99 1:134/103 Gordon Muirhead T-6in4 he.net f
    100 1:134/302 Adam Park T-6in4 he.net f
    101 1:134/301 Brandon Moore T-6in4 he.net f INO4
    102 1:153/7715 Dallas Hinton Native Shaw Comms.
    103 1:218/840 Morgan Collins Native Linode
    104 2:5020/921 Andrew Savin T-6in4 he.net
    105 2:240/1634 Hugo Andriessen Native Vodafone
    106 2:280/2040 Leo Barnhoorn Native Ziggo


    T-6in4 Static 6in4
    T-AYIY Dynamic AYIYA
    T-6to4 6to4
    T-6RD 6RD

    Remarks:

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    (zone, net, node in decimal notation)
    IO Incoming only (Node can not make outgoing IPv6 calls)
    OO Outgoing only (Node can not accept incoming IPv6 calls).
    INO4 No IPv4 (Node can not accept incoming IPv4 calls).
    PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
    but is configured to try IPv4 first)
    6DWN The IPv6 connectivity of this node is temporarely down.
    NO6 The node no longer presents an IPv6 address in the nodelist
    and will soon be removed from this list.
    HOLD The node is temporarely off-line. Mail may be routed.
    DOWN This node is Down for both IPv4 and IPv6 and will be
    removed from this list if the condition pertains.
    PM Prospective Member. The node has demonstrated IPv6
    capability but is not listed or does not advertise an
    IPv6 address in the Fidonet nodelist yet.

    PM *1 [2600:3c01::f03c:91ff:fe2b:c319]


    Notes:

    To make an IPv6 connection to a node connected via 6to4 tunneling
    one may have to force the mailer into IPv6 (-6 option in binkd's
    node config for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
    and up when compiled with AF_FORCE=1). If the destination address
    is a 6to4 tunnel address (2002::/16) many OSs default to IPv4 if
    an IPv4 address is present.

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to All on Sun Nov 28 19:46:00 2021
    Hello All,

    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555

    Updated 28 November 2021


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen Native Xs4All f
    2 2:280/5003 Kees van Eeten Native Xs4All f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
    4 2:280/5555 Michiel van der Vlist Native Ziggo f
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula Native Hetzner f
    7 2:221/6 Tommi Koivula Native OVH
    8 2:5053/54 Denis Mikhlevich Native TTK-Volga
    9 2:5030/257 Vova Uralsky Native PCextreme
    10 1:154/10 Nicholas Bol Native Spectrum f
    11 2:203/0 Bjrn Felten T-6in4 he.net
    12 2:280/5006 Kees van Eeten Native Xs4All f INO4
    13 3:712/848 Scott Little T-6in4 he.net f
    14 2:5020/545 Alexey Vissarionov Native Hetzner f
    15 1:103/17 Stephen Hurd T-6in4 he.net
    16 2:5020/9696 Alexander Skovpen T-6in4 TUNNELBROKER-0
    17 2:421/790 Viktor Cizek T-6in4 he.net
    18 2:222/2 Kim Heino Native TeliaSonera
    19 3:633/280 Stephen Walsh Native AusNetServers f
    20 2:463/877 Alex Shuman Native Nline f IO
    21 1:19/10 Matt Bedynek T-6in4 he.net
    22 3:770/1 Paul Hayton T-6in4 he.net
    23 3:770/100 Paul Hayton T-6in4 he.net
    24 2:5053/58 Alexander Kruglikov Native TTK-Volga f
    25 1:103/1 Stephen Hurd Native Choopa
    26 3:633/281 Stephen Walsh Native Internode
    27 2:310/31 Richard Menedetter Native DE-NETCUP f
    28 3:633/410 Tony Langdon Native IINET
    29 2:5020/329 Oleg Lukashin Native Comfortel f
    30 2:246/1305 Emil Schuster Native TAL.DE
    31 2:2448/4000 Tobias Burchhardt Native DTAG IO
    32 2:331/51 Marco d'Itri Native BOFH-IT
    33 1:154/30 Mike Miller Native LINODE
    34 2:5001/100 Dmitry Protasoff Native OVH
    35 2:5059/38 Andrey Mundirov T-6in4 he.net
    36 2:240/5853 Philipp Giebel Native Hetzner
    37 2:5083/444 Peter Khanin Native OVH
    38 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
    39 1:123/10 Wayne Smith T-6in4 he.net
    40 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    41 1:135/300 Eric Renfro Native Amazon.com
    42 1:103/13 Stephen Hurd Native Choopa
    43 2:5020/1042 Michael Dukelsky Native FORPSI Ktis f
    44 2:5095/0 Sergey V. Efimoff T-6in4 he.net
    45 2:5095/20 Sergey V. Efimoff T-6in4 he.net
    46 2:5019/400 Konstantin Kuzov Native LT-LT
    47 2:467/239 Mykhailo Kapitanov Native Vultr f
    48 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    49 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
    50 2:280/2000 Michael Trip Native Xs4All
    51 2:230/38 Benny Pedersen Native Linode
    52 2:460/58 Stas Mishchenkov T-6in4 he.net f
    53 1:135/367 Antonio Rivera Native RRSW-V6 DOWN
    54 2:5020/2123 Anton Samsonov T-6in4 he.net
    55 2:5020/2332 Andrey Ignatov Native ru.rtk
    56 2:5005/49 Victor Sudakov T-6in4 he.net f
    57 2:5005/77 Valery Lutoshkin T-6in4 NTS f
    58 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    59 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    60 2:5010/352 Dmitriy Smirnov Native EkranTV f
    61 2:292/854 Ward Dossche Native Proximus
    62 2:469/122 Sergey Zabolotny T-6in4 he.net f
    63 2:5053/400 Denis Mikhlevich Native TTK-Volga
    64 1:135/371 Eric Renfro Native Cox Cmmunctns 6DWN
    65 2:421/21 Stepan Gabriel Native NETDATACOMM 6DWN
    66 2:5030/1997 Alexey Fayans T-6in4 he.net
    67 1:220/70 Joseph Werle T-6in4 he.net DOWN
    68 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    69 2:2452/502 Ludwig Bernhartzeder Native DTAG
    70 2:423/39 Karel Kral Native WEDOS
    71 2:5080/102 Stas Degteff T-6to4 NOVATOR
    72 2:280/1049 Simon Voortman Native Solcon
    73 1:102/127 Bradley Thornton Native Hetzner
    74 2:335/364 Fabio Bizzi Native IT-ALBACOM
    75 1:124/5016 Nigel Reed Native DAL1-US f
    76 2:5020/843 Petr Antonov Native BelCloud 6DWN
    77 2:5075/37 Andrew Komardin Native IHC-NET
    79 1:106/633 William Williams Native LINODE-US PM *1
    79 2:263/5 Martin List-Petersen Native TuxBox
    80 2:5030/1520 Andrey Geyko T-6in4 he.net f
    81 1:229/664 Jay Harris Native Rogers
    82 1:142/103 Brian Rogers T-6in4 he.net
    83 1:134/101 Kostie Muirhead T-6in4 he.net f
    84 2:280/2030 Martien Korenblom Native Transip
    85 3:633/509 Deon George Native Telstra
    86 2:5020/4441 Yuri Myakotin Native SOVINTEL
    87 1:320/319 Andrew Leary Native Comcast f
    88 2:240/5824 Anna Christina Nass T-6in4 he.net f
    89 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
    90 1:218/401 James Downs Native ORG-TT1
    91 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
    92 2:301/812 Benoit Panizon Native WOODYV6
    93 1:229/616 Vasily Losev Native GIGEPORT
    94 2:301/113 Alisha Manuela Stutz T-6in4 he.net
    95 1:134/100 Kostie Muirhead T-6in4 he.net f
    96 1:134/101 Kostie Muirhead T-6in4 he.net f
    97 1:134/102 Shelley Petersen T-6in4 he.net f INO4
    98 1:134/103 Gordon Muirhead T-6in4 he.net f
    99 1:134/301 Brandon Moore T-6in4 he.net f INO4
    100 1:134/302 Adam Park T-6in4 he.net f
    101 1:153/7715 Dallas Hinton Native Shaw Comms
    102 1:218/840 Morgan Collins Native Linode
    103 2:5020/921 Andrew Savin T-6in4 he.net
    104 2:240/1634 Hugo Andriessen Native Vodafone
    105 2:280/2040 Leo Barnhoorn Native Ziggo
    106 2:5020/736 Egor Glukhov Native RUWEB f
    107 2:221/10 Tommi Koivula Native Hetzner f INO4
    108 1:266/420 Scott Street Native Comcast OO
    109 2:5053/400 Alexander Kruglikov Native Oracle f
    110 1:218/850 John Nicpon Native LINODE-US



    T-6in4 Static 6in4
    T-AYIY Dynamic AYIYA
    T-6to4 6to4
    T-6RD 6RD

    Remarks:

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    (zone, net, node in decimal notation)
    IO Incoming only (Node can not make outgoing IPv6 calls)
    OO Outgoing only (Node can not accept incoming IPv6 calls).
    INO4 No IPv4 (Node can not accept incoming IPv4 calls).
    PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
    but is configured to try IPv4 first)
    6DWN The IPv6 connectivity of this node is temporarely down.
    NO6 The node no longer presents an IPv6 address in the nodelist
    and will soon be removed from this list.
    HOLD The node is temporarely off-line. Mail may be routed.
    DOWN This node is Down for both IPv4 and IPv6 and will be
    removed from this list if the condition pertains.
    PM Prospective Member. The node has demonstrated IPv6
    capability but is not listed or does not advertise an
    IPv6 address in the Fidonet nodelist yet.

    PM *1 [2600:3c01::f03c:91ff:fe2b:c319]

    Notes:

    To make an IPv6 connection to a node connected via 6to4 tunneling
    one may have to force the mailer into IPv6 (-6 option in binkd's
    node config for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
    and up when compiled with AF_FORCE=1). If the destination address
    is a 6to4 tunnel address (2002::/16) many OSs default to IPv4 if
    an IPv4 address is present.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to All on Mon Jan 3 12:04:00 2022

    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555

    Updated 3 January 2022


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen Native Xs4All f
    2 2:280/5003 Kees van Eeten Native Xs4All f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
    4 2:280/5555 Michiel van der Vlist Native Ziggo f
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula Native Hetzner f
    7 2:221/6 Tommi Koivula Native OVH
    8 2:5030/257 Vova Uralsky Native PCextreme
    9 1:154/10 Nicholas Bol Native Spectrum f
    10 2:203/0 Bjrn Felten T-6in4 he.net
    11 2:280/5006 Kees van Eeten Native Xs4All f INO4
    12 3:712/848 Scott Little T-6in4 he.net f
    13 2:5020/545 Alexey Vissarionov Native Hetzner f
    14 1:103/17 Stephen Hurd T-6in4 he.net
    15 2:5020/9696 Alexander Skovpen T-6in4 TUNNELBROKER-0
    16 2:421/790 Viktor Cizek T-6in4 he.net
    17 2:222/2 Kim Heino Native TeliaSonera
    18 3:633/280 Stephen Walsh Native AusNetServers f
    19 2:463/877 Alex Shuman Native Nline f IO
    20 1:19/10 Matt Bedynek T-6in4 he.net
    21 3:770/1 Paul Hayton T-6in4 he.net
    22 3:770/100 Paul Hayton T-6in4 he.net
    23 2:5053/58 Alexander Kruglikov Native TTK-Volga f
    24 1:103/1 Stephen Hurd Native Choopa
    25 3:633/281 Stephen Walsh Native Internode
    26 2:310/31 Richard Menedetter Native DE-NETCUP f
    27 3:633/410 Tony Langdon Native IINET
    28 2:5020/329 Oleg Lukashin Native Comfortel f
    29 2:246/1305 Emil Schuster Native TAL.DE
    30 2:2448/4000 Tobias Burchhardt Native DTAG IO
    31 2:331/51 Marco d'Itri Native BOFH-IT
    32 1:154/30 Mike Miller Native LINODE
    33 2:5001/100 Dmitry Protasoff Native OVH
    34 2:5059/38 Andrey Mundirov T-6in4 he.net
    35 2:240/5853 Philipp Giebel Native Hetzner
    36 2:5083/444 Peter Khanin Native OVH
    37 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
    38 1:123/10 Wayne Smith T-6in4 he.net
    39 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    40 1:135/300 Eric Renfro Native Amazon.com
    41 1:103/13 Stephen Hurd Native Choopa
    42 2:5020/1042 Michael Dukelsky Native FORPSI Ktis f
    43 2:5095/0 Sergey V. Efimoff T-6in4 he.net
    44 2:5095/20 Sergey V. Efimoff T-6in4 he.net
    45 2:5019/400 Konstantin Kuzov Native LT-LT
    46 2:467/239 Mykhailo Kapitanov Native Vultr f
    47 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    48 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
    49 2:280/2000 Michael Trip Native Xs4All
    50 2:230/38 Benny Pedersen Native Linode
    51 2:460/58 Stas Mishchenkov T-6in4 he.net f
    52 2:5020/2123 Anton Samsonov T-6in4 he.net
    53 2:5020/2332 Andrey Ignatov Native ru.rtk
    54 2:5005/49 Victor Sudakov T-6in4 he.net f
    55 2:5005/77 Valery Lutoshkin T-6in4 NTS f
    56 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    57 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    58 2:5010/352 Dmitriy Smirnov Native EkranTV f
    59 2:292/854 Ward Dossche Native Proximus
    60 2:469/122 Sergey Zabolotny T-6in4 he.net f
    61 2:5053/400 Alexander Kruglikov Native Oracle f
    62 2:5030/1997 Alexey Fayans T-6in4 he.net
    63 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    64 2:2452/502 Ludwig Bernhartzeder Native DTAG
    65 2:423/39 Karel Kral Native WEDOS
    66 2:5080/102 Stas Degteff T-6to4 NOVATOR
    67 2:280/1049 Simon Voortman Native Solcon
    68 1:102/127 Bradley Thornton Native Hetzner
    69 2:335/364 Fabio Bizzi Native OVH
    70 1:124/5016 Nigel Reed Native DAL1-US f
    71 2:5075/37 Andrew Komardin Native IHC-NET
    72 1:106/633 William Williams Native LINODE-US PM *1
    73 2:263/5 Martin List-Petersen Native TuxBox
    74 2:5030/1520 Andrey Geyko T-6in4 he.net f
    75 1:229/664 Jay Harris Native Rogers
    76 1:142/103 Brian Rogers T-6in4 he.net
    77 1:134/101 Kostie Muirhead T-6in4 he.net f
    78 2:280/2030 Martien Korenblom Native Transip
    79 3:633/509 Deon George Native Telstra
    80 2:5020/4441 Yuri Myakotin Native SOVINTEL
    81 1:320/319 Andrew Leary Native Comcast f
    82 2:240/5824 Anna Christina Nass T-6in4 he.net f
    83 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
    84 1:218/401 James Downs Native ORG-TT1
    85 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
    86 2:301/812 Benoit Panizon Native WOODYV6
    87 1:229/616 Vasily Losev Native GIGEPORT
    88 2:301/113 Alisha Manuela Stutz T-6in4 he.net
    89 1:134/100 Kostie Muirhead T-6in4 he.net f
    90 1:134/101 Kostie Muirhead T-6in4 he.net f
    91 1:134/102 Shelley Petersen T-6in4 he.net f INO4
    92 1:134/103 Gordon Muirhead T-6in4 he.net f
    93 1:134/301 Brandon Moore T-6in4 he.net f INO4
    94 1:134/302 Adam Park T-6in4 he.net f
    95 1:153/7715 Dallas Hinton Native Shaw Comms
    96 1:218/840 Morgan Collins Native Linode
    97 2:5020/921 Andrew Savin T-6in4 he.net
    98 2:240/1634 Hugo Andriessen Native Vodafone
    99 2:280/2040 Leo Barnhoorn Native Ziggo
    100 2:5020/736 Egor Glukhov Native RUWEB f
    101 2:221/10 Tommi Koivula Native Hetzner f INO4
    102 1:266/420 Scott Street Native Comcast OO
    103 1:218/850 John Nicpon Native LINODE-US
    104 1:142/104 Clive Reuben Native SNETFCC-1



    T-6in4 Static 6in4
    T-AYIY Dynamic AYIYA
    T-6to4 6to4
    T-6RD 6RD

    Remarks:

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    (zone, net, node in decimal notation)
    IO Incoming only (Node can not make outgoing IPv6 calls)
    OO Outgoing only (Node can not accept incoming IPv6 calls).
    INO4 No IPv4 (Node can not accept incoming IPv4 calls).
    PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
    but is configured to try IPv4 first)
    6DWN The IPv6 connectivity of this node is temporarely down.
    NO6 The node no longer presents an IPv6 address in the nodelist
    and will soon be removed from this list.
    HOLD The node is temporarely off-line. Mail may be routed.
    DOWN This node is Down for both IPv4 and IPv6 and will be
    removed from this list if the condition pertains.
    PM Prospective Member. The node has demonstrated IPv6
    capability but is not listed or does not advertise an
    IPv6 address in the Fidonet nodelist yet.

    PM *1 [2600:3c01::f03c:91ff:fe2b:c319]


    Notes:

    To make an IPv6 connection to a node connected via 6to4 tunneling
    one may have to force the mailer into IPv6 (-6 option in binkd's
    node config for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
    and up when compiled with AF_FORCE=1). If the destination address
    is a 6to4 tunnel address (2002::/16) many OSs default to IPv4 if
    an IPv4 address is present.


    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Anna Christina Nass@2:240/5824.1 to Michiel van der Vlist on Mon Jan 3 15:45:00 2022
    Am 03.01.22 schrieb Michiel van der Vlist@2:280/5555 in IPV6:

    Hallo Michiel,

    MvdV> 82 2:240/5824 Anna Christina Nass T-6in4 he.net f

    I've switched from my he.net tunnel to the native IPv6 stack from my
    provider (Deutsche Telekom).
    As the prefix may change from time to time, I'm using the Dynv6 DynDNS service to keep track of my IPv6 prefix.
    (Before, I chose the he.net tunnel to ensure a static prefix, but I
    had more and more trouble because of GeoIP stuff for some services...)

    The BBS is reachable via the DNS Name box.imzadi.de; at the moment, it
    has the IPv6 address 2003:e9:2745:a100:f1d0:2:240:5824 :)

    Regards,
    Anna


    --- OpenXP 5.0.51
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Michiel van der Vlist@2:280/5555 to Anna Christina Nass on Mon Jan 3 17:11:09 2022
    Hello Anna,

    On Monday January 03 2022 15:45, you wrote to me:

    Hallo Michiel,

    MvdV>> 82 2:240/5824 Anna Christina Nass T-6in4 he.net f

    I've switched from my he.net tunnel to the native IPv6 stack from my provider (Deutsche Telekom).

    OK, thanks for the update. I will update the list accordingly.

    As the prefix may change from time to time, I'm using the Dynv6 DynDNS
    service to keep track of my IPv6 prefix. (Before, I chose the he.net tunnel to ensure a static prefix, but I had more and more trouble
    because of GeoIP stuff for some services...)

    A well known problem. When I used a he.net tunnel, most geolocation services positioned me in the USA, despite the POP being in Amsterdam...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Anna Christina Nass@2:240/5824.1 to Michiel van der Vlist on Mon Jan 3 20:31:00 2022
    Am 03.01.22 schrieb Michiel van der Vlist@2:280/5555 in IPV6:

    Hallo Michiel,

    I've switched from my he.net tunnel to the native IPv6 stack from my
    provider (Deutsche Telekom).

    MvdV> OK, thanks for the update. I will update the list accordingly.

    Thank you!

    [GeoIP]
    MvdV> A well known problem. When I used a he.net tunnel, most geolocation
    MvdV> services positioned me in the USA, despite the POP being in Amsterdam...

    I tried two tunnels, one in Frankfurt and one in Berlin.
    Using either tunnel, two TV streaming services and one food ordering
    service did not let me in. Now, it is working just fine...

    I even tried a website which should tell me where my IP address is
    located and one even told me I'm in Germany when using one of the
    he.net tunnels...

    This whole geolocation stuff is just meeehh...

    Regards,
    Anna

    --- OpenXP 5.0.51
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Michiel van der Vlist@2:280/5555 to Anna Christina Nass on Mon Jan 3 22:24:00 2022
    Hello Anna,

    On Monday January 03 2022 20:31, you wrote to me:

    I even tried a website which should tell me where my IP address is
    located and one even told me I'm in Germany when using one of the
    he.net tunnels...

    This whole geolocation stuff is just meeehh...

    I had no problems since I got native IPv6 fom my provider six years ago. I only had problems with the he.net tunnel.

    The SixXs tunnel gave no problems.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Anna Christina Nass@2:240/5824.1 to Michiel van der Vlist on Tue Jan 4 15:49:00 2022
    Am 03.01.22 schrieb Michiel van der Vlist@2:280/5555 in IPV6:

    Hallo Michiel,

    This whole geolocation stuff is just meeehh...

    MvdV> I had no problems since I got native IPv6 fom my provider six years ago. MvdV> I only had problems with the he.net tunnel.
    MvdV> The SixXs tunnel gave no problems.

    I did not use SixXs, but it stopped its service anyway some years ago.
    The he.net tunnel ran fine for many, many years - and I had my fixed
    prefix where I even could provide my reverse DNS for.

    The native IPv4+IPv6 connection from Telekom does work, but as it's
    only a consumer-grade connection, I don't get fixed addresses or a
    fixed prefix. But I found a workaround using Dynv6 :)

    So my router (Fritz!Box) calls a script on one of my rented vServers
    (via a https request), which in turn sets the IPv4 address and the
    IPv6 prefix on Dynv6 and on my own DNS zone. And it seems to work fine
    :)

    Regards,
    Anna

    --- OpenXP 5.0.51
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Michiel van der Vlist@2:280/5555 to Anna Christina Nass on Wed Jan 5 13:41:25 2022
    Hello Anna,

    On Tuesday January 04 2022 15:49, you wrote to me:

    MvdV>> I had no problems since I got native IPv6 fom my provider six years
    MvdV>> ago. I only had problems with the he.net tunnel. The SixXs tunnel
    MvdV>> gave no problems.

    SixXs used "local" POPs and the prefixes allocated were taken out of the block assigned to the ASN that ran the POP servers. My POP was located in Ede, just 30 km frome here. So no problems with geolocation.

    I did not use SixXs, but it stopped its service anyway some years ago.

    I used their tunnel until they stopped in june 2017.

    http://www.vlist.eu/downloads/fidonews/myarticles/sixxscls.art https://www.sixxs.net/sunset/

    The he.net tunnel ran fine for many, many years - and I had my fixed prefix where I even could provide my reverse DNS for.

    I ran the he.net tunnel in parallel with the SixXs tunnel for a couple of years.

    The native IPv4+IPv6 connection from Telekom does work, but as it's
    only a consumer-grade connection, I don't get fixed addresses or a
    fixed prefix. But I found a workaround using Dynv6 :)

    I never understood why providers still issue dynamic adresses to their customers. It made sense in the time of dial up. But now with "always on" connections...

    Anyway, I too have a dynamic IPv4 address and a dynamic IPv6 pefix. But in practice it is semi static. It does not change often enough to invest time and energy in automatic updates.

    So my router (Fritz!Box) calls a script on one of my rented vServers
    (via a https request), which in turn sets the IPv4 address and the
    IPv6 prefix on Dynv6 and on my own DNS zone. And it seems to work fine

    Good! ;-)


    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 Wed Jan 5 14:28:16 2022
    Hi Michiel,

    On 2022-01-05 13:41:25, you wrote to Anna Christina Nass:

    MvdV> I never understood why providers still issue dynamic adresses to
    MvdV> their customers. It made sense in the time of dial up. But now with
    MvdV> "always on" connections...

    So they can charge extra for static addresses?

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Björn Felten@2:203/2 to Michiel van der Vlist on Wed Jan 5 15:23:26 2022
    MvdV> So no problems with geolocation.

    I deliberately change my geolocation (VPN) to extend my various streaming services (e.g. Netflix, Prime, BBS, NRK) by a magnitude. Unfortunately I still haven't found a VPN service that handles IPv6. It'll probably take another decade or so before they catch up.



    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se (2:203/2)
  • From Richard Menedetter@2:310/31 to Michiel van der Vlist on Wed Jan 5 15:55:30 2022
    Hi Michiel!

    05 Jan 2022 13:41, from Michiel van der Vlist -> Anna Christina Nass:

    I never understood why providers still issue dynamic adresses to their customers.

    Same here.
    But I learned something.
    It seems many customers see that as a privacy enhancing thing.
    Also some services use the IP to meter free usage.
    I have heared of people that reboot their modem to get a new IP and start with 0 MB downlaoded all over ;)

    CU, Ricsi

    ... Wisdom has two parts: 1) Having a lot to say. 2) Not saying it.
    --- GoldED+/LNX
    * Origin: I post, therefore I am. (2:310/31)
  • From Alexey Vissarionov@2:5020/545 to Björn Felten on Wed Jan 5 20:02:44 2022
    Good ${greeting_time}, Bjrn!

    05 Jan 2022 15:23:26, you wrote to Michiel van der Vlist:

    MvdV>> So no problems with geolocation.
    I deliberately change my geolocation (VPN) to extend my various
    streaming services (e.g. Netflix, Prime, BBS, NRK) by a magnitude. Unfortunately I still haven't found a VPN service that handles IPv6.
    It'll probably take another decade or so before they catch up.

    If you were a really smart ass, you'd search for some cheap VPS instead.

    Just for 1 (or 2) EUR/month you may get everything you really need.


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

    ... :wq!
    --- /bin/vi
    * Origin: ::1 (2:5020/545)
  • From Anna Christina Nass@2:240/5824.1 to Michiel van der Vlist on Thu Jan 6 08:55:00 2022
    Am 05.01.22 schrieb Michiel van der Vlist@2:280/5555 in IPV6:

    Hallo Michiel,

    MvdV> I never understood why providers still issue dynamic adresses to their MvdV> customers. It made sense in the time of dial up. But now with "always MvdV> on" connections...

    I think, today it is a way to sell their 'business' rates which
    include static IPv4 and IPv6 prefix...

    MvdV> Anyway, I too have a dynamic IPv4 address and a dynamic IPv6
    MvdV> pefix. But in practice it is semi static. It does not change
    MvdV> often enough to invest time and energy in automatic updates.

    My first boss once told me: If something is to be done more than one
    time, it's worth writing a script to automate it :)
    But besides, you have to be noticed somehow that the IP/prefix has
    been changed - or how do you know when to manually update your DNS?

    Regards,
    Anna

    --- OpenXP 5.0.51
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Thu Jan 6 13:20:33 2022
    Hello Wilfred,

    On Wednesday January 05 2022 14:28, you wrote to me:

    MvdV>> I never understood why providers still issue dynamic adresses
    MvdV>> to their customers. It made sense in the time of dial up. But
    MvdV>> now with "always on" connections...

    So they can charge extra for static addresses?

    My provider (Ziggo) does not offer that. They have a Business Pro package that includes a static /29 for IPv4 and a static /48 for IPv6, but for that you need a commercial registration. (KvK nummer) They do not offer static adresses on consumer accounts. Not for money and not for free.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Anna Christina Nass on Thu Jan 6 13:10:11 2022
    Hello Anna,

    On Thursday January 06 2022 08:55, you wrote to me:

    MvdV>> I never understood why providers still issue dynamic adresses to
    MvdV>> their customers. It made sense in the time of dial up. But now
    MvdV>> with "always on" connections...

    I think, today it is a way to sell their 'business' rates which
    include static IPv4 and IPv6 prefix...

    Here that "Business Pro" package is not available without a commercial registration.

    MvdV>> Anyway, I too have a dynamic IPv4 address and a dynamic IPv6
    MvdV>> pefix. But in practice it is semi static. It does not change
    MvdV>> often enough to invest time and energy in automatic updates.

    My first boss once told me: If something is to be done more than one
    time, it's worth writing a script to automate it :)

    I see the point but I disagree with that boss of yours. If it happens twice it is still not worth to invest time and energy in automating it. Most of the time at least. Problem is of course that one generally does not know in advance how often it is going to happen. I intended to automate the DNS update, I simply never got around doing it. If it were to happen once a week, I would have done it by now, but as it is, it simply does not have priority.

    But besides, you have to be noticed somehow that the IP/prefix has
    been changed - or how do you know when to manually update your DNS?

    If my IPv6 pefix changes I notice soon enough. There is always someone in the Fidonet IPv6 club that warns me within a day. ;-)


    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 Thu Jan 6 13:45:42 2022
    Hi Michiel,

    On 2022-01-06 13:20:33, you wrote to me:

    MvdV>>> I never understood why providers still issue dynamic adresses
    MvdV>>> to their customers. It made sense in the time of dial up. But
    MvdV>>> now with "always on" connections...

    So they can charge extra for static addresses?

    MvdV> My provider (Ziggo) does not offer that. They have a Business Pro package
    MvdV> that includes a static /29 for IPv4 and a static /48 for IPv6, but for that
    MvdV> you need a commercial registration. (KvK nummer) They do not offer static
    MvdV> adresses on consumer accounts. Not for money and not for free.

    So maybe it is just to save a bit on addresses? If only 1% of customers isn't online at any give time, if you have a milion customers that is still 10000 addresses...

    And it's probably easier to "administer" dynamic addresses.

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Michiel van der Vlist@2:280/5555 to Richard Menedetter on Thu Jan 6 13:59:04 2022
    Hello Richard,

    On Wednesday January 05 2022 15:55, you wrote to me:

    Hi Michiel!

    05 Jan 2022 13:41, from Michiel van der Vlist -> Anna Christina Nass:

    I never understood why providers still issue dynamic adresses to
    their customers.

    Same here.
    But I learned something.
    It seems many customers see that as a privacy enhancing thing.

    There are so many ways to identify a user that changing IP adresses offer very little added privacy I'd say...

    Also some services use the IP to meter free usage.
    I have heared of people that reboot their modem to get a new IP and
    start with 0 MB downlaoded all over ;)

    Aha. ;-)


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Alexey Vissarionov on Thu Jan 6 14:01:20 2022
    Hello Alexey,

    On Wednesday January 05 2022 20:02, you wrote to Bjrn Felten:

    If you were a really smart ass, you'd search for some cheap VPS
    instead.

    Then I am not a smart ass. I LIKE to run my Fidonet stuff from home. With whatever I can put together to make it work.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Thu Jan 6 14:04:52 2022
    Hello Wilfred,

    On Thursday January 06 2022 13:45, you wrote to me:

    So maybe it is just to save a bit on addresses? If only 1% of
    customers isn't online at any give time, if you have a milion
    customers that is still 10000 addresses...

    1) For IPv6 it is no issue. There is no shortage on IPv6 adresses. (yet)

    2) 1% is too little for an overbooking system with a resonable margin for fluctuations. You can't just use all those 10000 adresses elsewehere, you have to leave a subsatnatial number on the shelve just in case a lot off those off-liners decide to come on-line at the same time. I don't think it is worth it with those margins.

    3) They don't do it. It I go off-line my address remains reserved for me for at least a week.

    And it's probably easier to "administer" dynamic addresses.

    Is it? With dynamic adresses they have to keep logs of who uses what address (prefix) at what time. (For law enforcement purposes).


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Tommi Koivula@2:221/1 to Michiel van der Vlist on Thu Jan 6 19:23:06 2022

    06 Jan 22 14:01, Michiel van der Vlist wrote to Alexey Vissarionov:

    Hello Alexey,

    On Wednesday January 05 2022 20:02, you wrote to Bjrn Felten:

    If you were a really smart ass, you'd search for some cheap VPS
    instead.

    Then I am not a smart ass. I LIKE to run my Fidonet stuff from home. With whatever I can put together to make it
    work.

    If you read the message thread again, you will notice that they were not talking about running fidonet stuff. They were talking about VPN.

    You can have a VPS with static /64 and run your own VPN server there. That's exactly how I have a static ipv6 address everywhere I want. For example at home to run fidonet stuff. :)

    'Tommi

    ---
    * Origin: 2a01:4f9:c011:1ec5:f1d0:2:221:1 (2:221/1)
  • From Victor Sudakov@2:5005/49 to Michiel van der Vlist on Fri Jan 7 10:32:48 2022
    Dear Michiel,

    06 Jan 22 14:04, you wrote to Wilfred van Velzen:

    So maybe it is just to save a bit on addresses? If only 1% of
    customers isn't online at any give time, if you have a milion
    customers that is still 10000 addresses...

    1) For IPv6 it is no issue. There is no shortage on IPv6 adresses.
    (yet)

    And may never happen. But a shortage on IPv6 prefixes can happen IMHO, if /48s are given away easily. There is only 35 million million (35 trillion) /48 blocks in the current global 2000::/3 pool. A trillion is not that much, I think a trillion bacteria live on 1 human person.

    Do you know if the 2000::/3 global pool can be extended if necessary?

    OTOH, we don't need an IPv6 *prefix* per each bacteria, one IPv6 *address* per bacteria is sufficient, so a /64 for each human being is more than enough.

    Victor Sudakov, VAS4-RIPE, VAS47-RIPN
    --- GoldED+/BSD 1.1.5-b20170303-b20170303
    * Origin: Ulthar (2:5005/49)
  • From Victor Sudakov@2:5005/49 to Tommi Koivula on Fri Jan 7 10:42:50 2022
    Dear Tommi,

    06 Jan 22 19:23, you wrote to Michiel van der Vlist:
    You can have a VPS with static /64 and run your own VPN server there. That's exactly how I have a static ipv6 address everywhere I want. For example at home to run fidonet stuff. :)

    I have a Vultr VPS with a static /64 on its interface. But to use it as a VPN server, you need to carve some IPv6 subnet out of this /64, how do you do it?

    Victor Sudakov, VAS4-RIPE, VAS47-RIPN
    --- GoldED+/BSD 1.1.5-b20170303-b20170303
    * Origin: Ulthar (2:5005/49)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Fri Jan 7 10:36:42 2022
    Hello Tommi,

    On Thursday January 06 2022 19:23, you wrote to me:


    Then I am not a smart ass. I LIKE to run my Fidonet stuff from
    home. With whatever I can put together to make it work.

    If you read the message thread again, you will notice that they were
    not talking about running fidonet stuff. They were talking about VPN.

    That is not how I read Alexey's message.

    You can have a VPS with static /64 and run your own VPN server there. That's exactly how I have a static ipv6 address everywhere I want. For example at home to run fidonet stuff. :)

    Ok... So you run your Fidonet server at home and you have a VPN conection to a server in a data centre. You have a /64 from the address range of the data centre and all your IPv6 traffic goes through the data centre. Yes?

    Hmm... It seems to me that the same description fits a tunnel...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Anna Christina Nass@2:240/5824.1 to Michiel van der Vlist on Fri Jan 7 11:07:00 2022
    Am 06.01.22 schrieb Michiel van der Vlist@2:280/5555 in IPV6:

    Hallo Michiel,

    I think, today it is a way to sell their 'business' rates which
    include static IPv4 and IPv6 prefix...

    MvdV> Here that "Business Pro" package is not available without a commercial MvdV> registration.

    As far as I've read, at least as a customer of Deutsche Telekom it is
    also possible to get the business packages.
    I don't know how other ISPs handle it, though.

    My first boss once told me: If something is to be done more than one
    time, it's worth writing a script to automate it :)

    MvdV> I see the point but I disagree with that boss of yours. If it happens MvdV> twice it is still not worth to invest time and energy in automating it. MvdV> Most of the time at least. Problem is of course that one generally does MvdV> not know in advance how often it is going to happen.

    Yep, that's the problem :) So I try to handle it in the way that if automating a problem is not excessively hard, I try to write a script
    if I probably have to solve a problem several times.

    But besides, you have to be noticed somehow that the IP/prefix has
    been changed - or how do you know when to manually update your DNS?

    MvdV> If my IPv6 pefix changes I notice soon enough. There is always someone MvdV> in the Fidonet IPv6 club that warns me within a day. ;-)

    Okay, so it can happen that your IPv6 connection isn't reachable for
    some time (via DNS). So it's good that IPv4 is still working :)

    Regards,
    Anna

    --- OpenXP 5.0.51
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Tommi Koivula@2:221/360 to Victor Sudakov on Fri Jan 7 12:49:57 2022

    07 Jan 22 10:42, Victor Sudakov wrote to Tommi Koivula:

    You can have a VPS with static /64 and run your own VPN server
    there. That's exactly how I have a static ipv6 address everywhere
    I want. For example at home to run fidonet stuff. :)

    I have a Vultr VPS with a static /64 on its interface. But to use it
    as a VPN server, you need to carve some IPv6 subnet out of this /64,
    how do you do it?

    I have a wireguard server running in my VPS (Ubuntu 20.04.3 LTS). It is using a /112 of /64 for it's clients.

    'Tommi

    ---
    * Origin: =========================>>>> (2:221/360)
  • From Tommi Koivula@2:221/360 to Michiel van der Vlist on Fri Jan 7 12:54:30 2022

    07 Jan 22 10:36, Michiel van der Vlist wrote to Tommi Koivula:

    Then I am not a smart ass. I LIKE to run my Fidonet stuff from
    home. With whatever I can put together to make it work.

    If you read the message thread again, you will notice that they
    were not talking about running fidonet stuff. They were talking
    about VPN.

    That is not how I read Alexey's message.

    Ok. Alexey may correct me if I misundertood him.

    You can have a VPS with static /64 and run your own VPN server
    there. That's exactly how I have a static ipv6 address everywhere
    I want. For example at home to run fidonet stuff. :)

    Ok... So you run your Fidonet server at home and you have a VPN
    conection to a server in a data centre. You have a /64 from the
    address range of the data centre and all your IPv6 traffic goes
    through the data centre. Yes?

    No. That was just an example. But I could do my home fidonet that way.

    Hmm... It seems to me that the same description fits a tunnel...

    Of course VPN (virtual private network) is a tunnel. :D

    'Tommi

    ---
    * Origin: ==========================>>> (2:221/360)
  • From Alexey Vissarionov@2:5020/545 to Michiel van der Vlist on Fri Jan 7 14:44:44 2022
    Good ${greeting_time}, Michiel!

    07 Jan 2022 10:36:42, you wrote to Tommi Koivula:

    Then I am not a smart ass. I LIKE to run my Fidonet stuff from
    home. With whatever I can put together to make it work.
    If you read the message thread again, you will notice that they
    were not talking about running fidonet stuff. They were talking
    about VPN.
    MvdV> That is not how I read Alexey's message.

    Running the Fidonet node is not (and can not ever be) restricted by GeoIP services.

    You can have a VPS with static /64 and run your own VPN server
    there. That's exactly how I have a static ipv6 address everywhere
    I want. For example at home to run fidonet stuff. :)
    MvdV> Ok... So you run your Fidonet server at home and you have a VPN

    Avoiding use of well-known VPNs is a good (though uncommon) practice.

    MvdV> conection to a server in a data centre. You have a /64 from the
    MvdV> address range of the data centre

    Yes. Or several addresses from different ASes.

    MvdV> and all your IPv6 traffic goes through the data centre. Yes?

    s/ all/, when necessary,/

    MvdV> Hmm... It seems to me that the same description fits a tunnel...

    Or several tunnels.


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

    ... GPG: 8832FE9FA791F7968AC96E4E909DAC45EF3B1FA8 @ hkp://keys.gnupg.net
    --- /bin/vi
    * Origin: ::1 (2:5020/545)
  • From Dmitry Protasoff@2:5001/100.1 to Michiel van der Vlist on Sat Jan 8 03:15:26 2022
    Hello, Michiel!

    Thursday January 06 2022 14:01, you wrote to Alexey Vissarionov:

    If you were a really smart ass, you'd search for some cheap VPS
    instead.

    Then I am not a smart ass. I LIKE to run my Fidonet stuff from home.
    With whatever I can put together to make it work.

    Alexey is a well-known troll/abuser, please ignore his rude comments.
    I am using VPN to get ipv6 connectivity (the same VPN is used to place myself in Luxembourg for many external services) and it works perfectly.

    Best regards,
    dp.

    --- GoldED+/W64-MSVC 1.1.5-b20180707
    * Origin: No rest for the wicked (2:5001/100.1)
  • From Victor Sudakov@2:5005/49 to Tommi Koivula on Sat Jan 8 12:40:08 2022
    Dear Tommi,

    07 Jan 22 12:49, you wrote to me:

    You can have a VPS with static /64 and run your own VPN server
    there. That's exactly how I have a static ipv6 address
    everywhere I want. For example at home to run fidonet stuff. :)

    I have a Vultr VPS with a static /64 on its interface. But to use
    it as a VPN server, you need to carve some IPv6 subnet out of
    this /64, how do you do it?

    I have a wireguard server running in my VPS (Ubuntu 20.04.3 LTS). It
    is using a /112 of /64 for it's clients.

    Do you mean to say you can have a /64 network on your VPS' main interface and at the same time a /112 from the *same* *network* on a wg0 interface?
    Is this even permitted by the OS?

    Victor Sudakov, VAS4-RIPE, VAS47-RIPN
    --- GoldED+/BSD 1.1.5-b20170303-b20170303
    * Origin: Ulthar (2:5005/49)
  • From Alexey Vissarionov@2:5020/545 to Victor Sudakov on Sat Jan 8 09:29:00 2022
    Good ${greeting_time}, Victor!

    08 Jan 2022 12:40:08, you wrote to Tommi Koivula:

    I have a wireguard server running in my VPS (Ubuntu 20.04.3 LTS).
    It is using a /112 of /64 for it's clients.
    Do you mean to say you can have a /64 network on your VPS' main
    interface and at the same time a /112 from the *same* *network*
    on a wg0 interface? Is this even permitted by the OS?

    Yes - at least properly configured Linux allows this.


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

    ... god@universe:~ # cvs up && make world
    --- /bin/vi
    * Origin: ::1 (2:5020/545)
  • From Victor Sudakov@2:5005/49 to Alexey Vissarionov on Sat Jan 8 13:48:30 2022
    Dear Alexey,

    08 Jan 22 09:29, you wrote to me:
    I have a wireguard server running in my VPS (Ubuntu 20.04.3
    LTS). It is using a /112 of /64 for it's clients.
    Do you mean to say you can have a /64 network on your VPS' main
    interface and at the same time a /112 from the *same* *network*
    on a wg0 interface? Is this even permitted by the OS?

    Yes - at least properly configured Linux allows this.

    What do you mean by "properly configured"? You mean the out-of-the-box configuration still does not allow this?

    A Cisco router would not allow the same L2 network on two different L3 interfaces IMHO, even if one of the prefixes is more specific. If it would, how should it know whether the destination is behind a gateway or can be reached by ARP/NDP?

    Victor Sudakov, VAS4-RIPE, VAS47-RIPN
    --- GoldED+/BSD 1.1.5-b20170303-b20170303
    * Origin: Ulthar (2:5005/49)
  • From Tommi Koivula@2:221/1 to Victor Sudakov on Sat Jan 8 10:05:24 2022

    08 Jan 22 12:40, Victor Sudakov wrote to Tommi Koivula:

    You can have a VPS with static /64 and run your own VPN server
    there. That's exactly how I have a static ipv6 address
    everywhere I want. For example at home to run fidonet stuff. :)

    I have a Vultr VPS with a static /64 on its interface. But to use
    it as a VPN server, you need to carve some IPv6 subnet out of
    this /64, how do you do it?

    I have a wireguard server running in my VPS (Ubuntu 20.04.3 LTS). It
    is using a /112 of /64 for it's clients.

    Do you mean to say you can have a /64 network on your VPS' main interface and at the same time a /112 from the
    *same* *network* on a wg0 interface?

    Yes.

    Is this even permitted by the OS?

    Seems so. :) I am no linux expert, but that's how I got it working. :)

    'Tommi

    ---
    * Origin: 2a01:4f9:c011:1ec5:f1d0:2:221:1 (2:221/1)
  • From Michiel van der Vlist@2:280/5555 to Anna Christina Nass on Sat Jan 8 11:40:13 2022
    Hello Anna,

    On Friday January 07 2022 11:07, you wrote to me:

    I think, today it is a way to sell their 'business' rates which
    include static IPv4 and IPv6 prefix...

    MvdV>> Here that "Business Pro" package is not available without a
    MvdV>> commercial registration.

    As far as I've read, at least as a customer of Deutsche Telekom it is
    also possible to get the business packages. I don't know how other
    ISPs handle it, though.

    It is up to the ISP how they deal with it. Point is that even if you could get the Business Pro package without a commercial registration, it is still not just "paying extra for the fixed IP". You get a lot more, like support guaranteed within a certain time frame etc, end you pay for that. A lot...

    But besides, you have to be noticed somehow that the IP/prefix
    has been changed - or how do you know when to manually update
    your DNS?

    MvdV>> If my IPv6 pefix changes I notice soon enough. There is always
    MvdV>> someone in the Fidonet IPv6 club that warns me within a day. ;-)

    Okay, so it can happen that your IPv6 connection isn't reachable for
    some time (via DNS). So it's good that IPv4 is still working :)

    Indeed, it occasionally happens that my IPv6 is down for a couple of hours or so. It also occasiaonally happens that my system is completely down for a couple of hours. This is a hobby system. I do maintenance once in a while and there the occasional power failure.

    If I still had a business and it depended on my servers being 24/7 on line, I would take measures. As it is, I do not consider it an issue for a hobby system...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Sat Jan 8 11:49:58 2022
    Hello Tommi,

    On Friday January 07 2022 12:54, you wrote to me:

    Hmm... It seems to me that the same description fits a tunnel...

    Of course VPN (virtual private network) is a tunnel. :D

    And so you have the same geolocation issues...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Alexey Vissarionov on Sat Jan 8 11:52:03 2022
    Hello Alexey,

    On Friday January 07 2022 14:44, you wrote to me:

    Running the Fidonet node is not (and can not ever be) restricted by
    GeoIP services.

    At least I have not heard of such problems yet.

    But the world of IPv6 is bigger than Fidonet.

    MvdV>> Hmm... It seems to me that the same description fits a
    MvdV>> tunnel...

    Or several tunnels.

    My point exactly.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Anna Christina Nass@2:240/5824.1 to Michiel van der Vlist on Sat Jan 8 16:09:00 2022
    Am 08.01.22 schrieb Michiel van der Vlist@2:280/5555 in IPV6:

    Hallo Michiel,

    MvdV> It is up to the ISP how they deal with it. Point is that even if you MvdV> could get the Business Pro package without a commercial registration, it MvdV> is still not just "paying extra for the fixed IP". You get a lot more, MvdV> like support guaranteed within a certain time frame etc, end you pay for MvdV> that. A lot...

    Same here. Although how much of "a lot" it costs more depends on the
    speed and other extras that you wish to have.
    Basically a 50 MBit/s (downstream) / 10 MBit/s (upstream) is around
    40 EUR/month for consumers and around 52 EUR/month for business
    customers.

    Okay, so it can happen that your IPv6 connection isn't reachable for
    some time (via DNS). So it's good that IPv4 is still working :)

    MvdV> Indeed, it occasionally happens that my IPv6 is down for a couple of MvdV> hours or so. It also occasiaonally happens that my system is completely MvdV> down for a couple of hours. This is a hobby system. I do maintenance MvdV> once in a while and there the occasional power failure.

    Same here. The IPv6 connection for my BBS also had problems on friday
    because Dynv6 'forgot' the AAAA record that I've configured - but it
    seems to be a known problem. Maybe I rewrite the update script (and
    recreate the AAAA record on every prefix change) or switch to my own
    dyndns solution...

    And in the near future, my BBS will also be down due to a Synchronet update...

    MvdV> If I still had a business and it depended on my servers being 24/7 on MvdV> line, I would take measures. As it is, I do not consider it an issue for MvdV> a hobby system...

    That's true, indeed.

    Regards,
    Anna

    --- OpenXP 5.0.51
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Tommi Koivula@2:221/1 to Michiel van der Vlist on Sat Jan 8 17:26:11 2022
    On 8.1.2022 12:49, Michiel van der Vlist wrote:


    Hmm... It seems to me that the same description fits a tunnel...

    Of course VPN (virtual private network) is a tunnel. :D

    And so you have the same geolocation issues...

    What issues? I'm not following you now... I have no geolocation issues
    with the vpn server located in Finland.

    The he.net tunnel to Amsterdam causes websites to speak dutch to me, but
    I'm not using that tunnel for web.

    'Tommi

    ---
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)
  • From Björn Felten@2:203/2 to Anna Christina Nass on Sat Jan 8 21:44:03 2022
    Basically a 50 MBit/s (downstream) / 10 MBit/s (upstream) is around
    40 EUR/month for consumers

    WOW! That's a lot. I pay EUR40 per month for my 100/100. A 50/10 fiber costs less than EUR20 here in Sweden. And we are a loooong country, with a lot of rural space, we need long fibres. :)



    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se (2:203/2)
  • From Michiel van der Vlist@2:280/5555 to Victor Sudakov on Sun Jan 9 00:03:27 2022
    Hello Victor,

    On Friday January 07 2022 10:32, you wrote to me:

    Do you know if the 2000::/3 global pool can be extended if necessary?

    Sure. When 2000::/3 runs out, there is 4000::/3. And when that runs out, there is 6000::/3. Up until c000::/3.

    I do not expect to live to see that happen.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Sun Jan 9 00:05:31 2022
    Hello Tommi,

    On Saturday January 08 2022 17:26, you wrote to me:

    Of course VPN (virtual private network) is a tunnel. :D

    And so you have the same geolocation issues...

    What issues? I'm not following you now... I have no geolocation issues with the vpn server located in Finland.

    I was using "you" in the general sense, not meaning you personal.

    The he.net tunnel to Amsterdam causes websites to speak dutch to me,
    but I'm not using that tunnel for web.

    Understood.

    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Victor Sudakov@2:5005/49 to Michiel van der Vlist on Sun Jan 9 13:00:06 2022
    Dear Michiel,

    09 Jan 22 00:03, you wrote to me:

    Do you know if the 2000::/3 global pool can be extended if
    necessary?

    Sure. When 2000::/3 runs out, there is 4000::/3. And when that runs
    out, there is 6000::/3. Up until c000::/3.

    That's great news!

    I do not expect to live to see that happen.

    Things do happen. We may reach a technological singularity where every AI will request a /48 for itself and its minions, for example.

    Victor Sudakov, VAS4-RIPE, VAS47-RIPN
    --- GoldED+/BSD 1.1.5-b20170303-b20170303
    * Origin: Ulthar (2:5005/49)
  • From Alexey Vissarionov@2:5020/545 to Victor Sudakov on Sun Jan 9 09:21:00 2022
    Good ${greeting_time}, Victor!

    08 Jan 2022 13:48:30, you wrote to me:

    I have a wireguard server running in my VPS (Ubuntu 20.04.3
    LTS). It is using a /112 of /64 for it's clients.
    Do you mean to say you can have a /64 network on your VPS' main
    interface and at the same time a /112 from the *same* *network*
    on a wg0 interface? Is this even permitted by the OS?
    Yes - at least properly configured Linux allows this.
    What do you mean by "properly configured"? You mean the
    out-of-the-box configuration still does not allow this?

    Obviously.

    A Cisco router would not allow the same L2 network on two different
    L3 interfaces IMHO, even if one of the prefixes is more specific.

    That's a limitation of BSD-style IP stack.


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

    ... GPG: 8832FE9FA791F7968AC96E4E909DAC45EF3B1FA8 @ hkp://keys.gnupg.net
    --- /bin/vi
    * Origin: ::1 (2:5020/545)
  • From Alexey Vissarionov@2:5020/545 to Björn Felten on Sun Jan 9 09:28:28 2022
    Good ${greeting_time}, Bjrn!

    08 Jan 2022 21:44:02, you wrote to Anna Christina Nass:

    Basically a 50 MBit/s (downstream) / 10 MBit/s (upstream) is around
    40 EUR/month for consumers
    WOW! That's a lot. I pay EUR40 per month for my 100/100.

    Pffff... 500 RUB (approx. 6 EUR) for 500 Mbps.

    A 50/10 fiber costs less than EUR20 here in Sweden.

    Asymmetric? Why?

    And we are a loooong country, with a lot of rural space, we need long fibres. :)

    Slightly less than 1600 km. We are 6 times loooooooooooooooooooooooonger :-)


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

    ... that's why I really dislike fools.
    --- /bin/vi
    * Origin: ::1 (2:5020/545)
  • From Victor Sudakov@2:5005/49 to Alexey Vissarionov on Sun Jan 9 14:03:50 2022
    Dear Alexey,

    09 Jan 22 09:21, you wrote to me:

    I have a wireguard server running in my VPS (Ubuntu 20.04.3
    LTS). It is using a /112 of /64 for it's clients.
    Do you mean to say you can have a /64 network on your VPS' main
    interface and at the same time a /112 from the *same* *network*
    on a wg0 interface? Is this even permitted by the OS?
    Yes - at least properly configured Linux allows this.
    What do you mean by "properly configured"? You mean the
    out-of-the-box configuration still does not allow this?

    Obviously.

    What do you need to configure to enable this behaviour on Linux?

    A Cisco router would not allow the same L2 network on two
    different L3 interfaces IMHO, even if one of the prefixes is more
    specific.

    That's a limitation of BSD-style IP stack.

    Interestingly enough, FreeBSD 12.3 has just let me do exactly that (sorry, an IPv4 example), without any additional configuration. The world is full of wonders:

    root@vas:~ # apply ifconfig lo{2,3}
    lo2: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
    options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
    inet 192.168.13.1/24
    groups: lo
    nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
    lo3: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
    options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
    inet 192.168.13.129/25
    groups: lo
    nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
    root@vas:~ #
    root@vas:~ # apply 'route get ' 192.168.13.2 192.168.13.200
    route to: 192.168.13.2
    destination: 192.168.13.0
    mask: 255.255.255.0
    fib: 0
    interface: lo2
    flags: <UP,DONE,PROTO1>
    recvpipe sendpipe ssthresh rtt,msec mtu weight expire
    0 0 0 0 16384 1 0

    route to: 192.168.13.200
    destination: 192.168.13.128
    mask: 255.255.255.128
    fib: 0
    interface: lo3
    flags: <UP,DONE,PROTO1>
    recvpipe sendpipe ssthresh rtt,msec mtu weight expire
    0 0 0 0 16384 1 0
    root@vas:~ #



    Victor Sudakov, VAS4-RIPE, VAS47-RIPN
    --- GoldED+/BSD 1.1.5-b20170303-b20170303
    * Origin: Ulthar (2:5005/49)
  • From Tommi Koivula@2:221/360 to Alexey Vissarionov on Sun Jan 9 21:15:17 2022
    On 9.1.2022 8:28, Alexey Vissarionov wrote:

    A 50/10 fiber costs less than EUR20 here in Sweden.

    Asymmetric? Why?

    Maybe the cheap solution: Only one fiber; downstream and upstream on
    different wavelengths.

    'Tommi

    ---
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Sun Jan 9 21:18:00 2022
    Hello Tommi,

    On Sunday January 09 2022 21:15, you wrote to Alexey Vissarionov:

    A 50/10 fiber costs less than EUR20 here in Sweden.

    Asymmetric? Why?

    Maybe the cheap solution: Only one fiber; downstream and upstream on different wavelengths.

    That's no reason for asymetry. Here Delta Fiber will give me two fibers to the PON, but only one is used. Max 8GB up and down on the same fiber, different wavelength. XSGPON technology. The second fiber is the spare, or to be used by a third party.

    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Alexey Vissarionov@2:5020/545 to Tommi Koivula on Mon Jan 10 12:00:00 2022
    Good ${greeting_time}, Tommi!

    09 Jan 2022 21:15:16, you wrote to me:

    A 50/10 fiber costs less than EUR20 here in Sweden.
    ^^^^^^^
    Who had screwed the quoting? This line is not written by me.

    Asymmetric? Why?
    Maybe the cheap solution: Only one fiber; downstream and upstream
    on different wavelengths.

    Yes, but this technology is symmetric.


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

    ... GPG: 8832FE9FA791F7968AC96E4E909DAC45EF3B1FA8 @ hkp://keys.gnupg.net
    --- /bin/vi
    * Origin: ::1 (2:5020/545)
  • From Björn Felten@2:203/2 to Alexey Vissarionov on Mon Jan 10 10:55:05 2022
    Maybe the cheap solution: Only one fiber; downstream and upstream
    on different wavelengths.

    (I agree with Alexey, the above quote looks like shit, what crappy abandonware is responsible for this?)

    The signal is already encoded via a multitude of frequencies and of course light can travel in both directions at the same time, so no, that's not the reason. Nota bene, it's the same fiber and equipment, just different speeds at very different cost, I can change it any time without any hardware changes.

    Yes, but this technology is symmetric.

    I agree. The only reason I can figure out, is that some ISPs don't want people to run servers, they want their customers to buy their contents (usually lots of encoded TV channels).

    One package offered by Telia (the former government owned TelCo in Sweden) costs EUR 60 per month, 12 month binding time, for just the content -- the fiber not included.

    So they pretend that it's still ADSL technique, that many customers started with in the early internet days?



    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se (2:203/2)
  • From Björn Felten@2:203/2 to Björn Felten on Mon Jan 10 10:57:41 2022
    Maybe the cheap solution: Only one fiber; downstream and upstream
    on different wavelengths.

    (I agree with Alexey, the above quote looks like shit, what crappy abandonware is responsible for this?)

    Oops, Thunderbird managed to correct it? It looked like crap in Alexeys comment, but in my it looked OK. Strange...



    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se (2:203/2)
  • From Anna Christina Nass@2:240/5824.1 to Björn Felten on Mon Jan 10 13:21:00 2022
    Am 08.01.22 schrieb Bjrn Felten@2:203/2 in IPV6:

    Hallo Bjrn,

    Basically a 50 MBit/s (downstream) / 10 MBit/s (upstream) is around
    40 EUR/month for consumers

    WOW! That's a lot. I pay EUR40 per month for my 100/100. A 50/10 fiber costs less than EUR20 here in Sweden. And we are a loooong country, with a lot of rural space, we need long fibres. :)

    Well, here in Germany, we screwed up so many things up concerning telecommunications, and now we have to pay the price.
    (In the 80s, because of "personal interests" of some politicians,
    copper cables were preferred over fiber and a nationwide cable TV
    system was established. Phone cables also stayed in copper, but at
    least the system went digital (ISDN).
    After the counter-revolution in the GDR and after we bought the
    country, the phone system in east Germany was rebuilt using fiber, but
    later we had to add copper for DSL (as the fiber technology was
    different from the newer one) instead of updating the fiber tech.
    As everything had been privatized, this was logical as it was cheaper
    in the current quarter...
    And the mobile phone frequencies that were auctioned from the state
    were really expensive, so that also counts on the price tag of
    everything in the telco business...)

    Oh, and my connection isn't fiber, but copper DSL.
    I don't know if fiber is even available here...

    In another part of the city, the municipal services are searching for
    fiber (FTTH) clients, but it also won't be cheap and you'll only get a
    "dual stack lite" connection :-(

    Regards,
    Anna

    --- OpenXP 5.0.51
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Michiel van der Vlist@2:280/5555 to Anna Christina Nass on Mon Jan 10 13:34:44 2022
    Hello Anna,

    On Saturday January 08 2022 16:09, you wrote to me:

    MvdV>> It is up to the ISP how they deal with it. Point is that even if
    MvdV>> you could get the Business Pro package without a commercial
    MvdV>> registration, it is still not just "paying extra for the fixed
    MvdV>> IP". You get a lot more, like support guaranteed within a
    MvdV>> certain time frame etc, end you pay for that. A lot...

    Same here. Although how much of "a lot" it costs more depends on the
    speed and other extras that you wish to have.

    But that is the thing: I do not want/need the speed and other extras and so I do not want to pat for it. I would perhaps pay a small fee for just a fixed IP, but that is not offered.

    Same here. The IPv6 connection for my BBS also had problems on friday because Dynv6 'forgot' the AAAA record that I've configured - but it
    seems to be a known problem. Maybe I rewrite the update script (and recreate the AAAA record on every prefix change) or switch to my own dyndns solution...

    We patiently wait... ;-)

    Please share your experience with us.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Victor Sudakov on Mon Jan 10 13:39:17 2022
    Hello Victor,

    On Sunday January 09 2022 13:00, you wrote to me:


    Sure. When 2000::/3 runs out, there is 4000::/3. And when that
    runs out, there is 6000::/3. Up until c000::/3.

    That's great news!

    It is not really news I'd say. Ans I suppose when push come to shove 1000::/4 coild also be used. And even 0::/4 with the exeption of 0::/64.

    I do not expect to live to see that happen.

    Things do happen. We may reach a technological singularity where every
    AI will request a /48 for itself and its minions, for example.

    Many ISPs only offer a /48 to business accounts. For consumer accounts it is often a /56. A /56 is plenty for most I'd say.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Anna Christina Nass on Mon Jan 10 13:47:40 2022
    Hello Anna,

    On Monday January 10 2022 13:21, you wrote to Bjrn Felten:

    In another part of the city, the municipal services are searching for
    fiber (FTTH) clients, but it also won't be cheap and you'll only get
    a "dual stack lite" connection :-(

    That should be no surprise. The Intenet has de facto run out of IPv4 adresses ten years ago. For years I have been saying that DS-Lite is unavoidable in the long run. There just aren't enough IPv4 adresses left for everyone and so we will reach a point where "normal" users will not get an IPv4 address all for themselves. IPv4 adresses will only be available for those demonstrating teh need for them. An effective way to demenostrate need is willingness to pay for it...

    We - sysops of an amateur network - will have to learn to do without a globaly routable IPv4 address. I have demonstrated that we can. I published my findings in Fidonews.

    http://www.vlist.eu/downloads/fidonews/myarticles/dsltxp.art

    http://www.vlist.eu/downloads/fidonews/myarticles/dsltsol.art

    http://www.vlist.eu/downloads/fidonews/myarticles/dsltxp2.art

    http://www.vlist.eu/downloads/fidonews/myarticles/dsltxpr2.art

    http://www.vlist.eu/downloads/fidonews/myarticles/dsltxp21.art

    Enjoy.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Richard Menedetter@2:310/31 to Michiel van der Vlist on Mon Jan 10 14:38:18 2022
    Hi Michiel!

    10 Jan 2022 13:39, from Michiel van der Vlist -> Victor Sudakov:

    Many ISPs only offer a /48 to business accounts. For consumer accounts
    it is often a /56. A /56 is plenty for most I'd say.

    Or a /64 for residential.
    And you don't have to fuss around with how to subnet.
    The CPE simply announces the IPv6 net on the LAN side and you are done ;)

    CU, Ricsi

    ... Conscience is what hurts when everything else feels so good.
    --- GoldED+/LNX
    * Origin: Haggis - Gaelic for Spam. (2:310/31)
  • From Michiel van der Vlist@2:280/5555 to Richard Menedetter on Mon Jan 10 14:59:46 2022
    Hello Richard,

    On Monday January 10 2022 14:38, you wrote to me:

    Many ISPs only offer a /48 to business accounts. For consumer
    accounts it is often a /56. A /56 is plenty for most I'd say.

    Or a /64 for residential.
    And you don't have to fuss around with how to subnet.
    The CPE simply announces the IPv6 net on the LAN side and you are done
    ;)

    Just one /64 would not be satisfactory to me. As it is I already have three subnets in use. One for the stuff on the normal LAN, one for the guest network and one for the sandbox.

    I think a /60 is the minimum.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Björn Felten@2:203/2 to Michiel van der Vlist on Mon Jan 10 15:48:57 2022
    MvdV> Just one /64 would not be satisfactory to me.

    Doesn't a /64 contain 2^64 addresses? Not enough? The entire IPv4 pool is 2^32...



    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se (2:203/2)
  • From Michiel van der Vlist@2:280/5555 to Björn Felten on Mon Jan 10 16:06:26 2022
    Hello Bjrn,

    On Monday January 10 2022 15:48, you wrote to me:

    MvdV>> Just one /64 would not be satisfactory to me.

    Doesn't a /64 contain 2^64 addresses? Not enough? The entire IPv4
    pool is 2^32...

    It is not that 2^64 addresses are not enough for all my devices, it is that a /64 can not be divided into subnets. That is the way it is designed. A /64 is the smallest subnet. I might have designed it different but I was not involved at the time.

    So... if one wants/needs more than one subnet, one needs more than one /64. That is the way it is.

    It should be no problem, there is enough for everyone.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Alexey Vissarionov@2:5020/545 to Michiel van der Vlist on Mon Jan 10 19:12:34 2022
    Good ${greeting_time}, Michiel!

    10 Jan 2022 16:06:26, you wrote to Bjrn Felten:

    MvdV>>> Just one /64 would not be satisfactory to me.
    Doesn't a /64 contain 2^64 addresses? Not enough? The entire IPv4
    pool is 2^32...
    MvdV> It is not that 2^64 addresses are not enough for all my devices,
    MvdV> it is that a /64 can not be divided into subnets.

    [Top-secret, burn before reading!]
    It can.

    And on my early experiments, when the /64 was the only block I had, that was really great.

    MvdV> That is the way it is designed. A /64 is the smallest subnet.

    No. The /64 is the default subnet size, and people normally SHOULD NOT (as in FTA-1006) split these blocks further, but that IS possible and NOT prohibited.

    MvdV> I might have designed it different but I was not involved at
    MvdV> the time.

    IPv6 is not that strict as, for example, IPX was.

    MvdV> So... if one wants/needs more than one subnet, one needs more than
    MvdV> one /64. That is the way it is. It should be no problem, there is
    MvdV> enough for everyone.

    Here in Russia the de-facto standard is one MAC-based IPv6 address for the outer-side link and /64 subnet routed via that address to the customer's LAN. Additional subnets may be requested as well, but ISP admins say most people don't request them.


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

    ... GPG: 8832FE9FA791F7968AC96E4E909DAC45EF3B1FA8 @ hkp://keys.gnupg.net
    --- /bin/vi
    * Origin: ::1 (2:5020/545)
  • From deon@3:633/509 to Michiel van der Vlist on Tue Jan 11 10:00:58 2022
    Re: List of IPv6 nodes
    By: Michiel van der Vlist to Bjrn Felten on Mon Jan 10 2022 04:06 pm

    designed. A /64 is the smallest subnet. I might have designed it different but I was not involved at the time.

    So... if one wants/needs more than one subnet, one needs more than one /64. That is the way it is.

    Sure it can!

    I use /80's a lot, which in reality could be /96's but I'm being generous to the network that I use the /80's on.

    Certainly, having a /64 is "simplier" - its, in many cases, no configuration required (or minimal "enabling" in your router). But anything smaller, its pretty much manual.


    ...
    --- SBBSecho 3.14-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)
  • From Anna Christina Nass@2:240/5824.1 to Michiel van der Vlist on Tue Jan 11 10:21:00 2022
    Am 10.01.22 schrieb Michiel van der Vlist@2:280/5555 in IPV6:

    Hallo Michiel,

    In another part of the city, the municipal services are searching for
    fiber (FTTH) clients, but it also won't be cheap and you'll only get
    a "dual stack lite" connection :-(

    MvdV> That should be no surprise. The Intenet has de facto run out of IPv4 MvdV> adresses ten years ago.

    Yep, I know :) And thus the 'newer' ISPs don't had the chance to get
    enough IPv4 addresses for all new customers, while 'older' ISPs (like Deutsche Telekom in my case) have bigger IPv4 address pools.

    MvdV> For years I have been saying that DS-Lite is unavoidable in the
    MvdV> long run.

    Correct.
    But as long as IPv6 is not the default case for accessing the
    Internet, I still want to have a 'real' IPv4 address to be able to
    access my home devices from the Internet.
    And in my case, I don't have IPv6 at work, for example.
    But all my (own, private) servers do have IPv6 enabled and reachable
    for years now (and I also have the IPv6 T-Shirt from he.net *g*), so
    at least I'm prepared :)

    Regards,
    Anna

    --- OpenXP 5.0.51
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Anna Christina Nass@2:240/5824.1 to Michiel van der Vlist on Tue Jan 11 10:24:00 2022
    Am 10.01.22 schrieb Michiel van der Vlist@2:280/5555 in IPV6:

    Hallo Michiel,

    Same here. Although how much of "a lot" it costs more depends on the
    speed and other extras that you wish to have.

    MvdV> But that is the thing: I do not want/need the speed and other extras and MvdV> so I do not want to pat for it. I would perhaps pay a small fee for just MvdV> a fixed IP, but that is not offered.

    Same here. That's the reason I 'only' have a 50/10 MBit/s connection
    and not 100 (40 up? don't remember..) or maybe more.
    And I also would pay extra for a fixed IP, or at least a fixed
    prefix...

    Same here. The IPv6 connection for my BBS also had problems on friday
    because Dynv6 'forgot' the AAAA record that I've configured - but it
    seems to be a known problem. Maybe I rewrite the update script (and
    recreate the AAAA record on every prefix change) or switch to my own
    dyndns solution...

    MvdV> We patiently wait... ;-)
    MvdV> Please share your experience with us.

    I'll do that :)
    At the moment, the AAAA that I've manually configured some days ago is
    still present.

    Regards,
    Anna

    --- OpenXP 5.0.51
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Michiel van der Vlist@2:280/5555 to Alexey Vissarionov on Wed Jan 12 15:21:30 2022
    Hello Alexey,

    On Monday January 10 2022 19:12, you wrote to me:

    MvdV>> It is not that 2^64 addresses are not enough for all my
    MvdV>> devices, it is that a /64 can not be divided into subnets.

    [Top-secret, burn before reading!]

    Done. But thanks to the Fidoweb, I have a copy. ;-)

    And on my early experiments, when the /64 was the only block I had,
    that was really great.

    Yes, now that you mention it, I remember yuo experimenting with dividing a /64 into 32 bit subnets.

    MvdV>> That is the way it is designed. A /64 is the smallest subnet.

    No. The /64 is the default subnet size, and people normally SHOULD NOT
    (as in FTA-1006) split these blocks further, but that IS possible and
    NOT prohibited.

    OK, so I stand corrected, it is possible.

    But many things won't work any more. SLAAC comes to mind.

    So one /should/ avoid it.

    At first glance one would say: a /64? what a waste! But keep in mind that "waste" is only a problem when there is a shortage. "Waste and shortage" is IPv4 think.

    MvdV>> So... if one wants/needs more than one subnet, one needs more
    MvdV>> than one /64. That is the way it is. It should be no problem,
    MvdV>> there is enough for everyone.

    Here in Russia the de-facto standard is one MAC-based IPv6 address for
    the outer-side link and /64 subnet routed via that address to the customer's LAN. Additional subnets may be requested as well, but ISP admins say most people don't request them.

    So most people in Russia do not need more than one subnet....


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to deon on Wed Jan 12 15:28:52 2022
    Hello deon,

    On Tuesday January 11 2022 10:00, you wrote to me:

    So... if one wants/needs more than one subnet, one needs more than
    one /64. That is the way it is.

    Sure it can!

    Yes, Alexey already corrected me.

    I use /80's a lot, which in reality could be /96's but I'm being
    generous to the network that I use the /80's on.

    But why? When you can have enough space to make /64 subnets?

    Certainly, having a /64 is "simplier" - its, in many cases, no configuration required (or minimal "enabling" in your router). But anything smaller, its pretty much manual.

    And some thing will not work any more.

    BTW, this is a real name echo, please use your full real name when posting here. Thank you for your cooperation.

    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Anna Christina Nass on Wed Jan 12 17:38:35 2022
    Hello Anna,

    On Tuesday January 11 2022 10:21, you wrote to me:

    MvdV>> That should be no surprise. The Intenet has de facto run out of
    MvdV>> IPv4 adresses ten years ago.

    Yep, I know :) And thus the 'newer' ISPs don't had the chance to get enough IPv4 addresses for all new customers, while 'older' ISPs (like
    Deutsche Telekom in my case) have bigger IPv4 address pools.

    The "newer" ISP have problems, but with some old the older ISPs the bottom of the IPv4 treasure hold is also in sight.

    MvdV>> For years I have been saying that DS-Lite is unavoidable in the
    MvdV>> long run.

    Correct.
    But as long as IPv6 is not the default case for accessing the
    Internet, I still want to have a 'real' IPv4 address to be able to
    access my home devices from the Internet.

    I do not know if that is a realistic wish.

    The transition to IPv6 should have been completed 10 years ago, /before/ the world ran out of IPv4 adresses. Then we would have no problems now. As it is we have the situation that not everyone has IPv6 yet and there is not enough IPv4 left for everyone. Lacking time machines we can not correct the mistakes made in the past and so we have to live with the situation as it is. Which means that some of us will have to do without a globally routable IPv4 address.

    With that in mind, I did my DS-Lite emulation experiments. I am prepaired. ;-)

    And in my case, I don't have IPv6 at work, for example.

    So tell your boss that he needs to prepair for the case that when you are forced to work from home and can only be reached via IPv6.

    I mentioned feste-ip.net didn't I?

    But all my (own, private) servers do have IPv6 enabled and reachable
    for years now (and I also have the IPv6 T-Shirt from he.net *g*), so
    at least I'm prepared :)

    The T-shirt... I already showed you mine didn't I? How about showing yours? ;-)


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From deon@3:633/509 to Michiel van der Vlist on Thu Jan 13 10:10:42 2022
    Re: List of IPv6 nodes
    By: Michiel van der Vlist to deon on Wed Jan 12 2022 03:28 pm

    Howdy,

    I use /80's a lot, which in reality could be /96's but I'm being generous to the network that I use the /80's on.

    But why? When you can have enough space to make /64 subnets?

    Because in my use case, having a /64 for 2 or 3 hosts is a waste - and given in that use case it is a manual config anyway, spliting up an already routed /64 into smaller parts, is easier than routing multiple /64 through intermediate hosts.

    And some thing will not work any more.

    From an IP comms point of view, I've never not handing work anymore. From a SLAAC point of view, sure - which was my earlier comment around simple setup.


    ...
    --- SBBSecho 3.14-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)
  • From Alexey Vissarionov@2:5020/545 to Michiel van der Vlist on Thu Jan 13 02:20:20 2022
    Good ${greeting_time}, Michiel!

    12 Jan 2022 15:21:30, you wrote to me:

    MvdV>>> It is not that 2^64 addresses are not enough for all my
    MvdV>>> devices, it is that a /64 can not be divided into subnets.
    And on my early experiments, when the /64 was the only block
    I had, that was really great.
    MvdV> Yes, now that you mention it, I remember yuo experimenting
    MvdV> with dividing a /64 into 32 bit subnets.

    Yes, of size /96

    MvdV>>> That is the way it is designed. A /64 is the smallest subnet.
    No. The /64 is the default subnet size, and people normally
    SHOULD NOT (as in FTA-1006) split these blocks further, but
    that IS possible and NOT prohibited.
    MvdV> OK, so I stand corrected, it is possible.
    MvdV> But many things won't work any more. SLAAC comes to mind.
    MvdV> So one /should/ avoid it.

    Exactly.

    MvdV> At first glance one would say: a /64? what a waste! But keep in
    MvdV> mind that "waste" is only a problem when there is a shortage.
    MvdV> "Waste and shortage" is IPv4 think.

    IPX had 32 bits for network number and 48 bits for node number (actually 47, because it used MACs for the node numbers by default).

    And many good features of IPv6 were inspired by this protocol.

    MvdV>>> So... if one wants/needs more than one subnet, one needs more
    MvdV>>> than one /64. That is the way it is. It should be no problem,
    MvdV>>> there is enough for everyone.
    Here in Russia the de-facto standard is one MAC-based IPv6 address
    for the outer-side link and /64 subnet routed via that address to
    the customer's LAN. Additional subnets may be requested as well,
    but ISP admins say most people don't request them.
    MvdV> So most people in Russia do not need more than one subnet....

    This may be safely extrapolated to the whole globe: most people just don't bother of separate subnets in their LANs - they simply use plastic routers putting all internal devices in one big "LAN" segment (computers, phones, fridges, phones... everything) and allow one-way connections to "external" networks, regargless of whether they use IPv4 or IPv6.


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

    ... god@universe:~ # cvs up && make world
    --- /bin/vi
    * Origin: ::1 (2:5020/545)
  • From Anna Christina Nass@2:240/5824.1 to Michiel van der Vlist on Thu Jan 13 15:57:00 2022
    Am 12.01.22 schrieb Michiel van der Vlist@2:280/5555 in IPV6:

    Hallo Michiel,

    Correct.
    But as long as IPv6 is not the default case for accessing the
    Internet, I still want to have a 'real' IPv4 address to be able to
    access my home devices from the Internet.

    MvdV> I do not know if that is a realistic wish.

    MvdV> The transition to IPv6 should have been completed 10 years ago, /before/ MvdV> the world ran out of IPv4 adresses.

    You're absolutely right!

    And in my case, I don't have IPv6 at work, for example.

    MvdV> So tell your boss that he needs to prepair for the case that when you MvdV> are forced to work from home and can only be reached via IPv6.

    :) I'm working for the local public library, a part of the
    municipality. And as I'm living in Germany, I'm happy that I do have a working computer and not only a typewriter and a fax machine.
    Our library building still has some IBM Type-1 cabling (from Token
    Ring-days) that we're using for Ethernet via some adapters...
    I don't think that IPv6 days will come soon here...

    MvdV> I mentioned feste-ip.net didn't I?

    I didn't know that page, thanks for that info :)
    But I'm happy that my setup is working at the moment as I've set it up
    :)

    But all my (own, private) servers do have IPv6 enabled and reachable
    for years now (and I also have the IPv6 T-Shirt from he.net *g*), so
    at least I'm prepared :)

    MvdV> The T-shirt... I already showed you mine didn't I? How about showing MvdV> yours? ;-)

    Hehe, nice try :) I guess it's looking basically the same :)

    Regards,
    Anna

    --- OpenXP 5.0.51
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Andrew Leary@1:320/219 to Anna Christina Nass on Thu Jan 13 12:30:15 2022
    Hello Anna!

    13 Jan 22 15:57, you wrote to Michiel van der Vlist:

    MvdV>> The T-shirt... I already showed you mine didn't I? How about
    MvdV>> showing yours? ;-)

    Hehe, nice try :) I guess it's looking basically the same :)

    I daresay that yours probably looks better. ;-)

    Andrew

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Victor Sudakov@2:5005/49 to Michiel van der Vlist on Sat Jan 15 13:38:26 2022
    Dear Michiel,

    10 Jan 22 13:39, you wrote to me:


    Sure. When 2000::/3 runs out, there is 4000::/3. And when that
    runs out, there is 6000::/3. Up until c000::/3.

    That's great news!

    It is not really news I'd say.

    I've never seen an RFC or any other standard referring to a global unicast address block other than 2000::/3. Of course it looks reasonable that in the future you can slice 0000::/1 or 8000::/1 into /3 blocks, but I've never read anything official. So at least it's news for me.

    Ans I suppose when push come to shove
    1000::/4 coild also be used. And even 0::/4 with the exeption of
    0::/64.

    BTW what is already in use within 0000::/1 and 8000::/1 besides 2000::/3?

    Victor Sudakov, VAS4-RIPE, VAS47-RIPN
    --- GoldED+/BSD 1.1.5-b20170303-b20170303
    * Origin: Ulthar (2:5005/49)
  • From Victor Sudakov@2:5005/49 to Björn Felten on Sat Jan 15 13:57:12 2022
    Dear Bjrn,

    10 Jan 22 10:55, you wrote to Alexey Vissarionov:

    I agree. The only reason I can figure out, is that some ISPs don't
    want people to run servers,

    Or rather, they don't want people to share content via bittorent etc.

    There are a lot of better options to run a server than a home connection IMHO.

    they want their customers to buy their
    contents (usually lots of encoded TV channels).

    Victor Sudakov, VAS4-RIPE, VAS47-RIPN
    --- GoldED+/BSD 1.1.5-b20170303-b20170303
    * Origin: Ulthar (2:5005/49)
  • From Victor Sudakov@2:5005/49 to Michiel van der Vlist on Sat Jan 15 14:13:28 2022
    Dear Michiel,

    12 Jan 22 15:21, you wrote to Alexey Vissarionov:

    Here in Russia the de-facto standard is one MAC-based IPv6
    address for the outer-side link and /64 subnet routed via that
    address to the customer's LAN. Additional subnets may be
    requested as well, but ISP admins say most people don't request
    them.

    So most people in Russia do not need more than one subnet....

    Most people in Russia cannot even get one *native* IPv6 address for their home connection, let alone a static one. Well, probably not most but the majority, I'm for one. I have not noticed ISPs here willing to adopt IPv6.

    Mobile operators (mts.ru for sure) give you a dynamic IPv6 address for each mobile device by default (to go together with an RFC1918 IPv4 address).

    Victor Sudakov, VAS4-RIPE, VAS47-RIPN
    --- GoldED+/BSD 1.1.5-b20170303-b20170303
    * Origin: Ulthar (2:5005/49)
  • From Michiel van der Vlist@2:280/5555 to Anna Christina Nass on Sun Jan 16 00:05:02 2022
    Hello Anna,

    On Thursday January 13 2022 15:57, you wrote to me:

    MvdV>> The transition to IPv6 should have been completed 10 years ago,
    MvdV>> /before/ the world ran out of IPv4 adresses.

    You're absolutely right!

    Thanks. But you end I being right does not change the reality that the transition is not completed and that we are past the point where it can be done without becoming ugly. Some of us will have to make do without a globally routable IPv4 address before IPv6 is the dominant protocol.

    And in my case, I don't have IPv6 at work, for example.

    MvdV>> So tell your boss that he needs to prepair for the case that
    MvdV>> when you are forced to work from home and can only be reached
    MvdV>> via IPv6.

    :) I'm working for the local public library, a part of the
    municipality.

    As a volunteer or as a payed employee? I think it makes a difference. As a volunteer you may have more influence and more freedom to make a difference.

    And as I'm living in Germany, I'm happy that I do have a working
    computer and not only a typewriter and a fax machine. Our library
    building still has some IBM Type-1 cabling (from Token Ring-days) that we're using for Ethernet via some adapters... I don't think that IPv6
    days will come soon here...

    While you equipment may be old, I do not think it is hopeless. Even WIndows XP supports IPv6 and that IBM-1 cabling with ethernet adapter should be IP version agnostic just like any other type of network cable. .

    So what is stopping you - other than a boss paying you salary - to do some updating?

    MvdV>> I mentioned feste-ip.net didn't I?

    I didn't know that page, thanks for that info :)
    But I'm happy that my setup is working at the moment as I've set it up

    Sure. But there is a reason I took an account with them. Five years ago, I figured there was a reasonable chance that I would loose my globally routable IPv4 address. That is why I ran the DS-Lite emulation experiments. I wanted to be prepared in case my ISP converted my connection to DS-Lite. It has not happened yet. But when it happens, I will be prepaired.

    But all my (own, private) servers do have IPv6 enabled and
    reachable for years now (and I also have the IPv6 T-Shirt from
    he.net *g*), so at least I'm prepared :)

    MvdV>> The T-shirt... I already showed you mine didn't I? How about
    MvdV>> showing yours? ;-)

    Hehe, nice try :) I guess it's looking basically the same :)

    The shirt, but my guess is the bearer will look different. BTW I have to confess I am not as young as I look on that picture of mine. It is over five years old. ;-)


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Tony Langdon@3:633/410 to Michiel van der Vlist on Sun Jan 16 20:11:00 2022
    On 01-10-22 13:39, Michiel van der Vlist wrote to Victor Sudakov <=-

    Many ISPs only offer a /48 to business accounts. For consumer accounts
    it is often a /56. A /56 is plenty for most I'd say.

    Yeah, I can't see myself using my /56 in my lifetime. What will I do with 256 networks? :)


    ... Life is not a cabaret, it's a circus!
    === MultiMail/Win v0.52
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Tony Langdon@3:633/410 to Richard Menedetter on Sun Jan 16 20:15:00 2022
    On 01-10-22 14:38, Richard Menedetter wrote to Michiel van der Vlist <=-

    Or a /64 for residential.
    And you don't have to fuss around with how to subnet.
    The CPE simply announces the IPv6 net on the LAN side and you are done
    ;)

    There are arguments for more than a /64 for residential use. That allows for different subnets with different security profiles, such as for IoT, the car, whatever other network of smart devices you want. For many, I suspect a /60 would be sufficient.


    ... It beeped and said "Countdown initiated". Is that bad?
    === MultiMail/Win v0.52
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Richard Menedetter@2:310/31 to Tony Langdon on Sun Jan 16 11:35:42 2022
    Hi Tony!

    16 Jan 2022 20:15, from Tony Langdon -> Richard Menedetter:

    Or a /64 for residential.
    And you don't have to fuss around with how to subnet.
    The CPE simply announces the IPv6 net on the LAN side and you are
    done ;)
    There are arguments for more than a /64 for residential use. That
    allows for different subnets with different security profiles, such as
    for IoT, the car, whatever other network of smart devices you want.
    For many, I suspect a /60 would be sufficient.

    Sure ... I agree.

    My reply was more from the ISP point of view.
    With 1 v6 subnet it is easy, you just announce the subnet.

    If you allow more, you need a way to configure them. (eg. VLANs, different subnet on different LAN port, etc.)

    That is added complexity for a low cost product, where most of your residential customers will have no clue what this is all about.

    So it makes more sense to offer that on higher tier (and more expensive) services.

    CU, Ricsi

    ... Swallowing angry words is much easier than having to eat them.
    --- GoldED+/LNX
    * Origin: I'm in total control, but don't tell my wife. (2:310/31)
  • From Anna Christina Nass@2:240/5824.1 to Michiel van der Vlist on Sun Jan 16 12:53:00 2022
    Am 16.01.22 schrieb Michiel van der Vlist@2:280/5555 in IPV6:

    Hallo Michiel,

    MvdV> Thanks. But you end I being right does not change the reality that the MvdV> transition is not completed and that we are past the point where it can MvdV> be done without becoming ugly. Some of us will have to make do without a MvdV> globally routable IPv4 address before IPv6 is the dominant protocol.

    At least the use of DS-Lite ISP connections makes it a little more
    apparent to the customers that IPv4 has some disadvantages over IPv6 nowadays.
    But I guess the vast majority of 'consumers' who only use simple web browsing, email and media streaming services won't notice it anyway.
    So in theory, the transition for those consumers can continue as long
    as the services that most people use are reachable via IPv6.

    :) I'm working for the local public library, a part of the
    municipality.

    MvdV> As a volunteer or as a payed employee? I think it makes a difference. As MvdV> a volunteer you may have more influence and more freedom to make a
    MvdV> difference.

    No, that's my full time job (and I get payed - lucky me *g*).
    And although I'm in the IT department of the library, there are other departments 'above' us who run the city-wide IT.

    And as I'm living in Germany, I'm happy that I do have a working
    computer and not only a typewriter and a fax machine. Our library
    building still has some IBM Type-1 cabling (from Token Ring-days) that AN>> we're using for Ethernet via some adapters... I don't think that IPv6
    days will come soon here...

    MvdV> While you equipment may be old, I do not think it is hopeless. Even
    MvdV> WIndows XP supports IPv6 and that IBM-1 cabling with ethernet adapter MvdV> should be IP version agnostic just like any other type of network cable.

    MvdV> So what is stopping you - other than a boss paying you salary - to do MvdV> some updating?

    Well, you're right (and yes, I know that even via 'real' Token Ring,
    you can use IPv6 *g*).
    My point was more in the direction of the mentality of German
    bureaucracy. Changes here take ages.
    We are still stuck to Microsoft (Windows, Office, AD... all the nice
    things that malware loves) and until this year we're still using Lotus
    Notes (Exchange/Outlook will follow ... *shiver*).

    And I'm trying to update things. We've moved out library management
    system to Linux servers some years ago (and now it's running much more
    stable and reliable than before) and are updating hardware as good as
    we can.
    But as said before, we're not on the top of the hierarchy in the municipality, we are dependant on others who run the network. So we
    can't move to IPv6 on our own :)

    MvdV> Sure. But there is a reason I took an account with them. Five years ago, MvdV> I figured there was a reasonable chance that I would loose my globally MvdV> routable IPv4 address. That is why I ran the DS-Lite emulation
    MvdV> experiments. I wanted to be prepared in case my ISP converted my
    MvdV> connection to DS-Lite. It has not happened yet. But when it happens, I MvdV> will be prepaired.

    That's always a good idea!
    I could set up a VPN tunnel to one of my vServers, or use some kind of service that you mentioned, to be reachable from outside again.
    Let's see how all this will turn out.

    Regards,
    Anna

    --- OpenXP 5.0.51
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Michiel van der Vlist@2:280/5555 to Victor Sudakov on Sun Jan 16 17:09:46 2022
    Hello Victor,

    On Saturday January 15 2022 13:38, you wrote to me:

    And I suppose when push come to shove 1000::/4 coild also be used.
    And even 0::/4 with the exeption of 0::/64.

    BTW what is already in use within 0000::/1 and 8000::/1 besides
    2000::/3?

    Only :: as the unspecified address and ::1 as the local loop AFAIK.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Victor Sudakov on Sun Jan 16 17:11:17 2022
    Hello Victor,

    On Saturday January 15 2022 13:57, you wrote to Bjrn Felten:

    There are a lot of better options to run a server than a home
    connection IMHO.

    "Better" is in the eye of the beholder.

    I get staisfaction out of running servers from my home connection on my own hardware. So fo me that is "better".


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Victor Sudakov on Sun Jan 16 18:04:07 2022
    Hello Victor,

    On Saturday January 15 2022 14:13, you wrote to me:

    Most people in Russia cannot even get one *native* IPv6 address for
    their home connection, let alone a static one. Well, probably not most
    but the majority, I'm for one. I have not noticed ISPs here willing to adopt IPv6.

    And yet, I see many Russian sysops with naitive IPv6 in my list. Maybe you should make more noise. O vote with the feet.

    Mobile operators (mts.ru for sure) give you a dynamic IPv6 address for each mobile device by default (to go together with an RFC1918 IPv4 address).

    In that case you are ahead of us. Moblile oparetors are in the process of converting, but the conversion is far from complete. Not many mobile devices have an IPv6 adress yet.

    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Tony Langdon on Sun Jan 16 18:06:54 2022
    Hello Tony,

    On Sunday January 16 2022 20:11, you wrote to me:

    Many ISPs only offer a /48 to business accounts. For consumer
    accounts it is often a /56. A /56 is plenty for most I'd say.

    Yeah, I can't see myself using my /56 in my lifetime. What will I do
    with 256 networks? :)

    Neither can I, but I can imagine some wanting/needing more than a /60. The "rule" should be "give them so much they will never come back for more". That wey they avoid having to make administrative exceptions for some customers. There is enough to give every customer a /56.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Tony Langdon on Sun Jan 16 18:11:08 2022
    Hello Tony,

    On Sunday January 16 2022 20:15, you wrote to Richard Menedetter:

    There are arguments for more than a /64 for residential use. That
    allows for different subnets with different security profiles, such as
    for IoT, the car, whatever other network of smart devices you want.
    For many, I suspect a /60 would be sufficient.

    But not for all, see my previous message.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Alexey Vissarionov@2:5020/545 to Richard Menedetter on Mon Jan 17 00:38:38 2022
    Good ${greeting_time}, Richard!

    16 Jan 2022 11:35:42, you wrote to Tony Langdon:

    There are arguments for more than a /64 for residential use. That
    allows for different subnets with different security profiles, such
    as for IoT, the car, whatever other network of smart devices you
    want. For many, I suspect a /60 would be sufficient.
    Sure ... I agree. My reply was more from the ISP point of view.
    With 1 v6 subnet it is easy, you just announce the subnet.

    No: when you need to provide the customer with IPv6, you assign one fixed address for a link, and route a /64 subnet through that address.

    Plastic routers (those sold for 20 EUR) deal with this setup just fine.

    If you allow more, you need a way to configure them. (eg. VLANs,
    different subnet on different LAN port, etc.)

    Or simply route more /64 subnets through that address. Or /56 at once.

    That is added complexity for a low cost product, where most of your residential customers will have no clue what this is all about. So
    it makes more sense to offer that on higher tier (and more expensive) services.

    That violates the KISS principle.


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

    ... that's why I really dislike fools.
    --- /bin/vi
    * Origin: ::1 (2:5020/545)
  • From Michiel van der Vlist@2:280/5555 to Alexey Vissarionov on Tue Jan 18 14:06:23 2022
    Hello Alexey,

    On Monday January 17 2022 00:38, you wrote to Richard Menedetter:

    Sure ... I agree. My reply was more from the ISP point of view.
    With 1 v6 subnet it is easy, you just announce the subnet.

    No: when you need to provide the customer with IPv6, you assign one
    fixed address for a link, and route a /64 subnet through that address.

    Plastic routers (those sold for 20 EUR) deal with this setup just
    fine.

    My provider issued "plastic box" already uses three subnets all by itself. The first subnet is routed to the local LAN. (WiFi + wired). The second subnet is rserverd for the private guest network. (WiFi only). The third subnet is for the providers own guest network. (WiFi only).

    The box supports pefix delegation, so I can connect another router and have more subnets routed to that router.

    If you allow more, you need a way to configure them. (eg. VLANs,
    different subnet on different LAN port, etc.)

    Or simply route more /64 subnets through that address. Or /56 at once.

    My provider gives me a /56 routed through that "plastic box".

    That is added complexity for a low cost product, where most of
    your residential customers will have no clue what this is all
    about. So it makes more sense to offer that on higher tier (and
    more expensive) services.

    That violates the KISS principle.

    Indeed. It is easier to just give every customer a /56. And just route the first /64 to the LAN, so that the user need not configure anything if he only needs one /64. And the provider does not need to configure anything if the customer needs more.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Richard Menedetter@2:310/31 to Alexey Vissarionov on Tue Jan 18 14:52:16 2022
    Hi Alexey!

    17 Jan 2022 00:38, from Alexey Vissarionov -> Richard Menedetter:

    With 1 v6 subnet it is easy, you just announce the subnet.
    No: when you need to provide the customer with IPv6, you assign one
    fixed address for a link, and route a /64 subnet through that address. Plastic routers (those sold for 20 EUR) deal with this setup just
    fine.

    Yeah ... this is what I tried to say.
    If you have 1 /64 you deal with it easily also in the dumbest router.
    If you have multiple subnets you need a way to configure which subnet is announced where.
    This makes it more complicated.

    If you allow more, you need a way to configure them. (eg. VLANs,
    different subnet on different LAN port, etc.)
    Or simply route more /64 subnets through that address. Or /56 at once.

    This is not really beneficial.
    From my point of view it makes only sense if you can split them up into multiple different subnets.
    And for 95+% of people it makes no difference, or they do not care.
    So ISPs say that this is a business feature, that is only supported by more expensive routers and more expensive ISP services.

    That is added complexity for a low cost product, where most of
    your residential customers will have no clue what this is all
    about. So it makes more sense to offer that on higher tier (and
    more expensive) services.
    That violates the KISS principle.

    Yes, and that is exactly the reason why there is only one /64.
    Keep it simple.

    CU, Ricsi

    ... I didn't know international smuggling involved so much lifting.
    --- GoldED+/LNX
    * Origin: You are sick and twisted... I like that in a person! (2:310/31)
  • From Richard Menedetter@2:310/31 to Michiel van der Vlist on Tue Jan 18 14:57:04 2022
    Hi Michiel!

    18 Jan 2022 14:06, from Michiel van der Vlist -> Alexey Vissarionov:

    That violates the KISS principle.
    Indeed. It is easier to just give every customer a /56. And just route
    the first /64 to the LAN, so that the user need not configure anything
    if he only needs one /64. And the provider does not need to configure anything if the customer needs more.

    It is even simpler to just to hand out a /64 ;)

    CU, Ricsi

    ... We have nothing to fear but fear itself or maybe a vengeful maniac.
    --- GoldED+/LNX
    * Origin: Famous Last Words: "Go away! I'm all right!" (2:310/31)
  • From Michiel van der Vlist@2:280/5555 to Anna Christina Nass on Tue Jan 18 14:26:36 2022
    Hello Anna,

    On Sunday January 16 2022 12:53, you wrote to me:

    At least the use of DS-Lite ISP connections makes it a little more apparent to the customers that IPv4 has some disadvantages over IPv6 nowadays.
    But I guess the vast majority of 'consumers' who only use simple web browsing, email and media streaming services won't notice it anyway.
    So in theory, the transition for those consumers can continue as long
    as the services that most people use are reachable via IPv6.

    Indeed, Auntie Gertrude won't even notice that she has been converted from IPv4 only to DS-Lite. Which is fine off course. My ISP tries to make the transition as invisible as possible for Auntie Gertrude.

    :) I'm working for the local public library, a part of the
    municipality.

    MvdV>> As a volunteer or as a payed employee? I think it makes a
    MvdV>> difference. As a volunteer you may have more influence and more
    MvdV>> freedom to make a difference.

    No, that's my full time job (and I get payed - lucky me *g*).
    And although I'm in the IT department of the library, there are other
    departments 'above' us who run the city-wide IT.

    So you hands are tied. I have occasionally done some voluntair work and I found that I had a lot more freedom than when I was a paid employee. In the volunteer job, I was the "expert", no other experts above me. Plus that if I staeyed within the budget, I could just say: "this is how I am going to do it". Well, that was a long time ago, before IPv6.

    MvdV>> So what is stopping you - other than a boss paying you salary -
    MvdV>> to do some updating?

    Well, you're right (and yes, I know that even via 'real' Token Ring,
    you can use IPv6 *g*).

    I don't think anybody has tried it, but yes in theorie it should be possible.

    My point was more in the direction of the mentality of German
    bureaucracy. Changes here take ages. We are still stuck to Microsoft (Windows, Office, AD... all the nice things that malware loves) and
    until this year we're still using Lotus Notes (Exchange/Outlook will follow ... *shiver*).

    I do not envy you...

    And I'm trying to update things. We've moved out library management
    system to Linux servers some years ago (and now it's running much more stable and reliable than before) and are updating hardware as good as
    we can. But as said before, we're not on the top of the hierarchy in
    the municipality, we are dependant on others who run the network. So
    we can't move to IPv6 on our own :)

    Here there is a directive that says all goverment websites (national, provicial and minicipal) must be reachable via IPv6 before 1 jan 2022. That goal has not been fully reached yet but if the library is part of the municipality it would be subedt to that directive. Here the public library is not (directly) financed by the municipality and so it is not subject to that diective, It does not support IPv6. :-(

    MvdV>> Sure. But there is a reason I took an account with them. Five
    MvdV>> years ago, I figured there was a reasonable chance that I would
    MvdV>> loose my globally routable IPv4 address. That is why I ran the
    MvdV>> DS-Lite emulation experiments. I wanted to be prepared in case
    MvdV>> my ISP converted my connection to DS-Lite. It has not happened
    MvdV>> yet. But when it happens, I will be prepaired.

    That's always a good idea!
    I could set up a VPN tunnel to one of my vServers, or use some kind of service that you mentioned, to be reachable from outside again. Let's
    see how all this will turn out.

    Indeed, we will see how it works out.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Richard Menedetter on Tue Jan 18 17:46:43 2022
    Hello Richard,

    On Tuesday January 18 2022 14:57, you wrote to me:

    That violates the KISS principle.
    Indeed. It is easier to just give every customer a /56. And just
    route the first /64 to the LAN, so that the user need not
    configure anything if he only needs one /64. And the provider
    does not need to configure anything if the customer needs more.

    It is even simpler to just to hand out a /64 ;)

    I disagree.

    You have to look al the bigger picture. It violates the rule "give them so much, they will never come back for more". Giving them just a /64 is simple. But then some will come back for more and then you have extra work. You have to give them a different modem and you have to do the adminstration. Of course giving everyone a slightly more complex modem that can deal with a /56 is also extra work to develop the firmware, but that has to be done only once for all customers and you need only one type of modem for all customers. That reduces the load on the helpdesk.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Tony Langdon@3:633/410 to Richard Menedetter on Wed Jan 19 18:18:00 2022
    On 01-16-22 11:35, Richard Menedetter wrote to Tony Langdon <=-

    There are arguments for more than a /64 for residential use. That
    allows for different subnets with different security profiles, such as
    for IoT, the car, whatever other network of smart devices you want.
    For many, I suspect a /60 would be sufficient.

    Sure ... I agree.

    My reply was more from the ISP point of view.
    With 1 v6 subnet it is easy, you just announce the subnet.

    If you allow more, you need a way to configure them. (eg. VLANs,
    different subnet on different LAN port, etc.)

    True, and as the market demands it, this will become available (and the vendors will probably screw it up LOL). I know I can add a router behind the primary router. The main manual setup will be to assign a /64 to the LAN side of that router. The existing router will pick up the advertisements, setup routing and optionally open the firewall for that /64 (so that filtering can be controlled by the second router).

    I haven't put that to the test yet, but tempted to give it a try sometime, as a learning exercise. :)

    That is added complexity for a low cost product, where most of your residential customers will have no clue what this is all about.

    If the market demands it, it will come (and in a low cost, easy to use form).

    So it makes more sense to offer that on higher tier (and more
    expensive) services.

    I can see that changing. As I said, when separation of functional networks becomes a thing.



    ... Dew knot trussed yore spell chequer two fined awl mistakes!
    === MultiMail/Win v0.52
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Tony Langdon@3:633/410 to Michiel van der Vlist on Wed Jan 19 18:20:00 2022
    On 01-16-22 18:06, Michiel van der Vlist wrote to Tony Langdon <=-

    Neither can I, but I can imagine some wanting/needing more than a /60. The "rule" should be "give them so much they will never come back for more". That wey they avoid having to make administrative exceptions for some customers. There is enough to give every customer a /56.

    Yeah, there is that argument. Over time, I can see myself using 3 or 4 /64s. More than 16 is unlikely, unless I start doing a lot of funky VPN stuff. ;)


    ... Apotheosis was the beginning before the beginning.
    === MultiMail/Win v0.52
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Michiel van der Vlist@2:280/5555 to Tony Langdon on Wed Jan 19 12:21:02 2022
    Hello Tony,

    On Wednesday January 19 2022 18:18, you wrote to Richard Menedetter:

    I know I can add a router behind the primary router. The main manual setup will be to assign a /64 to the LAN side of that router. The existing router will pick up the advertisements, setup routing and optionally open the firewall for that /64 (so that filtering can be controlled by the second router).

    I haven't put that to the test yet, but tempted to give it a try
    sometime, as a learning exercise. :)

    I did just that a couple of years ago to test prefix delegation. I connected a second router behind my primary router and IIRC it got a /61 out of the /56 assigned to me. Of that /61, one /64 was routed to the local LAN of the second router. I presume the process allows for cascading routers until the /56 is exhausted, but I did not explore that. I was satisfied that I demonstrated prefix delegation worked.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Tony Langdon on Wed Jan 19 12:36:15 2022
    Hello Tony,

    On Wednesday January 19 2022 18:20, you wrote to me:

    Neither can I, but I can imagine some wanting/needing more than
    a /60. The "rule" should be "give them so much they will never
    come back for more". That wey they avoid having to make
    administrative exceptions for some customers. There is enough to
    give every customer a /56.

    Yeah, there is that argument. Over time, I can see myself using 3 or
    4 /64s. More than 16 is unlikely, unless I start doing a lot of funky
    VPN stuff. ;)

    That reminds me of: "640K ought te be enough for everyone".

    That was DOS think. We got rid of that. Now 640M is meagre.

    We also have to get rid of IPv4 think. On top of that list are:

    1) NAT is not a security feature.
    2) There is no shortage of addresses. Address space is no longer a scarce commodity.

    With the mind still in IPv4 think mode, giving out a /56 to everyone while the vast majority will get no further than using 1 or 2% of that looks like a terrible waste.

    Then consider that "waste" is only an issue if there is shortage. With IPv6 there is no shortage of addreses. Thinking "waste" is IPv4 think. We have to get rid of that.


    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 Wed Jan 19 14:26:39 2022
    Hi Michiel,

    On 2022-01-19 12:36:15, you wrote to Tony Langdon:

    MvdV> 2) There is no shortage of addresses. Address space is no longer a
    MvdV> scarce commodity.

    It is for you, if your provider only gives you the bare minimum, and tries to sell you more... :-/

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Wed Jan 19 14:49:47 2022
    Hello Wilfred,

    On Wednesday January 19 2022 14:26, you wrote to me:

    MvdV>> 2) There is no shortage of addresses. Address space is no
    MvdV>> longer a scarce commodity.

    It is for you, if your provider only gives you the bare minimum, and
    tries to sell you more... :-/

    In the context at hand, we were looking at it from the provider's POV. For the provider there is plenty. No reason for the provider not to give their customers at least a /56.


    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 Wed Jan 19 15:10:21 2022
    Hi Michiel,

    On 2022-01-19 14:49:47, you wrote to me:

    MvdV>>> 2) There is no shortage of addresses. Address space is no
    MvdV>>> longer a scarce commodity.

    It is for you, if your provider only gives you the bare minimum, and
    tries to sell you more... :-/

    MvdV> In the context at hand, we were looking at it from the provider's POV. For
    MvdV> the provider there is plenty. No reason for the provider not to give their
    MvdV> customers at least a /56.

    Except when they think they can make an extra buck... :-/

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Thu Jan 20 11:57:37 2022
    Hello Wilfred,

    On Wednesday January 19 2022 15:10, you wrote to me:

    MvdV>> In the context at hand, we were looking at it from the
    MvdV>> provider's POV. For the provider there is plenty. No reason for
    MvdV>> the provider not to give their customers at least a /56.

    Except when they think they can make an extra buck... :-/

    Even without a degree in economics it should be obvious that making money on a commodity that is free and plentiful is not a sound bussines model.

    The current rate for an IPv4 address is around EUR 30. So making money on extra IPv4 should work. Trying teh same on IPv6 will not work, it will just make the customer go elsewhere.


    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 Thu Jan 20 13:17:16 2022
    Hi Michiel,

    On 2022-01-20 11:57:37, you wrote to me:

    Except when they think they can make an extra buck... :-/

    MvdV> Even without a degree in economics it should be obvious that making money
    MvdV> on a commodity that is free and plentiful is not a sound bussines model.

    MvdV> The current rate for an IPv4 address is around EUR 30. So making money on
    MvdV> extra IPv4 should work. Trying teh same on IPv6 will not work, it will just
    MvdV> make the customer go elsewhere.

    That isn't always as simpel as it sounds...

    There are probably lots of places where providers still more or less have a monopoly.


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Anna Christina Nass@2:240/5824.1 to Michiel van der Vlist on Thu Jan 20 16:08:00 2022
    Am 18.01.22 schrieb Michiel van der Vlist@2:280/5555 in IPV6:

    Hallo Michiel,

    No, that's my full time job (and I get payed - lucky me *g*).
    And although I'm in the IT department of the library, there are other
    departments 'above' us who run the city-wide IT.

    MvdV> So you hands are tied.

    Yep.

    Well, you're right (and yes, I know that even via 'real' Token Ring,
    you can use IPv6 *g*).

    MvdV> I don't think anybody has tried it, but yes in theorie it should be
    MvdV> possible.

    Yes, as it is another layer.

    MvdV> Here there is a directive that says all goverment websites (national, MvdV> provicial and minicipal) must be reachable via IPv6 before 1 jan 2022.

    I don't know of such a rule here in Germany...

    Regards,
    Anna

    --- OpenXP 5.0.51
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Thu Jan 20 23:56:59 2022
    Hello Wilfred,

    On Thursday January 20 2022 13:17, you wrote to me:

    MvdV>> The current rate for an IPv4 address is around EUR 30. So
    MvdV>> making money on extra IPv4 should work. Trying teh same on IPv6
    MvdV>> will not work, it will just make the customer go elsewhere.

    That isn't always as simpel as it sounds...

    There are probably lots of places where providers still more or less
    have a monopoly.

    Yes, ther are situations where the provider has a (semi) monopoly. There are also situations where the provider only issues one /64 to customers. I do not know if thee are situations where providers charge extra for more that one /64.

    How often will we see the combination of all three? I do not know of any.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Tony Langdon@3:633/410 to Michiel van der Vlist on Fri Jan 21 10:21:00 2022
    On 01-19-22 12:21, Michiel van der Vlist wrote to Tony Langdon <=-

    I did just that a couple of years ago to test prefix delegation. I connected a second router behind my primary router and IIRC it got a
    /61 out of the /56 assigned to me. Of that /61, one /64 was routed to
    the local LAN of the second router. I presume the process allows for cascading routers until the /56 is exhausted, but I did not explore
    that. I was satisfied that I demonstrated prefix delegation worked.

    Sounds like the results I'd expect. When I move house later in the year, I may segment my network physically, which would mean IPv4 subnets (which arrive via tunnels) could be on separate wires, and I could delegate IPv4 prefixes to those physical subnets. Just a thought at this stage, still in the very early planning stages. :)


    ... The greatest problem about old age is the fear that it may go on too long === MultiMail/Win v0.52
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Tony Langdon@3:633/410 to Michiel van der Vlist on Fri Jan 21 10:27:00 2022
    On 01-19-22 12:36, Michiel van der Vlist wrote to Tony Langdon <=-

    We also have to get rid of IPv4 think. On top of that list are:

    1) NAT is not a security feature.

    True, and a packet filter defaulting to blocking incoming traffic (like a lot of IPv6 routers do) has the same net effect, without the NAT ugliness.

    2) There is no shortage of addresses. Address space is no longer a
    scarce commodity.

    Good point. Anyone got the figures for how many /56 prefixes are available? All the estimates of abailable address space focus on single addresses, but really, /64s should be considered in these analyses, because that's effectively the smallest (convenient) LAN segment intended to be assigned.

    With the mind still in IPv4 think mode, giving out a /56 to everyone while the vast majority will get no further than using 1 or 2% of that looks like a terrible waste.

    Then consider that "waste" is only an issue if there is shortage. With IPv6 there is no shortage of addreses. Thinking "waste" is IPv4 think.
    We have to get rid of that.

    That's why I'd like some more relevant figures, taking into account current allocation practices (e.g. /56 per resifential customer, /64 minimum subnet allocation).


    ... Taglines: the toilet-stall walls of BBSdom.
    === MultiMail/Win v0.52
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Michiel van der Vlist@2:280/5555 to All on Tue Mar 1 16:44:06 2022
    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555

    Updated 1 March 2022


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen Native Xs4All f
    2 2:280/5003 Kees van Eeten Native Xs4All f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
    4 2:280/5555 Michiel van der Vlist Native Ziggo f
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula Native Hetzner f
    7 2:221/6 Tommi Koivula Native OVH
    8 2:5030/257 Vova Uralsky Native PCextreme
    9 1:154/10 Nicholas Bol Native Spectrum f
    10 2:203/0 Bjrn Felten T-6in4 he.net
    11 2:280/5006 Kees van Eeten Native Xs4All f INO4
    12 3:712/848 Scott Little T-6in4 he.net f
    13 2:5020/545 Alexey Vissarionov Native Hetzner f
    14 1:103/17 Stephen Hurd T-6in4 he.net
    15 2:5020/9696 Alexander Skovpen T-6in4 TUNNELBROKER-0
    16 2:421/790 Viktor Cizek T-6in4 he.net
    17 2:222/2 Kim Heino Native TeliaSonera
    18 3:633/280 Stephen Walsh Native AusNetServers f
    19 2:463/877 Alex Shuman Native Nline f IO
    20 1:19/10 Matt Bedynek T-6in4 he.net
    21 3:770/1 Paul Hayton T-6in4 he.net
    22 3:770/100 Paul Hayton T-6in4 he.net
    23 2:5053/58 Alexander Kruglikov Native TTK-Volga f
    24 1:103/1 Stephen Hurd Native Choopa
    25 3:633/281 Stephen Walsh Native Internode
    26 2:310/31 Richard Menedetter Native DE-NETCUP f
    27 3:633/410 Tony Langdon Native IINET
    28 2:5020/329 Oleg Lukashin Native Comfortel f
    29 2:246/1305 Emil Schuster Native TAL.DE
    30 2:2448/4000 Tobias Burchhardt Native DTAG IO
    31 2:331/51 Marco d'Itri Native BOFH-IT
    32 1:154/30 Mike Miller Native LINODE
    33 2:5001/100 Dmitry Protasoff Native OVH
    34 2:5059/38 Andrey Mundirov T-6in4 he.net
    35 2:240/5853 Philipp Giebel Native Hetzner
    36 2:5083/444 Peter Khanin Native OVH
    37 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
    38 1:123/10 Wayne Smith T-6in4 he.net
    39 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    40 1:135/300 Eric Renfro Native Amazon.com
    41 1:103/13 Stephen Hurd Native Choopa
    42 2:5020/1042 Michael Dukelsky Native FORPSI Ktis f
    43 2:5095/0 Sergey V. Efimoff T-6in4 he.net
    44 2:5095/20 Sergey V. Efimoff T-6in4 he.net
    45 2:5019/400 Konstantin Kuzov Native LT-LT
    46 2:467/239 Mykhailo Kapitanov Native Vultr f
    47 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    48 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
    49 2:280/2000 Michael Trip Native Xs4All
    50 2:230/38 Benny Pedersen Native Linode
    51 2:460/58 Stas Mishchenkov T-6in4 he.net f
    52 2:5020/2123 Anton Samsonov T-6in4 he.net
    53 2:5020/2332 Andrey Ignatov Native ru.rtk
    54 2:5005/49 Victor Sudakov T-6in4 he.net f
    55 2:5005/77 Valery Lutoshkin T-6in4 NTS f
    56 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    57 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    58 2:5010/352 Dmitriy Smirnov Native EkranTV f
    59 2:292/854 Ward Dossche Native Proximus
    60 2:469/122 Sergey Zabolotny T-6in4 he.net f
    61 2:5053/400 Alexander Kruglikov Native Oracle f
    62 2:5030/1997 Alexey Fayans T-6in4 he.net
    63 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    64 2:2452/502 Ludwig Bernhartzeder Native DTAG
    65 2:423/39 Karel Kral Native WEDOS
    66 2:5080/102 Stas Degteff T-6to4 NOVATOR
    67 2:280/1049 Simon Voortman Native Solcon
    68 1:102/127 Bradley Thornton Native Hetzner
    69 2:335/364 Fabio Bizzi Native OVH
    70 1:124/5016 Nigel Reed Native DAL1-US f
    71 2:5075/37 Andrew Komardin Native IHC-NET
    72 1:106/633 William Williams Native LINODE-US PM *1
    73 2:263/5 Martin List-Petersen Native TuxBox
    74 2:5030/1520 Andrey Geyko T-6in4 he.net f
    75 1:229/664 Jay Harris Native Rogers f
    76 1:142/103 Brian Rogers T-6in4 he.net
    77 1:134/101 Kostie Muirhead T-6in4 he.net f
    78 2:280/2030 Martien Korenblom Native Transip
    79 3:633/509 Deon George Native Telstra
    80 2:5020/4441 Yuri Myakotin Native SOVINTEL
    81 1:320/319 Andrew Leary Native Comcast f
    82 2:240/5824 Anna Christina Nass Native DTAG f
    83 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
    84 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
    85 2:301/812 Benoit Panizon Native WOODYV6
    86 1:229/616 Vasily Losev Native GIGEPORT
    87 2:301/113 Alisha Manuela Stutz T-6in4 he.net
    88 1:134/100 Kostie Muirhead T-6in4 he.net f
    89 1:134/101 Kostie Muirhead T-6in4 he.net f
    90 1:134/102 Shelley Petersen T-6in4 he.net f INO4
    91 1:134/103 Gordon Muirhead T-6in4 he.net f
    92 1:134/301 Brandon Moore T-6in4 he.net f INO4
    93 1:134/302 Adam Park T-6in4 he.net f
    94 1:153/7715 Dallas Hinton Native Shaw Comms
    95 1:218/840 Morgan Collins Native Linode
    96 2:5020/921 Andrew Savin T-6in4 he.net
    97 2:240/1634 Hugo Andriessen Native Vodafone
    98 2:280/2040 Leo Barnhoorn Native KPN f
    99 2:5020/736 Egor Glukhov Native RUWEB f
    100 2:221/10 Tommi Koivula Native Hetzner f INO4
    101 1:266/420 Scott Street Native Comcast OO
    102 1:218/850 John Nicpon Native LINODE-US
    103 1:142/104 Clive Reuben Native SNETFCC-1
    104 2:301/1 Alisha Stutz Native CH-DATAWIRE
    105 3:633/267 Andrew Clarke Native Widebandnetv6


    T-6in4 Static 6in4
    T-AYIY Dynamic AYIYA
    T-6to4 6to4
    T-6RD 6RD

    Remarks:

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    (zone, net, node in decimal notation)
    IO Incoming only (Node can not make outgoing IPv6 calls)
    OO Outgoing only (Node can not accept incoming IPv6 calls).
    INO4 No IPv4 (Node can not accept incoming IPv4 calls).
    PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
    but is configured to try IPv4 first)
    6DWN The IPv6 connectivity of this node is temporarely down.
    NO6 The node no longer presents an IPv6 address in the nodelist
    and will soon be removed from this list.
    HOLD The node is temporarely off-line. Mail may be routed.
    DOWN This node is Down for both IPv4 and IPv6 and will be
    removed from this list if the condition pertains.
    PM Prospective Member. The node has demonstrated IPv6
    capability but is not listed or does not advertise an
    IPv6 address in the Fidonet nodelist yet.

    PM *1 [2600:3c01::f03c:91ff:fe2b:c319]


    Notes:

    To make an IPv6 connection to a node connected via 6to4 tunneling
    one may have to force the mailer into IPv6 (-6 option in binkd's
    node config for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
    and up when compiled with AF_FORCE=1). If the destination address
    is a 6to4 tunnel address (2002::/16) many OSs default to IPv4 if
    an IPv4 address is present.


    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Anna Christina Nass@2:240/5824.1 to Michiel van der Vlist on Fri Mar 4 17:41:00 2022
    Am 10.01.22 schrieb Michiel van der Vlist@2:280/5555 in IPV6:

    Hallo Michiel,

    Same here. The IPv6 connection for my BBS also had problems on friday
    because Dynv6 'forgot' the AAAA record that I've configured - but it
    seems to be a known problem. Maybe I rewrite the update script (and
    recreate the AAAA record on every prefix change) or switch to my own
    dyndns solution...

    MvdV> We patiently wait... ;-)
    MvdV> Please share your experience with us.

    I just noticed that Dynv6 lost my AAAA record again, so I chose to
    update my update script.
    Dynv6 is offering the use of 'nsupdate', and as I'm already using
    nsupdate for my own DynDNS solution, I just added a nsupdate call for
    my Dynv6 zone to the script.
    It's basically working as noted in the API documentation: https://dynv6.com/docs/apis

    I hope that this solves the Dynv6 AAAA problem now - I hope that my
    IPv6 prefix changes more often than Dynv6 forgets my AAAA record :)

    Regards,
    Anna

    --- OpenXP 5.0.51
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Alexey Vissarionov@2:5020/545 to Anna Christina Nass on Sat Mar 5 06:55:00 2022
    Good ${greeting_time}, Anna!

    04 Mar 2022 17:41:00, you wrote to Michiel van der Vlist:

    Same here. The IPv6 connection for my BBS also had problems on
    friday because Dynv6 'forgot' the AAAA record that I've configured
    MvdV>> We patiently wait... ;-) Please share your experience with us.
    I just noticed that Dynv6 lost my AAAA record again, so I chose to
    update my update script. Dynv6 is offering the use of 'nsupdate',
    and as I'm already using nsupdate for my own DynDNS solution, I just added a nsupdate call for my Dynv6 zone to the script.
    [...]
    I hope that this solves the Dynv6 AAAA problem now - I hope that my
    IPv6 prefix changes more often than Dynv6 forgets my AAAA record :)

    Possibly, running your own DNS server on a cheap (2 EUR/month) VDS (or VPS) would be better solution.


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

    ... GPG: 8832FE9FA791F7968AC96E4E909DAC45EF3B1FA8 @ hkp://keys.gnupg.net
    --- /bin/vi
    * Origin: ::1 (2:5020/545)
  • From Michiel van der Vlist@2:280/5555 to Anna Christina Nass on Sat Mar 5 09:12:49 2022
    Hello Anna,

    On Friday March 04 2022 17:41, you wrote to me:

    MvdV>> We patiently wait... ;-)
    MvdV>> Please share your experience with us.

    I just noticed that Dynv6 lost my AAAA record again, so I chose to
    update my update script. Dynv6 is offering the use of 'nsupdate', and
    as I'm already using nsupdate for my own DynDNS solution, I just added
    a nsupdate call for my Dynv6 zone to the script. It's basically
    working as noted in the API documentation: https://dynv6.com/docs/apis

    It works for now. So don't touch it... ;-)

    + 08:52 [3224] call to 2:240/5824@fidonet
    08:52 [3224] trying box.imzadi.de [2003:e9:2701:1c00:f1d0:2:240:5824]...
    08:52 [3224] connected
    + 08:52 [3224] outgoing session with box.imzadi.de:24554
    [2003:e9:2701:1c00:f1d0:2:240:5824]
    - 08:53 [3224] OPT CRAM-MD5-4e4494d5e81be86e60c979d48471de51 CRYPT
    + 08:53 [3224] Remote requests MD mode
    + 08:53 [3224] Remote requests CRYPT mode
    - 08:53 [3224] SYS Imzadi Box
    - 08:53 [3224] ZYZ Anna Christina Nass
    - 08:53 [3224] LOC Karlsruhe, DEU
    - 08:53 [3224] NDL 115200,TCP,BINKP


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to All on Wed Apr 20 09:31:15 2022
    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555

    Updated 20 April 2022


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen Native Xs4All f
    2 2:280/5003 Kees van Eeten Native Xs4All f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
    4 2:280/5555 Michiel van der Vlist Native Ziggo f
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula Native Hetzner f
    7 2:221/6 Tommi Koivula Native OVH
    8 2:5030/257 Vova Uralsky Native PCextreme
    9 1:154/10 Nicholas Boel Native Spectrum f
    10 2:203/0 Bjorn Felten T-6in4 he.net
    11 2:280/5006 Kees van Eeten Native Xs4All f INO4
    12 3:712/848 Scott Little T-6in4 he.net f
    13 2:5020/545 Alexey Vissarionov T-6in4 he.net f 6DWN
    14 1:103/17 Stephen Hurd T-6in4 he.net
    15 2:5020/9696 Alexander Skovpen T-6in4 TUNNELBROKER-0
    16 2:421/790 Viktor Cizek T-6in4 he.net
    17 2:222/2 Kim Heino Native TeliaSonera
    18 3:633/280 Stephen Walsh Native AusNetServers f
    19 2:463/877 Alex Shuman Native Nline f IO
    20 1:19/10 Matt Bedynek T-6in4 he.net
    21 3:770/1 Paul Hayton T-6in4 he.net
    22 3:770/100 Paul Hayton T-6in4 he.net
    23 2:5053/58 Alexander Kruglikov Native TTK-Volga f
    24 1:103/1 Stephen Hurd Native Choopa
    25 3:633/281 Stephen Walsh Native Internode
    26 2:310/31 Richard Menedetter Native DE-NETCUP f
    27 3:633/410 Tony Langdon Native IINET
    28 2:5020/329 Oleg Lukashin Native Comfortel f
    29 2:246/1305 Emil Schuster Native TAL.DE
    30 2:2448/4000 Tobias Burchhardt Native DTAG IO
    31 2:331/51 Marco d'Itri Native BOFH-IT
    32 1:154/30 Mike Miller Native LINODE
    33 2:5001/100 Dmitry Protasoff Native OVH
    34 2:5059/38 Andrey Mundirov T-6in4 he.net
    35 2:240/5853 Philipp Giebel Native Hetzner
    36 2:5083/444 Peter Khanin Native OVH
    37 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
    38 1:123/10 Wayne Smith T-6in4 he.net
    39 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    40 1:135/300 Eric Renfro Native Amazon.com
    41 1:103/13 Stephen Hurd Native Choopa
    42 2:5020/1042 Michael Dukelsky Native FORPSI Ktis f
    43 2:5095/0 Sergey V. Efimoff T-6in4 he.net
    44 2:5095/20 Sergey V. Efimoff T-6in4 he.net
    45 2:5019/400 Konstantin Kuzov Native LT-LT
    46 2:467/239 Mykhailo Kapitanov Native Vultr f
    47 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    48 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
    49 2:280/2000 Michael Trip Native Xs4All
    50 2:230/38 Benny Pedersen Native Linode
    51 2:460/58 Stas Mishchenkov T-6in4 he.net f
    52 2:5020/2123 Anton Samsonov T-6in4 he.net
    53 2:5020/2332 Andrey Ignatov Native ru.rtk
    54 2:5005/49 Victor Sudakov T-6in4 he.net f
    55 2:5005/77 Valery Lutoshkin T-6in4 NTS f
    56 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    57 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    58 2:5010/352 Dmitriy Smirnov Native SAGE-SU-V6
    59 2:292/854 Ward Dossche Native Proximus
    60 2:469/122 Sergey Zabolotny T-6in4 he.net f
    61 2:5053/400 Alexander Kruglikov Native FirstVDS f
    62 2:5030/1997 Alexey Fayans T-6in4 he.net
    63 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    64 2:2452/502 Ludwig Bernhartzeder Native DTAG
    65 2:423/39 Karel Kral Native WEDOS
    66 2:5080/102 Stas Degteff T-6to4 NOVATOR
    67 2:280/1049 Simon Voortman Native Solcon
    68 1:102/127 Bradley Thornton Native Hetzner
    69 2:335/364 Fabio Bizzi Native OVH
    70 1:124/5016 Nigel Reed Native DAL1-US f
    71 2:5075/37 Andrew Komardin Native IHC-NET
    72 1:106/633 William Williams Native LINODE-US PM *1
    73 2:263/5 Martin List-Petersen Native TuxBox
    74 2:5030/1520 Andrey Geyko T-6in4 he.net f
    75 1:229/664 Jay Harris Native Rogers f
    76 1:142/103 Brian Rogers T-6in4 he.net
    77 1:134/101 Kostie Muirhead T-6in4 he.net f
    78 2:280/2030 Martien Korenblom Native Transip
    79 3:633/509 Deon George Native Telstra
    80 2:5020/4441 Yuri Myakotin Native SOVINTEL
    81 1:320/319 Andrew Leary Native Comcast f
    82 2:240/5824 Anna Christina Nass Native DTAG f
    83 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
    84 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
    85 2:301/812 Benoit Panizon Native WOODYV6
    86 1:229/616 Vasily Losev Native GIGEPORT
    87 2:301/113 Alisha Manuela Stutz T-6in4 he.net
    88 1:134/100 Kostie Muirhead T-6in4 he.net f
    89 1:134/101 Kostie Muirhead T-6in4 he.net f
    90 1:134/102 Shelley Petersen T-6in4 he.net f INO4
    91 1:134/103 Gordon Muirhead T-6in4 he.net f
    92 1:134/301 Brandon Moore T-6in4 he.net f INO4
    93 1:134/302 Adam Park T-6in4 he.net f
    94 1:153/7715 Dallas Hinton Native Shaw Comms
    95 1:218/840 Morgan Collins Native Linode
    96 2:5020/921 Andrew Savin T-6in4 he.net
    97 2:240/1634 Hugo Andriessen Native Vodafone
    98 2:280/2040 Leo Barnhoorn Native KPN f
    99 2:5020/736 Egor Glukhov Native RUWEB f
    100 2:221/10 Tommi Koivula Native Hetzner f INO4
    101 1:266/420 Scott Street Native Comcast OO
    102 1:218/850 John Nicpon Native LINODE-US
    103 1:142/104 Clive Reuben Native SNETFCC-1
    104 2:301/1 Alisha Stutz Native CH-DATAWIRE
    105 3:633/267 Andrew Clarke Native Widebandnetv6
    106 2:5035/63 Vladimir Goncharov Native RFEIV6NET
    107 2:5010/152 Dmitry Smirnov Native RU-SELECTCEL
    108 2:5010/252 Dmitry Smirnov T-6in4 TUNNEL-BROKER-NET-1
    109 2:5020/290 Andrew Kolchoogin T-6in4 he.net


    T-6in4 Static 6in4
    T-AYIY Dynamic AYIYA
    T-6to4 6to4
    T-6RD 6RD

    Remarks:

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    (zone, net, node in decimal notation)
    IO Incoming only (Node can not make outgoing IPv6 calls)
    OO Outgoing only (Node can not accept incoming IPv6 calls).
    INO4 No IPv4 (Node can not accept incoming IPv4 calls).
    PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
    but is configured to try IPv4 first)
    6DWN The IPv6 connectivity of this node is temporarely down.
    NO6 The node no longer presents an IPv6 address in the nodelist
    and will soon be removed from this list.
    HOLD The node is temporarely off-line. Mail may be routed.
    DOWN This node is Down for both IPv4 and IPv6 and will be
    removed from this list if the condition pertains.
    PM Prospective Member. The node has demonstrated IPv6
    capability but is not listed or does not advertise an
    IPv6 address in the Fidonet nodelist yet.

    PM *1 [2600:3c01::f03c:91ff:fe2b:c319]


    Notes:

    To make an IPv6 connection to a node connected via 6to4 tunneling
    one may have to force the mailer into IPv6 (-6 option in binkd's
    node config for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
    and up when compiled with AF_FORCE=1). If the destination address
    is a 6to4 tunnel address (2002::/16) many OSs default to IPv4 if
    an IPv4 address is present.


    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to All on Wed May 18 09:02:36 2022
    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555

    Updated 14 May 2022


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen T-6in4 he.net f PO4
    2 2:280/5003 Kees van Eeten Native KPN f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
    4 2:280/5555 Michiel van der Vlist Native Ziggo f
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula Native Hetzner f
    7 2:221/6 Tommi Koivula Native OVH
    8 2:5030/257 Vova Uralsky Native PCextreme
    9 1:154/10 Nicholas Boel Native Spectrum f
    10 2:203/0 Bjorn Felten T-6in4 he.net
    11 2:280/5006 Kees van Eeten Native KPN f INO4
    12 3:712/848 Scott Little T-6in4 he.net f
    13 2:5020/545 Alexey Vissarionov T-6in4 he.net f
    14 1:103/17 Stephen Hurd T-6in4 he.net
    15 2:5020/9696 Alexander Skovpen T-6in4 TUNNELBROKER-0
    16 2:421/790 Viktor Cizek Native CZ-IJC-20071015
    17 2:222/2 Kim Heino Native TeliaSonera
    18 3:633/280 Stephen Walsh Native AusNetServers f
    19 2:463/877 Alex Shuman Native Nline f IO
    20 1:19/10 Matt Bedynek T-6in4 he.net
    21 3:770/1 Paul Hayton T-6in4 he.net
    22 3:770/100 Paul Hayton T-6in4 he.net
    23 2:5053/58 Alexander Kruglikov Native TTK-Volga f
    24 1:103/1 Stephen Hurd Native Choopa
    25 3:633/281 Stephen Walsh Native Internode
    26 2:310/31 Richard Menedetter Native DE-NETCUP f
    27 3:633/410 Tony Langdon Native IINET
    28 2:5020/329 Oleg Lukashin Native Comfortel f
    29 2:246/1305 Emil Schuster Native TAL.DE
    30 2:2448/4000 Tobias Burchhardt Native DTAG IO
    31 2:331/51 Marco d'Itri Native BOFH-IT
    32 1:154/30 Mike Miller Native LINODE
    33 2:5001/100 Dmitry Protasoff Native OVH
    34 2:5059/38 Andrey Mundirov T-6in4 he.net
    35 2:240/5853 Philipp Giebel Native Hetzner
    36 2:5083/444 Peter Khanin Native OVH
    37 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
    38 1:123/10 Wayne Smith T-6in4 he.net
    39 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    40 1:135/300 Eric Renfro Native Amazon.com
    41 1:103/13 Stephen Hurd Native Choopa
    42 2:5020/1042 Michael Dukelsky Native FORPSI Ktis f
    43 2:5095/0 Sergey V. Efimoff T-6in4 he.net
    44 2:5095/20 Sergey V. Efimoff T-6in4 he.net
    45 2:5019/400 Konstantin Kuzov Native LT-LT
    46 2:467/239 Mykhailo Kapitanov Native Vultr f
    47 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    48 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
    49 2:280/2000 Michael Trip Native Xs4All
    50 2:230/38 Benny Pedersen Native Linode
    51 2:460/58 Stas Mishchenkov T-6in4 he.net f
    52 2:5020/2123 Anton Samsonov T-6in4 TUNNEL-BROKER-NET-0
    53 2:5020/2332 Andrey Ignatov Native ru.rtk
    54 2:5005/49 Victor Sudakov T-6in4 he.net f
    55 2:5005/77 Valery Lutoshkin T-6in4 NTS f
    56 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    57 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    58 2:5010/352 Dmitriy Smirnov Native SAGE-SU-V6
    59 2:292/854 Ward Dossche Native Proximus
    60 2:469/122 Sergey Zabolotny T-6in4 he.net f
    61 2:5053/400 Alexander Kruglikov Native FirstVDS f
    62 2:5030/1997 Alexey Fayans T-6in4 he.net
    63 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    64 2:2452/502 Ludwig Bernhartzeder Native DTAG
    65 2:423/39 Karel Kral Native WEDOS
    66 2:5080/102 Stas Degteff T-6to4 NOVATOR
    67 2:280/1049 Simon Voortman Native Solcon
    68 1:102/127 Bradley Thornton Native Hetzner
    69 2:335/364 Fabio Bizzi Native OVH
    70 1:124/5016 Nigel Reed Native DAL1-US f
    71 2:5075/37 Andrew Komardin Native IHC-NET
    72 1:106/633 William Williams Native LINODE-US PM *1
    73 2:263/5 Martin List-Petersen Native TuxBox
    74 2:5030/1520 Andrey Geyko T-6in4 he.net f
    75 1:229/664 Jay Harris Native Rogers f
    76 1:142/103 Brian Rogers T-6in4 he.net
    77 1:134/101 Kostie Muirhead T-6in4 he.net f
    78 2:280/2030 Martien Korenblom Native Transip
    79 3:633/509 Deon George Native Telstra
    80 2:5020/4441 Yuri Myakotin Native SOVINTEL
    81 1:320/319 Andrew Leary Native Comcast f
    82 2:240/5824 Anna Christina Nass Native DTAG f
    83 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
    84 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
    85 2:301/812 Benoit Panizon Native WOODYV6
    86 1:229/616 Vasily Losev Native GIGEPORT
    87 2:301/113 Alisha Manuela Stutz T-6in4 he.net
    88 1:134/100 Kostie Muirhead T-6in4 he.net f
    89 1:134/101 Kostie Muirhead T-6in4 he.net f
    90 1:134/102 Shelley Petersen T-6in4 he.net f INO4
    91 1:134/103 Gordon Muirhead T-6in4 he.net f
    92 1:134/301 Brandon Moore T-6in4 he.net f INO4
    93 1:134/302 Adam Park T-6in4 he.net f
    94 1:153/7715 Dallas Hinton Native Shaw Comms
    95 1:218/840 Morgan Collins Native Linode
    96 2:5020/921 Andrew Savin Native HURRICANE-IPV6-24
    97 2:240/1634 Hugo Andriessen Native Vodafone
    98 2:280/2040 Leo Barnhoorn Native KPN f
    99 2:5020/736 Egor Glukhov Native RUWEB f
    100 2:221/10 Tommi Koivula Native Hetzner f INO4
    101 1:266/420 Scott Street Native Comcast OO
    102 1:218/850 John Nicpon Native LINODE-US
    103 1:142/104 Clive Reuben Native SNETFCC-1
    104 2:301/1 Alisha Stutz Native CH-DATAWIRE
    105 3:633/267 Andrew Clarke Native Widebandnetv6
    106 2:5035/63 Vladimir Goncharov Native RFEIV6NET
    107 2:5010/152 Dmitry Smirnov Native RU-SELECTCEL
    108 2:5010/252 Dmitry Smirnov T-6in4 TUNNEL-BROKER-NET-1
    109 2:5020/290 Andrew Kolchoogin T-6in4 he.net HOLD


    T-6in4 Static 6in4
    T-AYIY Dynamic AYIYA
    T-6to4 6to4
    T-6RD 6RD

    Remarks:

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    (zone, net, node in decimal notation)
    IO Incoming only (Node can not make outgoing IPv6 calls)
    OO Outgoing only (Node can not accept incoming IPv6 calls).
    INO4 No IPv4 (Node can not accept incoming IPv4 calls).
    PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
    but is configured to try IPv4 first)
    6DWN The IPv6 connectivity of this node is temporarely down.
    NO6 The node no longer presents an IPv6 address in the nodelist
    and will soon be removed from this list.
    HOLD The node is temporarely off-line. Mail may be routed.
    DOWN This node is Down for both IPv4 and IPv6 and will be
    removed from this list if the condition pertains.
    PM Prospective Member. The node has demonstrated IPv6
    capability but is not listed or does not advertise an
    IPv6 address in the Fidonet nodelist yet.

    PM *1 [2600:3c01::f03c:91ff:fe2b:c319]


    Notes:

    To make an IPv6 connection to a node connected via 6to4 tunneling
    one may have to force the mailer into IPv6 (-6 option in binkd's
    node config for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
    and up when compiled with AF_FORCE=1). If the destination address
    is a 6to4 tunnel address (2002::/16) many OSs default to IPv4 if
    an IPv4 address is present.


    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Tommi Koivula@2:221/360 to Michiel van der Vlist on Wed May 18 18:54:16 2022
    Hi Michiel.

    18 May 22 09:02:36, you wrote to All:

    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555
    Updated 14 May 2022

    Node Nr. Sysop Type Provider Remark

    6 2:221/1 Tommi Koivula Native Hetzner f

    ^
    Elisa

    I think I mentioned about that in this echo some time ago?

    'Tommi

    ---
    * Origin: rbb.fidonet.fi (2:221/360)
  • From Tommi Koivula@2:221/6 to Michiel van der Vlist on Wed May 18 18:58:26 2022
    Hi Michiel.

    18 May 22 18:54, I wrote to you:

    Node Nr. Sysop Type Provider Remark

    6 2:221/1 Tommi Koivula Native Hetzner f

    ^
    Elisa

    I think I mentioned about that in this echo some time ago?

    Yes. "04 Feb 2022". :)

    'Tommi

    --- GoldED+/LNX 1.1.5-b20220424
    * Origin: nntps://news.fidonet.fi (2:221/6)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Wed May 18 23:16:08 2022
    Hello Tommi,

    On Wednesday May 18 2022 18:54, you wrote to me:


    6 2:221/1 Tommi Koivula Native Hetzner f

    ^
    Elisa

    I think I mentioned about that in this echo some time ago?

    Sorry, I must have missed it. It has been corrected now.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to All on Thu May 19 15:04:19 2022
    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555

    Updated 19 May 2022


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen T-6in4 he.net f PO4
    2 2:280/5003 Kees van Eeten Native KPN f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
    4 2:280/5555 Michiel van der Vlist Native Ziggo f
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula Native Elisa f
    7 2:221/6 Tommi Koivula Native OVH
    8 2:5030/257 Vova Uralsky Native PCextreme
    9 1:154/10 Nicholas Boel Native Spectrum f
    10 2:203/0 Bjorn Felten T-6in4 he.net
    11 2:280/5006 Kees van Eeten Native KPN f INO4
    12 3:712/848 Scott Little T-6in4 he.net f
    13 2:5020/545 Alexey Vissarionov T-6in4 he.net f
    14 1:103/17 Stephen Hurd T-6in4 he.net
    15 2:5020/9696 Alexander Skovpen T-6in4 TUNNELBROKER-0
    16 2:421/790 Viktor Cizek Native CZ-IJC-20071015
    17 2:222/2 Kim Heino Native TeliaSonera
    18 3:633/280 Stephen Walsh Native AusNetServers f
    19 2:463/877 Alex Shuman Native Nline f IO
    20 1:19/10 Matt Bedynek T-6in4 he.net
    21 3:770/1 Paul Hayton T-6in4 he.net
    22 3:770/100 Paul Hayton T-6in4 he.net
    23 2:5053/58 Alexander Kruglikov Native TTK-Volga f
    24 1:103/1 Stephen Hurd Native Choopa
    25 3:633/281 Stephen Walsh Native Internode
    26 2:310/31 Richard Menedetter Native DE-NETCUP f
    27 3:633/410 Tony Langdon Native IINET
    28 2:5020/329 Oleg Lukashin Native Comfortel f
    29 2:246/1305 Emil Schuster Native TAL.DE
    30 2:2448/4000 Tobias Burchhardt Native DTAG IO
    31 2:331/51 Marco d'Itri Native BOFH-IT
    32 1:154/30 Mike Miller Native LINODE
    33 2:5001/100 Dmitry Protasoff Native OVH
    34 2:5059/38 Andrey Mundirov T-6in4 he.net
    35 2:240/5853 Philipp Giebel Native Hetzner
    36 2:5083/444 Peter Khanin Native OVH
    37 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
    38 1:123/10 Wayne Smith T-6in4 he.net
    39 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    40 1:135/300 Eric Renfro Native Amazon.com
    41 1:103/13 Stephen Hurd Native Choopa
    42 2:5020/1042 Michael Dukelsky Native FORPSI Ktis f
    43 2:5095/0 Sergey V. Efimoff T-6in4 he.net
    44 2:5095/20 Sergey V. Efimoff T-6in4 he.net
    45 2:5019/400 Konstantin Kuzov Native LT-LT
    46 2:467/239 Mykhailo Kapitanov Native Vultr f
    47 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    48 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
    49 2:280/2000 Michael Trip Native Xs4All
    50 2:230/38 Benny Pedersen Native Linode
    51 2:460/58 Stas Mishchenkov T-6in4 he.net f
    52 2:5020/2123 Anton Samsonov T-6in4 TUNNEL-BROKER-NET-0
    53 2:5020/2332 Andrey Ignatov Native ru.rtk
    54 2:5005/49 Victor Sudakov T-6in4 he.net f
    55 2:5005/77 Valery Lutoshkin T-6in4 NTS f
    56 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    57 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    58 2:5010/352 Dmitriy Smirnov Native SAGE-SU-V6
    59 2:292/854 Ward Dossche Native Proximus
    60 2:469/122 Sergey Zabolotny T-6in4 he.net f
    61 2:5053/400 Alexander Kruglikov Native FirstVDS f
    62 2:5030/1997 Alexey Fayans T-6in4 he.net
    63 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    64 2:2452/502 Ludwig Bernhartzeder Native DTAG
    65 2:423/39 Karel Kral Native WEDOS
    66 2:5080/102 Stas Degteff T-6to4 NOVATOR
    67 2:280/1049 Simon Voortman Native Solcon
    68 1:102/127 Bradley Thornton Native Hetzner
    69 2:335/364 Fabio Bizzi Native OVH
    70 1:124/5016 Nigel Reed Native DAL1-US f
    71 2:5075/37 Andrew Komardin Native IHC-NET
    72 1:106/633 William Williams Native LINODE-US PM *1
    73 2:263/5 Martin List-Petersen Native TuxBox
    74 2:5030/1520 Andrey Geyko T-6in4 he.net f
    75 1:229/664 Jay Harris Native Rogers f
    76 1:134/101 Kostie Muirhead T-6in4 he.net f
    77 2:280/2030 Martien Korenblom Native Transip
    78 3:633/509 Deon George Native Telstra
    79 2:5020/4441 Yuri Myakotin Native SOVINTEL
    80 1:320/319 Andrew Leary Native Comcast f
    81 2:240/5824 Anna Christina Nass Native DTAG f
    82 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
    83 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
    84 2:301/812 Benoit Panizon Native WOODYV6
    85 1:229/616 Vasily Losev Native GIGEPORT
    86 2:301/113 Alisha Manuela Stutz T-6in4 he.net
    87 1:134/100 Kostie Muirhead T-6in4 he.net f
    88 1:134/101 Kostie Muirhead T-6in4 he.net f
    89 1:134/102 Shelley Petersen T-6in4 he.net f INO4
    90 1:134/103 Gordon Muirhead T-6in4 he.net f
    91 1:134/301 Brandon Moore T-6in4 he.net f INO4
    92 1:134/302 Adam Park T-6in4 he.net f
    93 1:153/7715 Dallas Hinton Native Shaw Comms
    94 1:218/840 Morgan Collins Native Linode
    95 2:5020/921 Andrew Savin Native HURRICANE-IPV6-24
    96 2:240/1634 Hugo Andriessen Native Vodafone
    97 2:280/2040 Leo Barnhoorn Native KPN f
    98 2:5020/736 Egor Glukhov Native RUWEB f
    99 2:221/10 Tommi Koivula Native Hetzner f INO4
    100 1:266/420 Scott Street Native Comcast OO
    101 1:218/850 John Nicpon Native LINODE-US
    102 1:142/104 Clive Reuben Native SNETFCC-1
    103 2:301/1 Alisha Stutz Native CH-DATAWIRE
    104 3:633/267 Andrew Clarke Native Widebandnetv6
    105 2:5035/63 Vladimir Goncharov Native RFEIV6NET
    106 2:5010/152 Dmitry Smirnov Native RU-SELECTCEL
    107 2:5010/252 Dmitry Smirnov T-6in4 TUNNEL-BROKER-NET-1
    108 2:5020/290 Andrew Kolchoogin T-6in4 he.net


    T-6in4 Static 6in4
    T-AYIY Dynamic AYIYA
    T-6to4 6to4
    T-6RD 6RD

    Remarks:

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    (zone, net, node in decimal notation)
    IO Incoming only (Node can not make outgoing IPv6 calls)
    OO Outgoing only (Node can not accept incoming IPv6 calls).
    INO4 No IPv4 (Node can not accept incoming IPv4 calls).
    PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
    but is configured to try IPv4 first)
    6DWN The IPv6 connectivity of this node is temporarely down.
    NO6 The node no longer presents an IPv6 address in the nodelist
    and will soon be removed from this list.
    HOLD The node is temporarely off-line. Mail may be routed.
    DOWN This node is Down for both IPv4 and IPv6 and will be
    removed from this list if the condition pertains.
    PM Prospective Member. The node has demonstrated IPv6
    capability but is not listed or does not advertise an
    IPv6 address in the Fidonet nodelist yet.

    PM *1 [2600:3c01::f03c:91ff:fe2b:c319]


    Notes:

    To make an IPv6 connection to a node connected via 6to4 tunneling
    one may have to force the mailer into IPv6 (-6 option in binkd's
    node config for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
    and up when compiled with AF_FORCE=1). If the destination address
    is a 6to4 tunnel address (2002::/16) many OSs default to IPv4 if
    an IPv4 address is present.


    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to All on Sun Jun 26 12:48:00 2022
    Hello All,

    Please check your entry. Ig it needs updateing, please let me know.


    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555

    Updated 26 Jun 2022


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen Native Freedom f
    2 2:280/5003 Kees van Eeten Native KPN f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
    4 2:280/5555 Michiel van der Vlist Native Ziggo f OO
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula Native Elisa f
    7 2:221/6 Tommi Koivula Native OVH
    8 2:5030/257 Vova Uralsky Native PCextreme
    9 1:154/10 Nicholas Boel Native Spectrum f
    10 2:203/0 Bjorn Felten T-6in4 he.net
    11 2:280/5006 Kees van Eeten Native KPN f INO4
    12 3:712/848 Scott Little T-6in4 he.net f
    13 2:5020/545 Alexey Vissarionov T-6in4 he.net f
    14 1:103/17 Stephen Hurd T-6in4 he.net
    15 2:5020/9696 Alexander Skovpen T-6in4 TUNNELBROKER-0
    16 2:421/790 Viktor Cizek Native CZ-IJC-20071015
    17 2:222/2 Kim Heino Native TeliaSonera
    18 3:633/280 Stephen Walsh Native AusNetServers f
    19 1:19/10 Matt Bedynek T-6in4 he.net
    20 3:770/1 Paul Hayton T-6in4 he.net
    21 3:770/100 Paul Hayton T-6in4 he.net
    22 2:5053/58 Alexander Kruglikov Native TTK-Volga f
    23 1:103/1 Stephen Hurd Native Choopa
    24 3:633/281 Stephen Walsh Native Internode
    25 2:310/31 Richard Menedetter Native DE-NETCUP f
    26 3:633/410 Tony Langdon Native IINET
    27 2:5020/329 Oleg Lukashin Native Comfortel f
    28 2:246/1305 Emil Schuster Native TAL.DE
    29 2:2448/4000 Tobias Burchhardt Native DTAG IO
    30 2:331/51 Marco d'Itri Native BOFH-IT
    31 1:154/30 Mike Miller Native LINODE
    32 2:5001/100 Dmitry Protasoff Native OVH
    33 2:5059/38 Andrey Mundirov T-6in4 he.net
    34 2:240/5853 Philipp Giebel Native Hetzner
    35 2:5083/444 Peter Khanin Native OVH
    36 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
    37 1:123/10 Wayne Smith T-6in4 he.net
    38 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    39 1:135/300 Eric Renfro Native Amazon.com
    40 1:103/13 Stephen Hurd Native Choopa
    41 2:5020/1042 Michael Dukelsky Native FirstByte
    42 2:5095/0 Sergey V. Efimoff T-6in4 he.net
    43 2:5095/20 Sergey V. Efimoff T-6in4 he.net
    44 2:5019/400 Konstantin Kuzov Native LT-LT
    45 2:467/239 Mykhailo Kapitanov Native Vultr f
    46 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    47 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
    48 2:280/2000 Michael Trip Native Xs4All
    49 2:230/38 Benny Pedersen Native Linode
    50 2:460/58 Stas Mishchenkov T-6in4 he.net f
    51 2:5020/2123 Anton Samsonov T-6in4 TUNNEL-BROKER-NET-0
    52 2:5020/2332 Andrey Ignatov Native ru.rtk
    53 2:5005/49 Victor Sudakov T-6in4 he.net f
    54 2:5005/77 Valery Lutoshkin T-6in4 NTS f
    55 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    56 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    57 2:5010/352 Dmitriy Smirnov Native SAGE-SU-V6
    58 2:292/854 Ward Dossche Native Proximus
    59 2:469/122 Sergey Zabolotny T-6in4 he.net f
    60 2:5053/400 Alexander Kruglikov Native FirstVDS f
    61 2:5030/1997 Alexey Fayans T-6in4 he.net
    62 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    63 2:2452/502 Ludwig Bernhartzeder Native DTAG
    64 2:423/39 Karel Kral Native WEDOS
    65 2:5080/102 Stas Degteff T-6to4 NOVATOR
    66 2:280/1049 Simon Voortman Native Solcon
    67 1:102/127 Bradley Thornton Native Hetzner
    68 2:335/364 Fabio Bizzi Native OVH
    69 1:124/5016 Nigel Reed Native DAL1-US f
    70 2:5075/37 Andrew Komardin Native IHC-NET
    71 2:263/5 Martin List-Petersen Native TuxBox
    72 2:5030/1520 Andrey Geyko T-6in4 he.net f
    73 1:229/664 Jay Harris Native Rogers f
    74 1:134/101 Kostie Muirhead T-6in4 he.net f
    75 2:280/2030 Martien Korenblom Native Transip
    76 3:633/509 Deon George Native Telstra
    77 2:5020/4441 Yuri Myakotin Native SOVINTEL
    78 1:320/319 Andrew Leary Native Comcast f
    79 2:240/5824 Anna Christina Nass Native DTAG f
    80 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
    81 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
    82 2:301/812 Benoit Panizon Native WOODYV6
    83 1:229/616 Vasily Losev Native GIGEPORT
    84 2:301/113 Alisha Manuela Stutz T-6in4 he.net
    85 1:134/100 Kostie Muirhead T-6in4 he.net f
    86 1:134/101 Kostie Muirhead T-6in4 he.net f
    87 1:134/102 Shelley Petersen T-6in4 he.net f INO4
    88 1:134/103 Gordon Muirhead T-6in4 he.net f
    89 1:134/301 Brandon Moore T-6in4 he.net f INO4
    90 1:134/302 Adam Park T-6in4 he.net f
    91 1:153/7715 Dallas Hinton Native Shaw Comms
    92 1:218/840 Morgan Collins Native Linode
    93 2:5020/921 Andrew Savin Native HURRICANE-IPV6-24
    94 2:240/1634 Hugo Andriessen Native Vodafone
    95 2:280/2040 Leo Barnhoorn Native KPN f
    96 2:5020/736 Egor Glukhov Native RUWEB f
    97 2:221/10 Tommi Koivula Native Hetzner f INO4
    97 1:266/420 Scott Street Native Comcast OO
    99 1:218/850 John Nicpon Native LINODE-US
    100 1:142/104 Clive Reuben Native SNETFCC-1
    101 2:301/1 Alisha Stutz Native CH-DATAWIRE
    102 3:633/267 Andrew Clarke Native Widebandnetv6
    103 2:5035/63 Vladimir Goncharov Native RFEIV6NET
    104 2:5010/152 Dmitry Smirnov Native RU-SELECTCEL
    105 2:5010/252 Dmitry Smirnov T-6in4 TUNNEL-BROKER-NET-1
    106 2:5020/290 Andrew Kolchoogin T-6in4 he.net


    T-6in4 Static 6in4
    T-AYIY Dynamic AYIYA
    T-6to4 6to4
    T-6RD 6RD

    Remarks:

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    (zone, net, node in decimal notation)
    IO Incoming only (Node can not make outgoing IPv6 calls)
    OO Outgoing only (Node can not accept incoming IPv6 calls).
    INO4 No IPv4 (Node can not accept incoming IPv4 calls).
    PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
    but is configured to try IPv4 first)
    6DWN The IPv6 connectivity of this node is temporarely down.
    NO6 The node no longer presents an IPv6 address in the nodelist
    and will soon be removed from this list.
    HOLD The node is temporarely off-line. Mail may be routed.
    DOWN This node is Down for both IPv4 and IPv6 and will be
    removed from this list if the condition pertains.
    PM Prospective Member. The node has demonstrated IPv6
    capability but is not listed or does not advertise an
    IPv6 address in the Fidonet nodelist yet.


    Notes:

    To make an IPv6 connection to a node connected via 6to4 tunneling
    one may have to force the mailer into IPv6 (-6 option in binkd's
    node config for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
    and up when compiled with AF_FORCE=1). If the destination address
    is a 6to4 tunnel address (2002::/16) many OSs default to IPv4 if
    an IPv4 address is present.



    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Jay Harris@1:229/664.2 to Michiel van der Vlist on Sun Jun 26 20:00:11 2022
    *** Quoting Michiel van der Vlist from a message to All ***

    Please check your entry. Ig it needs updateing, please let me know.

    96 2:5020/736 Egor Glukhov Native RUWEB f
    97 2:221/10 Tommi Koivula Native Hetzner f INO4
    97 1:266/420 Scott Street Native Comcast OO
    99 1:218/850 John Nicpon Native LINODE-US

    Just a nit pick, 97 appears twice, though the count is correct. :)


    Jay

    ... It is impossible to please the whole world and your mother-in-law

    --- Telegard v3.09.g2-sp4/mL
    * Origin: Northern Realms/TG tg.nrbbs.net Binbrook, ON (1:229/664.2)
  • From Michiel van der Vlist@2:280/5555 to Jay Harris on Mon Jun 27 07:19:36 2022
    Hello Jay,

    On Sunday June 26 2022 20:00, you wrote to me:

    97 2:221/10 Tommi Koivula Native Hetzner f INO4
    97 1:266/420 Scott Street Native Comcast

    Just a nit pick, 97 appears twice, though the count is correct. :)

    Thanks.

    Has been fixed.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to All on Mon Jul 18 18:29:28 2022
    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555

    Updated 18 July 2022


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen Native Freedom f
    2 2:280/5003 Kees van Eeten Native KPN f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
    4 2:280/5555 Michiel van der Vlist Native Ziggo f
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula Native Elisa f
    7 2:221/6 Tommi Koivula Native OVH
    8 2:5030/257 Vova Uralsky Native PCextreme
    9 1:154/10 Nicholas Boel Native Spectrum f
    10 2:203/0 Bjorn Felten T-6in4 he.net
    11 2:280/5006 Kees van Eeten Native KPN f INO4
    12 3:712/848 Scott Little T-6in4 he.net f
    13 2:5020/545 Alexey Vissarionov T-6in4 he.net f
    14 1:103/17 Stephen Hurd T-6in4 he.net
    15 2:5020/9696 Alexander Skovpen T-6in4 TUNNELBROKER-0
    16 2:421/790 Viktor Cizek Native CZ-IJC-20071015
    17 2:222/2 Kim Heino Native TeliaSonera
    18 3:633/280 Stephen Walsh Native AusNetServers f
    19 1:19/10 Matt Bedynek T-6in4 he.net
    20 3:770/1 Paul Hayton T-6in4 he.net
    21 3:770/100 Paul Hayton T-6in4 he.net
    22 2:5053/58 Alexander Kruglikov Native TTK-Volga f
    23 1:103/1 Stephen Hurd Native Choopa
    24 3:633/281 Stephen Walsh Native Internode
    25 2:310/31 Richard Menedetter Native DE-NETCUP f
    26 3:633/410 Tony Langdon Native IINET
    27 2:5020/329 Oleg Lukashin Native Comfortel f
    28 2:246/1305 Emil Schuster Native TAL.DE
    29 2:2448/4000 Tobias Burchhardt Native DTAG IO
    30 2:331/51 Marco d'Itri Native BOFH-IT
    31 1:154/30 Mike Miller Native LINODE
    32 2:5001/100 Dmitry Protasoff Native OVH
    33 2:5059/38 Andrey Mundirov T-6in4 he.net
    34 2:240/5853 Philipp Giebel Native Hetzner
    35 2:5083/444 Peter Khanin Native OVH
    36 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
    37 1:123/10 Wayne Smith T-6in4 he.net
    38 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    39 1:135/300 Eric Renfro Native Amazon.com
    40 1:103/13 Stephen Hurd Native Choopa
    41 2:5020/1042 Michael Dukelsky Native FirstByte
    42 2:5095/0 Sergey V. Efimoff T-6in4 he.net
    43 2:5095/20 Sergey V. Efimoff T-6in4 he.net
    44 2:5019/400 Konstantin Kuzov Native LT-LT
    45 2:467/239 Mykhailo Kapitanov Native Vultr f
    46 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    47 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
    48 2:280/2000 Michael Trip Native Xs4All
    49 2:230/38 Benny Pedersen Native Linode
    50 2:460/58 Stas Mishchenkov T-6in4 he.net f
    51 2:5020/2123 Anton Samsonov T-6in4 TUNNEL-BROKER-NET-0
    52 2:5020/2332 Andrey Ignatov Native ru.rtk
    53 2:5005/49 Victor Sudakov T-6in4 he.net f
    54 2:5005/77 Valery Lutoshkin T-6in4 NTS f
    55 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    56 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    57 2:5010/352 Dmitriy Smirnov Native SAGE-SU-V6
    58 2:292/854 Ward Dossche Native Proximus
    59 2:469/122 Sergey Zabolotny T-6in4 he.net f
    60 2:5053/400 Alexander Kruglikov Native FirstVDS f
    61 2:5030/1997 Alexey Fayans T-6in4 he.net
    62 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    63 2:2452/502 Ludwig Bernhartzeder Native DTAG
    64 2:423/39 Karel Kral Native WEDOS
    65 2:5080/102 Stas Degteff T-6to4 NOVATOR
    66 2:280/1049 Simon Voortman Native Solcon
    67 1:102/127 Bradley Thornton Native Hetzner
    68 2:335/364 Fabio Bizzi Native OVH
    69 1:124/5016 Nigel Reed Native DAL1-US f
    70 2:5075/37 Andrew Komardin Native IHC-NET
    71 2:263/5 Martin List-Petersen Native TuxBox
    72 2:5030/1520 Andrey Geyko T-6in4 he.net f
    73 1:229/664 Jay Harris Native Rogers f
    74 1:134/101 Kostie Muirhead T-6in4 he.net f
    75 2:280/2030 Martien Korenblom Native Transip
    76 3:633/509 Deon George Native Telstra
    77 2:5020/4441 Yuri Myakotin Native SOVINTEL
    78 1:320/319 Andrew Leary Native Comcast f
    79 2:240/5824 Anna Christina Nass Native DTAG f
    80 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
    81 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
    82 2:301/812 Benoit Panizon Native WOODYV6
    83 1:229/616 Vasily Losev Native GIGEPORT
    84 2:301/113 Alisha Manuela Stutz T-6in4 he.net
    85 1:134/100 Kostie Muirhead T-6in4 he.net f
    86 1:134/101 Kostie Muirhead T-6in4 he.net f
    87 1:134/102 Shelley Petersen T-6in4 he.net f INO4
    88 1:134/103 Gordon Muirhead T-6in4 he.net f
    89 1:134/301 Brandon Moore T-6in4 he.net f INO4
    90 1:134/302 Adam Park T-6in4 he.net f
    91 1:153/7715 Dallas Hinton Native Shaw Comms
    92 1:218/840 Morgan Collins Native Linode
    93 2:5020/921 Andrew Savin Native HURRICANE-IPV6-24
    94 2:240/1634 Hugo Andriessen Native Vodafone
    95 2:280/2040 Leo Barnhoorn Native KPN f
    96 2:5020/736 Egor Glukhov Native RUWEB f
    97 2:221/10 Tommi Koivula Native Hetzner f INO4
    98 1:266/420 Scott Street Native Comcast OO
    99 1:218/850 John Nicpon Native LINODE-US
    100 1:142/104 Clive Reuben Native SNETFCC-1
    101 2:301/1 Alisha Stutz Native CH-DATAWIRE
    102 3:633/267 Andrew Clarke Native Widebandnetv6
    103 2:5035/63 Vladimir Goncharov Native RFEIV6NET
    104 2:5010/252 Dmitry Smirnov T-6in4 TUNNEL-BROKER-NET-1
    105 2:5020/290 Andrew Kolchoogin T-6in4 he.net
    106 1:218/401 James Downs Native Scaleway PM *1


    T-6in4 Static 6in4
    T-AYIY Dynamic AYIYA
    T-6to4 6to4
    T-6RD 6RD

    Remarks:

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    (zone, net, node in decimal notation)
    IO Incoming only (Node can not make outgoing IPv6 calls)
    OO Outgoing only (Node can not accept incoming IPv6 calls).
    INO4 No IPv4 (Node can not accept incoming IPv4 calls).
    PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
    but is configured to try IPv4 first)
    6DWN The IPv6 connectivity of this node is temporarely down.
    NO6 The node no longer presents an IPv6 address in the nodelist
    and will soon be removed from this list.
    HOLD The node is temporarely off-line. Mail may be routed.
    DOWN This node is Down for both IPv4 and IPv6 and will be
    removed from this list if the condition pertains.
    PM Prospective Member. The node has demonstrated IPv6
    capability but is not listed or does not advertise an
    IPv6 address in the Fidonet nodelist yet.

    PM *1 lounge.egontech.com

    Notes:

    To make an IPv6 connection to a node connected via 6to4 tunneling
    one may have to force the mailer into IPv6 (-6 option in binkd's
    node config for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
    and up when compiled with AF_FORCE=1). If the destination address
    is a 6to4 tunnel address (2002::/16) many OSs default to IPv4 if
    an IPv4 address is present.


    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to All on Sun Jul 31 10:46:34 2022
    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555

    Updated 31 July 2022


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen Native Freedom f
    2 2:280/5003 Kees van Eeten Native KPN f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
    4 2:280/5555 Michiel van der Vlist Native Ziggo f
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula Native Elisa f
    7 2:221/6 Tommi Koivula Native OVH
    8 2:5030/257 Vova Uralsky Native PCextreme
    9 1:154/10 Nicholas Boel Native Spectrum f
    10 2:203/0 Bjorn Felten T-6in4 he.net
    11 2:280/5006 Kees van Eeten Native KPN f INO4
    12 3:712/848 Scott Little T-6in4 he.net f
    13 2:5020/545 Alexey Vissarionov T-6in4 he.net f
    14 1:103/17 Stephen Hurd T-6in4 he.net
    15 2:5020/9696 Alexander Skovpen T-6in4 TUNNELBROKER-0
    16 2:421/790 Viktor Cizek Native CZ-IJC-20071015
    17 2:222/2 Kim Heino Native TeliaSonera
    18 3:633/280 Stephen Walsh Native AusNetServers f
    19 1:19/10 Matt Bedynek T-6in4 he.net
    20 3:770/1 Paul Hayton T-6in4 he.net
    21 3:770/100 Paul Hayton T-6in4 he.net
    22 2:5053/58 Alexander Kruglikov Native TTK-Volga f
    23 1:103/1 Stephen Hurd Native Choopa
    24 3:633/281 Stephen Walsh Native Internode
    25 2:310/31 Richard Menedetter Native DE-NETCUP f
    26 3:633/410 Tony Langdon Native IINET
    27 2:5020/329 Oleg Lukashin Native Comfortel f
    28 2:246/1305 Emil Schuster Native TAL.DE
    29 2:2448/4000 Tobias Burchhardt Native DTAG IO
    30 2:331/51 Marco d'Itri Native BOFH-IT
    31 1:154/30 Mike Miller Native LINODE
    32 2:5001/100 Dmitry Protasoff Native OVH
    33 2:5059/38 Andrey Mundirov T-6in4 he.net
    34 2:240/5853 Philipp Giebel Native Hetzner
    35 2:5083/444 Peter Khanin Native OVH
    36 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f 6DWN
    37 1:123/10 Wayne Smith T-6in4 he.net
    38 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    39 1:135/300 Eric Renfro Native Amazon.com
    40 1:103/13 Stephen Hurd Native Choopa
    41 2:5020/1042 Michael Dukelsky Native FirstByte
    42 2:5095/0 Sergey V. Efimoff T-6in4 he.net
    43 2:5095/20 Sergey V. Efimoff T-6in4 he.net
    44 2:5019/400 Konstantin Kuzov Native LT-LT
    45 2:467/239 Mykhailo Kapitanov Native Vultr f
    46 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    47 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
    48 2:280/2000 Michael Trip Native Xs4All
    49 2:230/38 Benny Pedersen Native Linode
    50 2:460/58 Stas Mishchenkov T-6in4 he.net f
    51 2:5020/2123 Anton Samsonov T-6in4 TUNNEL-BROKER-NET-0
    52 2:5020/2332 Andrey Ignatov Native ru.rtk
    53 2:5005/49 Victor Sudakov T-6in4 he.net f
    54 2:5005/77 Valery Lutoshkin T-6in4 NTS f
    55 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    56 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    57 2:5010/352 Dmitriy Smirnov Native SAGE-SU-V6
    58 2:292/854 Ward Dossche Native Proximus
    59 2:469/122 Sergey Zabolotny T-6in4 he.net f
    60 2:5053/400 Alexander Kruglikov Native FirstVDS f
    61 2:5030/1997 Alexey Fayans T-6in4 he.net
    62 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    63 2:2452/502 Ludwig Bernhartzeder Native DTAG 6DWN
    64 2:423/39 Karel Kral Native WEDOS
    65 2:5080/102 Stas Degteff T-6to4 NOVATOR
    66 2:280/1049 Simon Voortman Native Solcon
    67 1:102/127 Bradley Thornton Native Hetzner
    68 2:335/364 Fabio Bizzi Native OVH
    69 1:124/5016 Nigel Reed Native DAL1-US f
    70 2:5075/37 Andrew Komardin Native IHC-NET
    71 2:263/5 Martin List-Petersen Native TuxBox
    72 2:5030/1520 Andrey Geyko T-6in4 he.net f
    73 1:229/664 Jay Harris Native Rogers f
    74 1:134/101 Kostie Muirhead T-6in4 he.net f
    75 2:280/2030 Martien Korenblom Native Transip
    76 3:633/509 Deon George Native Telstra
    77 2:5020/4441 Yuri Myakotin Native SOVINTEL
    78 1:320/319 Andrew Leary Native Comcast f
    79 2:240/5824 Anna Christina Nass Native DTAG f
    80 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
    81 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
    82 2:301/812 Benoit Panizon Native WOODYV6
    83 1:229/616 Vasily Losev Native GIGEPORT
    84 2:301/113 Alisha Manuela Stutz T-6in4 he.net
    85 1:134/100 Kostie Muirhead T-6in4 he.net f
    86 1:134/101 Kostie Muirhead T-6in4 he.net f
    87 1:134/102 Shelley Petersen T-6in4 he.net f INO4
    88 1:134/103 Gordon Muirhead T-6in4 he.net f
    89 1:134/301 Brandon Moore T-6in4 he.net f INO4
    90 1:134/302 Adam Park T-6in4 he.net f
    91 1:153/7715 Dallas Hinton Native Shaw Comms
    92 1:218/840 Morgan Collins Native Linode
    93 2:5020/921 Andrew Savin Native HURRICANE-IPV6-24
    94 2:240/1634 Hugo Andriessen Native Vodafone
    95 2:280/2040 Leo Barnhoorn Native KPN f
    96 2:5020/736 Egor Glukhov Native RUWEB f
    97 2:221/10 Tommi Koivula Native Hetzner f INO4
    98 1:266/420 Scott Street Native Comcast OO
    99 1:218/850 John Nicpon Native LINODE-US
    100 1:142/104 Clive Reuben Native SNETFCC-1
    101 2:301/1 Alisha Stutz Native CH-DATAWIRE
    102 3:633/267 Andrew Clarke Native Widebandnetv6
    103 2:5035/63 Vladimir Goncharov Native RFEIV6NET
    104 2:5010/252 Dmitry Smirnov T-6in4 TUNNEL-BROKER-NET-1
    105 2:5020/290 Andrew Kolchoogin T-6in4 he.net
    106 1:218/401 James Downs Native Scaleway PM *1
    107 1:214/22 Ray Quinn t-6in4 he.net
    108 2:5030/49 Sergey Myasoedov Native FR-VIRTUA-SYSTEMS
    109 1:218/820 Ryan Fantus Native DIGITALOCEAN


    T-6in4 Static 6in4
    T-AYIY Dynamic AYIYA
    T-6to4 6to4
    T-6RD 6RD

    Remarks:

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    (zone, net, node in decimal notation)
    IO Incoming only (Node can not make outgoing IPv6 calls)
    OO Outgoing only (Node can not accept incoming IPv6 calls).
    INO4 No IPv4 (Node can not accept incoming IPv4 calls).
    PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
    but is configured to try IPv4 first)
    6DWN The IPv6 connectivity of this node is temporarely down.
    NO6 The node no longer presents an IPv6 address in the nodelist
    and will soon be removed from this list.
    HOLD The node is temporarely off-line. Mail may be routed.
    DOWN This node is Down for both IPv4 and IPv6 and will be
    removed from this list if the condition pertains.
    PM Prospective Member. The node has demonstrated IPv6
    capability but is not listed or does not advertise an
    IPv6 address in the Fidonet nodelist yet.

    PM *1 lounge.egontech.com

    Notes:

    To make an IPv6 connection to a node connected via 6to4 tunneling
    one may have to force the mailer into IPv6 (-6 option in binkd's
    node config for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
    and up when compiled with AF_FORCE=1). If the destination address
    is a 6to4 tunnel address (2002::/16) many OSs default to IPv4 if
    an IPv4 address is present.


    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Ray Quinn@1:214/23 to Michiel van der Vlist on Sun Jul 31 05:22:08 2022

    Hello Michiel!

    31 Jul 22 10:46, you wrote to all:

    107 1:214/22 Ray Quinn t-6in4 he.net

    T-6in4 Static 6in4

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    (zone, net, node in decimal notation)

    I once had mine set up for this. For the life of me, I cannot find out what I did to make it work. It seems that I failed to backup the network settings when "upgrading" the last time. Can someone point me in the right direction? Using Debian 11 (bullseye)

    73 de W6RAY Ray Quinn
    Visalia, CA DM06II
    Ham Shack Hotline 4655

    If the right side of the brain controls the left side of the body,
    then only left-handed people are in their right mind.

    --- GoldED+/W64-MSVC 1.1.5-b20180707
    * Origin: Ray's Road Node | Somewhere in California. (1:214/23)
  • From Kees van Eeten@2:280/5003.4 to Ray Quinn on Sun Jul 31 15:56:46 2022
    Hello Ray!

    31 Jul 22 05:22, you wrote to Michiel van der Vlist:

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    (zone, net, node in decimal notation)

    I once had mine set up for this. For the life of me, I cannot find out what I did to make it work. It seems that I failed to backup the network settings when "upgrading" the last time. Can someone point me in the right direction? Using Debian 11 (bullseye)

    I added something like this to /etc/network/interfaces.
    Ignore the fact that I use a vlan, just use the interface name you use.

    iface vlan102 inet6 auto
    pre-up ip token set ::f1d0:2:280:5003 dev $IFACE

    Kees

    --- GoldED+/LNX 1.1.5--b20180707
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Kees van Eeten@2:280/5003.4 to Ray Quinn on Sun Jul 31 16:32:22 2022
    Hello Ray!

    31 Jul 22 05:22, you wrote to Michiel van der Vlist:

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    (zone, net, node in decimal notation)

    I once had mine set up for this. For the life of me, I cannot find out what I did to make it work. It seems that I failed to backup the network settings when "upgrading" the last time. Can someone point me in the right direction? Using Debian 11 (bullseye)

    Even more simple. On a Raspberry Pi I use just.

    -----------------
    auto eth0
    iface eth0 inet dhcp
    pre-up ip token set ::f1d0:2:280:5006 dev $IFACE
    ----------------

    Kees

    --- GoldED+/LNX 1.1.5--b20180707
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Jay Harris@1:229/664.1 to Ray Quinn on Sun Jul 31 10:45:38 2022
    *** Quoting Ray Quinn from a message to Michiel van der Vlist ***

    I once had mine set up for this. For the life of me, I cannot find
    out what I did to make it work. It seems that I failed to backup the network settings when "upgrading" the last time. Can someone point me
    in the right direction? Using Debian 11 (bullseye)

    This is how I have it setup on Ubuntu 20.04.4 LTS. I had to do something different on my Pi install, but I can't find those instructions anymore, it was more complicated.


    sudo nano /etc/netplan/00-installer-config.yaml

    # This is the network config written by 'subiquity'
    network:
    ethernets:
    ens160:
    dhcp4: true
    ipv6-address-token: "::f1d0:1:229:664"
    version: 2


    I believe all of the lines were already there, I just had to add in the the ipv6-address-token line.


    Jay

    ... I've started sleeping in our fireplace. Now I sleep like a log!

    --- Telegard v3.09.g2-sp4/mL
    * Origin: Northern Realms/TG tg.nrbbs.net Binbrook, ON (1:229/664.1)
  • From Michiel van der Vlist@2:280/5555 to All on Sat Oct 8 19:40:55 2022
    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555

    Updated 8 October 2022


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen Native Freedom f
    2 2:280/5003 Kees van Eeten Native KPN f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
    4 2:280/5555 Michiel van der Vlist Native Ziggo f
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula Native Elisa f
    7 2:221/6 Tommi Koivula Native OVH
    8 2:5030/257 Vova Uralsky Native PCextreme
    9 1:154/10 Nicholas Boel Native Spectrum f
    10 2:203/0 Bjorn Felten T-6in4 he.net
    11 2:280/5006 Kees van Eeten Native KPN f INO4
    12 3:712/848 Scott Little T-6in4 he.net f
    13 2:5020/545 Alexey Vissarionov T-6in4 he.net f
    14 1:103/17 Stephen Hurd T-6in4 he.net
    15 2:5020/9696 Alexander Skovpen T-6in4 TUNNELBROKER-0
    16 2:421/790 Viktor Cizek Native CZ-IJC-20071015
    17 2:222/2 Kim Heino Native TeliaSonera
    18 3:633/280 Stephen Walsh Native AusNetServers f
    19 1:19/10 Matt Bedynek T-6in4 he.net
    20 3:770/1 Paul Hayton T-6in4 he.net
    21 3:770/100 Paul Hayton T-6in4 he.net
    22 2:5053/58 Alexander Kruglikov Native TTK-Volga f
    23 1:103/1 Stephen Hurd Native Choopa
    24 3:633/281 Stephen Walsh Native Internode
    25 2:310/31 Richard Menedetter Native DE-NETCUP f
    26 3:633/410 Tony Langdon Native IINET
    27 2:5020/329 Oleg Lukashin Native Comfortel f
    28 2:246/1305 Emil Schuster Native TAL.DE
    29 2:2448/4000 Tobias Burchhardt Native DTAG IO
    30 2:331/51 Marco d'Itri Native BOFH-IT
    31 1:154/30 Mike Miller Native LINODE
    32 2:5001/100 Dmitry Protasoff Native OVH
    33 2:5059/38 Andrey Mundirov T-6in4 he.net
    34 2:240/5853 Philipp Giebel Native Hetzner
    35 2:5083/444 Peter Khanin Native OVH
    36 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
    37 1:123/10 Wayne Smith T-6in4 he.net
    38 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    39 1:135/300 Eric Renfro Native Amazon.com
    40 1:103/13 Stephen Hurd Native Choopa
    41 2:5020/1042 Michael Dukelsky Native FirstByte
    42 2:5095/0 Sergey V. Efimoff T-6in4 he.net
    43 2:5095/20 Sergey V. Efimoff T-6in4 he.net
    44 2:5019/400 Konstantin Kuzov Native LT-LT
    45 2:467/239 Mykhailo Kapitanov Native Vultr f
    46 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    47 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
    48 2:280/2000 Michael Trip Native KPN
    49 2:230/38 Benny Pedersen Native Linode
    50 2:460/58 Stas Mishchenkov T-6in4 he.net f
    51 2:5020/2123 Anton Samsonov T-6in4 TUNNEL-BROKER-NET-0
    52 2:5020/2332 Andrey Ignatov Native ru.rtk
    53 2:5005/49 Victor Sudakov T-6in4 he.net f
    54 2:5005/77 Valery Lutoshkin T-6in4 NTS f
    55 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    56 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    57 2:5010/352 Dmitriy Smirnov Native SAGE-SU-V6
    58 2:292/854 Ward Dossche Native Proximus
    59 2:469/122 Sergey Zabolotny T-6in4 he.net f
    60 2:5053/400 Alexander Kruglikov Native FirstVDS f
    61 2:5030/1997 Alexey Fayans T-6in4 he.net
    62 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    63 2:2452/502 Ludwig Bernhartzeder Native DTAG
    64 2:423/39 Karel Kral Native WEDOS
    65 2:5080/102 Stas Degteff T-6to4 NOVATOR
    66 2:280/1049 Simon Voortman Native Solcon
    67 1:102/127 Bradley Thornton Native Hetzner
    68 2:335/364 Fabio Bizzi Native OVH
    69 1:124/5016 Nigel Reed Native DAL1-US f
    70 2:5075/37 Andrew Komardin Native IHC-NET
    71 2:263/5 Martin List-Petersen Native TuxBox
    72 2:5030/1520 Andrey Geyko T-6in4 he.net f
    73 1:229/664 Jay Harris Native Rogers f
    74 1:134/101 Kostie Muirhead T-6in4 he.net f
    75 2:280/2030 Martien Korenblom Native Transip
    76 3:633/509 Deon George Native Telstra
    77 2:5020/4441 Yuri Myakotin Native SOVINTEL
    78 1:320/319 Andrew Leary Native Comcast f
    79 2:240/5824 Anna Christina Nass Native DTAG f
    80 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
    81 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
    82 2:301/812 Benoit Panizon Native WOODYV6
    83 1:229/616 Vasily Losev Native GIGEPORT
    84 2:301/113 Alisha Manuela Stutz T-6in4 he.net
    85 1:134/100 Kostie Muirhead T-6in4 he.net f
    86 1:134/101 Kostie Muirhead T-6in4 he.net f
    87 1:134/102 Shelley Petersen T-6in4 he.net f INO4
    88 1:134/103 Gordon Muirhead T-6in4 he.net f
    89 1:134/301 Brandon Moore T-6in4 he.net f INO4
    90 1:134/302 Adam Park T-6in4 he.net f
    91 1:153/7715 Dallas Hinton Native Shaw Comms
    92 1:218/840 Morgan Collins Native Linode
    93 2:5020/921 Andrew Savin Native HURRICANE-IPV6-24
    94 2:240/1634 Hugo Andriessen Native Vodafone
    95 2:280/2040 Leo Barnhoorn Native KPN f
    96 2:5020/736 Egor Glukhov Native RUWEB f
    97 2:221/10 Tommi Koivula Native Hetzner f INO4
    98 1:266/420 Scott Street Native Comcast OO
    99 1:218/850 John Nicpon Native LINODE-US
    100 1:142/104 Clive Reuben Native SNETFCC-1
    101 2:301/1 Alisha Stutz Native CH-DATAWIRE
    102 3:633/267 Andrew Clarke Native Widebandnetv6
    103 2:5035/63 Vladimir Goncharov Native RFEIV6NET
    104 2:5010/252 Dmitry Smirnov T-6in4 TUNNEL-BROKER-NET-1
    105 2:5020/290 Andrew Kolchoogin T-6in4 he.net
    106 1:218/401 James Downs Native Scaleway PM *1
    107 1:214/22 Ray Quinn t-6in4 he.net
    108 2:5030/49 Sergey Myasoedov Native FR-VIRTUA-SYSTEMS
    109 1:218/820 Ryan Fantus Native DIGITALOCEAN
    110 1:135/395 Charles Blackburn Native BHN-CPE PM *2


    T-6in4 Static 6in4
    T-AYIY Dynamic AYIYA
    T-6to4 6to4
    T-6RD 6RD

    Remarks:

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    (zone, net, node in decimal notation)
    IO Incoming only (Node can not make outgoing IPv6 calls)
    OO Outgoing only (Node can not accept incoming IPv6 calls).
    INO4 No IPv4 (Node can not accept incoming IPv4 calls).
    PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
    but is configured to try IPv4 first)
    6DWN The IPv6 connectivity of this node is temporarely down.
    NO6 The node no longer presents an IPv6 address in the nodelist
    and will soon be removed from this list.
    HOLD The node is temporarely off-line. Mail may be routed.
    DOWN This node is Down for both IPv4 and IPv6 and will be
    removed from this list if the condition pertains.
    PM Prospective Member. The node has demonstrated IPv6
    capability but is not listed or does not advertise an
    IPv6 address in the Fidonet nodelist yet.

    PM *1 lounge.egontech.com
    PM *2 bbs.thefbo.us


    Notes:

    To make an IPv6 connection to a node connected via 6to4 tunneling
    one may have to force the mailer into IPv6 (-6 option in binkd's
    node config for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
    and up when compiled with AF_FORCE=1). If the destination address
    is a 6to4 tunnel address (2002::/16) many OSs default to IPv4 if
    an IPv4 address is present.


    === Cut ===
    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to All on Tue Nov 1 22:55:54 2022
    List of IPv6 nodes
    By Michiel van der Vlist, 2:280/5555

    Updated 1 November 2022


    Node Nr. Sysop Type Provider Remark

    1 2:280/464 Wilfred van Velzen Native Freedom f
    2 2:280/5003 Kees van Eeten Native KPN f
    3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
    4 2:280/5555 Michiel van der Vlist Native Ziggo f
    5 1:320/219 Andrew Leary Native Comcast f
    6 2:221/1 Tommi Koivula Native Elisa f
    7 2:221/6 Tommi Koivula Native OVH
    8 2:5030/257 Vova Uralsky Native PCextreme
    9 1:154/10 Nicholas Boel Native Spectrum f
    10 2:203/0 Bjorn Felten T-6in4 he.net
    11 2:280/5006 Kees van Eeten Native KPN f INO4
    12 3:712/848 Scott Little T-6in4 he.net f
    13 2:5020/545 Alexey Vissarionov T-6in4 he.net f
    14 1:103/17 Stephen Hurd T-6in4 he.net
    15 2:5020/9696 Alexander Skovpen T-6in4 TUNNELBROKER-0
    16 2:421/790 Viktor Cizek Native CZ-IJC-20071015
    17 2:222/2 Kim Heino Native TeliaSonera
    18 3:633/280 Stephen Walsh Native AusNetServers f
    19 1:19/10 Matt Bedynek T-6in4 he.net
    20 3:770/1 Paul Hayton T-6in4 he.net
    21 3:770/100 Paul Hayton T-6in4 he.net
    22 2:5053/58 Alexander Kruglikov Native TTK-Volga f
    23 1:103/1 Stephen Hurd Native Choopa
    24 3:633/281 Stephen Walsh Native Internode
    25 2:310/31 Richard Menedetter Native DE-NETCUP f
    26 3:633/410 Tony Langdon Native IINET
    27 2:5020/329 Oleg Lukashin Native Comfortel f
    28 2:246/1305 Emil Schuster Native TAL.DE
    29 2:2448/4000 Tobias Burchhardt Native DTAG IO
    30 2:331/51 Marco d'Itri Native BOFH-IT
    31 1:154/30 Mike Miller Native LINODE
    32 2:5001/100 Dmitry Protasoff Native OVH
    33 2:5059/38 Andrey Mundirov T-6in4 he.net
    34 2:240/5853 Philipp Giebel Native Hetzner
    35 2:5083/444 Peter Khanin Native OVH
    36 2:240/5413 Ingo Juergensmann Native RRBONE-COLO f PM *4
    37 1:123/10 Wayne Smith T-6in4 he.net
    38 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    39 1:135/300 Eric Renfro Native Amazon.com
    40 1:103/13 Stephen Hurd Native Choopa
    41 2:5020/1042 Michael Dukelsky Native FirstByte
    42 2:5095/0 Sergey V. Efimoff T-6in4 he.net
    43 2:5095/20 Sergey V. Efimoff T-6in4 he.net
    44 2:5019/400 Konstantin Kuzov Native LT-LT
    45 2:467/239 Mykhailo Kapitanov Native Vultr f
    46 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    47 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
    48 2:280/2000 Michael Trip Native KPN
    49 2:230/38 Benny Pedersen Native Linode
    50 2:460/58 Stas Mishchenkov T-6in4 he.net f
    51 2:5020/2123 Anton Samsonov T-6in4 TUNNEL-BROKER-NET-0
    52 2:5020/2332 Andrey Ignatov Native ru.rtk
    53 2:5005/49 Victor Sudakov T-6in4 he.net f
    54 2:5005/77 Valery Lutoshkin T-6in4 NTS f
    55 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    56 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    57 2:5010/352 Dmitriy Smirnov Native SAGE-SU-V6
    58 2:292/854 Ward Dossche Native Proximus
    59 2:469/122 Sergey Zabolotny T-6in4 he.net f
    60 2:5053/400 Alexander Kruglikov Native FirstVDS f
    61 2:5030/1997 Alexey Fayans T-6in4 he.net
    62 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    63 2:240/502 Ludwig Bernhartzeder Native DTAG PM *3
    64 2:423/39 Karel Kral Native WEDOS
    65 2:5080/102 Stas Degteff T-6to4 NOVATOR
    66 2:280/1049 Simon Voortman Native Solcon
    67 1:102/127 Bradley Thornton Native Hetzner
    68 2:335/364 Fabio Bizzi Native OVH
    69 1:124/5016 Nigel Reed Native DAL1-US f
    70 2:5075/37 Andrew Komardin Native IHC-NET
    71 2:263/5 Martin List-Petersen Native TuxBox
    72 2:5030/1520 Andrey Geyko T-6in4 he.net f
    73 1:229/664 Jay Harris Native Rogers f
    74 1:134/101 Kostie Muirhead T-6in4 he.net f
    75 2:280/2030 Martien Korenblom Native Transip
    76 3:633/509 Deon George Native Telstra
    77 2:5020/4441 Yuri Myakotin Native SOVINTEL
    78 1:320/319 Andrew Leary Native Comcast f
    79 2:240/5824 Anna Christina Nass Native DTAG f
    80 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
    81 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
    82 2:301/812 Benoit Panizon Native WOODYV6
    83 1:229/616 Vasily Losev Native GIGEPORT
    84 2:301/113 Alisha Manuela Stutz T-6in4 he.net
    85 1:134/100 Kostie Muirhead T-6in4 he.net f
    86 1:134/101 Kostie Muirhead T-6in4 he.net f
    87 1:134/102 Shelley Petersen T-6in4 he.net f INO4
    88 1:134/103 Gordon Muirhead T-6in4 he.net f
    89 1:134/301 Brandon Moore T-6in4 he.net f INO4
    90 1:134/302 Adam Park T-6in4 he.net f
    91 1:153/7715 Dallas Hinton Native Shaw Comms
    92 1:218/840 Morgan Collins Native Linode
    93 2:5020/921 Andrew Savin Native HURRICANE-IPV6-24
    94 2:240/1634 Hugo Andriessen Native Vodafone
    95 2:280/2040 Leo Barnhoorn Native KPN f
    96 2:5020/736 Egor Glukhov Native RUWEB f
    97 2:221/10 Tommi Koivula Native Hetzner f INO4
    98 1:266/420 Scott Street Native Comcast OO
    99 1:218/850 John Nicpon Native LINODE-US
    100 1:142/104 Clive Reuben Native SNETFCC-1
    101 2:301/1 Alisha Stutz Native CH-DATAWIRE
    102 3:633/267 Andrew Clarke Native Widebandnetv6
    103 2:5035/63 Vladimir Goncharov Native RFEIV6NET
    104 2:5010/252 Dmitry Smirnov T-6in4 TUNNEL-BROKER-NET-1
    105 2:5020/290 Andrew Kolchoogin T-6in4 he.net
    106 1:218/401 James Downs Native Scaleway PM *1
    107 1:214/22 Ray Quinn t-6in4 he.net
    108 2:5030/49 Sergey Myasoedov Native FR-VIRTUA-SYSTEMS
    109 1:218/820 Ryan Fantus Native DIGITALOCEAN
    110 1:135/395 Charles Blackburn Native BHN-CPE PM *2


    T-6in4 Static 6in4
    T-AYIY Dynamic AYIYA
    T-6to4 6to4
    T-6RD 6RD

    Remarks:

    f Has a ::f1d0:<zone>:<net>:<node> style host address.
    (zone, net, node in decimal notation)
    IO Incoming only (Node can not make outgoing IPv6 calls)
    OO Outgoing only (Node can not accept incoming IPv6 calls).
    INO4 No IPv4 (Node can not accept incoming IPv4 calls).
    PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
    but is configured to try IPv4 first)
    6DWN The IPv6 connectivity of this node is temporarely down.
    NO6 The node no longer presents an IPv6 address in the nodelist
    and will soon be removed from this list.
    HOLD The node is temporarely off-line. Mail may be routed.
    DOWN This node is Down for both IPv4 and IPv6 and will be
    removed from this list if the condition pertains.
    PM Prospective Member. The node has demonstrated IPv6
    capability but is not listed or does not advertise an
    IPv6 address in the Fidonet nodelist yet.

    PM *1 lounge.egontech.com
    PM *2 bbs.thefbo.us
    PM *3 Was: 2:2452/502
    PM *4 Was: 2:2452/413

    Notes:

    To make an IPv6 connection to a node connected via 6to4 tunneling
    one may have to force the mailer into IPv6 (-6 option in binkd's
    node config for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
    and up when compiled with AF_FORCE=1). If the destination address
    is a 6to4 tunnel address (2002::/16) many OSs default to IPv4 if
    an IPv4 address is present.


    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Stas Mishchenkov@2:460/5858 to Michiel van der Vlist on Wed Nov 2 12:06:44 2022
    Hi Michiel!

    Tuesday November 01 2022 22:55, you wrote to All:

    MvdV> 80 2:460/5858 Stas Mishchenkov T-6in4 he.net f
    MvdV> INO4

    [fido@brorabbit inbound]$ grep ',5858,' ~/nodelist/nodelist.367 ,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpublished-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4

    ;)

    Have a nice night.
    Stas Mishchenkov.

    --- Have You daily sexual life? Hide it proper from Your wife! ;)
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Michiel van der Vlist@2:280/5555 to Stas Mishchenkov on Wed Nov 2 10:14:20 2022
    Hello Stas,

    On Wednesday November 02 2022 12:06, you wrote to me:

    Tuesday November 01 2022 22:55, you wrote to All:

    MvdV>> 80 2:460/5858 Stas Mishchenkov T-6in4 he.net
    MvdV>> f INO4

    [fido@brorabbit inbound]$ grep ',5858,' ~/nodelist/nodelist.367 ,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpubli shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4

    Your point?


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Stas Mishchenkov@2:460/5858 to Michiel van der Vlist on Wed Nov 2 16:53:10 2022
    Hi Michiel!

    Wednesday November 02 2022 10:14, you wrote to me:

    Tuesday November 01 2022 22:55, you wrote to All:

    MvdV>>> 80 2:460/5858 Stas Mishchenkov T-6in4 he.net
    MvdV>>> f INO4

    [fido@brorabbit inbound]$ grep ',5858,' ~/nodelist/nodelist.367
    ,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpubli
    shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4

    MvdV> Your point?

    This node is on my desktop computer. It is used for debugging and testing software.

    Have a nice night.
    Stas Mishchenkov.

    --- Have You daily sexual life? Hide it proper from Your wife! ;)
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Michiel van der Vlist@2:280/5555 to Stas Mishchenkov on Wed Nov 2 15:45:03 2022
    Hello Stas,

    On Wednesday November 02 2022 16:53, you wrote to me:

    [fido@brorabbit inbound]$ grep ',5858,' ~/nodelist/nodelist.367
    ,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-U
    npubli shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4

    MvdV>> Your point?

    This node is on my desktop computer. It is used for debugging and
    testing software.

    OK.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Benny Pedersen@2:230/0 to Michiel van der Vlist on Tue Nov 8 21:52:28 2022
    Hello Michiel!

    02 Nov 2022 10:14, Michiel van der Vlist wrote to Stas Mishchenkov:

    MvdV> Hello Stas,

    MvdV> On Wednesday November 02 2022 12:06, you wrote to me:

    Tuesday November 01 2022 22:55, you wrote to All:

    MvdV>>> 80 2:460/5858 Stas Mishchenkov T-6in4 he.net
    MvdV>>> f INO4

    [fido@brorabbit inbound]$ grep ',5858,' ~/nodelist/nodelist.367
    ,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpubli
    shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4

    MvdV> Your point?

    space after 300


    Regards Benny

    ... too late to die young :)

    --- Msged/LNX 6.1.2 (Linux/6.0.5-gentoo-dist (x86_64))
    * Origin: gopher://fido.junc.eu/ (2:230/0)
  • From Stas Mishchenkov@2:460/5858 to Benny Pedersen on Wed Nov 9 09:33:08 2022
    Hi Benny!

    Tuesday November 08 2022 21:52, you wrote to Michiel van der Vlist:

    MvdV>>>> 80 2:460/5858 Stas Mishchenkov T-6in4 he.net
    MvdV>>>> f INO4

    [fido@brorabbit inbound]$ grep ',5858,' ~/nodelist/nodelist.367
    ,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpubli
    shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4

    MvdV>> Your point?

    space after 300

    It's not my. :)

    Have a nice night.
    Stas Mishchenkov.

    --- Have You daily sexual life? Hide it proper from Your wife! ;)
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Björn Felten@2:203/2 to Benny Pedersen on Wed Nov 9 14:29:08 2022
    shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4

    MvdV>> Your point?

    space after 300

    That's a line wrap error. Some antiquated FTN editors still don't support format=flowed as defined in RFC3676.


    --
    United we are strong, we win. Divided we are weak, we lose.

    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se:4119 (2:203/2)
  • From Björn Felten@2:203/2 to Stas Mishchenkov on Wed Nov 9 14:32:43 2022
    space after 300

    It's not my. :)

    Of course not. That would have caused an ;E line in the nodelist, if I recall correctly from my MakeNl reverse engineering days. 8-)


    --
    United we are strong, we win. Divided we are weak, we lose.

    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se:4119 (2:203/2)
  • From Stas Mishchenkov@2:460/5858 to Björn Felten on Wed Nov 9 17:07:42 2022

    *** Answering a msg posted in area _Carbon.Mail (Carbon.Mail).

    Hi Bjrn!

    Wednesday November 09 2022 14:32, you wrote to me:

    space after 300

    It's not my. :)

    Of course not. That would have caused an ;E line in the nodelist, if I recall correctly from my MakeNl reverse engineering days. 8-)

    In my case it was af fall of quoting. Take a look at the original message.

    Have a nice night.
    Stas Mishchenkov.

    --- Have You daily sexual life? Hide it proper from Your wife! ;)
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Ingo Juergensmann@2:240/5413 to Michiel van der Vlist on Mon Jan 16 18:52:30 2023
    Hello Michiel!

    08 Oct 22 19:40, you wrote to all:

    36 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f

    I think this should be changed to 2:240/5413 after net 2:2452 shut down.

    Ingo


    --- GoldED+/LNX 1.1.5--b20170303
    * Origin: AmigaXess - back in FidoNet after 17 years (2:240/5413)
  • From Michiel van der Vlist@2:280/5555 to Ingo Juergensmann on Mon Jan 23 09:53:20 2023
    Hello Ingo,

    On Monday January 16 2023 18:52, you wrote to me:

    08 Oct 22 19:40, you wrote to all:

    That's a long time ago...

    36 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f

    I think this should be changed to 2:240/5413 after net 2:2452 shut
    down.

    It was already changed in the first week of November...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)