• Binkit v2 and connecting to Mystic BBS Hub

    From Keith Matthews@3:712/620 to All on Sun Apr 1 11:38:02 2018
    Hi Guy's, need a little help here.

    I have done the Binkit V2 upgrade and all seems ok to my normal Fido hub.

    So I have been trying to join fsxnet and have configured everything.

    I know my Dan's fsxnet hub is Mystic BBS so I have used BinkpAllowPlainText=true as
    suggested, YET I see from the logs that Binkit is still trying to do CRAM-MD5 Auth.

    It is also using the wrong source address so I set BinkpSourceAddress=21:4/124 as well, yet it still uses my Fido address? What is going on here?

    Here is the stanza in sbbsech.ini (binkit.ini is gone after the upgd)

    -----------------------------
    [node:21:4/100@fsxnet]
    Name=Dan Richter
    Comment=FSXNet Echo Mail CastleRock BBS
    Archive=ZIP
    PacketType=2+
    PacketPwd=
    AreaFix=true
    AreaFixPwd=removed
    TicFilePwd=removed
    Inbox=
    Outbox=
    Passive=false
    Direct=true
    Notify=false
    Keys=
    Status=Normal
    Route=21:4/100
    GroupHub=
    SessionPwd=removed
    BinkpHost=bbs.castlerockbbs.com
    BinkpPort=24560
    BinkpPoll=true
    BinkpAllowPlainAuth=false
    BinkpAllowPlainText=true
    BinkpSourceAddress=21:4/124

    -------------------------------


    Here is the output of a poll

    --------------------------------

    Attempting poll for node 21:4/100@fsxnet
    JSBinkP/1.106 callout to 21:4/100@fsxnet started
    Sent M_NUL command args: OPT CRYPT
    Sent M_NUL command args: SYS The Dungeon
    Sent M_NUL command args: ZYZ Keith Matthews
    Sent M_NUL command args: LOC Canberra, ACT, Australia
    Sent M_NUL command args: NDL 115200,TCP,BINKP
    Sent M_NUL command args: TIME Sun Apr 01 2018 11:36:40 GMT+1000 (AEDT)
    Sent M_NUL command args: VER BinkIT/2.0,JSBinkP/1.106,sbbs3.17a/Linux binkp/1.1 Sent M_ADR command args: 3:712/620@fidonet
    Got M_NUL command args: OPT CRAM-MD5-3153b4b41636ea9f8a08f161f749f2c3
    Got M_NUL command args: SYS fsxHUB Niba [NET4]
    Got M_NUL command args: ZYZ Black Panther
    Got M_NUL command args: VER Mystic/1.12A39 binkp/1.0
    Peer version: Mystic/1.12A39 binkp/1.0
    Got M_ADR command args: 21:4/0@fsxnet 21:4/100@fsxnet
    Sent M_PWD command args: CRAM-MD5-800ae954e0c06e1994e65ad1ffd09ec5
    Got M_ERR command args: Bad address or password
    BinkP got fatal error from remote: 'Bad address or password'.
    Unlocking /usr/local/sbbs/fido/outbound.015/00040064.bsy.
    /sbbs/exec/binkit.js executed in 2.16 seconds

    JavaScript: Destroying context
    JavaScript: Destroying runtime

    ------------------------------------------------------

    Can anyone suggest what is going on here?

    P.S. I have also tried without those keys options set, and also tried whilst still using
    the binkit V1 setup.

    Thx.
    8-)
    Regards..Geo
    ooooOOOOoooo
    --- SBBSecho 3.03-Linux
    * Origin: The Dungeon BBS Canberra, Australia. (3:712/620)
  • From Digital Man@1:103/705 to Keith Matthews on Sat Mar 31 18:57:46 2018
    Re: Binkit v2 and connecting to Mystic BBS Hub
    By: Keith Matthews to All on Sun Apr 01 2018 11:38 am

    Hi Guy's, need a little help here.

    I have done the Binkit V2 upgrade and all seems ok to my normal Fido hub.

    So I have been trying to join fsxnet and have configured everything.

    I know my Dan's fsxnet hub is Mystic BBS so I have used BinkpAllowPlainText=true as
    suggested, YET I see from the logs that Binkit is still trying to do CRAM-MD5 Auth.

    Right, "PlainText" references to encryption of the session data, not the Authentication.

    Outbound CRAM-MD5 has *no* known issues/incompatibilities with Mystic or any other mailers.

    It is also using the wrong source address so I set BinkpSourceAddress=21:4/124 as well, yet it still uses my Fido address? What is going on here?

    I'm not sure. I haven't needed used that particular setting myself (works fine without it and I'm in both FidoNet zone 1 and fsxnet zone 21).

    Here is the stanza in sbbsech.ini (binkit.ini is gone after the upgd)

    -----------------------------
    [node:21:4/100@fsxnet]
    Name=Dan Richter
    Comment=FSXNet Echo Mail CastleRock BBS
    Archive=ZIP
    PacketType=2+
    PacketPwd=
    AreaFix=true
    AreaFixPwd=removed
    TicFilePwd=removed
    Inbox=
    Outbox=
    Passive=false
    Direct=true
    Notify=false
    Keys=
    Status=Normal
    Route=21:4/100

    You probably want to remove that "Route" setting. The way you would use Route would be more like this (if you wanted to route all netmail in zone 21 through this link):

    [21:ALL]
    Route=21:4/100

    GroupHub=
    SessionPwd=removed
    BinkpHost=bbs.castlerockbbs.com
    BinkpPort=24560
    BinkpPoll=true
    BinkpAllowPlainAuth=false
    BinkpAllowPlainText=true
    BinkpSourceAddress=21:4/124

    -------------------------------


    Here is the output of a poll

    --------------------------------

    Attempting poll for node 21:4/100@fsxnet
    JSBinkP/1.106 callout to 21:4/100@fsxnet started
    Sent M_NUL command args: OPT CRYPT
    Sent M_NUL command args: SYS The Dungeon
    Sent M_NUL command args: ZYZ Keith Matthews
    Sent M_NUL command args: LOC Canberra, ACT, Australia
    Sent M_NUL command args: NDL 115200,TCP,BINKP
    Sent M_NUL command args: TIME Sun Apr 01 2018 11:36:40 GMT+1000 (AEDT)
    Sent M_NUL command args: VER BinkIT/2.0,JSBinkP/1.106,sbbs3.17a/Linux binkp/1.1 Sent M_ADR command args: 3:712/620@fidonet

    Do you have your zone 21 address configured in SCFG->Networks->FidoNet->Addresses?

    Got M_NUL command args: OPT CRAM-MD5-3153b4b41636ea9f8a08f161f749f2c3
    Got M_NUL command args: SYS fsxHUB Niba [NET4]
    Got M_NUL command args: ZYZ Black Panther
    Got M_NUL command args: VER Mystic/1.12A39 binkp/1.0
    Peer version: Mystic/1.12A39 binkp/1.0
    Got M_ADR command args: 21:4/0@fsxnet 21:4/100@fsxnet
    Sent M_PWD command args: CRAM-MD5-800ae954e0c06e1994e65ad1ffd09ec5
    Got M_ERR command args: Bad address or password
    BinkP got fatal error from remote: 'Bad address or password'.

    That could just be because you're sending the zone 3 address instead of the zone 21 address (and he doesn't have your zone 3 address configured as a link or its using a different password).

    digital man

    This Is Spinal Tap quote #28:
    We've got Armadillos in our trousers. It's really quite frightening.
    Norco, CA WX: 67.7oF, 51.0% humidity, 13 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.04-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Al@1:103/705 to Digital Man on Sat Mar 31 22:02:24 2018
    Re: Binkit v2 and connecting to Mystic BBS Hub
    By: Digital Man to Keith Matthews on Sat Mar 31 2018 06:57 pm

    That could just be because you're sending the zone 3 address instead of the zone 21 address (and he doesn't have your zone 3 address configured as a link or its using a different password).

    I am having a similar issue with the same hub in fsxnet. I just replied to a message in fsxnet and this is the log..


    Mar 31 21:42:34 trmb synchronet: term Node 1 Al posted on fsxNet General Chat Mar 31 21:42:37 trmb synchronet: evnt Semaphore signaled for Timed Event: FIDOO UT
    Mar 31 21:42:37 trmb synchronet: evnt Running native timed event: FIDOOUT
    Mar 31 21:42:37 trmb synchronet: evnt Executing external: /sbbs/exec/sbbsecho - ni
    Mar 31 21:42:38 trmb synchronet: evnt Timed event: FIDOOUT returned 0
    Mar 31 21:42:42 trmb synchronet: evnt Semaphore signaled for Timed Event: BINKO UT
    Mar 31 21:42:42 trmb synchronet: evnt Running timed event: BINKOUT
    Mar 31 21:42:42 trmb synchronet: evnt Executing external: ?binkit
    Mar 31 21:42:42 trmb synchronet: evnt BinkIT/2.0 invoked with options:
    Mar 31 21:42:42 trmb synchronet: evnt Running outbound
    Mar 31 21:42:42 trmb synchronet: evnt Outbound roots: ["/sbbs/fido/outbound"] Mar 31 21:42:42 trmb synchronet: evnt Outbound dirs: ["/sbbs/fido/outbound/","/ sbbs/fido/outbound.002/","/sbbs/fido/outbound.003/","/sbbs/fido/outbound.004/", "/sbbs/fido/outbound.00b/","/sbbs/fido/outbound.015/","/sbbs/fido/outbound.02c/ ","/sbbs/fido/outbound.13c/","/sbbs/fido/outbound.27d/"]
    Mar 31 21:42:42 trmb synchronet: evnt Running outbound dir /sbbs/fido/outbound/ Mar 31 21:42:42 trmb synchronet: evnt Done checking in /sbbs/fido/outbound/. Mar 31 21:42:42 trmb synchronet: evnt Running outbound dir /sbbs/fido/outbound. 002/
    Mar 31 21:42:42 trmb synchronet: evnt Done checking in /sbbs/fido/outbound.002/ .
    Mar 31 21:42:42 trmb synchronet: evnt Running outbound dir /sbbs/fido/outbound. 003/
    Mar 31 21:42:42 trmb synchronet: evnt Done checking in /sbbs/fido/outbound.003/ .
    Mar 31 21:42:42 trmb synchronet: evnt Running outbound dir /sbbs/fido/outbound. 004/
    Mar 31 21:42:42 trmb synchronet: evnt Done checking in /sbbs/fido/outbound.004/ .
    Mar 31 21:42:42 trmb synchronet: evnt Running outbound dir /sbbs/fido/outbound. 00b/
    Mar 31 21:42:42 trmb synchronet: evnt Done checking in /sbbs/fido/outbound.00b/ .
    Mar 31 21:42:42 trmb synchronet: evnt Running outbound dir /sbbs/fido/outbound. 015/
    Mar 31 21:42:42 trmb synchronet: evnt Locking /sbbs/fido/outbound.015/00040064. bsy
    Mar 31 21:42:42 trmb synchronet: evnt Lock successful.
    Mar 31 21:42:42 trmb synchronet: evnt Attempting callout for file /sbbs/fido/ou tbound.015/00040064.clo
    Mar 31 21:42:42 trmb synchronet: evnt JSBinkP/1.106 callout to 21:4/100 started Mar 31 21:42:43 trmb synchronet: evnt Connection to f100.n4.z21.binkp.net:24554
    failed.
    Mar 31 21:42:43 trmb synchronet: evnt Unlocking /sbbs/fido/outbound.015/0004006 4.bsy.
    Mar 31 21:42:43 trmb synchronet: evnt No flow files to be processed.
    Mar 31 21:42:43 trmb synchronet: evnt Done checking in /sbbs/fido/outbound.015/ .
    Mar 31 21:42:43 trmb synchronet: evnt Running outbound dir /sbbs/fido/outbound. 02c/
    Mar 31 21:42:43 trmb synchronet: evnt Done checking in /sbbs/fido/outbound.02c/ .
    Mar 31 21:42:43 trmb synchronet: evnt Running outbound dir /sbbs/fido/outbound. 13c/
    Mar 31 21:42:43 trmb synchronet: evnt Done checking in /sbbs/fido/outbound.13c/ .
    Mar 31 21:42:43 trmb synchronet: evnt Running outbound dir /sbbs/fido/outbound. 27d/
    Mar 31 21:42:43 trmb synchronet: evnt Done checking in /sbbs/fido/outbound.27d/ .
    Mar 31 21:42:43 trmb synchronet: evnt Timed event: BINKOUT returned 0

    I seem to be bugged by the binkp.net look up now I just ran "jsexec binkit upgrade" yesterday so the settings are all in sbbsecho.ini now and are new to me but everything looks right. Here's a section of my sbbsecho.ini..

    ; Converted from e:\stock\ctrl\sbbsecho.cfg using sbbsecho_upgrade.js 1.9 CheckPathsForDupes = true
    KillEmptyNetmail = true
    AreaAddFromEcholistsOnly = true
    SecureEchomail = true
    BinkleyStyleOutbound = true
    TruncateBundles = false
    FuzzyNetmailZones = false
    StripLineFeeds = false
    ConvertTearLines = false

    ZoneBlind = true
    LogLevel = Informational
    inbound = /sbbs/fido/inbound/
    nocircularfwd =
    outbound = /sbbs/fido/outbound/
    SecureInbound = /sbbs/fido/sec.in/
    AreaFile = /sbbs/data/areas.bbs
    AreaFileBackups = 5
    CfgFileBackups = 5
    BadAreaFile = /sbbs/data/badareas.lst
    EchoStats = /sbbs/data/echostats.ini
    LogFile = /sbbs/data/sbbsecho.log
    LogTimeFormat = %m-%d-%y %H:%M:%S
    TempDirectory = /sbbs/temp/sbbsecho
    BundleSize = 500K
    PacketSize = 250K
    SysopAliasList = SYSOP,ADMINISTRATOR,COORDINATOR
    ZoneBlindThreshold = 4
    StrictPacketPasswords = false
    EchomailNotify = true
    AutoAddSubs = false
    BsyTimeout = 12H
    BsoLockDelay = 10S
    BsoLockAttempts = 60
    MaxEchomailAge = 0S
    MaxNetmailAge = 0S
    RelayFilteredMsgs = true
    DeleteNetmail = true
    DeletePackets = true
    IgnoreNetmailDestAddr = false
    IgnoreNetmailSentAttr = false
    IgnoreNetmailKillAttr = false
    IgnoreNetmailRecvAttr = false
    IgnoreNetmailLocalAttr = false
    DefaultRecipient = 1
    UseFTNDomains = false
    OutgoingSemaphore=/sbbs/data/binkout.now

    [BinkP]
    Capabilities=
    Sysop=

    [node:21:4/100@fsxnet]
    Name = Dan Richter
    Comment = fsxNet Hub
    Archive = ZIP
    PacketType = 2+
    PacketPwd = XXXXXXXX
    AreaFix = false
    AreaFixPwd =
    SessionPwd = XXXXXXXX
    TicFilePwd = XXXXXXXX
    Inbox =
    Outbox =
    Passive = false
    Direct = true
    Notify = false
    Keys = FSXNET
    Status = Crash
    GroupHub = fsxNet
    BinkpHost = bbs.castlerockbbs.com
    BinkpPort = 24560
    BinkpPoll = false
    BinkpAllowPlainAuth = false
    BinkpAllowPlainText = true
    BinkpSourceAddress =
    [domain:fidonet]
    Zones = 1,2,3,4
    DNSSuffix =
    NodeList = /sbbs/fido/nodelist/nodelist.089
    [domain:fsxnet]
    Zones = 21
    DNSSuffix =
    NodeList = /sbbs/fido/nodelist/FSXNET.089

    Ttyl :-),
    Al


    ... I can't decide between EDLIN and Word for Windows...

    ---
    * Synchronet * The Rusty MailBox - Penticton, BC Canada - trmb.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Keith Matthews@3:712/620 to Digital Man on Sun Apr 1 15:04:12 2018
    Re: Binkit v2 and connecting to Mystic BBS Hub
    By: Digital Man to Keith Matthews on Sat Mar 31 2018 18:57:46

    Do you have your zone 21 address configured in SCFG->Networks->FidoNet->Addresses?



    Thanks Rob, you nailed it as usual 8-)

    All fixed. 8-)


    Regards..Geo
    ooooOOOOoooo
    --- SBBSecho 3.03-Linux
    * Origin: The Dungeon BBS Canberra, Australia. (3:712/620)
  • From Digital Man@1:103/705 to Al on Sat Mar 31 23:25:12 2018
    Re: Binkit v2 and connecting to Mystic BBS Hub
    By: Al to Digital Man on Sat Mar 31 2018 10:02 pm

    Mar 31 21:42:42 trmb synchronet: evnt Attempting callout for file /sbbs/fido/ou tbound.015/00040064.clo
    Mar 31 21:42:42 trmb synchronet: evnt JSBinkP/1.106 callout to 21:4/100 started Mar 31 21:42:43 trmb synchronet: evnt Connection to f100.n4.z21.binkp.net:24554
    failed.

    I seem to be bugged by the binkp.net look up now I just ran "jsexec binkit upgrade" yesterday so the settings are all in sbbsecho.ini now and are new to me but everything looks right. Here's a section of my sbbsecho.ini..

    [node:21:4/100@fsxnet]
    ...

    BinkpHost = bbs.castlerockbbs.com

    That looks good and *should* work. Try removing the '@fsxnet' from the [node:21:4/100@fsxnet] section name and see if it then works.

    digital man

    Synchronet "Real Fact" #55:
    Synchronet Terminal Server introduced RLogin support w/v3.00c (2000).
    Norco, CA WX: 57.5oF, 76.0% humidity, 0 mph S wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.04-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Al on Sun Apr 1 00:06:22 2018
    Re: Binkit v2 and connecting to Mystic BBS Hub
    By: Digital Man to Al on Sat Mar 31 2018 11:25 pm

    Re: Binkit v2 and connecting to Mystic BBS Hub
    By: Al to Digital Man on Sat Mar 31 2018 10:02 pm

    Mar 31 21:42:42 trmb synchronet: evnt Attempting callout for file /sbbs/fido/ou tbound.015/00040064.clo
    Mar 31 21:42:42 trmb synchronet: evnt JSBinkP/1.106 callout to 21:4/100 started Mar 31 21:42:43 trmb synchronet: evnt Connection to f100.n4.z21.binkp.net:24554
    failed.

    I seem to be bugged by the binkp.net look up now I just ran "jsexec binkit upgrade" yesterday so the settings are all in sbbsecho.ini now and are new to me but everything looks right. Here's a section of my sbbsecho.ini..

    [node:21:4/100@fsxnet]
    ...

    BinkpHost = bbs.castlerockbbs.com

    That looks good and *should* work. Try removing the '@fsxnet' from the [node:21:4/100@fsxnet] section name and see if it then works.

    I think I just fixed this problem with the most recent update to fido_syscfg.js. Please give it a shot.

    digital man

    Synchronet/BBS Terminology Definition #40:
    POP3 = Post Office Protocol version 3
    Norco, CA WX: 56.7oF, 78.0% humidity, 0 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.04-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)