• Not receiving FTN packets

    From Errol Casey@1337:3/194 to All on Sun Jan 4 13:45:17 2026
    I've recently joined a FTN and my synchronet logs show it authenticates
    but the HUB is running mystic, and his logs shows authenticating failing.

    Any ideas where the mismatch could be? Thinking I've enabled or not enabled
    a parameter on my BBS that is causing the confusion.

    His also says there is a packet waiting, but when I poll I don't get anything. ===
    Amessyroom
    toolazy.synchro.net:2323 (telnet)





    ...For once I'm at a loss for words. Mark down the date!
    --- SBBSecho 3.33-Linux
    * Origin: Too Lazy BBS - toolazy.synchro.net:2323 (1337:3/194)
  • From deon@1337:2/101 to Errol Casey on Mon Jan 5 12:22:37 2026
    Re: Not receiving FTN packets
    By: Errol Casey to All on Sun Jan 04 2026 01:45 pm

    Howdy,

    I've recently joined a FTN and my synchronet logs show it authenticates
    but the HUB is running mystic, and his logs shows authenticating failing.

    Lot entries would help.

    Because during a BINKP session, its one sided authentication, so you both cannot validated "Authentication" at the same time.

    The server authenticates the client, and reports to the client that authentication passed or failed. (Which the client may report it its logs.)

    At a guess, if your hub polls you (you are the server in this instance), and you pass authentication, but when you poll the hub (the hub is the server in the instance), and the hub reports failure - then I would suggest the hub needs to be restarted.




    ...ëîåï
    --- SBBSecho 3.29-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (1337:2/101)
  • From Shurato@1337:3/185 to Errol Casey on Mon Jan 5 18:23:00 2026

    I've recently joined a FTN and my synchronet logs show it authenticates but the HUB is running mystic, and his logs shows authenticating failing.

    Any ideas where the mismatch could be? Thinking I've enabled or not enabled a parameter on my BBS that is causing the confusion.

    His also says there is a packet waiting, but when I poll I don't get anything. === Amessyroom toolazy.synchro.net:2323
    (telnet)

    Show us the log. Are you each using your BBS's binkp's or binkd?

    --
    Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
    ,wss) (Ports 22,23,110,21,119,999)


    *** THE READER V4.50 [freeware]
    ---
    * Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (1337:3/185)
  • From Errol Casey@1337:3/194 to Shurato on Mon Jan 5 20:46:09 2026
    Re: Not receiving FTN packets
    By: Shurato to Errol Casey on Mon Jan 05 2026 06:23 pm


    I've recently joined a FTN and my synchronet logs show it authenticates but the HUB is running mystic, and his logs shows
    authenticating failing.

    Any ideas where the mismatch could be? Thinking I've enabled or not enabled a parameter on my BBS that is causing the
    confusion.

    His also says there is a packet waiting, but when I poll I don't get anything. === Amessyroom toolazy.synchro.net:2323
    (telnet)

    Show us the log. Are you each using your BBS's binkp's or binkd?

    I have received data from him once, he found a typo on his side with the binkp port.

    But nothing since. Asking him to confirm if mail is crash or hold state.


    Jan 5 20:19:43 vmi1943160 synchronet[792509]: evnt BINKPOLL Authentication successful: secure
    Jan 5 20:19:43 vmi1943160 synchronet[792509]: evnt BINKPOLL Attempting poll for node 63:10/100@familyne
    Jan 5 20:19:43 vmi1943160 synchronet[792509]: evnt BINKPOLL JSBinkP/4 callout to 63:10/100@familyne started
    Jan 5 20:19:43 vmi1943160 synchronet[792509]: evnt BINKPOLL Connecting to 63:10/100@familyne at familybbs.ddns.net:24554
    Jan 5 20:19:43 vmi1943160 synchronet[792509]: evnt BINKPOLL Peer version: Mystic/1.12A46
    Jan 5 20:19:44 vmi1943160 synchronet[792509]: evnt BINKPOLL Authentication successful: non-secure
    Jan 5 20:19:45 vmi1943160 synchronet[792509]: evnt BINKPOLL Timed event: '?binkit -p' returned 0

    I've sent areafix messages but have not received responses.

    we are using binkp


    ===
    Amessyroom
    toolazy.synchro.net:2323 (telnet)
    --- SBBSecho 3.33-Linux
    * Origin: Too Lazy BBS - toolazy.synchro.net:2323 (1337:3/194)
  • From MeaTLoTioN@1337:1/101 to Errol Casey on Tue Jan 6 08:17:25 2026
    On 04 Jan 2026, Errol Casey said the following...

    I've recently joined a FTN and my synchronet logs show it authenticates but the HUB is running mystic, and his logs shows authenticating failing.

    Any ideas where the mismatch could be? Thinking I've enabled or not enabled a parameter on my BBS that is causing the confusion.

    Sounds like the hub is trying to connect to your system and authenticate a session password that is different/unset on your system perhaps? Make sure that all the password fields match between the hub and your system?

    ---
    |14Best regards,
    |11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N // @meatlotion:erb.pw

    |07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
    |07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

    ... Documentation: The worst part of programming.

    --- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
    * Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (1337:1/101)