I've got a downlink, 1:102/401, who's getting a password error. He says that I'm matching one of my Fido AKAs to him, not my primary AKA which we have a password set for.
I tried overriding the local address in echocfg to 1:218/700, but when I try polling using jsexec binkit -l (his node number) it shows me presenting my AKAs, and not in the order listed in scfg (1:218/700 is my primary AKA)
Sending M_ADR command args: 1:143/1@fidonet 1:143/0@fidonet 1:10/1@fidonet 1:10/ 0@fidonet 1:1/1@fidonet 1:218/700@fidonet 1:218/1@fidonet 1:218/0@fidonet 46:1/115@agoranet 21:4/122@fsxnet 618:300/16@micronet 618:300/1@micronet 700:100/20@spooknet 9:91/4@survnet
The help file mentions something about trying to choose a local address that best matches the net and node number, it looks like it's doing that. He's matching on 143/1.
Any clues as to why specifying a local AKA isn't working?
Re: Binkit and AKAs
By: poindexter FORTRAN to All on Sun Jan 06 2019 01:49 pm
The "Local Address" setting in echocfg is for packet generation by SBBSecho. I think what you're looking for is the "Source Address" under the BinkP Settings for the linked node.
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 31 |
Nodes: | 8 (0 / 8) |
Uptime: | 88:29:37 |
Calls: | 2,069 |
Calls today: | 2 |
Files: | 11,134 |
Messages: | 946,759 |