• FidoNews 41:01 [00/08]: The Front Page

    From FidoNews Robot@2:2/2 to All on Mon Jan 1 02:56:49 2024
    The F I D O N E W S Volume 41, Number 01 01 Jan 2024 +--------------------------+-----------------------------------------+
    | |The newsletter of the | | |
    | | FidoNet community. | | Netmail attach to (POTS): |
    | | Est. 1984 | | Editor @ 2:2/2 (+46-31-960447) |
    | | ____________| | |
    | | / __ | Netmail attach to (BinkP): |
    | | / / \ | Editor @ 2:203/0 |
    | | WOOF! ( /|oo \ | |
    | \_______\(_| /_) | Email attach to: |
    | _ @/_ \ _ | b @ felten dot se |
    | | | \ \\ | |
    | | (*) | \ ))| |
    | |__U__| / \// | Editor: Bj”rn Felten |
    | ______ _//|| _\ / | |
    | / Fido \ (_/(_|(____/ | Newspapers should have no friends. |
    | (________) (jm) | -- JOSEPH PULITZER | +--------------------------+-----------------------------------------+


    Table of Contents
    1. FOOD FOR THOUGHT ......................................... 1
    2. GENERAL ARTICLES ......................................... 2
    IPv6 in 2023 ............................................. 2
    A different kind of wish ................................. 6
    3. LIST OF FIDONET IPV6 NODES ............................... 7
    List of IPv6 nodes ....................................... 7
    4. JAMNNTPD SERVERS LIST .................................... 10
    The Johan Billing JamNNTPd project ....................... 10
    5. FIDONEWS'S FIDONET SOFTWARE LISTING ...................... 11
    6. SPECIAL INTEREST ......................................... 18
    Statistics from the Fidoweb .............................. 18
    Nodelist Stats ........................................... 19
    7. FIDONEWS INFORMATION ..................................... 21
    How to Submit an Article ................................. 21
    Credits, Legal Infomation, Availability .................. 23

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Mon Jan 1 02:56:49 2024
    =================================================================
    FOOD FOR THOUGHT =================================================================

    There are two days that we can do nothing about,
    yesterday and tomorrow.

    -- Mahatma Gandhi

    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Mon Jan 1 02:56:49 2024
    =================================================================
    GENERAL ARTICLES =================================================================

    IPv6 in 2023
    By Michiel van der Vlist, 2:280/5555


    Another year has passed. When we compare the statistics as published
    by the end of 2022 with those of today, we see that for the first
    time he growth of IPv6 in Fidonet has stopped. Not just stopped but
    the number of nodes has decreased from 108 to 98 nodes.


    110 _| .
    _| .
    100 _| .
    _| .
    90 _|
    _| .
    80 _| .
    _|
    70 _| .
    _|
    60 _|
    _| .
    50 _|
    _|
    40 _| .
    _|
    30 _|
    _| .
    20 _|
    _|
    10 _| .
    _| .
    0 _|__.___________________________________________________________
    | | | | | | | | | | | | |
    2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024


    I have no simple explanation for the drop. It is probably a combina-
    tion of factors. The general decline of Fidonet is almost certainly
    one of them. Whatever the reasons, it is not what I had expected.

    The number of nodes carrying the INO4 flag remained stable at 5. So
    the vast majority of Fidonet nodes still supports IPv4 and apparently
    still has a public IPv4 address. This is also against my expectation
    that the scarcety of IPv4 addresses would have had more impact on
    Fidonet by now. In the very long run we will of course see that when
    the InterNet moves towards IPv6 only that the number of INO4 flags
    rises. When we reach the point that it becomes a majority, we may
    consider dropping the INO4 flag and introduce an IPV4 flag instead.
    But that is still far in the future and I (or Fidonet) may not live
    to see it.

    Outside of Fidonet IPv6 continues to grow. According to Google world-
    wide IPv6 adoptation now hovers around 45%. Almost half of those
    visiting Google do so via IPv6.

    https://www.google.com/intl/nl/ipv6/statistics.html

    Some even claim the tipping point has been reached where IPv6 is now
    the norm.

    https://www.sidn.nl/en/news-and-blogs/tipping-point-reached- transition-to-ipv6-enters-a-new-phase

    Last year I wrote about IPv6 hoarders that sit on large blocks of IPv4
    that they hope to sell at fantastic prices in the future. They may be
    too late already. While the price of IPv4 has doubled from EUR 25 to
    EUR 50 in 2021, in 2023 the price dropped to about EUR 35.

    https://www.sidn.nl/en/news-and-blogs/are-we-past-peak-ipv4

    So do not be surprised if this bubble will burst in the coming years.


    Regarding my personal situation: I now have Fiber To The Home. The
    company that runs the hardware is roling out their fiber network
    like madness. The competition on the FTTH market is enormous and their
    first priority seems to be to plant their flag in as many households
    in The Netherlands as possible in order to be ahead of the competi-
    tion. IPv6 was not on their list of priorities, the network was rolled
    out as IPv4 only. Until about three or four month ago when they ran
    out of IPv4...

    Then two things happened: one: they started putting their customers
    on CGNAT and two: they finally started rolling out IPv6.
    In that order...

    The switch to CGNAT was not announced in advance. Groups of customers
    had their public IPv4 address changed overnight to an address in the
    RFC 6598 range. (100.64.0.0/10) While the vast majority of customers
    never even noticed, those that had port forwarding active were "not
    amused" to say the least. Fortunately they offered a way to reverse
    the process for those that wanted to keep a public IPv4 address but
    the damage was done. One of he reasons they did not - and still do not
    - informm the customers concerned in advance is that the vast majority
    of customers would have no idea what it was all about and start over-
    loading the help desk in panic. It was a balancing act. Later they
    started excluding customers from the CGNAT pool that had a port
    forward defined in the modem/router that was given to them. That
    calmed down the uproar. I personally escaped the CGNAT. Possibly
    because I configured a port forward minutes after the connection was
    active or I was just lucky.

    IMNSHO they should have rolled out IPv6 before CGNAT became unavoid-
    able. But they waited until they no longer had a choice and what
    happened next was predictable. In fact I predicted it years ago. They
    still have to figure out the child's diseases. My FTTH connection be-
    came active on September 14. IPv4 only. On October 6th, I suddenly got
    IPv6. I was happy until I discovered that there was no way to open a
    pinhole in the IPv6 firewall of the modem/router they had given me.
    I reported this next day and the first response was that I could not
    expect such an "advanced feature" in a simple modem/router. It took me
    about a month to convince them that pinholing is the IPv6 way to do
    what port forwarding does for IPv4 and that not supporting it is a
    serious shortcoming. Finally they admitted that it is something that
    should be fixed and will be fixed. But it has not been fixed at the
    moment I write this and I was told there is no schedule for the fix
    yet, but it certainly will not be fixed before 2024.

    Fortunately I foresaw problems like this and I did not cancel my cable connection yet. So for the time being I am dual homed and my full IPv6 connectivity is still intact. Yeah, those are the problems that can be
    expected when one postpones IPv6 until one runs out of options and it
    has to be done in a hurry. Wait with fixing the roof untill it starts
    raining and you will get wet...

    Actually I think the FTTH company missed an opportunity. Instead of
    rolling out the network as IPv4 only first, they should have rolled it
    out as IPv6 only with IPv4 As A Service. That would have saved them at
    least one step in the transition. But that probably did not go well
    with their goal of rolling out the fibres as quickly as they could...


    Something else: (semi) public WiFi networks. In the beginning of 2023
    whenever I came across a (semi) public WiFi network I started checking
    for IPv6 support. The result was disappointing. In the over two dozen
    networks that I checked over the years, only TWO of them offered IPv6.
    One was a camping in the East of The Netherlands and the other a venue
    in the centre of The Netherlands that is often used by the Dutch com-
    puter club HCC. That network is maintained by the club members... It
    means we still have a long way to go to an IPv6 only world.


    In order not to have to tell the same story over and over again, I
    sometimes refer people to Fidonews articles I wrote in the past.
    Since there seems to be no easely available searcheable archive, I
    made a list of these articles. I hope I did not miss any.

    My previous Fidonews articles about IPv6:


    FN 26:31 Jul 2009 FidoNet and IPv6
    FN 28:04 Jan 2011 FidoNet and IPv4 depletion
    FN 28:07 Feb 2011 Fido and IPv6 Day
    FN 28:16 Apr 2011 APNIC runs out
    FN 28:20 May 2011 The IPv6 echo
    FN 28:31 Aug 2011 A SECOND LIFE FOR THE LINKSYS Part 1
    FN 28:32 Aug 2011 A SECOND LIFE FOR THE LINKSYS PArt 2
    FN 28:45 Nov 2011 A "first"
    FN 29:04 Jan 2012 World IPv6 Launch Day, 6 June 2012
    FN 29:09 Feb 2012 A SECOND LIFE FOR THE LINKSYS Part 3
    FN 29:38 Sep 2012 RIPE is out of IPv4 addresses.
    FN 32:17 Apr 2015 IPv6 penetration in the nodelist
    FN 32:26 Jun 2015 ARIN is out of IPv4 addresses.
    FN 3:252 Dec 2015 IPv6 in Fidonet by the end of 2015
    FN 33:02 Jan 2016 IPv6 in two thousand SIX teen
    FN 33:06 Feb 2016 Another barrier broken.
    FN 34:01 Jan 2017 IPv6 in 2016
    FN 34:13 Mar 2017 SixXs Sunset 06-06-2017
    FN 34:30 Jul 2017 TV without IPv6
    FN 34:31 Jul 2017 DS-Lite emulation experiment v2.0
    FN 34:37 Sep 2017 DS-Lite emulation experiment 2.0, the results
    FN 34:33 Aug 2017 DS-Lite: a solution
    FN 34:38 Sep 2017 DS-Lite Emulation experiment v2.1
    FN 35:01 Jan 2018 IPv6 in 2017
    FN 35:53 Dec 2018 IPv6 in 2018
    FN 36:52 Dec 2019 IPv6 in 2019
    FN 38:01 Jan 2021 IPv6 in 2020
    FN 38:20 May 2021 100 IPv6 nodes
    FN 39:01 Jan 2022 IPv6 in 2021
    FN 40:01 Jan 2023 IPv6 in 2022


    Happy IPv6 in 2024.



    -----------------------------------------------------------------
    A different kind of wish
    Ward Dossche - 2:292/854

    It is the time of wishing well, of beautiful lights, of grandchildren
    with cramped stomachs because they have to go through a 'New Year's
    letter', good food, warmth and "especially good health"... (at least
    if you happen to live in this part of the world).

    And yet ...

    ... and yet there are times when the wishes do not turn out as they
    were desired, when you want to be together with your loved one today
    but that is not possible ...

    Moments when everyone assumes that everything is fine with the others,
    that you can wish anything to anyone...

    ... while you are only interested in the "health" of that special
    one who has been lying in a hospital bed for 2 months with a plethora
    of tubes, drip-bags, needles, syringes, pills, potions, 'stuff',
    blood samples..

    And yet ...

    ...and yet, despite all the misery she experiences, there is so much
    to be grateful for.

    There is a roof over our heads, we have food when we are hungry, we
    can enjoy the best medical care available, there are friends, family,
    children, grandchildren... we have warmth when the cold comes, there
    is safe drinking water, we have the freedom to express our opinions...
    there is peace... here.

    We are doing well, despite everything ...

    Happy New Year ... Tine ...... Come home soon ... <3 ...

    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Mon Jan 1 02:56:49 2024
    =================================================================
    LIST OF FIDONET IPV6 NODES =================================================================

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

    Updated 17 Dec 2023


    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 1:154/10 Nicholas Boel Native Spectrum f
    9 2:203/0 Bjorn Felten T-6in4 he.net
    10 2:280/5006 Kees van Eeten Native KPN f INO4
    11 3:712/848 Scott Little T-6in4 he.net f
    12 2:5020/545 Alexey Vissarionov T-6in4 he.net f
    13 1:103/17 Stephen Hurd T-6in4 he.net
    14 2:5020/9696 Alexander Skovpen T-6in4 IP4Market
    15 2:421/790 Viktor Cizek Native CZ-IJC-20071015
    16 2:222/2 Kim Heino Native TeliaSonera
    17 3:633/280 Stephen Walsh Native AusNetServers f
    18 1:19/10 Matt Bedynek T-6in4 he.net
    19 3:770/1 Paul Hayton Native VETTA
    20 3:770/100 Paul Hayton Native VETTA
    21 2:5053/58 Alexander Kruglikov Native JSC IOT f
    22 1:103/1 Stephen Hurd Native Choopa
    23 3:633/281 Stephen Walsh Native Internode
    24 2:310/31 Richard Menedetter Native DE-NETCUP f
    25 3:633/410 Tony Langdon Native IINET
    26 2:5020/329 Oleg Lukashin Native Comfortel f
    27 2:2448/4000 Tobias Burchhardt Native DTAG IO
    28 2:331/51 Marco d'Itri Native BOFH-IT
    29 1:154/30 Mike Miller Native LINODE
    30 2:5001/100 Dmitry Protasoff Native OVH
    31 2:5059/38 Andrey Mundirov T-6in4 he.net
    32 2:5083/444 Peter Khanin Native OVH
    33 2:240/5413 Ingo Juergensmann Native RRBONE-COLO f
    34 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
    35 1:103/13 Stephen Hurd Native Choopa
    36 2:5020/1042 Michael Dukelsky Native FirstByte
    37 2:5019/400 Konstantin Kuzov Native LT-LT
    38 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
    39 2:5010/275 Evgeny Chevtaev T-6in4 IP4Market f
    40 2:280/2000 Michael Trip Native KPN
    41 2:230/38 Benny Pedersen Native Linode
    42 2:460/58 Stas Mishchenkov T-6in4 he.net f
    43 2:5101/1 Andrey Ignatov Native HETZNER
    44 2:5005/49 Victor Sudakov T-6in4 he.net f
    45 2:5005/106 Alexey Osiyuk T-6in4 he.net f
    46 2:5057/53 Ivan Kovalenko Native ER-Telecom f
    47 2:5010/352 Dmitriy Smirnov Native SAGE-SU-V6
    48 2:292/854 Ward Dossche Native Proximus
    49 2:469/122 Sergey Zabolotny T-6in4 he.net f
    50 2:5053/400 Alexander Kruglikov Native FirstVDS f
    51 2:5030/1997 Alexey Fayans T-6in4 he.net
    52 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
    53 2:240/502 Ludwig Bernhartzeder Native DTAG
    54 2:423/39 Karel Kral Native WEDOS
    55 2:280/1049 Simon Voortman Native Solcon
    56 2:335/364 Fabio Bizzi Native OVH
    57 1:124/5016 Nigel Reed Native DAL1-US f
    58 2:5030/1520 Andrey Geyko T-6in4 he.net f
    59 1:229/664 Jay Harris Native Rogers f
    60 2:280/2030 Martien Korenblom Native Transip
    61 3:633/509 Deon George Native Telstra
    62 2:5020/4441 Yuri Myakotin Native SOVINTEL
    63 1:320/319 Andrew Leary Native Comcast f
    64 2:240/5824 Anna Christina Nass Native DTAG f
    65 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
    66 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
    67 2:301/812 Benoit Panizon Native WOODYV6
    68 1:229/616 Vasily Losev Native GIGEPORT
    69 2:301/113 Alisha Stutz T-6in4 he.ne
    70 1:153/7715 Dallas Hinton Native Shaw Comms
    71 1:218/840 Morgan Collins Native Linode
    72 2:5020/921 Andrew Savin Native HURRICANE-IPV6-24
    73 2:240/1634 Hugo Andriessen Native Vodafone
    74 2:280/2040 Leo Barnhoorn Native KPN f
    75 2:5020/736 Egor Glukhov Native RUWEB f
    76 2:221/10 Tommi Koivula Native Hetzner f INO4
    77 1:218/850 John Nicpon Native LINODE-US
    78 2:301/1 Alisha Stutz Native CH-DATAWIRE
    79 1:134/0 Kostie Muirhead Native LINODE-US f INO4
    80 1:134/100 Kostie Muirhead Native LINODE-US f INO4
    81 2:5035/63 Vladimir Goncharov Native RFEIV6NET
    82 2:5020/290 Andrew Kolchoogin T-6in4 he.net
    83 1:214/22 Ray Quinn T-6in4 he.net
    84 2:5030/49 Sergey Myasoedov Native FR-VIRTUA-SYSTEMS
    85 1:218/820 Ryan Fantus Native DIGITALOCEAN
    86 1:103/705 Rob Swindell Native Spectrum f
    87 2:5020/5858 Alexander Kruglikov T-6in4 IP4Market f
    88 2:292/789 Niels Joncheere T-6in4 he.net
    89 1:135/395 Charles Blackburn Native Charter Comms
    90 1:134/303 Travis Mehrer Native Shaw Comms
    91 2:5057/19 Max Vasilyev Native ER-Telecom f
    92 2:5075/35 Eugene Subbotin Native RUWEB f
    93 2:5075/37 Andrew Komardin Native IHC
    94 2:5075/128 Eugene Subbotin T-6in4 IP4Market f
    95 2:550/278 Vladislav Muschinskikh Native FirstByte
    96 2:5010/278 Vladislav Muschinskikh T-6in4 he.net f


    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.


    Submitted on day 365

    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)
  • From FidoNews Robot@2:2/2 to All on Mon Jan 1 02:56:49 2024
    =================================================================
    SPECIAL INTEREST =================================================================

    Last week's statistics from the Fidoweb
    By EchoTime @ 2:203/0

    (Some nets may have lost their last
    digit for technical reasons)

    pkt (toss-toss) msg (write-toss)
    nodes mean dev no mean dev no

    221/* 0.9m 0.4m 596 4.0h 6.0h 596
    280/* 0.7m 0.6m 711 4.5h 5.7h 710
    292/* 3.3m 2.1m 7 1.0h 1.6h 6
    320/* 2.0m 0.8m 216 2.4h 4.5h 216

    Sigma 1.0m 0.7m 1530 4.0h 5.7h 1528

    -----------------------------------------------------------------
    Nodelist Stats

    Input nodelist nodelist.363
    size 159.8kb
    date 2023-12-29

    The nodelist has 849 nodes in it
    and a total of 1249 non-comment entries

    including 4 zones
    31 regions
    157 hosts
    61 hubs
    admin overhead 253 ( 29.80 %)

    and 94 private nodes
    35 nodes down
    18 nodes on hold
    off line overhead 147 ( 17.31 %)


    Speed summary:

    >9600 = 23 ( 2.71 %)
    9600 = 124 ( 14.61 %)
    (HST = 3 or 2.42 %)
    (CSP = 0 or 0.00 %)
    (PEP = 0 or 0.00 %)
    (MAX = 0 or 0.00 %)
    (HAY = 0 or 0.00 %)
    (V32 = 61 or 49.19 %)
    (V32B = 0 or 0.00 %)
    (V34 = 58 or 46.77 %)
    (V42 = 52 or 41.94 %)
    (V42B = 0 or 0.00 %)
    2400 = 1 ( 0.12 %)
    1200 = 0 ( 0.00 %)
    300 = 701 ( 82.57 %)

    ISDN = 19 ( 2.24 %)

    -----------------------------------------------------
    IP Flags Protocol Number of systems -----------------------------------------------------
    IBN Binkp 731 ( 86.10 %) ----------------------------------
    IFC Raw ifcico 67 ( 7.89 %) ----------------------------------
    IFT FTP 48 ( 5.65 %) ----------------------------------
    ITN Telnet 114 ( 13.43 %) ----------------------------------
    IVM Vmodem 14 ( 1.65 %) ----------------------------------
    IP Other 1 ( 0.12 %) ----------------------------------
    INO4 IPv6 only 5 ( 0.59 %) ----------------------------------

    CrashMail capable = 782 ( 92.11 %)
    MailOnly nodes = 243 ( 28.62 %)
    Listed-only nodes = 18 ( 2.12 %)



    [Report produced by NETSTATS - A PD pgm]
    [ Revised by B Felten, 2:203/2]
    [ NetStats 3.8 2014-11-23]

    -----------------------------------------------------------------

    --- Azure/NewsPrep 3.0
    * Origin: Home of the Fidonews (2:2/2.0)