The first node was attempted using the "address method" of trying to

connec

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"?

I have the "@micronet" for that node.

It would appear that the nodes that used the binkphost setting instead do
not have the domain included on their entries. I took it off due to the
issue I was having with tickit.

---
þ SLMR 2.1a þ Spelling is a sober man's game
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: binkit address selection
By: Dumas Walker to DIGITAL MAN on Sun Aug 19 2018 08:00 am

The first node was attempted using the "address method" of trying to connec
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"?

I have the "@micronet" for that node.

It would appear that the nodes that used the binkphost setting instead do not have the domain included on their entries. I took it off due to the issue I was having with tickit.

So if you remove the "@micronet" it works as expected?

What you called the "net/node method" is actually the "DNS method", so if you need more help (e.g. from deuce in irc.synchro.net), you know know what to call it. :-)

digital man

Synchronet "Real Fact" #93:
Synchronet v3.16c was released in August of 2015 (5 years after v3.15b).
Norco, CA WX: 89.5øF, 48.0% humidity, 2 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.06-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

I have the "@micronet" for that node.

It would appear that the nodes that used the binkphost setting instead do not have the domain included on their entries. I took it off due to the issue I was having with tickit.

So if you remove the "@micronet" it works as expected?

I am not sure about that. It appears to happen with nodes that have a flo waiting, but maybe only the ones with a flo and a domain.

Actually, the node in question had been able to poll here for mail until sometime this weekend. I did not change anything in the sbbsecho.ini file,
and he apparently did not change anything on his end either (he is running binkp/d) but now he is getting CRAM-MD5 and/or bad password errors. His password is the same as it always has been on this end.

I tried updating exec earlier today... got a newer version of binkit.js but
it still did not help.

Ironically, he has made an actual connection or two that was successful
amid more failures than I can count.

Does binkit log its activity anywhere? I have checked /data/logs and only
see sbbs activity.

I removed his node entirely from sbbsecho.ini, so I would assume that
binkit should have no expectation about any passwords, yet here is what I
see in the console from just now:

8/19 19:23:24 srvc 0066 BinkIT connection accepted from: 107.181.135.102
port 34712
8/19 19:23:24 srvc 0066 BinkIT BinkIT/2.7 invoked with options:
8/19 19:23:24 srvc 0066 BinkIT JSBinkP/1.109 inbound connection from 107.181.135.102:34712
8/19 19:23:24 srvc 0066 BinkIT Peer version: binkd/1.0.4/Linux binkp/1.1
8/19 19:23:24 srvc 0066 BinkIT Will encrypt session.
8/19 19:23:24 srvc 0066 BinkIT Inbound session for: 618:250/19@micronet
8/19 19:23:24 srvc 0066 BinkIT CRAM-MD5 password mismatch for 618:250/19@micronet (expected: CRAM-MD5-aa34d00b811cf18992adf16b27a08311, received: CRAM-MD5-ccbd2e010e2e2b3875fc438b2c37fa2b)
8/19 19:23:24 srvc 0066 BinkIT Sending M_ERR command args: Password mismatch 8/19 19:23:24 srvc 0066 BinkIT service thread terminated (0 clients remain,
0 total, 224 served)

So how does binkit know what to "expect" when sbbsecho.ini has the entry removed?

What you called the "net/node method" is actually the "DNS method", so if you need more help (e.g. from deuce in irc.synchro.net), you know know what to

cal

it. :-)

Thanks! I will remember that.

---
þ SLMR 2.1a þ Does anybody here remember Vera Lynn?
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: binkit address selection
By: Digital Man to Dumas Walker on Sun Aug 19 2018 13:04:36

What you called the "net/node method" is actually the "DNS method", so if yo need more help (e.g. from deuce in irc.synchro.net), you know know what to c it. :-)

I left a message in there. It said umpteen people were in there, including deuce, but I don't think any of them were really there. Also, the instructions are so long and scroll by so fast it was very frustrating for a first time user to figure out what is going on or how to use it.

I left my email addy.

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

> > It would appear that the nodes that used the binkphost setting instead do

not have the domain included on their entries. I took it off due to the issue I was having with tickit.

So if you remove the "@micronet" it works as expected?

What you called the "net/node method" is actually the "DNS method", so if you need more help (e.g. from deuce in irc.synchro.net), you know know what to call it. :-)

