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)

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?

I think I fixed this bug.

Sorry again!

Best regards,
dp.

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

Hello, Michiel!

Sunday September 21 2025 12:10, you wrote to me:

But what would be usefull to me is a list of nodes that advertise IPv6

How do they advertise it?

Also, please check the new list of IPv6-capable nodes:

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

It still has some bugs! I haven't found them yet ;)

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 Saturday October 11 2025 05:10, you wrote to me:

Hello, Michiel!

Sunday September 21 2025 12:10, you wrote to me:

But what would be usefull to me is a list of nodes that advertise
IPv6

How do they advertise it?

By having an AAAA record in the DNS for the host name(s) in the nodelist.

Or a literal IPv6 address in the nodelist. (A method not presently in use)

Also, please check the new list of IPv6-capable nodes:

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

It still has some bugs! I haven't found them yet ;)

I haven't found any bugs yet.;-)


Cheers, Michiel

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

Hi Dmitry.

11 Oct 25 21:52, Michiel van der Vlist wrote to you:

Or a literal IPv6 address in the nodelist. (A method not presently in use)

Also, please check the new list of IPv6-capable nodes:

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

It still has some bugs! I haven't found them yet ;)

I haven't found any bugs yet.;-)

I have, the site is IPv4-only! ;-)

'Tommi

---
* Origin: nntps://news.fidonet.fi (2:221/1)

Hello, Michiel!

Saturday October 11 2025 21:52, you wrote to me:

By having an AAAA record in the DNS for the host name(s) in the
nodelist.

Or a literal IPv6 address in the nodelist. (A method not presently in
use)

Something like: https://nodelist.fidonet.cc/analytics/ipv6-nonworking ?


Best regards,
dp.

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

Hello, Tommi!

Saturday October 11 2025 23:26, you wrote to me:

I haven't found any bugs yet.;-)

I have, the site is IPv4-only! ;-)

Oh, forgot to allow 80/443 ports for ipv6, thanks :)

Best regards,
dp.

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

Hi Michiel!

Saturday October 11 2025 21:52, you wrote to Dmitry Protasoff:

It still has some bugs! I haven't found them yet ;)

MvdV> I haven't found any bugs yet.;-)

The list is still incomplete. It's also sorted incorrectly.

Have a nice night.
Stas Mishchenkov.

--- Have You daily sexual life? Hide it proper from Your wife! ;)
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hello Dmitry,

On Sunday October 12 2025 01:37, you wrote to me:

By having an AAAA record in the DNS for the host name(s) in the
nodelist.

Or a literal IPv6 address in the nodelist. (A method not
presently in use)

Something like: https://nodelist.fidonet.cc/analytics/ipv6-nonworking
?

Yes, something like that.


Cheers, Michiel

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

Hello Dmitry,

Sunday October 12 2025 08:30, I wrote to you:

Something like:
https://nodelist.fidonet.cc/analytics/ipv6-nonworking ?

Yes, something like that.

56 IPv6 non-working nodes found.

That's more than I expected. There is work to do!


Cheers, Michiel

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

Hello, Michiel!

Monday October 13 2025 16:25, you wrote to me:

Yes, something like that.

56 IPv6 non-working nodes found.

That's more than I expected. There is work to do!

Please note (this is also written on the website):

for working nodes:
This report shows nodes that have IPv6 addresses resolved and have been successfully tested with at least one protocol over the last 30 days.

for non working nodes:
This report shows nodes that have IPv6 addresses (either from nodelist or resolved from hostnames) but no IPv6 services are currently working over the last 30 days.

So a node will be moved from working to non-working state only after 30 days of loosing ipv6 access.

I'll add a simple API to get these reports and updates with curl, but I need to refactor the code first: it was written before I even knew what this website would become and it's a bit of a mess :)

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 Monday October 13 2025 18:52, you wrote to me:

56 IPv6 non-working nodes found.

That's more than I expected. There is work to do!

Please note (this is also written on the website):

for working nodes:
This report shows nodes that have IPv6 addresses resolved and have
been successfully tested with at least one protocol over the last 30
days.

for non working nodes:
This report shows nodes that have IPv6 addresses (either from nodelist
or resolved from hostnames) but no IPv6 services are currently working over the last 30 days.

