Re: List of IPv6 nodes
By: Michiel van der Vlist to All on Sun Oct 19 2025 22:00:01
You may not have the answer, but I used to have this set up some time
ago, but I cannot remember nor figure out how I did it. How does one
set up in Linux (Debian variant) the f1d0 address?
f Has a ::f1d0:<zone>:<net>:<node> style host address.
Example: ::f1d0:2:280:5555 (for node 2:280/5555)
In my case ::f1d0:1:214:22.
Thanks.
You may not have the answer, but I used to have this set up some time
ago, but I cannot remember nor figure out how I did it. How does one set up in Linux (Debian variant) the f1d0 address?
f Has a ::f1d0:<zone>:<net>:<node> style host address.
Example: ::f1d0:2:280:5555 (for node 2:280/5555)
In my case ::f1d0:1:214:22.
You'll generally need a domain name for your BBS or some way to refer
to your BBS by a domain name and then configure DNS with an AAAA
record.
That is a response to the question on how to set it up in DNS. But as I read it that is not what Ray asked. He wanted to know how to set up such an address in Linux.
Michiel van der Vlist wrote to All <=-
*List of IPv6 nodes
List of IPv6 nodes
By Michiel van der Vlist, 2:280/5555
Updated 2 Nov 2025
No one cares about this non-useful "information".
Now you know.
No one cares about this non-useful "information".
Now you know.
Fake news again. I care.
Donald, is it you?
List of IPv6 nodes
By Michiel van der Vlist, 2:280/5555
Updated 2 Nov 2025
<SNIP>
No one cares about this non-useful "information".
Now you know.
*List of IPv6 nodes
List of IPv6 nodes
By Michiel van der Vlist, 2:280/5555
Updated 2 Nov 2025
<SNIP>
No one cares about this non-useful "information".
Now you know.
It is a classic example of the US exceptionalism that especially
the MAGA morons demonstrate over and over again.
Michiel van der Vlist wrote to All <=-
*List of IPv6 nodes
List of IPv6 nodes
By Michiel van der Vlist, 2:280/5555
Updated 2 Nov 2025
<SNIP>
No one cares about this non-useful "information".
Now you know.
MvdV> 40 2:460/58 Stas Mishchenkov Native
MvdV> KCT f 6DWN
MvdV> 61 2:460/5858 Stas Mishchenkov Native KCT
MvdV> HOLD f INO4
MvdV> 40 2:460/58 Stas Mishchenkov Native
MvdV> KCT f 6DWN
2025-12-07 09:50:16.979 callip.pl v.0.9.6.0. -c callip.conf -b -f 2:460/58 2025-12-07 09:50:16.980 Finding last nodelist file from /bbs/nodelist/NODELIST.NDL. 2025-12-07 09:50:16.980 Last nodelist found at 0.000 seconds. 2025-12-07 09:50:16.996 Nodelist for Sunday, December 7, 2025 -- Day number 341 parsed, 940 IP-nodes processed (0.016 sec) 2025-12-07
09:50:17.448 Calling 2:460/58 2025-12-07 09:50:17.448 brorabbit.g0x.ru:24554 2025-12-07 09:50:17.448 2a0b:db80:8c:9246:f1d0:2:460:58 - Ok. 2025-12-07 09:50:17.448 193.107.113.122 - Ok.
MvdV> 61 2:460/5858 Stas Mishchenkov Native KCT
MvdV> HOLD f INO4
2025-12-07 09:51:49.188 callip.pl v.0.9.6.0. -c callip.conf -b -f 2:460/5858 2025-12-07 09:51:49.188 Finding last nodelist file from /bbs/nodelist/NODELIST.NDL. 2025-12-07 09:51:49.188 Last nodelist found at 0.000 seconds. 2025-12-07 09:51:49.204 Nodelist for Sunday, December 7, 2025 -- Day number 341 parsed, 940 IP-nodes processed (0.016 sec) 2025-12-07
09:52:04.261 Calling 2:460/5858 2025-12-07 09:52:04.261 burrow.g0x.ru:24554 2025-12-07 09:52:04.261 2a0b:db80:86:150:f1d0:2:460:5858 - Error: Connection timed out
2a0b:db80:86:150:f1d0:2:460:5858 - Error: Connection timed out
Thanks, I hope it fixed.
alling 2:460/5858 2025-12-07 09:52:04.261
burrow.g0x.ru:24554 2025-12-07 09:52:04.261
2a0b:db80:86:150:f1d0:2:460:5858 - Error: Connection timed out
Thanks, I hope it fixed.
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.
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.
| Sysop: | Eric Oulashin |
|---|---|
| Location: | Beaverton, Oregon, USA |
| Users: | 127 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 05:14:19 |
| Calls: | 7,713 |
| Calls today: | 6 |
| Files: | 9,376 |
| U/L today: |
27 files (5,040K bytes) |
| D/L today: |
301 files (144M bytes) |
| Messages: | 393,803 |
| Posted today: | 3 |