Hello All,

We have a new one: ( with two nodes )

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

Ruslan, welcome to the Fidonet IPv6 club!


Cheers, Michiel

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

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)

�ਢ������ ���, 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, Michiel.

08 ��� 24 18:38, Michiel van der Vlist -> All:

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!

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

May be, earlier... =/


With best regards, Vladislav
--- Me on Telegram http://t.me/VladisMus
* Origin: (2:550/278.1)

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