• Update on my setup

    From Sean Rima@2:263/1 to All on Thu Jul 2 12:56:18 2026
    OK, I reset the providers router and that seems to have fixed the changing the firewall so ipv6 inbound is working. I went back to BBBS and it doens't currently do ipv6 outbound calls. Asked in the BBBS.ENGLISH eccho about it

    Sean


    ... Pets were put on Earth to show that unconditional love is real

    --- BBBS/LiR v4.10 Toy-7
    * Origin: TCOB1 https://binkd.rima.ie (2:263/1)
  • From Tommi Koivula@2:221/1 to Sean Rima on Thu Jul 2 19:29:30 2026
    Hi Sean.

    02 Jul 26 12:56, you wrote to All:

    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.


    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)
    OPT CRAM-MD5-acd1da250883d766bfbd4527a72a7b02
    SYS There Can Only Be 1
    ZYZ Sean Rima
    LOC Letterfrack, Ireland
    VER BBBS/LiR v4.10 Toy-7 binkp/1.0
    NDL XX
    address: 2:263/1.0@fidonet
    address: 618:500/1.0@micronet
    address: 21:1/229.0@fsxnet
    address: 314:413/30.0@pinet
    address: 999:1/10.0@health
    address: 86:553/20.0@nixnet
    address: 46:20/119.0@agoranet
    address: 25:41/123.0@metronet
    address: 618:510/1.0@micronet
    address: 618:500/14.0@micronet
    address: 618:14/0.0@micronet
    address: 618:500/0.0@micronet
    address: 2:263/0.0@fidonet
    address: 618:50/0.0@micronet
    address: 618:50/1.0@micronet
    2a06:5900:8194:100:acb:a059:6e85:1ded - Ok.
    Session with 2:263/1 done.
    Calling 2:263/1 (51.182.63.136:24554)
    error (Connection timed out)


    'Tommi

    --- GoldED+/LNX 1.1.5-b20260304
    * Origin: nntps://news.fidonet.fi (2:221/1)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Thu Jul 2 18:53:23 2026
    Hi Tommi,

    On 2026-07-02 19:29:30, you wrote to Sean Rima:

    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)


    Bye, Wilfred.

    --- FMail-lnx64 2.3.4.1-B20260520
    * Origin: FMail development HQ (2:280/464)
  • From Sean Rima@2:263/1 to Tommi Koivula on Fri Jul 3 11:42:02 2026
    Tommi Koivula wrote to Sean Rima <=-

    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.


    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)

    odd, it works for others :

    260703 11:31 Got raw:24554 from 109.204.184.25:40995, spawning node 20.
    260703 11:31 Closing raw at node 20, 2079 bytes in, 503 bytes out.
    260703 11:31 Got raw:24554 from 92.241.109.98:47436, spawning node 21.
    260703 11:31 Closing raw at node 21, 292 bytes in, 472 bytes out.
    260703 11:31 Got raw:24554 from 153.100.180.21:59117, spawning node 3.
    260703 11:31 Closing raw at node 3, 845 bytes in, 472 bytes out.

    I did take BBBS node 1 down for a short time, I wonder was that when I did it when you called

    Sean


    ... Pets were put on Earth to show that unconditional love is real

    --- BBBS/LiR v4.10 Toy-7
    * Origin: TCOB1 https://binkd.rima.ie (2:263/1)
  • From Sean Rima@2:263/1 to Wilfred Van Velzen on Fri Jul 3 11:42:02 2026
    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)

    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

    Sean


    ... Connemara Weather https://connemaraweather.eu

    --- BBBS/LiR v4.10 Toy-7
    * Origin: TCOB1 https://binkd.rima.ie (2:263/1)
  • From Wilfred van Velzen@2:280/464 to Sean Rima on Fri Jul 3 12:57:07 2026
    Hi Sean,

    On 2026-07-03 11:42:02, you wrote to me:

    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

    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


    Bye, Wilfred.

    --- FMail-lnx64 2.3.4.1-B20260520
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/1 to Sean Rima on Fri Jul 3 13:58:54 2026
    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)

    :(

    'Tommi

    ---
    * Origin: nntps://news.fidonet.fi (2:221/1)
  • From Wilfred van Velzen@2:280/464 to Sean Rima on Fri Jul 3 13:07:53 2026
    Hi Sean,

    On 2026-07-03 12:57:07, I wrote to you:

    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:

    Calling '2:263/1'. Call time: '0000-2400' UTC.
    Now is: 1107 UTC.
    bbs.rima-iot.eu, 24554
    Calling 2:263/1 (2a06:5900:8194:100:acb:a059:6e85:1ded:24554)
    OPT CRAM-MD5-54d871c8703fff1e029ddcf230f4554a
    SYS There Can Only Be 1
    ZYZ Sean Rima
    LOC Letterfrack, Ireland
    VER BBBS/LiR v4.10 Toy-7 binkp/1.0
    NDL XX
    address: 2:263/1.0@fidonet
    ...
    2a06:5900:8194:100:acb:a059:6e85:1ded - Ok.
    Session with 2:263/1 done.
    Calling 2:263/1 (51.182.63.136:24554)
    OPT CRAM-MD5-54d871c8703fff1e029ddcf230f4554a
    SYS There Can Only Be 1
    ZYZ Sean Rima
    LOC Letterfrack, Ireland
    VER BBBS/LiR v4.10 Toy-7 binkp/1.0
    NDL XX
    address: 2:263/1.0@fidonet
    ...
    51.182.63.136 - Ok.
    Session with 2:263/1 done.


    Bye, Wilfred.

    --- FMail-lnx64 2.3.4.1-B20260520
    * Origin: FMail development HQ (2:280/464)
  • From Sean Rima@2:263/1 to Wilfred Van Velzen on Fri Jul 3 12:39:20 2026
    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�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

    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

    telnet bbs.rima-iot.eu 24554
    Trying 51.182.63.136...
    Connected to bbs.rima-iot.eu.
    Escape character is '^]'.
    �.OPT CRAM-MD5-dd5595a335e47904dd4472c8076488b3�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 is wrong

    Sean

    ... TCOB1: binkd.rima.ie or bbbs.rima-iot.eu

    --- BBBS/LiR v4.10 Toy-7
    * Origin: TCOB1 https://binkd.rima.ie (2:263/1)
  • From Sean Rima@2:263/1 to Tommi Koivula on Fri Jul 3 12:39:20 2026
    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)

    :(

    I am beginning to hate networks :)

    Sean

    ... TCOB1: binkd.rima.ie or bbbs.rima-iot.eu

    --- BBBS/LiR v4.10 Toy-7
    * Origin: TCOB1 https://binkd.rima.ie (2:263/1)
  • From Wilfred van Velzen@2:280/464 to Sean Rima on Fri Jul 3 17:08:31 2026
    Hi Sean,

    On 2026-07-03 12:39:20, you wrote to me:

    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 :)

    It seems so, because now it's not:

    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...


    Bye, Wilfred.

    --- FMail-lnx64 2.3.4.1-B20260520
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/1.1 to Sean Rima on Fri Jul 3 20:00:04 2026
    Hi Sean.

    03 Jul 26 17:08:31, Wilfred van Velzen wrote to you:

    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)

    'Tommi

    --- FMail-W64 2.3.4.1-B20260521
    * Origin: IPv6 Point One (2:221/1.1)
  • From Jay Harris@1:229/664 to Sean Rima on Fri Jul 3 14:28:48 2026
    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!


    Jay

    ... What do call a criminal landing an airplane? Condescending

    --- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
    * Origin: Northern Realms (1:229/664)
  • From Tommi Koivula@2:221/1 to Jay Harris on Fri Jul 3 21:48:20 2026
    On 03.07.2026 21.28, Jay Harris wrote:

    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!

    And now:

    $ 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!

    $ nc -zv -4 binkd.rima.ie 24554
    nc: connect to binkd.rima.ie (51.182.63.136) port 24554 (tcp) failed: No route to host

    'Tommi

    ---
    * Origin: news://news.fidonet.fi (2:221/1.0)
  • From Sean Rima@2:263/1 to Tommi Koivula on Fri Jul 3 21:36:38 2026
    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)

    What I have done is remove port triggering and port forewarding, rebooted the router and added 24554/23/80/443 for the bbbs machine. went to a remote pc on a different network and can connect to all

    The issue is finding the right Pi, it just lists them as Raspberry Pi, no mac address etc, so hard to find when I have about 12 :)

    Sean


    ... Connemara Weather https://connemaraweather.eu

    --- BBBS/LiR v4.10 Toy-7
    * Origin: TCOB1 https://binkd.rima.ie (2:263/1)
  • From Sean Rima@2:263/1 to Jay Harris on Fri Jul 3 21:36:38 2026
    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.

    I am waiting on a new router so I can replace the provider issued one. I did cancel my first order of a Ubiquiti one and waiting on a Omada one as most of my network is Omada based. Will need a poe switch as well capable of up to 10gbe


    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!


    I keep forgetting that command. The remote network I can connect to isn't using ipv6, must fix that

    Sean


    ... TCOB1: binkd.rima.ie or bbbs.rima-iot.eu

    --- BBBS/LiR v4.10 Toy-7
    * Origin: TCOB1 https://binkd.rima.ie (2:263/1)