Subj : Problem with Binkley
To : Bob Ackley
From : Andrew Leary
Date : Sun Oct 24 2010 11:14 pm
Hello Bob!
Sunday October 24 2010 17:42, Bob Ackley wrote to Sean Dennis:
BA> I wonder why Binkley was saying 'Nothing to send to 618:150/0'. it
BA> sounds to me like the other end said 'send traffic for 618:150/0' and
BA> Binkley reported there wasn't any. Some traffic has been moving, the
BA> backlogged packets are gone.
I believe that the adding the domain to your micronet address in BINKLEY.CFG is
what fixed it. Binkley is more forgiving about such things than Xenia is,
apparently. I still haven't figured out why Binkley wasn't able to drop DTR to
hang up, when every other piece of software on the machine has been able to do
so with no problem. That includes Xenia/2, FrontDoor/2, ZapOCom, etc. It's
got to be some oddity with the serial ports built into the Intel L440GX
motherboard in the server that's running the BBS currently. I did find an old
ISA dual 16550AFN serial port card; sometime I'll try installing that and
disabling the onboard serial ports.
SD>> You really should double-check your Squish configuration. I'm
SD>> 99% sure that's where the problem lies and not with Binkley.
BA> Watergate's ROUTE.CFG simply says to route all 618:* traffic to
BA> 618:150/1. Watergate's user configuration has 618:150/1 subscribed to
BA> all the MIN_* echoes; 150/0 isn't subscribed to anything.
BA> Everything was working just fine until about six week or so ago. I
BA> didn't change anything here (I have in the past week or so). I added
BA> the PickUpAll to Binkley, and added a password for 618:150/0 in the
BA> password file for FASTLIST, then forced a recompile of my nodelist.
BA> Andrew's system was reporting a password mismatch - according to the
BA> log he sent me it looked like no password was being received, although
BA> the password has been in that file (for 618:150/1) since I joined
BA> Micronet.
Six weeks ago is when I switched from BinkleyTerm-XE to Xenia/2, due to the DTR
drop issue noted above. I may go back to Binkley if I can resolve that issue
by swapping to the add on serial card/disabling the onboard ports.
I think that the password issue was caused when you copied the .FLO file for
150/1 to 150/0, since you didn't have 150/0 setup with the password. Your
system would try dialing 150/0 and not send the password, and then try 150/1
with the password. I believe the domain issue is why Xenia & Binkley didn't
agree that the mail should be sent.
