Synchronet v3.19b-Win32 (install) has been released (Jan-2022).

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 revisionPrevious revision
Next revision		Previous revision
faq:tcpip [2020/04/17 20:19] – [Bind] expand on the rebind issue. digital manfaq:tcpip [2024/11/02 13:48] (current) – [Ports] List the disabled service ports too (for reference) digital man
Line 48: Line 48:
 |WS             |1123   |       |WebSocket Service - to support the [[http://ftelnet.ca|fTelnet web browser-based terminal]] | |WS             |1123   |       |WebSocket Service - to support the [[http://ftelnet.ca|fTelnet web browser-based terminal]] |
 |WSS            |11235  |       |WebSocket Secure Service - to support the [[http://ftelnet.ca|fTelnet web browser-based terminal]] over TLS | |WSS            |11235  |       |WebSocket Secure Service - to support the [[http://ftelnet.ca|fTelnet web browser-based terminal]] over TLS |
 +
 +Additionally, a default Synchronet installation includes *disabled* servers and services on the following ports:
 +
 +^Protocol ^TCP ^UDP ^Comments^
 +|QOTD         |17 |17     |Allows remote querying of BBS's auto-message (e.g. via ''qotdservice.js'')|
 +|IMAP           |143    |-      |Allows remote download of user's email (similar to POP3, via ''imapservice.js'')|
 +|IMAPS          |993    |-      |Allows secure remote download of user's email (similar to POP3/TLS)|
 +|BINKP          |24554  |-      |Allows exchange of FidoNet files (e.g. mail bundles and packets, via ''binkit.js'')|
 +|BINKPS         |24553  |-      |Allows secure exchange of FidoNet files|
 +|NNTPS         |563 |- |Allows BBS users to securely read and post messages using standard news readers/clients|
 +|Hotline        |5500   |-      |Allows interaction with Hotline client|
 +|Hotline-TRANS  |5501   |-      |""|
 +
 +
  
 Enabling connectivity to Synchronet through your firewall is no different than enabling connectivity to any other TCP/IP server. Follow your firewall documentation for forwarding or opening ports for TCP/IP servers located "behind" the firewall. Your firewall may have the option of placing the entire BBS computer in a "DMZ" (opening all its ports to the public Internet), but doing so is not normally recommended.  Enabling connectivity to Synchronet through your firewall is no different than enabling connectivity to any other TCP/IP server. Follow your firewall documentation for forwarding or opening ports for TCP/IP servers located "behind" the firewall. Your firewall may have the option of placing the entire BBS computer in a "DMZ" (opening all its ports to the public Internet), but doing so is not normally recommended. 
Line 270: Line 284:
 This error upon binding usually means that you're running Synchronet as non-privileged user account (e.g. not 'root') and the operating system you're running does not allow processes run under non-privileged user accounts to bind to low (TCP or UDP) port numbers (usually less than 1024). You can either use higher TCP port numbers in your configuration or have Synchronet switch to a non-privileged user *after* binding the TCP ports (see [[config:nix]] for details), see also: [[howto:Linux non-root]]. This error upon binding usually means that you're running Synchronet as non-privileged user account (e.g. not 'root') and the operating system you're running does not allow processes run under non-privileged user accounts to bind to low (TCP or UDP) port numbers (usually less than 1024). You can either use higher TCP port numbers in your configuration or have Synchronet switch to a non-privileged user *after* binding the TCP ports (see [[config:nix]] for details), see also: [[howto:Linux non-root]].
  
 +==== Rebind ====
 :!: **Answer:**\\ :!: **Answer:**\\
 If you're running a Unix-like operating system (not Windows) and get bind errors //only// when recycling servers: If you're running a Unix-like operating system (not Windows) and get bind errors //only// when recycling servers:
Line 275: Line 290:
   sbbs: term 0001 Will retry in 15 seconds (1 of 2)   sbbs: term 0001 Will retry in 15 seconds (1 of 2)
  
-... this is most likely because a TCP session is stuck in a ''TCP TIMEWAIT'' state (you can use ''[[man>netstat]]'' to verify this). The session will eventually time-out and close properly on its own, allowing the port to be re-bound at that time. To work-around this problem, you can either increase the ''BindRetryCount'' and/or ''BindRetryDelay'' values in your ''[[dir:ctrl]]/[[config:sbbs.ini]]'' file, or you can add the following line to the root section of your ''[[dir:ctrl]]/[[config:sockopts.ini]]'' file: +... this is most likely because a TCP session is stuck in a TCP "TIME WAIT" or "CLOSE WAIT" state (you can use ''[[man>netstat]]'' to verify this). The session will eventually time-out and close properly on its own, allowing the port to be re-bound at that time. To work-around this problem, you can either increase the ''BindRetryCount'' and/or ''BindRetryDelay'' values in your ''[[dir:ctrl]]/[[config:sbbs.ini]]'' file, or you can add the following line to the root section of your ''[[dir:ctrl]]/[[config:sockopts.ini]]'' file: 
   REUSEADDR=1    REUSEADDR=1 
  

Trace: