Michiel;

Is there a full listing somewhere?

* Origin: he.net certified sage (2:280/5555)

As am I twice over.

... Never judge a fruit by its skin. Neelix
--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)

Hello Michiel;

Michiel van der Vlist wrote to Brian Rogers <=-

It is published weekly in Fidonews.
See also next message.

Yes I saw it.

You have two T-shirts?

No they seemed to have stopped the T-shirt mailing. My system should be
dual stacked... I know my main stuff on the box is:
n1uro@n1uro:~$ host bbs.n1uro.com
bbs.n1uro.com has address 44.88.0.9
bbs.n1uro.com has IPv6 address 2001:470:8a1e::3
bbs.n1uro.com mail is handled by 5 mail.n1uro.com.

My IPv6 takes priority. My block is mainly used for IPv6 under ax.25 but I
also use it for my postfix, apache, and other servers. My packet node is IPv6 ready as well, and I believe my bink should be. If not I'll have to
investigate why.

... QUID PRO QUO, Doktor!!
--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)

Re: New ones
By: Michiel van der Vlist to All on Fri May 14 2021 05:03 pm

Yay v6 club!
===
Underminer - The Undermine BBS
--- SBBSecho 3.14-Linux
* Origin: The Undermine - bbs.undermine.ca (1:134/101)

Hello Michiel;

Michiel van der Vlist wrote to Brian Rogers <=-

http://www.vlist.eu/fotos/sage-f.jpg
http://www.vlist.eu/fotos/sage-b.jpg

Nice! One of the blocks I got was for a client of mine. I was also pleased
to learn that one of the guys in their tech support is also a ham. He was surprised to learn how I got IPv6 routed over the ax.25 protocol.

No need to investigate, it works fine:

+ 10:03 [2736] call to 1:142/103@fidonet
10:03 [2736] trying bbs.n1uro.com [2001:470:8a1e::3]...
10:03 [2736] connected
+ 10:03 [2736] outgoing session with bbs.n1uro.com:24554 [2001:470:8a1e::3] - 10:03 [2736] OPT

Good, thanks for the report! Basically SBBS and it's built in Bink saw the active IPv6 and ported it right in automatically.

+ 10:03 [2736] addr: 432:1/157@vkradio (n/a or busy)

Ahh now I have to figure out why this is!

Cheers and thanks again for the verification.

-Brian

... What is mind? No matter! What is matter? Never mind! - Homer S.
--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)

Hello Tony;

Tony Langdon wrote to Brian Rogers <=-

As you feed off me on VKRadio, you should be connecting to me by
default over IPv6, unless you override that.

If there's an IPv6 path available, it takes priority... but it appears
we've been having handshaking issues (password). Chalk it up to social distancing? <G>

... Hey! Stop that!! You're being redundant again
--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)

Hello Michiel;

Michiel van der Vlist wrote to Brian Rogers <=-

HAMs are everywhere! ;-)

Yes we are!

Once, a long time ago I pioneered in data over HAM radio. That was
before IPv6, even before AX25. I still kept the call, but I am no
longer active as a HAM.

I'm a coordinator for 44-net. I handle 1/5th of the USA. They're now just beginning to talk about incorporating IPv6 into amprnet however in my case
it's unneeded. I have a /48 from he.net and broker IPs to various points whether they be ipencap tunnel on 44net OR encapsulated under ax.25! The
trick was simple too. To route IP on ax.25 it demands ARP so it can use
the callsign as a mac address and we all know IPv6 uses NDS not ARP... so depending on the remote source I do a 6-to-4 mapping to their 44-net IP
or to their commercial IP. For radio, the mapping goes to their 44-net IP
since that's the only IP they have. Speed wise, it's not much different
than IPv4... and it's slick because using 44-net that's your ARP mapping.

No need for action. That is the standard response when Binkd sees an
AKA in an unknown domain. My binkd does not know about the domain vkradio.

Interesting. It does however appear that it's not loading the nodelist.
I've reconfigured it so it knows it's there.

73 de PA0MMV

Dust off that TNC OM :)
73 de N1URO

-Brian

... Quigley's Law: Whoever has any authority over you, no matter how small, will
--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)

Hello Tony;

Tony Langdon wrote to Brian Rogers <=-

Yeah I'm native IPv6 on my end. :) Yeah, have to compare passwords -
show me yours and I'll show you mine (in email, not here)... :D

I have an HE.net 6-to-4 tunnel/map however it still take priority in my
routing - as it should. I'll try to send you an ascii in email of what
I have. I really have a feeling that the nodelist isn't loading... but that's just my hunch.

... Equal opportunity antagonist
--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)

Hey Tony;

Tony Langdon wrote to Brian Rogers <=-

On 05-16-21 10:05, Brian Rogers wrote to Michiel van der Vlist <=-

I'm a coordinator for 44-net. I handle 1/5th of the USA. They're now
just beginning to talk about incorporating IPv6 into amprnet however in
my case it's unneeded. I have a /48 from he.net and broker IPs to
various points whether they be ipencap tunnel on 44net OR encapsulated under ax.25! The trick was simple too. To route IP on ax.25 it demands
ARP so it can use the callsign as a mac address and we all know IPv6
uses NDS not ARP... so depending on the remote source I do a 6-to-4 mapping to their 44-net IP or to their commercial IP. For radio, the mapping goes to their 44-net IP since that's the only IP they have.
Speed wise, it's not much different than IPv4... and it's slick because using 44-net that's your ARP mapping.

Interesting, would like to know the details. I'm fully IPv6 capable,
and would like to be able to transmit it over AX.25 one day.

Details are above.

If you want a Proof of Concept, traceroute6 wb2snn.ampr.org
That's an RF Only site with -no- internet whatsoever. You should get to gw-ipv6.n1uro.com then to wb2snn:

n1uro@n1uro:~$ traceroute6 wb2snn.ampr.org
traceroute to wb2snn.ampr.org (2001:470:8a1e::17), 30 hops max, 80 byte packets
1 gw-ipv6.n1uro.com (2001:470:8a1e::1) 1.432 ms 1.893 ms 2.747 ms
2 wb2snn.ampr.org (2001:470:8a1e::17) 3753.106 ms 3758.076 ms 3758.812 ms n1uro@n1uro:~$

And...

n1uro@n1uro:~$ telnet6 wb2snn.ampr.org node
Trying 2001:470:8a1e::17...
Connected to wb2snn.ampr.org.
Escape character is '^]'.
(wb2snn.ampr.org:uronode) login:

Not only is ipv6 working, but my URONode is IPv6 compatable.

73

... "Data, people do not _have_ internal chronometers." - Riker
--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)

Hey Tony;

Tony Langdon wrote to Brian Rogers <=-

Yeah I'm native IPv6 on my end. :) Yeah, have to compare passwords -
show me yours and I'll show you mine (in email, not here)... :D

Ha! If I had a nickel for every time I heard that, I'd still be waiting
to get a nickel <G>

What you sent looked good. And if you need a file copy of the nodelist (as opposed to DNS), you can download that from my file areas (again, anonymous HTTP/FTP work fine). :)

I have one, I'm surprised it didn't load up for me.

... To my embarrassment, I was born in bed with a lady!

We used to have a chain store called Two Guys years ago. In today's world
you'd think that's where some of the more vocal ones came from :)




--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)

Hello Tony;

Tony Langdon wrote to Brian Rogers <=-

The detailed details - I have a vague idea, but lacks enough for me to fully grasp it. :)

When the time comes I can help ya get things going.

Little bit hard right now, while I'm offline on a plane going up the
east coast of Australia. ;)

Plane? What happened to the ol' feet? :) .. or do you have shoes like
Apollo - with wings on them <G>

Another reason I should check out UORNode. I'm in need of a new RF node/gateway, after I get back home. And since you support IPv6,
you've gone to the front of the queue. :)

My axMail-FAX system, which uses Postfix as a backend MTA, also is IPv6 ready... since Postfix handles the mail in reality.

... "Data, people do not _have_ internal chronometers." - Riker

I've been accused of it. :D

Just don't play footsies with you, you've known to "nail" that one down? :D

... Elves do it in the trees.
--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)

Tony Langdon wrote to Brian Rogers <=-

Hmm, strange. It's built from raw data with MakeNL.

I have it loaded up now. I just had to manually enter it in the .ini file.

... McSushi--cooked fresh EVERYDAY!!!
--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)

Tony Langdon wrote to Brian Rogers <=-

Cool, I'll take you up on that one day. :)

It's really no where near as difficult as one thinks.

Haha, it was a 1500+ km trip, this is a BIG country. Wasn't even an interstate flight! ;)

One big LONG sprint - no problem right? :)


... Vegetarians beware! You are what you eat
--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)

Tony Langdon wrote to Brian Rogers <=-

I have it loaded up now. I just had to manually enter it in the .ini
file.

Ahh OK, cool. :)

I'm making the connect attempt, and via IPV6 no less. I'm receiving your alias nodes though from what I see.

... I'll torture you SO slowly, you'll think it's a career
--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)

Tony Langdon wrote to Brian Rogers <=-

Mor a case of getting used to the lay of the land. :)

You do it once, it becomes old hat from then on :)

Hmm, kind of an oxymoron. :P

OR... you can have very VERY large feet <G>

... The best way to stop smoking is to carry wet matches.
--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)

Hey Tony;

Tony Langdon wrote to Brian Rogers <=-

Cool. I may set you to IPv6+IPv4. My IPv6 connectivity is actually better on the hub (native vs OpenVPN). How does that sound?

That's perfect!.. it's like putting a humidifier and a dehumidifier in the
same room and letting them hash it out <G>

Haha catch me. :P

With my neuropathy are you kidding me?? :)

... Jeffrey Dahmer is so lonely for sex he can almost taste it.
--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)

Hello Tony;

Tony Langdon wrote to Brian Rogers <=-

Seems the IPv6 path is working fine.

LOL, I had a track meet today (the reason I'm in Cairns, actually). :) Backing that up tomorrow with a 5k road race, for a change of pace, literally! :)

I'm lucky just to keep up with the daily rat race - and I've been on the
losing end of that lately too.

... "Are we clinging tenatiously to my buttocks?"- Powdered Toast Man
--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)

Hello Tony;

Tony Langdon wrote to Brian Rogers <=-

Cool, well it's more direct on my end. I'm unusual in that I run
native IPv6 on the BBS and tunnel IPv4. :)

I *could* do that but my ISP filters too many ports. Pretty much useless.
It reminds me of when AOL first claimed to pass IPs to their users. I asked them what hostname do I use for port 25 and 110. They said you can't it's blocked. So I said "why should I stay if I can't use standard IP software?"
the silence was deafening!

LOL, I had a track meet today (the reason I'm in Cairns, actually). :) Backing that up tomorrow with a 5k road race, for a change of pace, literally! :)

When tracks meet... what do they say to each other? <G>

I ended up winning the 5k in my age group, FYI. :)

Congrats! That extra spoonful of geritol helped I see :D

... Know yourself, know your business, know your men. Randall Jacobs
--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)

Hi Michiel!

Saturday September 28 2024 18:35, you wrote to All:

MvdV> We have a new one: ( with two nodes )

MvdV> 106 2:467/4 Ruslan Suleimanov T-6in4 he.net
MvdV> 107 2:467/888 Ruslan Suleimanov T-6in4 he.net f

MvdV> Ruslan, welcome to the Fidonet IPv6 club!

[11:39:52 brorabbit jamstat]$ cat ~/logs/callip.log
2024-09-30 11:39:33.459 callip.pl v.0.9.6.0. -c /home/fido/etc/callip.conf -b -f 2:467/4
2024-09-30 11:39:35.066 Finding last nodelist file from /home/fido/nodelist/nodelist.367.
2024-09-30 11:39:35.066 Last nodelist found at 0.000 seconds.
2024-09-30 11:39:35.119 Nodelist for Saturday, September 14, 2024 -- Day number 258 parsed, 942 IP-nodes processed (0.053 sec)
2024-09-30 11:39:35.143 Calling 2:467/4
2024-09-30 11:39:35.143 ip.fido.odessa.ua:24554
2024-09-30 11:39:35.143 Error: Cannot getaddrinfo - ������⭮� ��� ��� �㦡� 2024-09-30 11:39:52.859 callip.pl v.0.9.6.0. -c /home/fido/etc/callip.conf -b -f 2:467/888
2024-09-30 11:39:52.887 Finding last nodelist file from /home/fido/nodelist/nodelist.367.
2024-09-30 11:39:52.887 Last nodelist found at 0.000 seconds.
2024-09-30 11:39:52.939 Nodelist for Saturday, September 14, 2024 -- Day number 258 parsed, 942 IP-nodes processed (0.052 sec)
2024-09-30 11:39:52.943 Calling 2:467/888
2024-09-30 11:39:52.943 fido.paket.ua:24554
2024-09-30 11:39:52.943 Error: Cannot getaddrinfo - ������⭮� ��� ��� �㦡� [11:40:05 brorabbit jamstat]$


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)

