Subj : Problem with Binkley
To : Sean Dennis
From : Bob Ackley
Date : Sun Oct 24 2010 05:42 pm
Replying to a message of Sean Dennis to Bob Ackley:
SD> Hi, Bob-
BA>> Note that my system dials 150/1 (150/0 is the same number) and
BA>> connects just fine. But it still logs a message that there's no
BA>> traffic for 150/0. Note that I'd copied the 00960001.FLO file to
BA>> 00960000.FLO, so the two FLO files (150/0 and 150/1) both pointed to
BA>> the same set of packets - and during a successful connect the
BA>> packets don't get sent. Traffic from 150/1 to me is flowing just
BA>> fine. I did netmail Andrew about the problem (thru Fidonet) but he
BA>> hasn't responded yet.
SD> That sounds like you have Squish misconfigured either in the area
SD> declaration block in SQUISH.CFG or ROUTE.CFG is messed up.
I don't use Squish excpet to clean up database problems. I haven't changed
Watergate's configuration for years.
SD> The reason why mail to 150/0 doesn't get sent is because Andrew
SD> doesn't "fly" 150/0; I've instructed all of my hubs to NOT fly that
SD> flag because my system doesn't use it. There's no need in such a
SD> small network to use the regional addresses.
I wonder why Binkley was saying 'Nothing to send to 618:150/0'. it sounds
to me like the other end said 'send traffic for 618:150/0' and Binkley reported
there wasn't any. Some traffic has been moving, the backlogged packets are
gone.
SD> You really should double-check your Squish configuration. I'm 99%
SD> sure that's where the problem lies and not with Binkley.
Watergate's ROUTE.CFG simply says to route all 618:* traffic to 618:150/1.
Watergate's user configuration has 618:150/1 subscribed to all the MIN_*
echoes; 150/0 isn't subscribed to anything.
Everything was working just fine until about six week or so ago. I didn't
change anything here (I have in the past week or so). I added the PickUpAll
to Binkley, and added a password for 618:150/0 in the password file for
FASTLIST, then forced a recompile of my nodelist. Andrew's system was
reporting a password mismatch - according to the log he sent me it looked
like no password was being received, although the password has been in that
file (for 618:150/1) since I joined Micronet.