The F I D O N E W S Volume 42, Number 18 05 May 2025 +--------------------------+-----------------------------------------+
| |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
Configuring my own fiberglass modem/router part 1 ........ 1
2. LIST OF FIDONET IPV6 NODES ............................... 3
List of IPv6 nodes ....................................... 3
3. JAMNNTPD SERVERS LIST .................................... 6
The Johan Billing JamNNTPd project ....................... 6
4. FIDONEWS'S FIDONET SOFTWARE LISTING ...................... 7
5. SPECIAL INTEREST ......................................... 15
Nodelist Stats ........................................... 15
6. FIDONEWS INFORMATION ..................................... 17
How to Submit an Article ................................. 17
Credits, Legal Information, Availability ................. 19

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

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

Configuring my own fiberglass modem/router part 1
By Michiel van der Vlist, 2:280/5555

It has been well over a year now that I have fiber glass installed in
my house. There is a lot of competition at the moment. Several parties
are trying to get a foothold in the market. As a result priority lies
on getting as many flags planted in as many households in The
Netherlands as soon as possible. Quality of the provided service comes
later. So I was a bit reluctant in canceling my subscription with the
cable company when the fibre connection was delivered. I thought let's
keep them both for the moment just to be sure. And while I had two
connections I figured I might as well get the most of it by providing
dual homing for my Fidonet connection. So I installed an extra network
card on my Fidonet PC. It took some tuning and I found it worked best
when I configured the same DNS servers for both connections. No idea
why, but that was my experience. It turned out keeping the cable
connection for a while was a good decision. The modem/router (Nokia
XS-2426G-B) from the fiber company has problems with port forwarding
and IPv6 pinholing. I reported these issues but after well over a year
it still has not been fixed. It does not seem to have priority. So I
decided it was time to take action. My first step was to change
providers. The company that installed and exploits the fiber is not
the same company that provides the connection. In fact there are
several companies that offer connection on the fibre network. One of
those had an interesting offer for internet only. So I changed.
Unfortunatley that did not solve my problem. They gave me the same
Nokia XS-2426G-B with the very same firmware version. And of course
the same problems with port forwarding and IPv6 pinholing.

Fortunately internet providers here are by law required to facilitate
customers that want to use their own modems and routers. So I decided
to go for the adventure and forget about buggy stuff from the provider
and get my own modem and router. And I have to give it to them, that
contrary to the cable company that fought legal battles for many years
to block it, the fiber internet provider, Delta, loyally cooperates to facilitate the use of customer owned modems and routers.

There are a few snags though. For starters any change to the
admininstrative parameters in the connection can only be made with
the original modem/router connected. Think about upgrade to a higher
speed or... changing from CGNAT to having a public IPv4 address.
Apparently the new fiber companies have problems getting IPv4 addresse
for the fast growing number of their new customers. So about a year ag
they stopped issuing public IPv4 adresses to their customers. They
offer a CGNAT address in the range 100.64.0.0/10. That is OK for most
customers but not for those that run their own servers. Fortunately
they still have enough IPv4 to accommodate costomers thats need a
public routable IPv4 address. Just ask for it by subscribing to the
service "dynamic IP". Oddly enough they use the term "fixed address"
for a CGNAT address in the 192.168.100.0/10 range. That CGNAT address
is indeed fixed. Once issued it does not change any more. Whatever...
For now this service is free of charge. That may change in the future.
Anyway, I got a public IPv4 address in a few hours.

Next step is to have your own "modem" registered. They publish a list
of equipment that is compatible with their network. The list is quit
long but most of what is on the list is not available on the market.
Only a handfull remain. But if your "modem" is on the list all you hav
to do is connect it, call them and give then the PON-id. That is it.
My choice fell on the easy available Nokia XS-010X-Q which from now on
I shall refer to as the ONT. ( Optical Network Terminator )

Shortly after The ONT was connected the power led started flashing for
a couple of minutes indicating that a firmware upgrade is in progress.
That was one of the reasons for choosing the Nokia. It is the only one
of the available alternatives that automatically gets firmware upgrade
from Delta.