Hi Stas,

On 2024-09-30 11:40:30, you wrote to Michiel van der Vlist:

MvdV>> We have a new one: ( with two nodes )

MvdV>> 106 2:467/4 Ruslan Suleimanov T-6in4 he.net
MvdV>> 107 2:467/888 Ruslan Suleimanov T-6in4 he.net f

MvdV>> Ruslan, welcome to the Fidonet IPv6 club!

[11:39:52 brorabbit jamstat]$ cat ~/logs/callip.log
2024-09-30 11:39:33.459 callip.pl v.0.9.6.0. -c /home/fido/etc/callip.conf -b
-f 2:467/4 2024-09-30 11:39:35.066 Finding last nodelist file from /home/fido/nodelist/nodelist.367. 2024-09-30 11:39:35.066 Last nodelist found
at 0.000 seconds. 2024-09-30 11:39:35.119 Nodelist for Saturday, September 14,
2024 -- Day number 258 parsed, 942 IP-nodes processed (0.053 sec) 2024-09-30
11:39:35.143 Calling 2:467/4 2024-09-30 11:39:35.143 ip.fido.odessa.ua:24554
2024-09-30 11:39:35.143 Error: Cannot getaddrinfo - eu??ec??oe u?? u?u c?y?6a
2024-09-30 11:39:52.859 callip.pl v.0.9.6.0. -c /home/fido/etc/callip.conf -b
-f 2:467/888 2024-09-30 11:39:52.887 Finding last nodelist file from /home/fido/nodelist/nodelist.367. 2024-09-30 11:39:52.887 Last nodelist found
at 0.000 seconds. 2024-09-30 11:39:52.939 Nodelist for Saturday, September 14,
2024 -- Day number 258 parsed, 942 IP-nodes processed (0.052 sec) 2024-09-30
11:39:52.943 Calling 2:467/888 2024-09-30 11:39:52.943
fido.paket.ua:24554 2024-09-30 11:39:52.943 Error: Cannot getaddrinfo - eu??ec??oe u?? u?u c?y?6a [11:40:05 brorabbit jamstat]$

