Subj : hpt + binkd direct messages to different zone
To   : Javier Sturman
From : Tommi Koivula
Date : Fri Sep 26 2025 10:08 am

Javier Sturman wrote:

JS> 25 Sep 25 09:04, I wrote to you:
JS>
JS> I kept troubleshooting and I found that the binkd process was not
JS> getting properly shutdown. After starting it cleanly I see on the
JS> error log many outgoind connections but with undesired netowrks and
JS> zones combination.

....

JS> f360.n221.z2.binkp.net:24554 [51.38.115.207]

....

JS> 26 Sep 00:05:25 [72511] ZYZ Tommi Koivula
JS> 26 Sep 00:05:25 [72511] LOC EU
JS> 26 Sep 00:05:25 [72511] NDL CM,IBN
JS> 26 Sep 00:05:25 [72511] TIME Fri, 26 Sep 2025 06:05:25 +0300
JS> 26 Sep 00:05:25 [72511] VER binkd/1.1a-115/Linux binkp/1.1
JS> 26 Sep 00:05:25 [72511] addr: 2:221/6@fidonet
JS> 26 Sep 00:05:25 [72511] called 2:221/360@fidonet, but remote has no
JS> such AKA 26 Sep 00:05:25 [72511] done (to 2:221/360@fidonet,
JS> failed, S/R: 0/0 (0/0 bytes))
JS> 26 Sep 00:05:25 [72511] session closed, quitting...
JS> 26 Sep 00:05:25 [72510] rc(72511)=0

Now your binkd here is using the standard binkp port instead of what is
in the nodelist and in the binkp.net dns srv record. :(

I've seen this happening in windows...

JS>  JS> 1 09:01:57  Scanning NetmailArea NETMAIL
JS>  JS> 7 09:01:57  Msg packed with flavour 'direct': 4:900/733 ->
JS>  JS> 2:221/1.58 1 09:01:57  End
JS>  JS> -+-

Routing direct for points not your own might not be the best idea. ;)

How about "route crash boss ..."

'Tommi

--- FastEcho/2 1.46.1 Revival
 * Origin: nntp://rbb.fidonet.fi - Finland (2:221/360.0)

.