When the power and PON led are steady green it is time for the next
step. Connect something to the ONT and get data flowing. The ONT is
just a bridge, it has no router functions. But it has a user interface accesable on 192.168.100.1. No DHCP server so to access it I configure
the laptop that I use for my point 1 and other experiments to have a
fixed address of 192.168.100.2. Then I could acces the ONT's web
interface. There is very little that one can do but I could check that
the latest firmware was installed and that the optical signal level wa
OK.

I reconfigured my laptop to get its address via DHCP and I configured
VLAN 100. The latter is required for an internet connection over the
fiber, They use VLANs to seperate the various services. Fortunately
this is easy in Windows with many network card drivers. Delta uses
VLAN 100 for consumer internet. VLAN 102 for TV and 105 for a bussines connection. Other providers on the fiber use different VLAN numbers.

When I did that I got an IP address (4 and 6) and I had an inernet
connection. I made an outgoing binkp connection from my point 1. Then
I knew that the ONT and all beyond was OK.

Well, actually this is not exactly the order of things that happened
but for the sake of this article it will do. I will save the trial and
error steps that led to this result for the follow up article that
will be about the rest of my adventure. The part of connecting and
configuring a router.

So... To be continued...


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

--- 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 20 Apr 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 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/2 Bjorn Felten T-6in4 he.net 6DWN HOLD
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 ER-Telecom 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:331/51 Marco d'Itri Native BOFH-IT
28 1:154/30 Mike Miller Native LINODE
29 2:5001/100 Dmitry Protasoff Native Layer7 Networks
30 2:5059/38 Andrey Mundirov T-6in4 he.net
31 2:5083/444 Peter Khanin Native OVH
32 2:240/5413 Ingo Juergensmann Native RRBONE-COLO f
33 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
34 1:103/13 Stephen Hurd Native Choopa
35 2:5020/1042 Stas Mishchenkov T-6-in4 he.net f
36 2:5019/400 Konstantin Kuzov Native LT-LT
37 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
38 2:5010/275 Evgeny Chevtaev T-6in4 IP4Market f
39 2:280/2000 Michael Trip Native KPN
40 2:230/38 Benny Pedersen Native Linode
41 2:460/58 Stas Mishchenkov T-6in4 he.net f
42 2:5101/1 Andrey Ignatov Native HETZNER
43 2:5005/49 Victor Sudakov T-6in4 he.net f
44 2:5005/106 Alexey Osiyuk T-6in4 he.net f
45 2:5057/53 Ivan Kovalenko Native ER-Telecom f
46 2:5010/352 Dmitriy Smirnov Native SAGE-SU-V6
47 2:292/854 Ward Dossche Native Proximus
48 2:469/122 Sergey Zabolotny T-6in4 he.net f
49 2:5053/400 Alexander Kruglikov Native FirstVDS f
50 2:5030/1997 Alexey Fayans T-6in4 he.net
51 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
52 2:240/502 Ludwig Bernhartzeder Native DTAG
53 2:423/39 Karel Kral Native WEDOS
54 2:280/1049 Simon Voortman Native Solcon
55 2:335/364 Fabio Bizzi Native OVH
56 1:124/5016 Nigel Reed Native DAL1-US f
57 2:5030/1520 Andrey Geyko T-6in4 he.net f
58 1:229/664 Jay Harris Native Rogers f
59 2:280/2030 Martien Korenblom Native Transip
60 3:633/509 Deon George Native Telstra
61 2:5020/4441 Yuri Myakotin Native SOVINTEL
62 1:320/319 Andrew Leary Native Comcast f
63 2:240/5824 Anna Christina Nass Native DTAG f
64 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
65 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
66 2:301/812 Benoit Panizon Native WOODYV6
67 1:229/616 Vasily Losev Native GIGEPORT
68 2:301/113 Alisha Stutz T-6in4 he.ne
69 1:153/7715 Dallas Hinton Native Shaw Comms
70 1:218/840 Morgan Collins Native Linode
71 2:5020/921 Andrew Savin Native HURRICANE-IPV6-24
72 2:240/1634 Hugo Andriessen Native Vodafone
73 2:280/2040 Leo Barnhoorn Native KPN f
74 2:5020/736 Egor Glukhov Native RUWEB f
75 2:221/10 Tommi Koivula Native Hetzner f INO4
76 1:218/850 John Nicpon Native LINODE-US
77 2:301/1 Alisha Stutz Native CH-DATAWIRE
78 2:5035/63 Vladimir Goncharov Native RFEIV6NET
79 2:5020/290 Andrew Kolchoogin T-6in4 he.net
80 1:214/22 Ray Quinn T-6in4 he.net 6DWN
81 2:5030/49 Sergey Myasoedov Native FR-VIRTUA-SYSTEMS
82 1:218/820 Ryan Fantus Native DIGITALOCEAN
83 1:103/705 Rob Swindell Native Spectrum f
84 1:135/395 Charles Blackburn Native Charter Comms
85 1:134/303 Travis Mehrer Native Shaw Comms
86 2:5057/19 Max Vasilyev Native ER-Telecom f
87 2:5075/35 Eugene Subbotin Native RUWEB f
88 2:5075/37 Andrew Komardin Native IHC
89 2:5075/128 Eugene Subbotin T-6in4 IP4Market f
90 2:550/278 Vladislav Muschinskikh Native FirstByte
91 2:5010/278 Vladislav Muschinskikh T-6in4 he.net f
92 2:240/5411 Stephan Gebbers Native DTAG
93 2:5020/715 Alex Barinov T-6in4 he.net f
94 1:16/201 Sergey Myasoedov Native Amazon
95 1:104/117 Vitaliy Aksyonov Native LLC
96 2:5030/1340 Dmitry Afanasiev T-6in4 TUNNEL-BROKER-NET
97 2:221/360 Tommi Koivula Native Elisa f
98 2:5031/25 Alex Kazankov Native VDSINA
99 4:902/26 Fernando Toledo Native Claro
100 2:280/2050 Floris van Unen Native Azure
101 2:280/2060 Dennis Slagers Native Ziggo f
102 2:467/4 Ruslan Suleimanov T-6in4 he.net
103 2:467/888 Ruslan Suleimanov T-6in4 he.net f
104 1:266/625 Scott Street Native Verizon
105 2:5020/5452 Alex Barinov T-6in4 he.net
106 2:5030/723 Alexey Khromov Native RU-AI-20240222
107 3:633/2744 Deon George Native EXETEL-AU
108 4:930/1 David Gonzalez Native EPMNET
109 3:633/267 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.
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 124


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

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

