1. Forum
  2. FidoNet
  3. MYSTIC

  • Re: binkp 1.1

    From Robert Wolfe@99:1/1 to All on Saturday, March 21, 2026 08:25:00
    -------- Forwarded Message ---------
    Original: DATE..... 3/20/2026 8:02 PM
    Original: FROM..... Winserver Support Agent ÿ
    Original: TO....... Robert Wolfe ÿ
    Original: SUBJECT.. Re: binkp 1.1
    Original: FORUM.... PXNet Beta Testers
    Forwarded By....... Robert Wolfe on 3/21/2026 8:22 AM

    The traces are helpful. A few observations:

    SWATS SESSION (outbound from you to 3:772/230)

    The file was sent -- "Binkp send: 0FC7B7B9.PKT" and "data sent, awaiting M_GOT" -- but the session ends with TX:Y PKT:N Bundle:N. TX:Y means the file was transmitted, but PKT:N means PX did not receive a M_GOT acknowledgment before the remote closed the connection. Mystic closed the session after receiving your EOB without sending M_GOT first.

    That is likely a Mystic behavior -- some versions close the connection as soon as they receive EOB without waiting to acknowledge individual files. The file probably landed in their inbound anyway. Worth asking the sysop at SWATS to check their inbound for 0FC7B7B9.PKT.

    The "Remote VER: Mystic/1.12A46 binkp/1.0" also shows they are advertising binkp/1.0, not 1.1. PX should handle that fine in compatibility mode, but it does mean some 1.1 features like CRAM-MD5 and offset resume will not be negotiated.

    YOUR MYSTIC/LINUX SESSION (inbound from 1:261/20.1)

    This one is clean. The remote connected, auth was accepted, no files were exchanged in either direction, both sides sent EOB, session closed normally. Nothing wrong there.

    Winserver Support Agen
    --- Platinum Xpress/Win/WINServer v10.0
    * Origin: Santronics Online (99:1/1)
  • From Jay Harris@1:229/664 to Robert Wolfe on Saturday, March 21, 2026 09:28:36
    On 21 Mar 2026, Robert Wolfe said the following...

    @MSGID: 99:1/1 e436bf1d
    * Origin: Santronics Online (99:1/1)
    ^^
    Looks like you need to update your aka for this base.


    Jay

    ... That's why we like you Mulder, your ideas are weirder than ours.

    --- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
    * Origin: Northern Realms (1:229/664)
  • From Robert Wolfe@1:261/20 to Jay Harris on Saturday, March 21, 2026 09:46:46
    On 3/21/2026 9:32 AM, Jay Harris wrote to Robert Wolfe:

    @MSGID: 1:229/664 3828bd2f
    @REPLY: 99:1/1 e436bf1d
    @TZUTC: -0400
    @TID: hpt/lnx 1.9 2024-03-02
    On 21 Mar 2026, Robert Wolfe said the following...

    @MSGID: 99:1/1 e436bf1d
    * Origin: Santronics Online (99:1/1)
    ^^
    Looks like you need to update your aka for this base.


    Jay

    ... That's why we like you Mulder, your ideas are weirder than ours.

    --- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
    * Origin: Northern Realms (1:229/664)

    My AKA is fine. if you notice that was a forwarded message from another system.
    --- Platinum Xpress/Win/WINServer v10.0
    * Origin: On the Brink *&Buffalo, NY USA * brinkbbs.org (1:261/20)
  • From Robert Wolfe@1:261/20.1 to All on Friday, May 01, 2026 12:45:44
    12:43:01 ------------------------------------------------------------ 05/01/26 12:43:01 Binkp answer: connection from 69.201.5.244
    12:43:01 Remote SYS: Over the Brink Test BBS
    12:43:01 Remote ZYZ: Robert Wolfe
    12:43:01 Remote VER: Mystic/1.12A49 binkp/1.0
    12:43:01 Remote ADR: 1:261/20.1@fidonet
    12:43:01 Remote PWD: accepted (exp: ***)
    12:43:01 Binkp answer: auth OK - session active
    12:43:01 Binkp: got remote EOB
    12:43:01 Binkp answer: sent EOB
    12:43:01 Binkp answer: session end PKT:N Bundle:N
    12:43:03 Binkp Inbound/Outbound Ready

    why no binkp 1.1??

    ... Do device drivers need a chauffeur's license?

    --- Mystic BBS v1.12 A49 2024/05/29 (Windows/64)
    * Origin: Listen To: http://radio.klyntar.net (1:261/20.1)