A couple of examples from a recent call-out:

8/18 08:59:04 evnt BINKIT JSBinkP/1.106 callout to 618:250/19@micronet started 8/18 08:59:04 evnt BINKIT Connection to f19.n250.z618.example.com:24554 failed. 8/18 08:59:04 evnt BINKIT Attempting callout for 618:250/17@micronet, file: /sbbs/fido/out.26a/00fa0011.flo
[...]
8/18 08:59:25 evnt BINKIT Attempting poll for node 21:1/10@fsxnet
8/18 08:59:25 evnt BINKIT JSBinkP/1.106 callout to 21:1/10@fsxnet started
8/18 08:59:26 evnt BINKIT Peer version: binkd/1.1a-89/Win32 binkp/1.1
8/18 08:59:27 evnt BINKIT Will encrypt session.
8/18 08:59:27 evnt BINKIT Authentication successful: secure
[...]

The first node was attempted using the "address method" of trying to connect rather than using the binkphost listed in sbbsecho.ini. I had noticed this happening in the past and thought that binkit would always make a second attempt during the session using the binkphost. However, this morning I noticed that it did not. For some reason, it chose to attempt to use the net/node to resolve about half the nodes (even though all have binkphost entries) and used the binkphost entries for the other half.

Seeing as how most of my othernet connections are not supported by the net/node method, I would prefer it not do this. :)

It appears that it uses the net/node method whenever there is mail waiting here to go out (i.e. it finds a flo file). The node above that it made a proper connection with, 21:1/10, did not have a flo waiting, so it used the address in the ini file.

In the ini file both nodes appear to have similar settings... status, binkpoll, etc.

---
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: binkit address selection issue
By: Dumas Walker to All on Sat Aug 18 2018 09:12 am

A couple of examples from a recent call-out:

8/18 08:59:04 evnt BINKIT JSBinkP/1.106 callout to 618:250/19@micronet started 8/18 08:59:04 evnt BINKIT Connection to f19.n250.z618.example.com:24554 failed. 8/18 08:59:04 evnt BINKIT Attempting callout for 618:250/17@micronet, file: /sbbs/fido/out.26a/00fa0011.flo

The first node was attempted using the "address method" of trying to connect rather than using the binkphost listed in sbbsecho.ini.

Do you actually have "618:250/19@micronet" in your sbbsecho.ini, or just "618:250/19"?

digital man

This Is Spinal Tap quote #29:
I find lost luggage. I locate mandolin strings in the middle of Austin!
Norco, CA WX: 89.7øF, 43.0% humidity, 9 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.06-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)