• Binkit and AKAs

    From Digital Man@1:229/2 to All on Sunday, January 06, 2019 16:43:00
    From: digital.man@vert.synchro.net.remove-d5g-this

    To: poindexter FORTRAN
    Re: Binkit and AKAs
    By: poindexter FORTRAN to All on Sun Jan 06 2019 01:49 pm

    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)

    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.

    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?

    There's 2 different settings for choosing the local AKA to use: one for SBBSecho (packet generation) and the other is for BinkIT (BinkP M_ADR ordering) and they're both in EchoCfg->Linked Nodes.

    digital man

    This Is Spinal Tap quote #36:
    Bobbi Flekman: Money talks, and bullshit walks.
    Norco, CA WX: 56.8øF, 60.0% humidity, 2 mph NNW wind, 0.21 inches rain/24hrs --- Synchronet 3.17b-Win32 NewsLink 1.110
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From poindexter FORTRAN@1:229/2 to All on Sunday, January 06, 2019 14:49:12
    From: poindexter.fortran@REALITY.remove-b2u-this

    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?

    Thanks!

    ---
    þ Synchronet þ realitycheckBBS -- http://realitycheckBBS.org
    --- Synchronet 3.17b-Win32 NewsLink 1.110
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)
  • From poindexter FORTRAN@1:229/2 to All on Sunday, January 06, 2019 23:52:09
    From: poindexter.fortran@REALITY.remove-y4b-this

    To: Digital Man
    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.

    Aha - found it, trying it now.

    ---
    þ Synchronet þ realitycheckBBS -- http://realitycheckBBS.org
    --- Synchronet 3.17c-Win32 NewsLink 1.110
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net

    --- SoupGate-Win32 v1.05
    * Origin: www.darkrealms.ca (1:229/2)