Hello, Michiel!

Tuesday October 08 2024 18:38, you wrote to All:

We have a couple of new ones.

BTW, if you are interested:

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

list of currently reachable ipv6 enabled nodes.



Best regards,
dp.

--- GoldED+/OSX 1.1.5-b20250409
* Origin: All is good in St. John's Wood (2:5001/100.1)

Hello Dmitry,

On Thursday September 18 2025 16:03, you wrote to me:

BTW, if you are interested:

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

list of currently reachable ipv6 enabled nodes.

Interesting indeed.

1) Why am I not in it?

2) You list all the non /0 AKA's of a node. F.e. 292/854 is listed with three other AKA's. In my list it is only listed once.

3) I doubt that explains all the differences between your list and mine. There may be a few that I missed.

To be continued...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello Dmitry,

Thursday September 18 2025 15:53, I wrote to you:

3) I doubt that explains all the differences between your list and
mine. There may be a few that I missed.

To be continued...

I did indeed miss a few but an important difference between your list and mine is that you include nodes that advertise an IPv6 in the host name but that answer only on IPv4. Example 2:301/1. Time out on IPv6.

An even more extreme example is 1:229/301. There is an AAAA record but it resolves to a ULA. Of course that can never result in an IPv6 connect.

In my list those nodes are not included.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello, Michiel!

Thursday September 18 2025 15:53, you wrote to me:

list of currently reachable ipv6 enabled nodes.

Interesting indeed.

1) Why am I not in it?

Damn! I was trying to simplify the testing logic by checking only one hostname per node, but your node has two hostnames in the nodelist with different IPv6 coverage. The new code is in place and your node has been retested.
Other nodes with multiple hostnames will be retested during the scheduled period (every 72 hours).

2) You list all the non /0 AKA's of a node. F.e. 292/854 is listed
with three other AKA's. In my list it is only listed once.

Yes, it's intentional behavior.

3) I doubt that explains all the differences between your list and
mine. There may be a few that I missed.

Well, some nodes from your list may have been unreachable during the last couple of days and some sysops probably never bothered to be added to your list.


Best regards,
dp.

--- GoldED+/OSX 1.1.5-b20250409
* Origin: All is good in St. John's Wood (2:5001/100.1)

Hello, Michiel!

Thursday September 18 2025 20:32, you wrote to me:

I did indeed miss a few but an important difference between your list
and mine is that you include nodes that advertise an IPv6 in the host
name but that answer only on IPv4. Example 2:301/1. Time out on IPv6.

Ah, yes, fixed how those cases are displayed.

Best regards,
dp.

--- GoldED+/OSX 1.1.5-b20250409
* Origin: All is good in St. John's Wood (2:5001/100.1)

Hello Dmitry,

On Thursday September 18 2025 23:01, you wrote to me:

I did indeed miss a few but an important difference between your
list and mine is that you include nodes that advertise an IPv6 in
the host name but that answer only on IPv4. Example 2:301/1. Time
out on IPv6.

Ah, yes, fixed how those cases are displayed.

Great!

I have updated my list with the help of your's. Eight new or returning nodes have been added. See next message. Thank you fo providing this service.



Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello, Michiel!

Friday September 19 2025 14:28, you wrote to me:

I have updated my list with the help of your's. Eight new or returning nodes have been added. See next message. Thank you fo providing this service.

Happy to help!

Do you need some "alert service" to receive weekly or daily updates via netmail?

Best regards,
dp.

--- GoldED+/OSX 1.1.5-b20250409
* Origin: All is good in St. John's Wood (2:5001/100.1)

x) Thursday Sep 18, 2025, 16:03. Dmitry Protasoff ÄÄ Michiel van der Vlist.

We have a couple of new ones.

BTW, if you are interested:
https://nodelist.fidonet.cc/analytics/ipv6
list of currently reachable ipv6 enabled nodes.

Why's my node is not there, I wonder... Or it requires expicit INA in nodelist?

--- Neon BBS Line 2, 570-57-80, 20:30-06:30. [bbs.ncc.org.ua]
* Origin: Neon_#2, Kiev, Ukraine (2:463/877)

Hello Dmitry,

On Friday September 19 2025 16:27, you wrote to me:

I have updated my list with the help of your's. Eight new or
returning nodes have been added. See next message. Thank you fo
providing this service.

Happy to help!

Do you need some "alert service" to receive weekly or daily updates
via netmail?

Not really.

But what would be usefull to me is a list of nodes that advertise IPv6 capability but fail to actually support it. I could use such a list to contact those sysops in order to help them solve the problem. I have done that in the past with more or less success, but an accurate up to date list would be helpfull.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello, Alex!

Sunday September 21 2025 05:07, you wrote to me:

Why's my node is not there, I wonder... Or it requires expicit INA in nodelist?

Mea culpa!

I made a mistake when implementing the use of System name as a fallback for the hostname on Saturday (is there any FTSC document about it?).
To make things worse, I jumped straight into refactoring the code afterwards. Yesterday I was busy with my parents visiting and today I had to deal with cancelling my flight to 5001 because I didn't want to risk my daughter's life with the ongoing Ukrainian drone attacks. So, unfortunately, this $%$ bug is still not fixed.

I am really sorry about this and I promise to fix it very soon.

Best regards,
dp.

--- GoldED+/OSX 1.1.5-b20250409
* Origin: All is good in St. John's Wood (2:5001/100.1)

Hello Dmitry!

18 Sep 25 16:03, you wrote to Michiel van der Vlist:

BTW, if you are interested:

https://nodelist.fidonet.cc/analytics/ipv6
list of currently reachable ipv6 enabled nodes.

Can we opt-out .. ?


Dennis


... Did you turn it off and back on?
--- GoldED+/LNX 1.1.5-b20250408
* Origin: ---- BOFH: Problem solved, user deleted. (2:280/2060)

Hello, Dennis!

Thursday October 02 2025 16:02, you wrote to me:

BTW, if you are interested:

https://nodelist.fidonet.cc/analytics/ipv6
list of currently reachable ipv6 enabled nodes.

Can we opt-out .. ?

Sure! You could become an unreachable node at any time. As they say: "Rome wasn't built in a day, but it can burn in one.
But I don't think that would make anyone on this planet happy, not even me.

Best regards,
dp.

--- GoldED+/OSX 1.1.5-b20250409
* Origin: All is good in St. John's Wood (2:5001/100.1)