Subj : Re: Future-proofing DOS BBSs
To   : akacastor
From : j0HNNY a1PHA
Date : Sat Feb 17 2024 16:21:16

 > Just the other day I learned of EtherDFS - it looks very useful and
 > definitely looks more straightforward to setup than the Microsoft
 > Network Client (though the Microsoft Network Client is doable, it
 > certainly isn't the lightest).  I haven't tried EtherDFS, it isn't
 > clear to me if it supports multiple simultaneous clients with
 > SHARE.EXE etc.

So it sounds like etherdfs doesn't support SHARE file locking, that's
good to know. I was hoping to use FDNET (instead of MSCLIENT), but
based on file locking needs, going to adjust my plans! 

Here's my new approach using my local proxmox for all the VMs:

1. Want to test your Ringdown to handle incomoing connections on a
dedicated linux machine to handle incoming (and SMB file share). I was
thinking about HAPROXY approach but I love what you are doing with bot
detection! 

2. 4x FreeDOS v1.3 VMs, each with own IP under MSCLIENT, etc.

3. Multi-node capable DOS BBS running on each FreeDOS machine (Renegade or
Iniquity or PCBOARD)

4. RLFOSSIL - a shim program to allow each BBS node to accept incoming
telnet connections.

Item 5 is now my biggest question mark, I read in forums that it works
suprisingly well, but curious how reliable it is.

I had a similar setup earlier this year, but I was using SOCAT to do
null-modem stuff and it was very brittle, as I had written my own telnet
server to handle incoming connections and manage routing (in Go) which
just wasn't very good :(

Cheers and thanks again for all the great info, especially the MSCLIENT
configs you posted.

|08.|05j|13A|08.


--- Talisman v0.53-dev (Linux/x86_64)
 * Origin: R3tr0/X BBS :: retrox.us:1992 (21:4/158)

.