I happened to scroll to the very bottom of my sbbsecho.ini file and found the culprit for both issues. I have sometimes notices that one of the utility pgms (not sure if it is tickit or sbbsecho's areafix functions or what) will alter the sbbsecho.ini file.

In this case, I had one entry that I had added for 618:250/19@micronet that had all of the pertinent information filled in. Some other process had added an entry at the bottom of sbbsecho.ini (below all the echolist and domain entries) that contained only the following two lines:

[node:618:250/19]
Name = Nigel Reed

And that was it. I deleted those two lines and binkit is now using the correct entry instead of the rogue one.

Now my outbound calls use the binkphost entry instead of the DNS lookup, and his inbound calls are no longer giving the false "incorrect password" errors.

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

Re: binkit address selection
By: Dumas Walker to DIGITAL MAN on Sun Aug 19 2018 07:28 pm

I have the "@micronet" for that node.

It would appear that the nodes that used the binkphost setting instead do not have the domain included on their entries. I took it off due to the issue I was having with tickit.

So if you remove the "@micronet" it works as expected?

I am not sure about that. It appears to happen with nodes that have a flo waiting, but maybe only the ones with a flo and a domain.

Actually, the node in question had been able to poll here for mail until sometime this weekend. I did not change anything in the sbbsecho.ini file, and he apparently did not change anything on his end either (he is running binkp/d) but now he is getting CRAM-MD5 and/or bad password errors. His password is the same as it always has been on this end.

Something changed. :-)

I tried updating exec earlier today... got a newer version of binkit.js but it still did not help.

Ironically, he has made an actual connection or two that was successful
amid more failures than I can count.

Does binkit log its activity anywhere? I have checked /data/logs and only see sbbs activity.

For outgoing connections, the BinkIt log output goes wherever you have timed event log output going. On Windows, by default, that's just your sbbsctrl->Events window.

For incoming connections, the BinkIt log output goes wherever you have services log output going (e.g. sbbsctrl->Services).

I removed his node entirely from sbbsecho.ini, so I would assume that
binkit should have no expectation about any passwords, yet here is what I see in the console from just now:

8/19 19:23:24 srvc 0066 BinkIT connection accepted from: 107.181.135.102 port 34712
8/19 19:23:24 srvc 0066 BinkIT BinkIT/2.7 invoked with options:
8/19 19:23:24 srvc 0066 BinkIT JSBinkP/1.109 inbound connection from 107.181.135.102:34712
8/19 19:23:24 srvc 0066 BinkIT Peer version: binkd/1.0.4/Linux binkp/1.1 8/19 19:23:24 srvc 0066 BinkIT Will encrypt session.
8/19 19:23:24 srvc 0066 BinkIT Inbound session for: 618:250/19@micronet
8/19 19:23:24 srvc 0066 BinkIT CRAM-MD5 password mismatch for 618:250/19@micronet (expected: CRAM-MD5-aa34d00b811cf18992adf16b27a08311, received: CRAM-MD5-ccbd2e010e2e2b3875fc438b2c37fa2b)
8/19 19:23:24 srvc 0066 BinkIT Sending M_ERR command args: Password mismatch 8/19 19:23:24 srvc 0066 BinkIT service thread terminated (0 clients remain, 0 total, 224 served)

So how does binkit know what to "expect" when sbbsecho.ini has the entry removed?

Most likely he sent a password and the expected match was against a "blank" password - which is CRAM-MD5 computed as just '-' (per the binkP spec).

digital man

This Is Spinal Tap quote #27:
As long as there's, y'know, sex and drugs, I can do without the rock and roll. Norco, CA WX: 88.4øF, 51.0% humidity, 4 mph N wind, 0.00 inches rain/24hrs
--- SBBSecho 3.06-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: binkit address selection
By: Dumas Walker to Digital Man on Sun Aug 19 2018 07:43 pm

Re: binkit address selection
By: Digital Man to Dumas Walker on Sun Aug 19 2018 13:04:36

What you called the "net/node method" is actually the "DNS method", so if yo need more help (e.g. from deuce in irc.synchro.net), you know know what to c it. :-)

I left a message in there. It said umpteen people were in there, including deuce, but I don't think any of them were really there. Also, the instructions are so long and scroll by so fast it was very frustrating for a first time user to figure out what is going on or how to use it.

Many people (including myself) keep an IRC client open most/all of the time and check it periodically for interesting/directed discussion.

I left my email addy.

Hopefully Deuce sees it, but normally you would hang-out and wait for a reply and discussion.

digital man

Synchronet "Real Fact" #62:
Name of Synchronet PCMS compiler/language "Baja" was coined by Michael Swindell.
Norco, CA WX: 88.4øF, 51.0% humidity, 4 mph N wind, 0.00 inches rain/24hrs
--- SBBSecho 3.06-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)