Subj : Nodes location. Funny statistics.
To : Nick Boel
From : Michiel van der Vlist
Date : Tue Aug 05 2025 10:32 am
Hello Nick,
On Monday August 04 2025 16:55, you wrote to me:
>> The list of IPv6 nodes that I weekly publish in Fidonews presently
>> has 101 entries. Significantly less than the 147 mentioned above. I
>> should mention that my list only contains nodes with whom I have
>> managed to establish an IPv6 binkp connect.
NB> Keep in mind also, that currently developed BBS softwares (Mystic and
NB> Synchronet, for example) have options to listen on IPv4, IPv6, or
NB> both. It could just be the fact that they've set it up to listen on
NB> IPv4 only, maybe not even knowing that they have IPv6 capability. Or,
NB> they may only want to connect via IPv4 because they have no way of
NB> setting any kind of firewall rules for IPv6 (crappy ISP issued router,
NB> or something).
All of that is possible. It is even possible that a node may make /outgoing/ IPv6 connections without the sysop being aware of it. Keep in mind however that these figures are derived from host names with AAAA records /advertised/ in the nodelist.
NB> Finally, they may just not know what the hell they're doing. ;)
Possibly... ;-)
NB> I'd be willing to bet a majority of those 46 nodes just have no idea
NB> they have IPv6,
Then where do the AAAA records come from? Those AAAA records do not fall out of the sky. AFAIK it always requires a premeditated affort from the owner of the host name.
NB> or don't know how to properly configure it (so they have an AAAA
NB> record, but it's not setup to listen on certain ports).
Did I mention that when I come across such a situation I always try to contact the sysop in order to try to help hem/her fix the problem? The vast majority of these attempt to contact the sysop fails. They do not respond at all. :(
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin:
http://www.vlist.org (2:280/5555)
