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
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.
And you might want to look into these: 2:5058/108 2:201/111 2:5066/35
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.
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.
15 3:633/280 Stephen Walsh Native AusNetServers f
20 3:633/281 Stephen Walsh Native Internode
20 3:633/281 Stephen Walsh Native Leaptel IO
Tnx. The list has been updated.
I assume the IO for 281 is because you are running a port proxy to
make the Amiga accept IPv6?
*List of IPv6 nodes
List of IPv6 nodes
By Michiel van der Vlist, 2:280/5555
Updated 17 May 2026
Node Nr. Sysop Type Provider Remark
Hello Sean,
On Friday May 22 2026 22:05, you wrote to me:
Just added my ipv6 setup, should be working, tested a telnet from
a
remote pc to the ipv6 binkd and got the reply
2:263/1 Sean Rima f Sky.com
+ 03:16 [4004] call to 2:263/1@fidonet
03:16 [4004] trying binkd.rima.ie [2a06:5900:8194:100:acb:a059:6e85:1ded]...
? 03:16 [4004] connection to 2:263/1@fidonet failed: {W32 API
error 10060} Connection timed out
03:16 [4004] trying binkd.rima.ie [51.182.63.136]...
? 03:17 [4004] connection to 2:263/1@fidonet failed: {W32 API
error 10060} Connection timed out
03:17 [3216] the queue is empty, quitting...
Looks like you still have to configure the firewall and port
forwarding...
+ 03:16 [4004] call to 2:263/1@fidonet
03:16 [4004] trying binkd.rima.ie
[2a06:5900:8194:100:acb:a059:6e85:1ded]... ? 03:16 [4004]
connection
to 2:263/1@fidonet failed: {W32 API
error 10060} Connection timed out
03:16 [4004] trying binkd.rima.ie [51.182.63.136]...
? 03:17 [4004] connection to 2:263/1@fidonet failed: {W32 API
error 10060} Connection timed out
03:17 [3216] the queue is empty, quitting...
Looks like you still have to configure the firewall and port
forwarding...
Can you make a poll to my system so that we can see if outgoing IPv6
workd for you?
Can you make a poll to my system so that we can see if outgoing
IPv6 workd for you?
I can poll Ward and Kim in ipv6, but here goes
23 May 18:30:59 [68041] trying f5555.n280.z2.binkp.net[..]
[2001:4c3c:7d02:ff00:f1d0:2:280:5555]... 23 May 18:30:59 [68041]
connected + 23 May 18:30:59 [68041] outgoing session with
f5555.n280.z2.binkp.net:24554
[2001:4c3c:7d02:ff00:f1d0:2:280:5555] - 23 May 18:30:59 [68041]
OPT CRAM-MD5-f985e9a5aa2a24b81a88bb80f1ac7bee
Check:
+ 23 May 19:31:17 [3088] incoming session with
2a06:5900:8194:100:acb:a059:6e85:1ded
- 23 May 19:31:17 [3088] SYS There Can Only Be 1
- 23 May 19:31:17 [3088] ZYZ Sean Rima
- 23 May 19:31:17 [3088] LOC Letterfrack, Ireland
- 23 May 19:31:17 [3088] NDL 115200,TCP,BINKP
- 23 May 19:31:17 [3088] TIME Sat, 23 May 2026 18:30:59 +0100
- 23 May 19:31:17 [3088] VER binkd/1.1a-115/Linux binkp/1.1
So I will list you in the IPv6 list as "OO" (Outgoing Only) for the
time being.
Check:
+ 23 May 19:31:17 [3088] incoming session with
2a06:5900:8194:100:acb:a059:6e85:1ded
- 23 May 19:31:17 [3088] SYS There Can Only Be 1
- 23 May 19:31:17 [3088] ZYZ Sean Rima
- 23 May 19:31:17 [3088] LOC Letterfrack, Ireland
- 23 May 19:31:17 [3088] NDL 115200,TCP,BINKP
- 23 May 19:31:17 [3088] TIME Sat, 23 May 2026 18:30:59 +0100
- 23 May 19:31:17 [3088] VER binkd/1.1a-115/Linux binkp/1.1
So I will list you in the IPv6 list as "OO" (Outgoing Only) for the
time being.
Should be in and out now :)
Hi Sean,
On 2026-05-26 11:46:31, you wrote to Michiel van der Vlist:
Should be in and out now :)
Not yet, just moments ago...
Nodelist for Tuesday, May 26, 2026 -- Day number 146 parsed, 955
IP-nodes processed (0.013 sec) Calling '2:263/1'. Call time:
'0000-2400' UTC. Now is: 1102 UTC.
bbs.rima-iot.eu, 24554
Calling 2:263/1 (2a06:5900:8194:100:acb:a059:6e85:1ded:24554)
error (Connection timed out)
Calling 2:263/1 (51.182.63.136:24554)
error (No route to host)
+ 23 May 19:31:17 [3088] incoming session with
2a06:5900:8194:100:acb:a059:6e85:1ded
- 23 May 19:31:17 [3088] SYS There Can Only Be 1
- 23 May 19:31:17 [3088] ZYZ Sean Rima
- 23 May 19:31:17 [3088] LOC Letterfrack, Ireland
- 23 May 19:31:17 [3088] NDL 115200,TCP,BINKP
- 23 May 19:31:17 [3088] TIME Sat, 23 May 2026 18:30:59 +0100
- 23 May 19:31:17 [3088] VER binkd/1.1a-115/Linux binkp/1.1
So I will list you in the IPv6 list as "OO" (Outgoing Only) for
the time being.
Should be in and out now :)
Alas, not yet:
+ 14:28 [3904] call to 2:263/1@fidonet
14:28 [3904] trying binkd.rima.ie [2a06:5900:8194:100:acb:a059:6e85:1ded]...
? 14:29 [3904] connection to 2:263/1@fidonet failed: {W32 API
error 10060} Connection timed out
14:29 [3904] trying binkd.rima.ie [51.182.63.136]...
? 14:29 [3904] connection to 2:263/1@fidonet failed: {W32 API
error 10060} Connection timed out
14:29 [3796] the queue is empty, quitting...
Nodelist for Tuesday, May 26, 2026 -- Day number 146 parsed, 955
IP-nodes processed (0.013 sec) Calling '2:263/1'. Call time:
'0000-2400' UTC. Now is: 1102 UTC.
bbs.rima-iot.eu, 24554
Calling 2:263/1 (2a06:5900:8194:100:acb:a059:6e85:1ded:24554)
error (Connection timed out)
Calling 2:263/1 (51.182.63.136:24554)
error (No route to host)
I had rebooted the network which may explain that :)
Sean
I disabled the router firewall as mine is there anyway. Will have to investigate it
26 May 15:45:08 [2003] rc(3467)=0
- 26 May 15:45:13 [2003] incoming from 2a10:3781:5d5d:1:502:da7a:cc60:c396
Hi Sean,
On 2026-05-26 13:33:22, you wrote to me:
I had rebooted the network which may explain that :)
Sean
Should it be fixed now? Because it isn't...
Btw: Did you see my netmail about spamming the STATS area?
Hi Sean,
On 2026-05-26 15:47:08, you wrote to me:
I disabled the router firewall as mine is there anyway. Will have
to
investigate it
26 May 15:45:08 [2003] rc(3467)=0
- 26 May 15:45:13 [2003] incoming from
2a10:3781:5d5d:1:502:da7a:cc60:c396
It seems to be working now:
26 May 16:44:10 [28669] trying binkd.rima.ie [2a06:5900:8194:100:acb:a059:6e85:1ded]... 26 May 16:45:13 [28669] connected + 26 May 16:45:13 [28669] outgoing session with binkd.rima.ie:24554 [2a06:5900:8194:100:acb:a059:6e85:1ded] - 26 May 16:45:14 [28669] OPT CRAM-MD5-78625f2fdb13c472b8b848d3f56d87ee
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: FMail development HQ (2:280/464)
It seems to be working now:
Turned out I didn't need port forwarding but port triggering :)
ok, going to reboot after I send this, but should be ok
| Sysop: | Dave Parker |
|---|---|
| Location: | Redhill, Surrey |
| Users: | 14 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 17:00:28 |
| Calls: | 167 |
| Calls today: | 1 |
| Files: | 12 |
| D/L today: |
4 files (348K bytes) |
| Messages: | 32,486 |