Subj : Re: exec/load/binkp.js
To   : Accession
From : Deuce
Date : Mon Apr 18 2016 12:00:00

  Re: Re: exec/load/binkp.js
  By: Accession to Deuce on Wed Apr 13 2016 08:06 pm

 > I don't see it with any other systems. But I did indeed have -nr set for
 > those two nodes when I gave you the logs. I have since removed that option
 > from their node line in binkd and am still seeing the same results
 > (including "remote is in NR mode" which I assume is telling me THEY are in
 > NR mode), and with connections still failing with both of them.

"remote is in NR mode" is printed when you get an M_FILE with the offset set to
-1... which indicates the remote is using NR mode for that transfer.  The
reason BinkIT is sending that is because it got an "OPT NR" from your end.

This may be related to the "ND" mode that is also being requested by your end,
but is so poorly documented on ftsc.org that I simply can't possibly implement
it.

Regardless, I just worked with the sysop of Shodan's core and got the NR issue
resolved.

---
 þ Synchronet þ The future of BBSing
 þ wcQWK 7.0 ÷ ILink * Omicron Theta * Southaven MS * winserver.org

--- QScan/PCB v1.20a / 01-0462
 * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1)

.