OK, I reset the providers router and that seems to have fixed the changing the
firewall so ipv6 inbound is working.
OK, I reset the providers router and that seems to have fixed the
changing the firewall so ipv6 inbound is working.
Ipv6 seems ok now, but ipv4 is not.
Calling 2:263/1 (51.182.63.136:24554)
error (Connection timed out)
Tommi Koivula wrote to Sean Rima <=-
OK, I reset the providers router and that seems to have fixed the
changingthe
firewall so ipv6 inbound is working.
Ipv6 seems ok now, but ipv4 is not.
Nodelist for Thursday, July 2, 2026 -- Day number 183 parsed, 962
IP-nodes processed (0.018 sec)
Calling '2:263/1'. Call time: '0000-2400' UTC.
Now is: 1627 UTC.
bbs.rima-iot.eu, 24554
Calling 2:263/1 (2a06:5900:8194:100:acb:a059:6e85:1ded:24554)
Session with 2:263/1 done.
Calling 2:263/1 (51.182.63.136:24554)
error (Connection timed out)
Wilfred van Velzen wrote to Tommi Koivula <=-
OK, I reset the providers router and that seems to have fixed the
changing the firewall so ipv6 inbound is working.
Ipv6 seems ok now, but ipv4 is not.
Calling 2:263/1 (51.182.63.136:24554)
error (Connection timed out)
Same here:
Calling 2:263/1 (51.182.63.136:24554)
error (Connection timed out)
OK, I reset the providers router and that seems to have fixed the
changing the firewall so ipv6 inbound is working.
Ipv6 seems ok now, but ipv4 is not.
Calling 2:263/1 (51.182.63.136:24554)
error (Connection timed out)
Same here:
Calling 2:263/1 (51.182.63.136:24554)
error (Connection timed out)
darn and blast it.
telnet binkd.rima.ie 24554 -4
Trying 51.182.63.136...
telnet: Unable to connect to remote host: Connection refused pi@raspbx:~ $ telnet binkd.rima.ie 24554 -4 Trying 51.182.63.136... Connected to binkd.rima.ie. Escape character is '^]'. �.OPT CRAM-MD5-c8cb4353958b7706cae778b7fea3de7f�SYS There Can Only Be 1�ZYZ Sean
Rima�LOC Letterfrack, Ireland�#VER BBBS/LiR v4.10 Toy-7 binkp/1.0�NDL
XX�-2:263/1.0@fidonet 618:500/1.0@micronet 21:1/229.0@fsxnet 314:413/30.0@pinet 999:1/10.0@health 86:553/20.0@nixnet 46:20/119.0@agoranet 25:41/123.0@metronet 618:510/1.0@micronet 618:500/14.0@micronet
618:14/0.0@micronet 618:500/0.0@micronet 2:263/0.0@fidonet 618:50/0.0@micronet
618:50/1.0@micronet
Not sure what I did, but it should be working again. Oddly some nodes were connecting
Ipv6 seems ok now, but ipv4 is not.
Calling 2:263/1 (51.182.63.136:24554)
error (Connection timed out)
Same here:
Calling 2:263/1 (51.182.63.136:24554)
error (Connection timed out)
darn and blast it.
Not sure what I did, but it should be working again. Oddly some nodes
were connecting
Right now IPv4 is still not working for me:
2026-07-03 12:56:27.590 Calling 2:263/1
2026-07-03 12:56:27.590 bbs.rima-iot.eu:24554
2026-07-03 12:56:27.590 (2a06:5900:8194:100:acb:a059:6e85:1ded:24554)
2026-07-03 12:56:27.590 OPT CRAM-MD5-724c94369ee346dd789aa68607f9ceed 2026-07-03 12:56:27.590 SYS There Can Only Be 1
2026-07-03 12:56:27.590 ZYZ Sean Rima
...
2026-07-03 12:56:27.590 2a06:5900:8194:100:acb:a059:6e85:1ded - Ok. 2026-07-03 12:56:27.590 Session with 2:263/1 done.
2026-07-03 12:56:27.590 (51.182.63.136:24554)
2026-07-03 12:56:27.590 51.182.63.136 - Error: Connection timed out
Wilfred van Velzen wrote to Sean Rima <=-
Trying 51.182.63.136...
telnet: Unable to connect to remote host: Connection refused
pi@raspbx:~ $
telnet binkd.rima.ie 24554 -4 Trying 51.182.63.136... Connected to
binkd.rima.ie. Escape character is '^]'. �.OPT
CRAM-MD5-c8cb4353958b7706cae778b7fea3de7f�SYS There Can Only Be
1�ZYZSean
Rima�LOC Letterfrack, Ireland�#VER BBBS/LiR v4.10 Toy-7binkp/1.0�NDL
XX�-2:263/1.0@fidonet 618:500/1.0@micronet 21:1/229.0@fsxnet618:50/0.0@micronet
314:413/30.0@pinet 999:1/10.0@health 86:553/20.0@nixnet
46:20/119.0@agoranet 25:41/123.0@metronet 618:510/1.0@micronet
618:500/14.0@micronet
618:14/0.0@micronet 618:500/0.0@micronet 2:263/0.0@fidonet
618:50/1.0@micronet
Not sure what I did, but it should be working again. Oddly some
nodes were
connecting
Right now IPv4 is still not working for me:
2026-07-03 12:56:27.590 Calling 2:263/1
2026-07-03 12:56:27.590 bbs.rima-iot.eu:24554
Tommi Koivula wrote to Sean Rima <=-
Hi Sean.
03 Jul 26 11:42, you wrote to Wilfred Van Velzen:
Ipv6 seems ok now, but ipv4 is not.
Calling 2:263/1 (51.182.63.136:24554)
error (Connection timed out)
Same here:
Calling 2:263/1 (51.182.63.136:24554)
error (Connection timed out)
darn and blast it.
Calling 2:263/1 (51.182.63.136:24554)
error (Connection timed out)
:(
Not sure what I did, but it should be working again. Oddly some
nodes
were connecting
Right now IPv4 is still not working for me:
2026-07-03 12:56:27.590 Calling 2:263/1
2026-07-03 12:56:27.590 bbs.rima-iot.eu:24554
2026-07-03 12:56:27.590
(2a06:5900:8194:100:acb:a059:6e85:1ded:24554
)
2026-07-03 12:56:27.590 OPT
CRAM-MD5-724c94369ee346dd789aa68607f9ceed
2026-07-03 12:56:27.590 SYS There Can Only Be 1
2026-07-03 12:56:27.590 ZYZ Sean Rima
...
2026-07-03 12:56:27.590 2a06:5900:8194:100:acb:a059:6e85:1ded -
Ok.
2026-07-03 12:56:27.590 Session with 2:263/1 done.
2026-07-03 12:56:27.590 (51.182.63.136:24554)
2026-07-03 12:56:27.590 51.182.63.136 - Error: Connection timed
out
And just now it is working:
It is being a pain. Murphy is playing games with me :)
Calling 2:263/1 (51.182.63.136:24554)
error (No route to host)
Different error though. This one is almost immediate, not a timeout...
I am beginning to hate networks :)
For what it's worth, both IPv4 & 6 are working from here at the moment:
$ nslookup binkd.rima.ie
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: binkd.rima.ie
Address: 51.182.63.136
Name: binkd.rima.ie
Address: 2a06:5900:8194:100:acb:a059:6e85:1ded
$ nc -zv -4 binkd.rima.ie 24554
Connection to binkd.rima.ie (51.182.63.136) 24554 port [tcp/binkp]
succeeded!
$ nc -zv -6 binkd.rima.ie 24554
Connection to binkd.rima.ie (2a06:5900:8194:100:acb:a059:6e85:1ded)
24554 port [tcp/binkp] succeeded!
Tommi Koivula wrote to Sean Rima <=-
Calling 2:263/1 (51.182.63.136:24554)
error (No route to host)
Different error though. This one is almost immediate, not a
timeout...
Yep, the same here now.
Calling 2:263/1 (51.182.63.136:24554)
error (No route to host)
Jay Harris wrote to Sean Rima <=-
On 03 Jul 2026, Sean Rima said the following...
I am beginning to hate networks :)
I hear ya, they can be very temperamental at times.
For what it's worth, both IPv4 & 6 are working from here at the moment:
$ nslookup binkd.rima.ie
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: binkd.rima.ie
Address: 51.182.63.136
Name: binkd.rima.ie
Address: 2a06:5900:8194:100:acb:a059:6e85:1ded
$ nc -zv -4 binkd.rima.ie 24554
Connection to binkd.rima.ie (51.182.63.136) 24554 port [tcp/binkp] succeeded!
$ nc -zv -6 binkd.rima.ie 24554
Connection to binkd.rima.ie (2a06:5900:8194:100:acb:a059:6e85:1ded)
24554 port [tcp/binkp] succeeded!
| Sysop: | Eric Oulashin |
|---|---|
| Location: | Beaverton, Oregon, USA |
| Users: | 104 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 04:39:30 |
| Calls: | 8,697 |
| Calls today: | 1 |
| Files: | 9,527 |
| D/L today: |
2,042 files (791M bytes) |
| Messages: | 418,428 |
| Posted today: | 3 |