Synchronet v3.18b-Win32 (install) has been released (Sept-2020).

Synchronet is switching to Git

You can donate to the Synchronet project using PayPal.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
util:sexpots [2012/03/13 01:54]
digitalman [Configuration] Added ReInit value to [modem] section.
util:sexpots [2020/08/25 20:46] (current)
digital man [NT Service Control] Added DebugView example
Line 5: Line 5:
 ===== Overview ===== ===== Overview =====
  
-Synchronet BBS Software version 3 was designed for client connections over TCP/IP protocols only (predominently,​ Telnet). Over the 7 years since Synchronet v3's release, I've received +Synchronet BBS Software version 3 was designed for client connections over TCP/IP protocols only (predominently,​ Telnet). Over the 7 years since Synchronet v3's release, I've received occasional (but persistent) inquiries about the possibility or likelihood of adding modem support back into Synchronet to support direct analog dial-up users of the old BBS days before the Internet/​broadband boom.
-occasional (but persistent) inquiries about the possibility or likelihood of adding modem support back into Synchronet to support direct analog dial-up users of the old BBS days before the Internet/​broadband boom.+
  
-I've resisted this idea (for a few significant reasons I won't go into here), +I've resisted this idea (for a few significant reasons I won't go into here), and have instead, suggested alternative methods of supporting dial-up users (e.g. running Synchronet v2.3 for DOS concurrently with v3, using *getty on Linux/Unix, using Manning'​s Dialup-to-Telnet Win32 gateway program with a front-end application,​ etc.). But these solutions all seemed insufficient in some ways or excessively complex or inconvenient. I wanted to provide something easier, more seemless.... "​nicer"​. Though I'm pretty sure there isn't much demand for dial-up BBSes today (30Kbps!), there has been enough interest from sysops to at least justify some effort (in my mind) to attempt to relive the BBS days of old, using actual *gasp* modems!
-and have instead, suggested alternative methods of supporting dial-up users +
-(e.g. running Synchronet v2.3 for DOS concurrently with v3, using *getty on +
-Linux/Unix, using Manning'​s Dialup-to-Telnet Win32 gateway program with a +
-front-end application,​ etc.). But these solutions all seemed insufficient +
-in some ways or excessively complex or inconvenient. I wanted to provide +
-something easier, more seemless.... "​nicer"​. Though I'm pretty sure there +
-isn't much demand for dial-up BBSes today (30Kbps!), there has been enough +
-interest from sysops to at least justify some effort (in my mind) to attempt +
-to relive the BBS days of old, using actual *gasp* modems!+
  
-I knew exactly what was required to write a Serial<​->​TCP tunneling program +I knew exactly what was required to write a Serial<​->​TCP tunneling program and blogged on the www.synchro.net web-site way back in 2002 that I planned on writing just such a program to give dial-up capabilities to Synchronet v3 Win32 sysops.
-and blogged on the www.synchro.net web-site way back in 2002 that I planned on +
-writing just such a program to give dial-up capabilities to Synchronet v3 +
-Win32 sysops.+
  
-Better late than never (?), I finally started writing this a program a few +Better late than never (?), I finally started writing this a program a few months ago (early 2007). I had to buy an analog modem (I'd thrown-out or donated all my modems years ago) and get a second phone line installed to test it, but finally, here it is: SEXPOTS (the name pays homage to [[SEXYZ]]). 
-months ago (early 2007). I had to buy an analog modem (I'd thrown-out or +
-donated all my modems years ago) and get a second phone line installed to test +
-it, but finally, here it is: SEXPOTS (the name pays homage to SEXYZ). ​+
  
-While SEXPOTS was designed with Synchronet-Win32 sysops in mind, it should +While SEXPOTS was designed with Synchronet-Win32 sysops in mind, it should work with any TCP Server (e.g. Telnet BBS software).
-work with any TCP Server (e.g. Telnet BBS software).+
  
-I recently discovered a couple of unrelated Win32 programs by the name of +I recently discovered a couple of unrelated Win32 programs by the name of COM2TCP which do fundamentally the same thing as SEXPOTS, but SEXPOTS is more robust/​reliable,​ and has some niceties and cool BBS and Synchronet-specific features you'll like:
-COM2TCP which do fundamentally the same thing as SEXPOTS, but SEXPOTS is more +
-robust/​reliable,​ and has some niceties and cool BBS and Synchronet-specific +
-features you'll like:+
  
 ==== Features ==== ==== Features ====
Line 79: Line 59:
     -port <​number> ​       Specify TCP port number     -port <​number> ​       Specify TCP port number
     -debug ​               Enable debug log output     -debug ​               Enable debug log output
 +</​code>​
  
 +Additional options for Windows version:
 +
 +<​code>​
 NT Service Options: NT Service Options:
  
Line 91: Line 75:
 ===== Installation ===== ===== Installation =====
  
-No installation is required. You should be able to just run "​sexpots",​ +No installation is required. You should be able to just run "​sexpots",​ optionally specifying command-line options to over-ride the default values (shown below), or the values in your ''​[[config:​sexpots.ini]]''​ file (if you have one).
-optionally specifying command-line options to over-ride the default +
-values (shown below), or the values in your ''​[[config:​sexpots.ini]]''​ file (if you +
-have one).+
  
-On Windows NT-based operating systems, you may install SEXPOTS as an +On Windows NT-based operating systems, you may install SEXPOTS as an NT service (runs in the background when your system boots up, before user login), by running ''​sexpots -install''​. You can then start and stop the service using the "​Services"​ Windows Control Panel applet or with the ''​net start sexpots''​ or ''​net stop sexpots''​ Windows command-lines. You can toggle the service start mode (between auto-start and disabled) with the ''​-enable''​ and ''​-disable''​ command-line options. When running as an NT service, the SEXPOTS log output goes to the "​Application Log" in the NT event viewer.
-NT service (runs in the background when your system boots up, before +
-user login), by running ''​sexpots -install''​. You can then start and +
-stop the service using the "​Services"​ Windows Control Panel applet or +
-with the ''​net start sexpots''​ or ''​net stop sexpots''​ Windows command-lines. +
-You can toggle the service start mode (between auto-start and disabled) +
-with the ''​-enable''​ and ''​-disable''​ command-line options. When running as +
-an NT service, the SEXPOTS log output goes to the "​Application Log" +
-in the NT event viewer.+
  
  
 ===== Configuration ===== ===== Configuration =====
  
-Configuration is normally performed by editing the file ''​[[config:​sexpots.ini]]'',​ located +Configuration is normally performed by editing the file ''​[[config:​sexpots.ini]]'',​ located in the same directory where the SEXPOTS program (e.g. ''​sexposts.exe''​) is located (e.g. ''​[[dir:​exec]]''​). If ''​[[config:​sexpots.ini]]''​ file doesn'​t exist or any of the ''​key=value''​ pairs are missing or blank in the file, the default values (indicated below) will be used.
-in the same directory where the SEXPOTS program (e.g. ''​sexposts.exe''​) is  +
-located (e.g. ''​[[dir:​exec]]''​). If ''​[[config:​sexpots.ini]]''​ file doesn'​t exist or any of the ''​key=value''​ pairs are missing or blank in the file, the default values (indicated below) will be used.+
  
 Optionally, a different [[config:​ini files|.ini file]] may be specified on the command-line (e.g. for running multiple concurrent instances of SEXPOTS on different COM ports). If an .ini file is specified on the command-line,​ it will be loaded **after** ''​[[config:​sexpots.ini]]''​ (if the file exists), over-riding any settings in ''​[[config:​sexpots.ini]]''​. Optionally, a different [[config:​ini files|.ini file]] may be specified on the command-line (e.g. for running multiple concurrent instances of SEXPOTS on different COM ports). If an .ini file is specified on the command-line,​ it will be loaded **after** ''​[[config:​sexpots.ini]]''​ (if the file exists), over-riding any settings in ''​[[config:​sexpots.ini]]''​.
Line 147: Line 118:
 Timeout = 5                 ; Seconds to wait for a response from modem Timeout = 5                 ; Seconds to wait for a response from modem
 ReInit = 60                 ; Minutes of inactivity while waiting for caller before re-initialization ReInit = 60                 ; Minutes of inactivity while waiting for caller before re-initialization
 +Answer = ATA                ; Answer command
 +Ring = RING                 ; Ring indication (from modem)
 +ManualAnswer = FALSE        ; Set to TRUE to disable auto-answer and use ring detection/​manual answer instead
  
 [TCP] [TCP]
Line 167: Line 141:
 </​file>​ </​file>​
  
 +Note: SEXPOTS v1.25 and earlier did not supports comments on ''​.ini''​ string value lines as shown above. As of v1.26 (and later), string values (e.g. com device name, modem strings, hostname, etc.) are terminated at the first white-space character so white-space characters are **not permitted** in the string values of the SEXPOTS ''​.ini''​ file.
 +
 +Note: Support for the ''​[modem] ReInit''​ key was added in SEXPOTS v1.27.
 ===== NT Service Control ===== ===== NT Service Control =====
  
Line 183: Line 160:
   net stop sexpots   net stop sexpots
  
 +==== DebugView ====
 +
 +When running SEXPOTS as an NT Service, you may want to use a debugger viewer (e.g. [[https://​docs.microsoft.com/​en-us/​sysinternals/​downloads/​debugview|DebugView]],​ run as Administrator) to see the detailed log messages:
 +
 +{{:​util:​dbgview_sexpots.jpg?​600|}}
 ===== Notes on Advanced Features ===== ===== Notes on Advanced Features =====
  
 :!: NOTE: Requires Synchronet v3.14b or later :!: NOTE: Requires Synchronet v3.14b or later
  
-SEXPOTS will report the connection (DCE) rate to a Synchronet Terminal Server +SEXPOTS will report the connection (DCE) rate to a Synchronet Terminal Server using the Telnet "​TERMINAL SPEED" sub-option. Synchronet will use the reported speed to calculate estimated file transfer durations, update the node record, log to the user logon list, and save in the user record as the user's most recent "​connection type".
-using the Telnet "​TERMINAL SPEED" sub-option. Synchronet will use the reported +
-speed to calculate estimated file transfer durations, update the node record, +
-log to the user logon list, and save in the user record as the user's most +
-recent "​connection type".+
  
-SEXPOTS can report Caller-ID information to the Synchronet Terminal Server using +SEXPOTS can report Caller-ID information to the Synchronet Terminal Server using the Telnet "​Location"​ option. Synchronet will store the Caller-ID reported Phone Number in the user's '​note'​ field (where the IP address is normally stored) and the Caller-ID reported Caller Name in the user's '​computer'​ field (where the Hostname is normally stored). Synchronet will also log each
-the Telnet "​Location"​ option. Synchronet will store the Caller-ID reported +
-Phone Number in the user's '​note'​ field (where the IP address is normally +
-stored) and the Caller-ID reported Caller Name in the user's '​computer'​ +
-field (where the Hostname is normally stored). Synchronet will also log each+
 caller'​s Caller-ID information for record-keeping purposes. caller'​s Caller-ID information for record-keeping purposes.
  
-Alternatively,​ SEXPOTS can report the Caller-ID information using the Ident +Alternatively,​ SEXPOTS can report the Caller-ID information using the Ident protocol, but this feature is disabled by default and is not the preferred mechanism (use the Telnet "​Location"​ option instead).
-protocol, but this feature is disabled by default and is not the preferred +
-mechanism (use the Telnet "​Location"​ option instead).+
  
-Using Synchronet v3.14a or earlier, the Synchronet Terminal Server will detect +Using Synchronet v3.14a or earlier, the Synchronet Terminal Server will detect the caller as just another Telnet connection, but coming in from the local network interface (IP address).
-the caller as just another Telnet connection, but coming in from the local +
-network interface (IP address).+
  
 ===== Linux/Unix Version ===== ===== Linux/Unix Version =====
Line 215: Line 185:
   * [[:​server:​terminal|Terminal Server]]   * [[:​server:​terminal|Terminal Server]]
   * [[:​util:​|Utilities]]   * [[:​util:​|Utilities]]
 +  * [[:​config:​INI files]]
  

In Other Languages