2024-09-30 11:12:53.994 callip.pl v.0.9.6.0. -c /home/fido/etc/callip_fido.cfg -f 2:467/4,2:467/888
2024-09-30 11:12:53.994 Finding last nodelist file from /home/fido/nodelist/Z2DAILY.???.
2024-09-30 11:12:53.994 Last nodelist found at 0.000 seconds.
2024-09-30 11:12:54.007 Nodelist for Monday, September 30, 2024 -- Day number 274 parsed, 945 IP-nodes processed (0.012 sec)
2024-09-30 11:12:54.737 Calling 2:467/888
2024-09-30 11:12:54.737 fido.paket.ua:24554
2024-09-30 11:12:54.737 (2001:470:6137:0:f1d0:2:467:888:24554)
2024-09-30 11:12:54.737 OPT CRAM-MD5-1171633ea60874c679428dc4507259ee 2024-09-30 11:12:54.737 SYS RSNET FIDO DRUZI 199X
2024-09-30 11:12:54.737 ZYZ Ruslan Suleimanov <http://fido.odessa.ua> 2024-09-30 11:12:54.737 LOC Odessa, UA
2024-09-30 11:12:54.737 NDL 500M,INA:fido.odessa.ua,IMI:f888.n467.z2@fido.odessa.ua,IBN,XW,TCP,BINKP,ICM
2024-09-30 11:12:54.737 TIME Mon, 30 Sep 2024 12:12:54 +0300
2024-09-30 11:12:54.737 VER binkd/1.1a-115/FreeBSD binkp/1.1
2024-09-30 11:12:54.737 address: 2:467/888@fidonet
2024-09-30 11:12:54.737 address: 888:888/8@rsnet
2024-09-30 11:12:54.737 TRF 0 0
2024-09-30 11:12:54.737 OPT EXTCMD GZ BZ2
2024-09-30 11:12:54.737 2001:470:6137:0:f1d0:2:467:888 - Ok.
2024-09-30 11:12:54.737 Session with 2:467/888 done.
2024-09-30 11:12:54.737 (213.231.5.55:24554)
2024-09-30 11:12:54.737 OPT CRAM-MD5-b3f346396b7b909a021728e270463dee 2024-09-30 11:12:54.737 SYS RSNET FIDO DRUZI 199X
2024-09-30 11:12:54.737 ZYZ Ruslan Suleimanov <http://fido.odessa.ua> 2024-09-30 11:12:54.737 LOC Odessa, UA
2024-09-30 11:12:54.737 NDL 500M,INA:fido.odessa.ua,IMI:f888.n467.z2@fido.odessa.ua,IBN,XW,TCP,BINKP,ICM
2024-09-30 11:12:54.737 TIME Mon, 30 Sep 2024 12:12:54 +0300
2024-09-30 11:12:54.737 VER binkd/1.1a-115/FreeBSD binkp/1.1
2024-09-30 11:12:54.737 address: 2:467/888@fidonet
2024-09-30 11:12:54.737 address: 888:888/8@rsnet
2024-09-30 11:12:54.737 TRF 0 0
2024-09-30 11:12:54.737 OPT EXTCMD GZ BZ2
2024-09-30 11:12:54.737 213.231.5.55 - Ok.
2024-09-30 11:12:54.737 Session with 2:467/888 done.
2024-09-30 11:12:55.622 Calling 2:467/4
2024-09-30 11:12:55.622 ip.fido.odessa.ua:24554
2024-09-30 11:12:55.622 (2001:470:70:222::2:24554)
2024-09-30 11:12:55.622 OPT CRAM-MD5-2b3279b04c855079d3a6c0034e8ab0ee 2024-09-30 11:12:55.622 SYS RSNET FIDONET2CLOUD DRUZI 199X
2024-09-30 11:12:55.622 ZYZ RS <Ruslan_Suleimanov@f888.n467.z2.fidonet.org> 2024-09-30 11:12:55.622 LOC Odessa, UA
2024-09-30 11:12:55.622 NDL 100M,INA:ip.fido.odessa.ua,IMI:f888.n467.z2@fido.odessa.ua,IBN,XW,TCP,BINKP,ICM
2024-09-30 11:12:55.622 TIME Mon, 30 Sep 2024 12:12:54 +0300
2024-09-30 11:12:55.622 VER binkd/1.1a-115/FreeBSD binkp/1.1
2024-09-30 11:12:55.622 address: 2:467/4@fidonet
2024-09-30 11:12:55.622 address: 2:467/999@fidonet
2024-09-30 11:12:55.622 TRF 0 0
2024-09-30 11:12:55.622 OPT EXTCMD GZ BZ2
2024-09-30 11:12:55.622 2001:470:70:222::2 - Ok.
2024-09-30 11:12:55.622 Session with 2:467/4 done.
2024-09-30 11:12:55.622 (213.231.2.124:24554)
2024-09-30 11:12:55.622 OPT CRAM-MD5-7ec1b95e4ecdc38ed73c8b41c975e7ee 2024-09-30 11:12:55.622 SYS RSNET FIDONET2CLOUD DRUZI 199X
2024-09-30 11:12:55.622 ZYZ RS <Ruslan_Suleimanov@f888.n467.z2.fidonet.org> 2024-09-30 11:12:55.622 LOC Odessa, UA
2024-09-30 11:12:55.622 NDL 100M,INA:ip.fido.odessa.ua,IMI:f888.n467.z2@fido.odessa.ua,IBN,XW,TCP,BINKP,ICM
2024-09-30 11:12:55.622 TIME Mon, 30 Sep 2024 12:12:55 +0300
2024-09-30 11:12:55.622 VER binkd/1.1a-115/FreeBSD binkp/1.1
2024-09-30 11:12:55.622 address: 2:467/4@fidonet
2024-09-30 11:12:55.622 address: 2:467/999@fidonet
2024-09-30 11:12:55.622 TRF 0 0
2024-09-30 11:12:55.622 OPT EXTCMD GZ BZ2
2024-09-30 11:12:55.622 213.231.2.124 - Ok.
2024-09-30 11:12:55.622 Session with 2:467/4 done.

