The F I D O N E W S Volume 41, Number 14 01 Apr 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. LIST OF FIDONET IPV6 NODES ............................... 1
List of IPv6 nodes ....................................... 1
2. JAMNNTPD SERVERS LIST .................................... 4
The Johan Billing JamNNTPd project ....................... 4
3. FIDONEWS'S FIDONET SOFTWARE LISTING ...................... 5
4. SPECIAL INTEREST ......................................... 12
Statistics from the Fidoweb .............................. 12
Nodelist Stats ........................................... 13
5. FIDONEWS INFORMATION ..................................... 15
How to Submit an Article ................................. 15
Credits, Legal Infomation, Availability .................. 17

--- 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 25 Mar 2024


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/Caiway 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 1:135/395 Charles Blackburn Native Charter Comms
89 1:134/303 Travis Mehrer Native Shaw Comms
90 2:5057/19 Max Vasilyev Native ER-Telecom f
91 2:5075/35 Eugene Subbotin Native RUWEB f
92 2:5075/37 Andrew Komardin Native IHC
93 2:5075/128 Eugene Subbotin T-6in4 IP4Market f
94 2:550/278 Vladislav Muschinskikh Native FirstByte
95 2:5010/278 Vladislav Muschinskikh T-6in4 he.net f
96 2:240/5411 Stephan Gebbers Native DTAG
97 2:5020/715 Alex Barinov T-6in4 he.net
98 1:16/201 Sergey Myasoedov Native Amazon
99 1:104/117 Vitaliy Aksyonov Native LLC
100 1:218/880 Lloyd Fellon Native Charter Comms
101 2:5030/1340 Dmitry Afanasiev T-6in4 TUNNEL-BROKER-NET
102 2:221/360 Tommi Koivula Native Elisa f
103 2:5031/25 Alex Kazankov Native VDSINA
104 4:902/26 Fernando Toledo Native Claro
105 3:633/257 Andrew Clarke Native widebandnetv6 OO


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 091

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