=================================================================
SPECIAL INTEREST =================================================================

Nodelist Stats

Input nodelist nodelist.122
size 154.9kb
date 2025-05-02

The nodelist has 807 nodes in it
and a total of 1199 non-comment entries

including 4 zones
30 regions
157 hosts
59 hubs
admin overhead 250 ( 30.98 %)

and 83 private nodes
18 nodes down
41 nodes on hold
off line overhead 142 ( 17.60 %)


Speed summary:

>9600 = 19 ( 2.35 %)
9600 = 88 ( 10.90 %)
(HST = 2 or 2.27 %)
(CSP = 0 or 0.00 %)
(PEP = 0 or 0.00 %)
(MAX = 0 or 0.00 %)
(HAY = 0 or 0.00 %)
(V32 = 51 or 57.95 %)
(V32B = 0 or 0.00 %)
(V34 = 52 or 59.09 %)
(V42 = 45 or 51.14 %)
(V42B = 0 or 0.00 %)
2400 = 1 ( 0.12 %)
1200 = 0 ( 0.00 %)
300 = 699 ( 86.62 %)

ISDN = 18 ( 2.23 %)

-----------------------------------------------------
IP Flags Protocol Number of systems -----------------------------------------------------
IBN Binkp 692 ( 85.75 %) ----------------------------------
IFC Raw ifcico 61 ( 7.56 %) ----------------------------------
IFT FTP 33 ( 4.09 %) ----------------------------------
ITN Telnet 91 ( 11.28 %) ----------------------------------
IVM Vmodem 11 ( 1.36 %) ----------------------------------
IP Other 1 ( 0.12 %) ----------------------------------
INO4 IPv6 only 5 ( 0.62 %) ----------------------------------

CrashMail capable = 743 ( 92.07 %)
MailOnly nodes = 242 ( 29.99 %)
Listed-only nodes = 19 ( 2.35 %)



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