2:280/1049 thecoastbbs.nl:24554
2001:9e0:8547:7c01:ac0:77:8500:100 No such AKA.
2:280/2060 fidonet.aroundmyroom.com:24554 2001:1c00:c204:4300:f1d0:2:280:2060 No such AKA.
I tested the dutch nodes in your list.
On 2026-02-04 17:18:50, you wrote to Michiel van der Vlist:
2:280/1049 thecoastbbs.nl:24554
2001:9e0:8547:7c01:ac0:77:8500:100 No such AKA.
I get an OK for this node!?
Calling '2:280/1049'. Call time: '0000-2400' UTC.
thecoastbbs.nl, 24554
Calling 2:280/1049 (2001:9e0:8547:7c01:ac0:77:8500:100:24554)
address: 2:280/1049@fidonet
2001:9e0:8547:7c01:ac0:77:8500:100 - Ok.
So?
2:280/2060 fidonet.aroundmyroom.com:24554
2001:1c00:c204:4300:f1d0:2:280:2060 No such AKA.
Indeed point 2:280/2060.6 is answering on this IPv6 address! And not the node...
2:280/1049 thecoastbbs.nl:24554
2001:9e0:8547:7c01:ac0:77:8500:100 No such AKA.
I get an OK for this node!?
Calling '2:280/1049'. Call time: '0000-2400' UTC.
thecoastbbs.nl, 24554
Calling 2:280/1049 (2001:9e0:8547:7c01:ac0:77:8500:100:24554)
address: 2:280/1049@fidonet
2001:9e0:8547:7c01:ac0:77:8500:100 - Ok.
So?
Now I got "Ok" too. Hm.
2:280/2060 fidonet.aroundmyroom.com:24554
2001:1c00:c204:4300:f1d0:2:280:2060 No such AKA.
Indeed point 2:280/2060.6 is answering on this IPv6 address! And not the
node...
Does he know about it?
And what about "connection refused" and "no route to host" results?
So I tested your full list. I get a few Ok's, and a few 'No such
AKA''s:
I have dedicted "AKA Mismatch" report:
https://nodelist.fidonet.cc/analytics/aka-mismatch?days=30&limit=1000& includeZero=true
So I tested your full list. I get a few Ok's, and a few 'No such
AKA''s:
I have dedicted "AKA Mismatch" report:
https://nodelist.fidonet.cc/analytics/aka-mismatch?days=30&limit=1000&includeZ
ero=true
1:104/0 binkp.pharcyde.org:24554 2603:6000:dc00:44:f1d0:1:154:10 No
such AKA.
1:114/0 binkp.pharcyde.org:24554 2603:6000:dc00:44:f1d0:1:154:10 No
such AKA.
*List of IPv6 nodes
List of IPv6 nodes
By Michiel van der Vlist, 2:280/5555
Updated 29 Jan 2026
2:280/2060 fidonet.aroundmyroom.com:24554
2001:1c00:c204:4300:f1d0:2:280:2060 No such AKA.
Indeed point 2:280/2060.6 is answering on this IPv6 address! And not
the node...
Does he know about it?
If he doesn't respond here, I'll let him know. ;-)
Note that in the particular case of 280/2060, the AKA mismatch
only occurs when connecting via IPv6. There is no problem when
connecting via IPv4. So you may have to split it up and test both
protocols.
Wow, that's amazing! I never thought someone would provide different addresses on ipv4 and ipv6. It was really beyond my imagination.
New tests will handle such cases: I was testing both ipv4 and ipv6,
but saved node information only once (ipv6 preferred). This is
actually a good case, because now I am getting node information:
binkp ipv6
binkp ipv4
ifcico ipv6
ifcico ipv4
modem ifcico
and more to come..
If it's complicated, I am having a good time testing and fixing it :)
And what about "connection refused" and "no route to host" results?
So I tested your full list. I get a few Ok's, and a few 'No such AKA''s:
1:135/220 bbs.archaicbinary.net:24554 2001:470:1d:4aa::2
Ok.
2:222/2 bbbs.net:24554 2a10:a5c0:24f:f000::1 Ok.
2:280/1049 thecoastbbs.nl:24554
2001:9e0:8547:7c01:ac0:77:8500:100 Ok.
The others don't get a connect here either. Does this answer your question? ;-)
1:135/220 bbs.archaicbinary.net:24554 2001:470:1d:4aa::2
Ok.
Strange.
[14:38:05 brorabbit logs]$ callip -c ~/etc/callip.conf -b -f 1:135/220
You have actual version.
Parsing nodelist file /home/fido/nodelist/nodelist.367
Nodelist for Thursday, February 5, 2026 -- Day number 036 parsed, 949 IP-nodes
processed (0.052 sec) Calling '1:135/220'. Call time: '0000-2400' UTC. Now is:
1139 UTC. bbs.archaicbinary.net, 24554 Calling 1:135/220 (2001:470:1d:4aa::2:24554) error (Connection timed out) Calling 1:135/220 (167.114.108.156:24554) error (Connection timed out)
I've created a report that produces the same list, but based on
real-life tests (check "Download as Text" button):
https://nodelist.fidonet.cc/analytics/ipv6-node-list
Many Russian nodes got a 6UNS status. This is because the Russian
Internet is now heavily filtered and connections from Oracle Cloud
fail during drone attacks or when new anti VPN filters are applied by
the Russian censorship authorities.
I could test them from Russia, but I think that wouldn't be accurate
at all. It's better to show that those nodes are actually unstable for other FidoNet nodes.
Yes, I too noticed that the mojority of the 6UNS nodes are Russian.
Some are in Ukraine. But there are some in "the west" as well. I
flagged then as 6UNS but they may be just as unstable with IPv6. But
my list is about IPv6, so that is what I list.
1:104/0 binkp.pharcyde.org:24554 2603:6000:dc00:44:f1d0:1:154:10 No
such AKA.
1:114/0 binkp.pharcyde.org:24554 2603:6000:dc00:44:f1d0:1:154:10 No
such AKA.
These should be fixed.
Just "interim" NC numbers I never paid much attention to and never
added to binkd. The 2-3 nodes in each have no care
in the world to be NC, and don't want to change their node number.
C'est la vie.
Thanks for the report, though!
1:104/0 binkp.pharcyde.org:24554 2603:6000:dc00:44:f1d0:1:154:10
No such AKA.
1:114/0 binkp.pharcyde.org:24554 2603:6000:dc00:44:f1d0:1:154:10
No such AKA.
These should be fixed.
It MUST be fixed.
It doesn't need to be changed, it just needs to be added. It's
assumed that this isn't a particularly technically challenging task
for the network coordinator.
89 4:902/26 Fernando Toledo Native Claro 6DWN
89 4:902/26 Fernando Toledo Native
Claro 6DWN
I'm online again
can you verify if connect to me via ipv6 ?
thanks!
address: 4:902/26@fidonet
address: 666:1/1@latinet
address: 21:2/151@fsxnet
address: 618:500/45@micronet
address: 46:10/182@agoranet
address: 39:943/0@amiganet
address: 39:943/1@amiganet
address: 954:895/37@hobbynet
address: 15:1/1@zudaka
address: 15:1/0@zudaka
address: 15:0/0@zudaka
address: 4:4/0@fidonet
address: 4:90/0@fidonet
address: 4:900/0@fidonet
address: 4:902/0@fidonet
address: 4:904/0@fidonet
address: 4:905/0@fidonet
address: 80:774/16@retronet
address: 64:500/16@cnet
address: 314:413/16@pinet
I'm online again
can you verify if connect to me via ipv6 ?
Stas Mishchenkov -> Fernando Toledo skrev 2025-12-12 04:58:
address: 4:902/26@fidonet
address: 666:1/1@latinet
address: 21:2/151@fsxnet
address: 618:500/45@micronet
address: 46:10/182@agoranet
address: 39:943/0@amiganet
address: 39:943/1@amiganet
address: 954:895/37@hobbynet
address: 15:1/1@zudaka
address: 15:1/0@zudaka
address: 15:0/0@zudaka
address: 4:4/0@fidonet
address: 4:90/0@fidonet
address: 4:900/0@fidonet
address: 4:902/0@fidonet
address: 4:904/0@fidonet
address: 4:905/0@fidonet
address: 80:774/16@retronet
address: 64:500/16@cnet
address: 314:413/16@pinet
Not anymore. I'm back on he.net.
| Sysop: | Drillsar |
|---|---|
| Location: | Livingston, NJ |
| Users: | 5 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 112:58:34 |
| Calls: | 16 |
| Messages: | 15,287 |