I am not sure what is going on. I have changed it back to port
forwarding but that seemed to fail as well. I logged into a remote pc
and telneted to 24554 and it always connects. There is currently no
way to replace the modem due to the method used for connection
I am not sure what is going on. I have changed it back to port
forwarding but that seemed to fail as well. I logged into a remote pc
and telneted to 24554 and it always connects. There is currently no way
to replace the modem due to the method used for connection
I am not sure what is going on. I have changed it back to port
forwarding but that seemed to fail as well. I logged into a
remote pc and telneted to 24554 and it always connects. There is
currently no way to replace the modem due to the method used for
connection
From about the time you wrote this, all outbound IPv6 connects are
still failing, but all outbound IPv4 connects area successful:
+ 28 May 15:55:07 [25412] call to 2:263/1@fidonet
28 May 15:55:07 [25412] trying bbs.rima-iot.eu [2a06:5900:8194:100:acb:a059:6e85:1ded]... ? 28 May 15:57:15 [25412] connection to 2:263/1@fidonet failed: Connection timed out 28 May
15:57:15 [25412] trying bbs.rima-iot.eu [51.182.63.136]:24554... 28
May 15:57:15 [25412] connected
...
Maybe your IPv6 changed?
The last 64 bits (0acb:a059:6e85:1ded) identify the specific
interface.
Randomized/Privacy-Focused: Looking at the interface ID, it does
not follow the older EUI-64 format (which embeds a device's physical
MAC address into the IP using ff:fe). Instead, it is either statically assigned by the server administrator or generated randomly using
privacy extensions (like RFC 4941 or RFC 7217). This is standard
practice for modern operating systems and security-focused networks to prevent device tracking.
On 28 May 2026, Sean Rima said the following...
I am not sure what is going on. I have changed it back to port
forwarding but that seemed to fail as well. I logged into a
remote pc and telneted to 24554 and it always connects. There is
currently no way
to replace the modem due to the method used for connection
I'm able to connect to IPv4 now (I couldn't before), but you're right, IPv6 is not working from here:
$ nc -w5 -zv4 binkd.rima.ie 24554
Connection to binkd.rima.ie (51.182.63.136) 24554 port [tcp/binkp] succeeded!
$ nc -w5 -zv6 binkd.rima.ie 24554
nc: connect to binkd.rima.ie (2a06:5900:8194:100:acb:a059:6e85:1ded)
port 24554 (tcp) timed out: Operation now in progress
I am not sure what is going on. I have changed it back to port
forwarding but that seemed to fail as well. I logged into a
remote pc and telneted to 24554 and it always connects. There is
currently no way to replace the modem due to the method used for
connection
From about the time you wrote this, all outbound IPv6 connects are
still failing, but all outbound IPv4 connects area successful:
+ 28 May 15:55:07 [25412] call to 2:263/1@fidonet
28 May 15:55:07 [25412] trying bbs.rima-iot.eu [2a06:5900:8194:100:acb:a059:6e85:1ded]... ? 28 May 15:57:15 [25412] connection to 2:263/1@fidonet failed: Connection timed out 28 May
15:57:15 [25412] trying bbs.rima-iot.eu [51.182.63.136]:24554... 28
May 15:57:15 [25412] connected
...
Maybe your IPv6 changed?
Your last connection to me:
- 30 May 11:01:51 [2003] incoming from 2a10:3781:5d5d:1:d82c:290d:c95b:9a46
Hi Sean,
On 2026-05-30 11:02:49, you wrote to me:
Your last connection to me:
- 30 May 11:01:51 [2003] incoming from
2a10:3781:5d5d:1:d82c:290d:c95b:9a46
And 45 minutes before it didn't:
+ 30 May 11:15:06 [5833] call to 2:263/1@fidonet
30 May 11:15:06 [5833] trying bbs.rima-iot.eu [2a06:5900:8194:100:acb:a059:6e85:1ded]... ? 30 May 11:17:14 [5833] connection to 2:263/1@fidonet failed: Connection timed out 30 May
11:17:14 [5833] trying bbs.rima-iot.eu [51.182.63.136]:24554... 30 May 11:17:14 [5833] connected + 30 May 11:17:14 [5833] outgoing session
with bbs.rima-iot.eu:24554 [51.182.63.136]
... Let's hope it stays working from now on...
+ 30 May 11:15:06 [5833] call to 2:263/1@fidonet
30 May 11:15:06 [5833] trying bbs.rima-iot.eu
[2a06:5900:8194:100:acb:a059:6e85:1ded]... ? 30 May 11:17:14
[5833] connection to 2:263/1@fidonet failed: Connection timed out
30 May
11:17:14 [5833] trying bbs.rima-iot.eu [51.182.63.136]:24554...
I have a tail -f on the binkd log running
+ 30 May 11:15:06 [5833] call to 2:263/1@fidonet
30 May 11:15:06 [5833] trying bbs.rima-iot.eu
[2a06:5900:8194:100:acb:a059:6e85:1ded]... ? 30 May 11:17:14
[5833] connection to 2:263/1@fidonet failed: Connection timed
out 30 May
11:17:14 [5833] trying bbs.rima-iot.eu [51.182.63.136]:24554...
I have a tail -f on the binkd log running
+ 30 May 20:29:40 [995186] call to 2:263/1@fidonet
30 May 20:29:47 [995186] trying f1.n263.z2.binkp.net [2a06:5900:8194:100:acb:a059:6e85:1ded]... 30 May 20:29:47 [995186] connected + 30 May 20:29:47 [995186] outgoing session with f1.n263.z2.binkp.net:24554
[2a06:5900:8194:100:acb:a059:6e85:1ded]
- 30 May 20:29:50 [995186] OPT
CRAM-MD5-48f4d43cf28e31d6c159524f4608a0ee
+ 30 May 20:29:50 [995186] Remote requests MD mode
- 30 May 20:29:50 [995186] SYS There Can Only Be 1
- 30 May 20:29:50 [995186] ZYZ Sean Rima
- 30 May 20:29:50 [995186] LOC Letterfrack, Ireland
- 30 May 20:29:50 [995186] NDL 115200,TCP,BINKP
- 30 May 20:29:50 [995186] TIME Sat, 30 May 2026 11:29:50 +0100
- 30 May 20:29:50 [995186] VER binkd/1.1a-115/Linux binkp/1.1
+ 30 May 20:29:51 [995186] addr: 2:263/1@fidonet
[...]
- 30 May 20:29:51 [995186] OPT EXTCMD GZ
+ 30 May 20:29:51 [995186] Remote supports EXTCMD mode
+ 30 May 20:29:51 [995186] Remote supports GZ mode
+ 30 May 20:29:51 [995186] done (to 2:263/1@fidonet, OK, S/R: 0/0 (0/0 bytes)) 30 May 20:29:51 [995186] session closed, quitting...
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,119 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 65:21:33 |
| Calls: | 14,342 |
| Files: | 186,358 |
| D/L today: |
15,029 files (4,942M bytes) |
| Messages: | 2,533,611 |