--- 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/* 1.0m 2.2m 722 4.0h 10.4h 722
280/* 0.7m 0.4m 1005 3.0h 4.3h 1005
292/* 2.2m 2.0m 5 2.8h 5.6h 4
320/* 2.6m 1.3m 250 2.1h 3.8h 249

Sigma 1.0m 1.6m 1982 3.3h 7.2h 1980

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

Input nodelist nodelist.089
size 159.9kb
date 2024-03-29

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

including 4 zones
31 regions
156 hosts
61 hubs
admin overhead 252 ( 29.72 %)

and 92 private nodes
38 nodes down
19 nodes on hold
off line overhead 149 ( 17.57 %)


Speed summary:

>9600 = 23 ( 2.71 %)
9600 = 123 ( 14.50 %)
(HST = 2 or 1.63 %)
(CSP = 0 or 0.00 %)
(PEP = 0 or 0.00 %)
(MAX = 0 or 0.00 %)
(HAY = 0 or 0.00 %)
(V32 = 60 or 48.78 %)
(V32B = 0 or 0.00 %)
(V34 = 57 or 46.34 %)
(V42 = 51 or 41.46 %)
(V42B = 0 or 0.00 %)
2400 = 1 ( 0.12 %)
1200 = 0 ( 0.00 %)
300 = 701 ( 82.67 %)

ISDN = 18 ( 2.12 %)

-----------------------------------------------------
IP Flags Protocol Number of systems -----------------------------------------------------
IBN Binkp 727 ( 85.73 %) ----------------------------------
IFC Raw ifcico 66 ( 7.78 %) ----------------------------------
IFT FTP 49 ( 5.78 %) ----------------------------------
ITN Telnet 114 ( 13.44 %) ----------------------------------
IVM Vmodem 14 ( 1.65 %) ----------------------------------
IP Other 1 ( 0.12 %) ----------------------------------
INO4 IPv6 only 5 ( 0.59 %) ----------------------------------

CrashMail capable = 781 ( 92.10 %)
MailOnly nodes = 243 ( 28.66 %)
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)

Re: FidoNews 41:14 [01/06]: List Of Fidonet Ipv6 Nodes
By: FidoNews Robot to All on Mon Apr 01 2024 12:59 am

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

I think this could be clarified better: The zone, net, and node values of the FidoNet address are actually in *hexadecimal* notation, but only using the hexadecimal digits 0-9, so that when viewing the IPv6 address in hexadecimal (as is the norm), it can be more easily visually compared with the decimal representation of that equivalent FidoNet address.
--
digital man (rob)

Sling Blade quote #20:
Doyle: Hey is this the kind of retard that drools and rubs shit in his hair? Norco, CA WX: 48.0øF, 80.0% humidity, 1 mph SSE wind, 0.12 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Hello Rob,

On Friday April 05 2024 10:05, you wrote to me:

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

I think this could be clarified better: The zone, net, and node values
of the FidoNet address are actually in *hexadecimal* notation, but
only using the hexadecimal digits 0-9, so that when viewing the IPv6 address in hexadecimal (as is the norm), it can be more easily
visually compared with the decimal representation of that equivalent FidoNet address.

Here we probably run into a case where more explanation will actually lead to more confusion. In the beginning it was considered self explanatory. Until some wise guy created an address with zone, net and node in actual hexadecimal and claimed the "f" for it. That conflicts with the idea of the zone, net and node number being easely identafiable by humans. So I declined and added the explanatory line. And now that leads to confusion. Perhaps just giving an example will be better. How about this:

f Has a ::f1d0:<zone>:<net>:<node> style host address.
Example: ::f1d0:2:280:5555

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: Michiel's laptop (2:280/464.5555)

Re: FidoNews 41:14 [01/06]: List Of Fidonet Ipv6 Nodes
By: Michiel van der Vlist to Rob Swindell on Mon Apr 08 2024 02:12 pm

Hello Rob,

On Friday April 05 2024 10:05, you wrote to me:

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

I think this could be clarified better: The zone, net, and node values of the FidoNet address are actually in *hexadecimal* notation, but
only using the hexadecimal digits 0-9, so that when viewing the IPv6 address in hexadecimal (as is the norm), it can be more easily
visually compared with the decimal representation of that equivalent FidoNet address.

Here we probably run into a case where more explanation will actually lead to more confusion. In the beginning it was considered self explanatory. Until some wise guy created an address with zone, net and node in actual hexadecimal and claimed the "f" for it. That conflicts with the idea of the zone, net and node number being easely identafiable by humans. So I declined and added the explanatory line. And now that leads to confusion. Perhaps just giving an example will be better. How about this:

f Has a ::f1d0:<zone>:<net>:<node> style host address.
Example: ::f1d0:2:280:5555

Yes, I think an example is a good idea, but clarify that the example IPv6 address represnts the FTN 3D address of 2:280/5555.

I think the actual term for this representation is "packed BCD": https://en.wikipedia.org/wiki/Binary-coded_decimal
--
digital man (rob)

Rush quote #84:
Looming low & ominous, twilight premature t-heads rumbling a distance overture Norco, CA WX: 62.1øF, 38.0% humidity, 5 mph W wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Hello Rob,

On Monday April 08 2024 20:54, you wrote to me:

Perhaps just giving an example will be better. How about this:

f Has a ::f1d0:<zone>:<net>:<node> style host address.
Example: ::f1d0:2:280:5555

Yes, I think an example is a good idea, but clarify that the example
IPv6 address represnts the FTN 3D address of 2:280/5555.

Isn't that self explanatory?

I think the actual term for this representation is "packed BCD": https://en.wikipedia.org/wiki/Binary-coded_decimal

Yes, Binary Coded Decimal... Some microprocessors even had special instructions for that. DAA for the Motorola serie IIRCs. But I don't think it is a good idea to mention that term here. It may lead to more confusion to those among us who have never come across it. So how about this:


f Has a ::f1d0:<zone>:<net>:<node> style host address.
Example: ::f1d0:2:280:5555 (for node 2:280/5555)


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: Michiel's laptop (2:280/464.5555)

Hello, Michiel van der Vlist.
On 9/4/24 10:17 you wrote:

f Has a ::f1d0:<zone>:<net>:<node> style host address.
Example: ::f1d0:2:280:5555 (for node 2:280/5555)

How about something like: "Decimal-looking hexadecimal numbers"

--
Carlos
--- Hotdoged/2.13.5/Android
* Origin: cyberiada (2:341/234.12)

Re: FidoNews 41:14 [01/06]: List Of Fidonet Ipv6 Nodes
By: Michiel van der Vlist to Rob Swindell on Tue Apr 09 2024 10:17 am

it is a good idea to mention that term here. It may lead to more confusion to those among us who have never come across it. So how about this:

f Has a ::f1d0:<zone>:<net>:<node> style host address.
Example: ::f1d0:2:280:5555 (for node 2:280/5555)

Yes, I think that's more clear.
--
digital man (rob)

Synchronet "Real Fact" #2:
Synchronet version 2 for DOS and OS/2 was released to the public domain in 1997 Norco, CA WX: 73.6øF, 17.0% humidity, 4 mph N wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Hello Carlos,

On Tuesday April 09 2024 17:00, you wrote to me:

f Has a ::f1d0:<zone>:<net>:<node> style host address.
Example: ::f1d0:2:280:5555 (for node 2:280/5555)

How about something like: "Decimal-looking hexadecimal numbers"

Nah, I think that will just give more confusion...

Thank you for your input.

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: Michiel's laptop (2:280/464.5555)

Hello Rob,

On Tuesday April 09 2024 11:25, you wrote to me:

f Has a ::f1d0:<zone>:<net>:<node> style host address.
Example: ::f1d0:2:280:5555 (for node 2:280/5555)

Yes, I think that's more clear.

Ok, so that is what it will be then.

Thank you for your input.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: Michiel's laptop (2:280/464.5555)