Subj : Re: Update on my setup
To   : Sean Rima
From : Wilfred van Velzen
Date : Fri Jul 03 2026 05:08 pm

Hi Sean,

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

 SR>>>> Not sure what I did, but it should be working again. Oddly some
 >>> nodes
 SR>>>> were connecting
 Wv>>
 WvV>>> Right now IPv4 is still not working for me:
 Wv>>
 WvV>>> 2026-07-03 12:56:27.590 Calling 2:263/1
 WvV>>> 2026-07-03 12:56:27.590  bbs.rima-iot.eu:24554
 WvV>>> 2026-07-03 12:56:27.590
 >>> (2a06:5900:8194:100:acb:a059:6e85:1ded:24554
 Wv>> )
 WvV>>> 2026-07-03 12:56:27.590  OPT
 >>> CRAM-MD5-724c94369ee346dd789aa68607f9ceed
 WvV>>> 2026-07-03 12:56:27.590  SYS There Can Only Be 1
 WvV>>> 2026-07-03 12:56:27.590  ZYZ Sean Rima
 WvV>>> ...
 WvV>>> 2026-07-03 12:56:27.590   2a06:5900:8194:100:acb:a059:6e85:1ded -
 >>> Ok.
 WvV>>> 2026-07-03 12:56:27.590 Session with 2:263/1 done.
 WvV>>> 2026-07-03 12:56:27.590      (51.182.63.136:24554)
 WvV>>> 2026-07-03 12:56:27.590   51.182.63.136 - Error: Connection timed
 >>> out
 Wv>>
 Wv>> And just now it is working:
 Wv>>

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

.