What nameserver do you use?


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

�ਢ������ ���, Stas!

30 ᥭ 24 11:40, Stas Mishchenkov wrote to Michiel van der Vlist:

MvdV>> Ruslan, welcome to the Fidonet IPv6 club!

[11:39:52 brorabbit jamstat]$ cat ~/logs/callip.log
2024-09-30 11:39:33.459 callip.pl v.0.9.6.0. -c

root@OpenWrt:~# ps w|grep dns
1586 root 1211m S /usr/sbin/dnscrypt-proxy -config /etc/dnscrypt-proxy2/dnscrypt-proxy.toml
6549 root 2764 S {dnsmasq} /sbin/ujail -t 5 -n dnsmasq -u -l -r /bin/ubus -r /etc/TZ -r /etc/dnsmasq.conf -r /etc/ethers -
6551 dnsmasq 4884 S /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf.cfg01411c -k -x /var/run/dnsmasq/dnsmasq.cfg01411c.pid
31479 root 1320 S grep dns

root@OpenWrt:~# nslookup fido.paket.ua
Server: 127.0.0.1
Address: 127.0.0.1:53

Non-authoritative answer:
Name: fido.paket.ua
Address: 213.231.5.55

Non-authoritative answer:
Name: fido.paket.ua
Address: 2001:470:6137:0:f1d0:2:467:888

root@OpenWrt:~# nslookup ip.fido.odessa.ua
Server: 127.0.0.1
Address: 127.0.0.1:53

Non-authoritative answer:
Name: ip.fido.odessa.ua
Address: 213.231.2.124

Non-authoritative answer:
Name: ip.fido.odessa.ua
Address: 2001:470:70:222::2

����ᥩ ��ਭ��

E-Mail: aleksey.v.barinov AT gmail.com Skype: huba-huba Telegram: @huba715 [Team ��த���] [F09F87BAF09F87A6]
... �祭�� ���� ��ᨫ쭮, ��⮬� �� ��� ��୮
--- GoldED+/W64-MSVC 1.1.5-b20240306
* Origin: Alex at Home (2:5020/5452)

x) Monday Sep 30, 2024, 11:40. Stas Mishchenkov �� Michiel van der Vlist.

IP-nodes processed (0.053 sec) 2024-09-30 11:39:35.143 Calling 2:467/4 2024-09-30 11:39:35.143 ip.fido.odessa.ua:24554 2024-09-30 11:39:35.143 Error: Cannot getaddrinfo - ������⭮� ��� ��� �㦡� 2024-09-30 11:39:52.859 callip.pl v.0.9.6.0. -c /home/fido/etc/callip.conf -b -f 2:467/888 2024-09-30 11:39:52.887 Finding last nodelist file from /home/fido/nodelist/nodelist.367. 2024-09-30 11:39:52.887 Last nodelist found at 0.000 seconds. 2024-09-30 11:39:52.939 Nodelist for Saturday, September 14, 2024 -- Day number 258 parsed, 942 IP-nodes processed (0.052 sec) 2024-09-30 11:39:52.943 Calling 2:467/888 2024-09-30 11:39:52.943 fido.paket.ua:24554 2024-09-30 11:39:52.943 Error: Cannot getaddrinfo - ������⭮� ��� ��� �㦡� [11:40:05 brorabbit jamstat]$

if your ISP blocks .UA domains resolving, set dns to

1.1.1.1
8.8.8.8
2606:4700:4700::1111
2001:4860:4860::8888

then retry. and if these DNS are blocked too... well, try a VPN.

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

Hi Alex!

Wednesday October 02 2024 05:44, you wrote to me:

