• docs/v322_new.md src/vdmo

    From Rob Swindell (on Windows@VERT to Git commit to main/sbbs/m on Sun Nov 8 17:55:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/29e975fd78bd69abe0e0492b
    Modified Files:
    docs/v322_new.md src/vdmodem/readme.txt vdmodem.c
    Log Message:
    vdmodem: hunt group, one listening TCP port shared by several nodes (#1175)

    Each SVDM process still serves one DOS node, but with Hunt=true in the root section of svdm.ini every node can listen on the same TCP port. The process that binds the port owns it: it accepts each connection, applies the IP
    filter, takes the call if idle, and otherwise offers the socket to the other nodes over per-node named pipes (\.\pipe\svdm-hunt-<port>-<node>), lowest
    node number first. The first idle node claims the offer, the owner
    duplicates the socket into that process with WSADuplicateSocket() and
    closes its own copy once the member acknowledges, and the member rings as
    if it had accepted the connection itself. When no node is free the caller
    gets the BusyNotice as before. A process that finds the port in use joins
    the group instead of exiting, and members retry the bind every 5 seconds so
    the port survives the owner exiting. Windows allows that bind while the departed owner's handed-off connections are still established, so no SO_REUSEADDR is needed.

    In hunt mode an off-hook or already-ringing owner also counts as busy, so
    such calls are handed on rather than parked on a node that will never
    ring. Non-hunt behavior is unchanged: a second process on the port still
    fails to bind, and the off-hook case is untouched.

    answer() and the S0= handler now test the Listen setting rather than the listening socket, since a member has no listening socket but must be able
    to auto-answer. WSAStartup requests Winsock 2.2 for WSADuplicateSocket().
    Hunt is ignored, with a warning, together with -h. All nodes of a group
    must run as the same user at the same elevation: a node whose pipe can't
    be opened, or that can't receive the duplicated socket, is logged and
    skipped.

    Bump SVDM to v0.8; document multi-node use and the Hunt key in readme.txt.

    Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
  • From Rob Swindell (on Windows@VERT to Git commit to main/sbbs/m on Sun Nov 8 17:55:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/300594a386d57f42613b520e
    Modified Files:
    docs/v322_new.md src/vdmodem/vdmodem.c
    Log Message:
    vdmodem: send the busy notice to callers when the modem is off-hook

    The listen thread only checked whether a call was already stored. A caller reaching a node that was off-hook with nobody connected (as a DOS BBS does
    with ATM0H1 during a local logon) was accepted and stored but never rang
    and got no busy notice: the connection sat silent until the caller gave
    up, and meanwhile the stored socket made the next caller receive the busy notice instead. The hunt group code already treated an off-hook, online or ringing node as busy; use the same test for every listening node, so such callers get the BusyNotice text and are disconnected.

    Behavior dates from the original listen thread in 3ec7fb7787 (2022-05-08).

    Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
  • From Rob Swindell (on Windows@VERT to Git commit to main/sbbs/m on Sun Nov 8 17:55:00 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/a02c3c7bf31dfb51fbe52e78
    Modified Files:
    docs/v322_new.md src/vdmodem/vdmodem.c
    Log Message:
    vdmodem: ring immediately for a new incoming call

    The RING result was only sent when RING_DELAY (6 seconds) had passed since
    the previous RING, and the timestamp of that RING was never reset when a
    new call arrived. A caller connecting within 6 seconds of the previous
    call's last RING therefore waited out the remainder of that interval
    before the first RING, and with it the auto-answer; the main loop also
    logged "Incoming connection" on every pass while it waited. Real modems
    ring as soon as a call arrives, and a hunt group makes back-to-back calls
    to one node common, so send the first RING at once and keep the 6-second cadence only for the rings that follow.

    Dates from the original main loop in 3ec7fb7787 (2022-05-08).

    Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>