So a node will be moved from working to non-working state only after
30 days of loosing ipv6 access.

I take it that applies to existing nodes that once had working IPv6 connectivity and become nonworking at some point. But how about /new/ nodes that advertise IPv6 connectivity but never had it working?

I also note that a significant fraction of the 56 nodes in the list of non working IPv6 nodes ha no connectivity at all. No IPv6 /and/ no IPv4. It is not what I expected but I can live with it.

I have send netmail to all the nodes that have IPv4 connectivity but no working IPv6. We shall see where that brings us.

I'll add a simple API to get these reports and updates with curl, but
I need to refactor the code first: it was written before I even knew
what this website would become and it's a bit of a mess :)

I stay tuned...


Cheers, Michiel

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

Hello, Michiel!

Tuesday October 14 2025 10:20, you wrote to me:

I take it that applies to existing nodes that once had working IPv6 connectivity and become nonworking at some point. But how about /new/ nodes that advertise IPv6 connectivity but never had it working?

Good idea.

TODO: Check for new node capabilities in new nodelist.

I also note that a significant fraction of the 56 nodes in the list of
non working IPv6 nodes ha no connectivity at all. No IPv6 /and/ no
IPv4. It is not what I expected but I can live with it.

Easy to implement!

TODO: Add new report.

I'll add a simple API to get these reports and updates with curl,
but I need to refactor the code first: it was written before I
even knew what this website would become and it's a bit of a mess
:)

I stay tuned...

Will be back shortly!

Best regards,
dp.

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

Hello, Michiel!

Tuesday October 14 2025 10:20, you wrote to me:

I take it that applies to existing nodes that once had working IPv6 connectivity and become nonworking at some point. But how about /new/ nodes that advertise IPv6 connectivity but never had it working?

Pls check:

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

This report uses data from the last 7 days (relative to the time you access this page) and compares it with the previous week.
I can extend the API to fetch this information with curl/python/perl if needed.

My idea is that checking for changes every day is too aggressive. But it's up to you.. Correct me if I'm wrong.

I also note that a significant fraction of the 56 nodes in the list of
non working IPv6 nodes ha no connectivity at all. No IPv6 /and/ no
IPv4. It is not what I expected but I can live with it.

Done!

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



Best regards,
dp.

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

Hello, Stas!

Sunday October 12 2025 01:51, you wrote to Michiel van der Vlist:

The list is still incomplete.

Fake news again! You are so lame, Stasik!

It's also sorted incorrectly.

Fake news again! You are so lame, Stasik! ;)


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 Wednesday October 15 2025 22:28, you wrote to me:

I take it that applies to existing nodes that once had working
IPv6 connectivity and become nonworking at some point. But how
about /new/ nodes that advertise IPv6 connectivity but never had
it working?

Pls check:

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

Great!

This report uses data from the last 7 days (relative to the time you access this page) and compares it with the previous week. I can extend
the API to fetch this information with curl/python/perl if needed.

My idea is that checking for changes every day is too aggressive. But
it's up to you.. Correct me if I'm wrong.

A daily check is indeed needlessly agressive. A weekly check is fine with me.

I also note that a significant fraction of the 56 nodes in the
list of non working IPv6 nodes ha no connectivity at all. No IPv6
/and/ no IPv4. It is not what I expected but I can live with it.

Done!

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

Great!

You realy did a great job with all this. It is very usefull to me in my attempts to promote IPv6 in Fidonet. Keep up the good work!


Cheers, Michiel

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

Hello, Michiel!

Thursday October 16 2025 18:28, you wrote to me:

Great!

BTW, if you move your mouse cursor over any (I hope so) red field, it will show you the real error, such as "connection refused" and so on.

A daily check is indeed needlessly agressive. A weekly check is fine
with me.

Feel free to ask for any additional functionality, because it looks like I've finished all the reports I wanted for now and will be moving on to fixing and improving the EMSI/modem part (which, hopefully, will also be used in my planned Fidonet mailer/tosser/nntp sever software).

I also note that a significant fraction of the 56 nodes in the
list of non working IPv6 nodes ha no connectivity at all. No
IPv6 /and/ no IPv4. It is not what I expected but I can live
with it.