IP-nodes processed (0.053 sec) 2024-09-30 11:39:35.143 Calling
2:467/4
2024-09-30 11:39:35.143 ip.fido.odessa.ua:24554 2024-09-30 11:39:35.143
Error: Cannot getaddrinfo - ������⭮� ��� ��� �㦡� 2024-09-30
11:39:52.859 callip.pl v.0.9.6.0. -c /home/fido/etc/callip.conf -b -f
2:467/888 2024-09-30 11:39:52.887 Finding last nodelist file from
/home/fido/nodelist/nodelist.367. 2024-09-30 11:39:52.887 Last nodelist
found at 0.000 seconds. 2024-09-30 11:39:52.939 Nodelist for Saturday,
September 14, 2024 -- Day number 258 parsed, 942 IP-nodes processed
(0.052 sec) 2024-09-30 11:39:52.943 Calling 2:467/888 2024-09-30
11:39:52.943 fido.paket.ua:24554 2024-09-30 11:39:52.943 Error: Cannot
getaddrinfo - ������⭮� ��� ��� �㦡� [11:40:05 brorabbit jamstat]$

if your ISP blocks .UA domains resolving, set dns to

1.1.1.1
8.8.8.8
2606:4700:4700::1111
2001:4860:4860::8888

[ustasm@MikroTik] > /ip dns print
servers: 8.8.8.8,8.8.4.4,74.82.42.42,2001:470:20::2
dynamic-servers: 91.205.216.34,8.8.8.8,fe80::1
use-doh-server:
verify-doh-cert: no
allow-remote-requests: yes
max-udp-packet-size: 4096
query-server-timeout: 2s
query-total-timeout: 10s
max-concurrent-queries: 100
max-concurrent-tcp-sessions: 20
cache-size: 2048KiB
cache-max-ttl: 1w
cache-used: 224KiB

then retry. and if these DNS are blocked too... well, try a VPN.

I do nothing. Now it works.

[07:28:36 brorabbit logs]$ host ip.fido.odessa.ua
ip.fido.odessa.ua has address 213.231.2.124
ip.fido.odessa.ua has IPv6 address 2001:470:70:222::2
[07:30:20 brorabbit logs]$ host fido.paket.ua
fido.paket.ua has address 213.231.5.55
fido.paket.ua has IPv6 address 2001:470:6137:0:f1d0:2:467:888
fido.paket.ua mail is handled by 10 213.231.5.55.

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)

x) Wednesday Oct 02, 2024, 07:24. Stas Mishchenkov �� Alex Shuman.

if your ISP blocks .UA domains resolving, set dns to
1.1.1.1
8.8.8.8
2606:4700:4700::1111
2001:4860:4860::8888

[ustasm@MikroTik] > /ip dns print
servers: 8.8.8.8,8.8.4.4,74.82.42.42,2001:470:20::2
dynamic-servers: 91.205.216.34,8.8.8.8,fe80::1

maybe, you were unlucky and 91.205.216.34 answered with host not found.

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

Hello, Alex!

Wednesday October 02 2024 13:15, you wrote to Stas Mishchenkov:

maybe, you were unlucky and 91.205.216.34 answered with host not
found.

Sometimes, Russian ISPs just redirect all DNS traffic to their own servers.

In such cases people often use DNS over HTTPS (DoH) to access the free Internet.

Best regards,
dp.

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

Hello All,

We have a couple of new ones.

109 2:5020/5452 Alex Barinov T-6in4 he.net
110 2:5030/723 Alexey Khromov Native RU-AI-20240222
111 2:550/278 Vladislav Muschinskikh Native Firstbyte
112 3:633/2744 Deon George Native EXETEL-AU

Alex Barinov and Deon George are not really new to the club, they already had an IPv6 node on air. The above is their second node. The others are new AFAIK.

So Alex and Vladislav, welcome to the Fidomnet IPv6 club!


Cheers, Michiel

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

Hello All,

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

I forgot this one

108 1:266/625 Scott Street Native Verizon

Scott, welcome to the Fidonet IPv6 club!


Cheers, Michiel

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

Hello Vladislav,

On Thursday October 10 2024 00:31, you wrote to me:

So Alex and Vladislav, welcome to the Fidomnet IPv6 club!

I also was in the list since 2023-08-09, with my two nodes

May be, earlier... =/

Yes I see hat now. Thanks for the correction.


Cheers, Michiel

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

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, 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,

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