The F I D O N E W S Volume 43, Number 01 05 Jan 2026 +--------------------------+-----------------------------------------+
| |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__| / \// | Publisher: Bj”rn Felten |
| ______ _//|| _\ / | |
| / Fido \ (_/(_|(____/ | Newspapers should have no friends. |
| (________) (jm) | -- JOSEPH PULITZER | +--------------------------+-----------------------------------------+


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

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

=================================================================
GENERAL ARTICLES =================================================================

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


Another year has passed. When we compare the statistics as published
by the end of 2023 and 2024 with those of today, we see that there is
little or no growth. The number of Fidonet IPv6 nodes keeps hoovering
around 110. On 31 December there were 116 IPv6 nodes. Considering that
Fidonet a s a whole has stopped growing a long time ago and is now
shrinking that isn't really bad.

120 _|
_| .
110 _| . .
_| .
100 _| .
_| .
90 _|
_| .
80 _| .
_|
70 _| .
_|
60 _|
_| .
50 _|
_|
40 _| .
_|
30 _|
_| .
20 _|
_|
10 _| .
_|
0 _|______________________________________________________________
| | | | | | | | | | | | |
2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026

Outside of Fidonet IPv6 continues to grow. Slowly but steadily. Accor-
ding to Google worldwide IPv6 adoptation now hoovers around or just
under 50%. 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 but I would say this is premature.

Back to Fidonet.

The number of Fidonet IPv6 nodes that still uses a tunnel dropped from
a quarter to a fifth. Nearly all of them via he.net, but a few via
another tunnel broker. So there is improvement but there are still too
many ISPs around that do not support IPv6. Shame!

The number of nodes carrying the INO4 flag dropped from 3 to 2. So the
vast majority of Fidonet still supports full IPv4. Not really what I
expected, but that is what it is. What I expected was that providers
switching their customers to CGNAT would have resulted in much more
IPv6 only nodes. But that obviously did no happen. Yet. That does not
mean CGNAT did not happen and that it is not a problem. With the
coming of FTTH (Fibre To The Home) especially here in Europe we see
many new ISPs that do not have lots of "historic" IPv4 and who do not
have, or do not want to spend, large sums of money to buy IPv4 on the
market. So they use CGNAT to have their customers connect to the IPv4
internet. Some of these providers - like mine - give customers the
option to get an IPv4 address outside the CGNAT pool and some don't.
But Fidonet sysops are resourcefull and they look for work arounds. In
Germany there is feste-ip.net that jumped in the gap. They provide
IPv4 access to servers run at home via an IPv4 to IPv6 port forwarder.
I mentioned that in my article titled "DS-Lite: a solution" in FN
34:33 Aug 2017. Some Fidonet sysop are using this or a similar service
to deal with CGNAT.

Another remarkable development is that a number of Fidonet systems
advertise IPv6 capability via an AAAA record on the host name in the
nodelist, but they dot not actually support IPv6. Dmitry Protasoff
maintains a system that (among other things) monitors the nodelist
for systems that advertise IPv6 capability.

https://nodelist.fidonet.cc/analytics/ipv6

Compare that to the list of nodes That advertise IPv6 but are actually
IPv4 only:

https://nodelist.fidonet.cc/analytics/ipv6-advertised-ipv4-only

So some 20% of the nodes advertising IPv6 connectivity do not actually
support it. One of the problems with dual stack is that if one of the advertised connection mechanims fails, it can take a long time before
it is discovered. Most applications just fall back to IPv4 if IPv6
fails. That includes nearly all binkp capable mailers. Winpoint is the
odd exception.

This large number of nodes that advertise IPv6 connectivity but that
do not actually support it is a bit of a mystery to me. My impression
is that many of those sysops are not even aware of the situation.
They make use of he services of a DNS provider that supports DDNS
and they get an IPv6 address assigned by default. Of which they do
not seem to be aware and so they do not configure their systems to
accept incoming IPv6 calls. This is a bit of speculation as most of
the sysops concerend do not respond to netmail, the systems seem to
run on autopilot.

Another phenomenon that may have existed for some time but that only
recently emerged from Dmitry's statistics is that there are a number
of nodes who's IPv6 reachability is unstable. One day they have IPv6
and the next day they haven't. To be back again after a couple of
days.

https://nodelist.fidonet.cc/analytics/ipv6-weekly-news

I have no explanation but the fact many of these nodes reside in
regions 46 and 50 suggests it may have to do with the war going on in
Eastern Europe. The observed instability may or may not be
specificallly linked to IPv6, it may affect their IPv4 reachability as
well, but that was not investigated.


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 32:52 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
FN 41:01 Jan 2024 IPv6 in 2023
FN 41:53 Dec 2024 IPv6 in 2024
FN 42:01 Jan 2025 IPv6 only experiment

Happy IPv6 in 2026.

No AI was used for writing this article. -----------------------------------------------------------------

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

=================================================================
LIST OF FIDONET IPV6 NODES =================================================================

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

Updated 30 Dec 2025


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/Ziggo f
3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
4 2:280/5555 Michiel van der Vlist Native Ziggo/Delta 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 Native Bahnhof
10 2:280/5006 Kees van Eeten Native KPN f INO4
11 3:712/848 Scott Little T-6in4 he.net f
12 1:103/17 Stephen Hurd T-6in4 he.net
13 2:5020/9696 Alexander Skovpen T-6in4 IP4Market
14 2:421/790 Viktor Cizek Native JON.CZ Network
15 2:222/2 Kim Heino Native TeliaSonera
16 3:633/280 Stephen Walsh Native AusNetServers f
17 1:19/10 Matt Bedynek T-6in4 he.net
18 3:770/1 Paul Hayton Native VETTA
19 3:770/100 Paul Hayton Native VETTA
20 2:5053/58 Alexander Kruglikov Native ER-Telecom f
21 1:103/1 Stephen Hurd Native Choopa
22 3:633/281 Stephen Walsh Native Internode
23 2:310/31 Richard Menedetter Native DE-NETCUP f
24 3:633/410 Tony Langdon Native IINET
25 2:5020/329 Oleg Lukashin Native Comfortel f
26 2:331/51 Marco d'Itri Native BOFH-IT
27 1:154/30 Mike Miller Native LINODE
28 2:5001/100 Dmitry Protasoff Native Layer7 Networks
29 2:5059/38 Andrey Mundirov T-6in4 he.net f
30 2:5083/444 Peter Khanin Native OVH
31 2:240/5413 Ingo Juergensmann Native RRBONE-COLO f
32 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
33 1:103/13 Stephen Hurd Native Choopa
34 2:5019/400 Konstantin Kuzov Native JSC IOT
35 2:463/1331 Andrei Dzedolik Native DigitalOcean
36 2:5010/275 Evgeny Chevtaev T-6in4 IP4Market f
37 2:280/2000 Michael Trip Native KPN
38 2:230/38 Benny Pedersen Native Linode
39 2:460/58 Stas Mishchenkov Native PE Tsibrankov f
40 2:460/5858 Stas Mishchenkov Native PE Tsibrankov f
41 2:5020/1042 Stas Mishchenkov Native PE Tsibrankov f
42 2:5101/1 Andrey Ignatov Native HETZNER
43 2:5005/49 Victor Sudakov T-6in4 he.net f
44 2:5057/53 Ivan Kovalenko Native ER-Telecom f
45 2:5010/352 Dmitriy Smirnov Native SAGE-SU-V6
46 2:292/854 Ward Dossche Native Proximus
47 2:469/122 Sergey Zabolotny T-6in4 he.net f
48 2:5053/400 Alexander Kruglikov Native FirstVDS f
49 2:5030/1997 Alexey Fayans T-6in4 he.net
59 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
51 2:240/502 Ludwig Bernhartzeder Native DTAG
52 2:423/39 Karel Kral Native HOSTUP f
53 2:280/1049 Simon Voortman Native Solcon
54 2:335/364 Fabio Bizzi Native OVH
55 1:124/5016 Nigel Reed Native DAL1-US f
56 1:229/664 Jay Harris Native Rogers f
57 2:280/2030 Martien Korenblom Native Transip
58 3:633/509 Deon George Native Telstra
59 2:5020/4441 Yuri Myakotin Native SOVINTEL
60 1:320/319 Andrew Leary Native Comcast f
61 2:240/5824 Anna Christina Nass Native DTAG f
62 2:301/812 Benoit Panizon Native WOODYV6
63 1:229/616 Vasily Losev Native Hostodo
64 2:301/113 Alisha Stutz T-6in4 he.net
65 1:153/7715 Dallas Hinton Native Shaw Comms
66 1:218/840 Morgan Collins Native Linode
67 2:5020/921 Andrew Savin Native HURRICANE-IPV6-24
68 2:240/1634 Hugo Andriessen Native Vodafone
69 2:280/2040 Leo Barnhoorn Native KPN f
79 2:5020/736 Egor Glukhov Native RUWEB f
71 2:221/10 Tommi Koivula Native Hetzner f INO4
72 1:218/850 John Nicpon Native LINODE-US
73 2:5035/63 Vladimir Goncharov Native RFEIV6NET
74 2:5020/290 Andrew Kolchoogin T-6in4 he.net
75 2:5030/49 Sergey Myasoedov Native FR-VIRTUA-SYSTEMS
76 1:103/705 Rob Swindell Native Spectrum f
77 1:134/303 Travis Mehrer Native Shaw Comms
78 2:5057/19 Max Vasilyev Native ER-Telecom f
79 2:5075/35 Eugene Subbotin Native EuroByte LLC f
80 2:5075/37 Andrew Komardin Native IHC
81 2:550/278 Vladislav Muschinskikh Native FirstByte
82 2:5010/278 Vladislav Muschinskikh T-6in4 he.net f
83 2:5020/715 Alex Barinov T-6in4 he.net f
84 1:16/201 Sergey Myasoedov Native Amazon
85 1:104/117 Vitaliy Aksyonov Native LLC
86 2:5030/1340 Dmitry Afanasiev T-6in4 TUNNEL-BROKER-NET
87 2:221/360 Tommi Koivula Native Elisa f
88 2:5031/25 Alex Kazankov Native VDSINA
89 4:902/26 Fernando Toledo Native Claro
90 2:280/2050 Floris van Unen Native Azure
91 2:280/2060 Dennis Slagers Native Ziggo f
92 1:266/625 Scott Street Native Verizon
93 2:5020/5452 Alex Barinov T-6in4 he.net
94 2:5030/723 Alexey Khromov Native RU-AI-20240222
95 3:633/2744 Deon George Native EXETEL-AU
96 4:930/1 David Gonzalez Native EPMNET
97 3:633/267 Andrew Clarke Native widebandnetv6 OO
98 2:463/877 Alex Shuman Native UA-WEBBER f
99 2:5030/1520 Ekaterina Geyko T-6in4 he.net f
100 2:201/127 Sergey Semernin Native Obenetwork
101 2:2448/400 Tobias Burchhardt Native DTAG
102 2:240/5853 Philipp Giebel Native Hetzner
103 2:5080/172 Stas Vlasov Native Internet Pro LLC
104 2:343/107 Enric Lleal Native Hetzner
105 1:128/10 Jordan McGilvray Native DigitalOcean
106 2:421/7902 Viktor Cozek Native JON.CZ Network
107 2:5020/1313 Sergey Efimoff T-6in4 he.net
108 1:16/201 Sergey Myasoedov Native Amazon
109 1:135/220 Wayne Smith T-6in4 he.net
110 1:229/112 Scott Tompkins T-6in4 he.net
111 2:5020/545 Alexey Vissarionov T-6in4 he.net f
112 1:267/160 Jeremy Brown Native Networks, LLC
113 2:5030/74 Michael Skolsky Native Skynet LLC
114 2:5030/843 Petr Antonov Native Belcloud LTD
115 2:240/8010 Siggi Schoenicke Native DTAG
116 1:214/22 Ray Quinn 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.
Example: ::f1d0:2:280:5555 (for node 2:280/5555)
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 004


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

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

=================================================================
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.7m 0.5m 22 0.0h 0.0h 22
280/* 0.8m 2.7m 1002 5.0h 6.7h 1001
292/* 2.8m 1.9m 6 5.1h 4.9h 5
320/* 2.2m 1.0m 556 0.8h 2.1h 556

Sigma 1.3m 2.3m 1586 3.5h 5.8h 1584

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

Input nodelist nodelist.002
size 160.3kb
date 2026-01-02

The nodelist has 827 nodes in it
and a total of 1206 non-comment entries

including 4 zones
30 regions
158 hosts
59 hubs
admin overhead 251 ( 30.35 %)

and 78 private nodes
15 nodes down
35 nodes on hold
off line overhead 128 ( 15.48 %)


Speed summary:

>9600 = 16 ( 1.93 %)
9600 = 75 ( 9.07 %)
(HST = 2 or 2.67 %)
(CSP = 0 or 0.00 %)
(PEP = 0 or 0.00 %)
(MAX = 0 or 0.00 %)
(HAY = 0 or 0.00 %)
(V32 = 43 or 57.33 %)
(V32B = 0 or 0.00 %)
(V34 = 49 or 65.33 %)
(V42 = 41 or 54.67 %)
(V42B = 0 or 0.00 %)
2400 = 1 ( 0.12 %)
1200 = 0 ( 0.00 %)
300 = 735 ( 88.88 %)

ISDN = 15 ( 1.81 %)

-----------------------------------------------------
IP Flags Protocol Number of systems -----------------------------------------------------
IBN Binkp 713 ( 86.22 %) ----------------------------------
IFC Raw ifcico 59 ( 7.13 %) ----------------------------------
IFT FTP 32 ( 3.87 %) ----------------------------------
ITN Telnet 91 ( 11.00 %) ----------------------------------
IVM Vmodem 11 ( 1.33 %) ----------------------------------
IP Other 1 ( 0.12 %) ----------------------------------
INO4 IPv6 only 5 ( 0.60 %) ----------------------------------

CrashMail capable = 756 ( 91.41 %)
MailOnly nodes = 242 ( 29.26 %)
Listed-only nodes = 19 ( 2.30 %)



[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)