Done!

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

Great!

You realy did a great job with all this. It is very usefull to me in
my attempts to promote IPv6 in Fidonet. Keep up the good work!

Thank you for the kind words! I've also decided to sign a contract with Vodafone for my new rented apartment in London, since they provide IPv6. So they should probably pay you a percentage of my bills, because you encouraged me to switch to an IPv6-enabled provider ;))


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 October 16 2025 20:53, you wrote to me:

BTW, if you move your mouse cursor over any (I hope so) red field, it
will show you the real error, such as "connection refused" and so on.

Ah, I had not discovered that yet. It is usefull!

Feel free to ask for any additional functionality, because it looks
like I've finished all the reports I wanted for now

Now that you mention it... There is just one categorie I have not seen yet: IPv6 only nodes. AFAIK here are just two of them at the moment but this number may rise in the foreseeable future. Hpw about adding "IPv6 only" to IPv6 Analytics?

and will be moving on to fixing and improving the EMSI/modem part
(which, hopefully, will also be used in my planned Fidonet mailer/tosser/nntp sever software).

OK...

You realy did a great job with all this. It is very usefull to me
in my attempts to promote IPv6 in Fidonet. Keep up the good work!

Thank you for the kind words! I've also decided to sign a contract
with Vodafone for my new rented apartment in London, since they
provide IPv6. So they should probably pay you a percentage of my
bills, because you encouraged me to switch to an IPv6-enabled provider
;))

What took you so long? ;-)


Cheers, Michiel

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

Hello Dmitry,

Friday October 17 2025 10:19, I wrote to you:

Now that you mention it... There is just one categorie I have not seen yet: IPv6 only nodes. AFAIK here are just two of them at the moment
but this number may rise in the foreseeable future. Hpw about adding
"IPv6 only" to IPv6 Analytics?

Wouw! I see that you already added that category.

And I am surprised. There er 9 entries. I expected just 2. 280/5006 and 450/5858. The later is not present as he is off-line at the moment. The other eight apparently advertise IPv4 connectivity but do not have it working. Surprise!


Cheers, Michiel

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

Hello Dmitry,

Friday October 17 2025 14:20, I wrote to you:

Wouw! I see that you already added that category.

And I am surprised. There er 9 entries. I expected just 2. 280/5006
and 450/5858. The later is not present as he is off-line at the
moment. The other eight apparently advertise IPv4 connectivity but do
not have it working. Surprise!

I wonder how many of them are behind CGNAT without realizing it.


Cheers, Michiel

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

Hello, Michiel!

Friday October 17 2025 14:20, you wrote to me:

Now that you mention it... There is just one categorie I have not
seen
yet: IPv6 only nodes. AFAIK here are just two of them at the
moment but this number may rise in the foreseeable future. Hpw
about adding "IPv6 only" to IPv6 Analytics?

Wouw! I see that you already added that category.

Oops! You've caught me in the process of adding and testing new code, which could be incorrect... ;)

My code lacked proper INO4 flag support, and I am still fixing remaining bugs. Please check the "History" button to see the test results - sometimes IPv6 only node is simply a misconfigured node that has lost IPv4 access.

Best regards,
dp.

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

Hello, Michiel!

Friday October 17 2025 10:19, you wrote to me:

Thank you for the kind words! I've also decided to sign a
contract with Vodafone for my new rented apartment in London,
since they provide IPv6. So they should probably pay you a
percentage of my bills, because you encouraged me to switch to an
IPv6-enabled provider ;))

What took you so long? ;-)

Good question :)

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 Friday October 17 2025 17:37, you wrote to me:

Hello, Michiel!

Friday October 17 2025 14:20, you wrote to me:

Now that you mention it... There is just one categorie I have not
seen yet: IPv6 only nodes. AFAIK here are just two of them at the
moment but this number may rise in the foreseeable future. Hpw about
adding "IPv6 only" to IPv6 Analytics?

Wouw! I see that you already added that category.

Oops! You've caught me in the process of adding and testing new code, which could be incorrect... ;)

My code lacked proper INO4 flag support, and I am still fixing
remaining bugs. Please check the "History" button to see the test
results - sometimes IPv6 only node is simply a misconfigured node that
has lost IPv4 access.

