1. Forum
  2. USENET
  3. alt.bbs.synchronet

  • Question from a non-Synchronet hub.

    From Marc Lewis@marc.lewis@1:396/45.remove-ju8-this to All on Mon Nov 23 20:43:49 2020
    From Newsgroup: alt.bbs.synchronet

    Hello All.

    Why is it that Syncrhonet's linux based BinkP always *seems* to drop it's inbound connection, ungracefully at that? Here's a couple of examples from my BinkP log:

    -o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
    * 20:37:00 (10) Sent to 1:106/633: 0122FDB4.MOB (2151 bytes)
    ? 20:37:00 (10) BinkP error: remote dropped connection.
    =-=-=-=
    * 09:38:19 (9) Sent to 1:106/987: TK426867.TIC (2013 bytes)
    ? 09:38:19 (9) BinkP error: remote dropped connection.
    =-=-=-=
    * 09:52:19 (9) Sent to 1:106/987: 0122FC52.SU1 (143743 bytes)
    ? 09:52:20 (9) BinkP error: remote dropped connection.
    =-=-=-=
    * 00:02:03 (10) Sent to 1:106/633: 0122FDB4.MO0 (567 bytes)
    ? 00:02:03 (10) BinkP error: remote dropped connection.

    -o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-

    Here's an example of a normal close-out of a BinkP session from a couple non-Synchronet Nodes:

    -o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
    * 00:05:07 (8) Sent to 1:124/5016: 0110EC95.MO0 (15247 bytes)
    - 00:05:07 (8) Connection closed.
    =-=-=-=
    * 01:00:23 (8) Sent to 1:387/20: 00090019.MO0 (848 bytes)
    - 01:00:23 (8) Connection closed.
    -o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-

    Is this a fault in the Synchronet BinkP daemon or is it a user configuration error?

    Thanks in advance for any help.

    Best regards,
    Marc

    --- timEd/2 1.10.y2k+
    * Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)
    --- Synchronet 3.18c-Win32 NewsLink 1.113
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.19c-Linux NewsLink 1.113
  • From Digital Man@digital.man@vert.synchro.net.remove-a1z-this to Marc Lewis on Mon Nov 23 20:13:38 2020
    From Newsgroup: alt.bbs.synchronet

    To: Marc Lewis
    Re: Question from a non-Synchronet hub.
    By: Marc Lewis to All on Mon Nov 23 2020 08:43 pm

    Hello All.

    Why is it that Syncrhonet's linux based BinkP always *seems* to drop it's inbound connection, ungracefully at that? Here's a couple of examples from my BinkP log:

    -o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
    * 20:37:00 (10) Sent to 1:106/633: 0122FDB4.MOB (2151 bytes)
    ? 20:37:00 (10) BinkP error: remote dropped connection.

    Dou you mean BinkD log?

    Here's an example of a normal close-out of a BinkP session from a couple non-Synchronet Nodes:

    -o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
    * 00:05:07 (8) Sent to 1:124/5016: 0110EC95.MO0 (15247 bytes)
    - 00:05:07 (8) Connection closed.
    =-=-=-=
    * 01:00:23 (8) Sent to 1:387/20: 00090019.MO0 (848 bytes)
    - 01:00:23 (8) Connection closed.

    I don't see a huge difference between "connection closed" and "connection dropped". I'm not clear what the difference would be.

    Is this a fault in the Synchronet BinkP daemon or is it a user configuration error?

    It's most likely something about the BinkIT implementation, but I don't think it's a serious issue. Full TCP dump/trace would help to identify the differences and possibly lead to a change that made your BinkP daemon (binkd?) happy.
    --
    digital man

    Synchronet "Real Fact" #62:
    Name of Synchronet PCMS compiler/language "Baja" was coined by Michael Swindell.
    Norco, CA WX: 53.0øF, 89.0% humidity, 0 mph S wind, 0.00 inches rain/24hrs
    --- Synchronet 3.18c-Win32 NewsLink 1.113
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.19c-Linux NewsLink 1.113