The result may not have been what you intended, but it did reveal an interesting category that I did not expect: nodes with working IPv6 with advertised but non working IPv4. Pleas keep it as a seperate caregory.


Cheers, Michiel

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

Hello, Michiel!

Friday October 17 2025 17:50, you wrote to me:

The result may not have been what you intended, but it did reveal an interesting category that I did not expect: nodes with working IPv6
with advertised but non working IPv4. Pleas keep it as a seperate caregory.

Jawel, kapitein! ;)

I've finished all the analytics changes - feel free to send me any new ideas later, since I don't have any..
And thank you for your effort in promoting IPv6!

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 Saturday October 18 2025 01:57, you wrote to me:

Hello, Michiel!

Friday October 17 2025 17:50, you wrote to me:

The result may not have been what you intended, but it did reveal
an interesting category that I did not expect: nodes with working
IPv6 with advertised but non working IPv4. Pleas keep it as a
seperate caregory.

Jawel, kapitein! ;)

I've finished all the analytics changes - feel free to send me any new ideas later, since I don't have any..

What I liked and what I miss in the latest version is the showing of the IPv6 address(es) when hovering the mouse cursor over the host name field. It is how I quickly spotted a host name with a ULA. I'd like to have it back. The new addition of fields for copying the host name, the IPv6 adresses and all of them may be something I might not use all that often.

And just one more thing I'd like: Splitting up the IPv6 only category in two. One just like the one you have now, IPv6 noes with non functioning IPv4 and the other for pure IPv6 only nodes, nodes that only advertise one or more IPv6 addresses and no IPv4 address at all.

And thank you for your effort in promoting IPv6!

You'r welcome. And thank you for your excellent work on nodelist analytics! :-)


Cheers, Michiel

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

Hello, Michiel!

Sunday October 19 2025 13:33, you wrote to me:

What I liked and what I miss in the latest version is the showing of
the IPv6 address(es) when hovering the mouse cursor over the host name field. It is how I quickly spotted a host name with a ULA. I'd like to have it back. The new addition of fields for copying the host name,

It could be a browser incompatibility issue - I just found that it wasn't working in my Safari, but working in Firefox.
I've made some changes - could you try again and refresh the page with clearing cache?
Not sure which browser you are using, so don't know the exact shortcut.

And just one more thing I'd like: Splitting up the IPv6 only category
in two. One just like the one you have now, IPv6 noes with non
functioning IPv4 and the other for pure IPv6 only nodes, nodes that
only advertise one or more IPv6 addresses and no IPv4 address at all.

Done! "Pure IPv6 Only".


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 Sunday October 19 2025 15:26, you wrote to me:

It could be a browser incompatibility issue - I just found that it
wasn't working in my Safari, but working in Firefox. I've made some changes - could you try again and refresh the page with clearing
cache? Not sure which browser you are using, so don't know the exact shortcut.

It still does not work. Hovering over the "red" protocols to disp;ay the error still works howver. I am using Firefox 115.28.0esr 32 bit. A somewhat older version that still works on Win8.

And just one more thing I'd like: Splitting up the IPv6 only
category in two. One just like the one you have now, IPv6 noes
with non functioning IPv4 and the other for pure IPv6 only nodes,
nodes that only advertise one or more IPv6 addresses and no IPv4
address at all.

Done! "Pure IPv6 Only".

Great! Thank you.


Cheers, Michiel

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

Hello, Michiel!

Sunday October 19 2025 15:52, you wrote to me:

It still does not work. Hovering over the "red" protocols to disp;ay
the error still works howver. I am using Firefox 115.28.0esr 32 bit. A somewhat older version that still works on Win8.

I've tried it (64-bit version, though I don't think there's a difference) and it works:

https://s.5001.ru/-M9SfB7oahc

Please try reloading the page with Ctrl+F5 to bypass cache.


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 Sunday October 19 2025 20:58, you wrote to me:

I've tried it (64-bit version, though I don't think there's a
difference) and it works:

https://s.5001.ru/-M9SfB7oahc

Please try reloading the page with Ctrl+F5 to bypass cache.

It is OK now! :-)


Cheers, Michiel

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