Differences

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

--- faq:tcpip [2018/06/05 21:45] – Added FAQ for SSH error: importing session key to protect private key digital man
+++ faq:tcpip [2024/11/02 13:48] (current) – [Ports] List the disabled service ports too (for reference) digital man
@@ Line 11: / Line 11: @@
   * [[#ftp_connect|Why can't users connect to my FTP server]]?
   * [[#ftp_nat|Why do FTP clients lock-up or time-out when listing directories or downloading files from my FTP server]]?
+  * [[#ftp_html|Why won't a web browser render HTML content from my FTP Server]]?
   * [[#bind|Why do some or all of my servers get bind errors when starting or recycling]]?
   * [[#bandwidth|How many nodes/clients/users can I support with my Internet connection]]?
   * [[#block_hackers|Can Synchronet automatically block the IP address of hackers]]?
-  * [[#ssh_kex_algo|Why do some SSH clients fail to connect to my BBS]]?
+  * [[#ssh_algo|Why do some SSH clients fail to connect to my BBS]]?
   * [[#ssh_session_key|How do resolve the SSH error: importing session key to protect private key]]?
@@ Line 31: / Line 32: @@
 |SSH	        |22	|-	|For SecureShell logins (recommended)|
 |RLogin	        |513	|-	|Optional for quick-login from RLogin clients (e.g. SyncTERM)|
-|SMTP	        |25	|-	|Necessary for receiving Internet e-mail and inter-BBS instant messages|
+|SMTP	        |25	|-	|Necessary for receiving Internet e-mail |
 |Submission     |587	|-	|Necessary for users to send Internet e-mail through the BBS from a standard e-mail client|
+|Submission/TLS |465	|-	|Necessary for users to send Internet e-mail through the BBS from a standard e-mail client using TLS((encrypted communications over TCP))|
 |POP3	        |110	|-	|Allows BBS users to check their e-mail using standard Internet mail clients (e.g. Outlook Express)|
+|POP3/TLS       |995	|-	|Allows BBS users to check their e-mail using standard Internet mail clients (e.g. Outlook Express) using TLS|
 |FTP	        |21	|-	|Allows access to the BBS file/download areas using a standard FTP client or web browser|
 |HTTP	        |80	|-	|Required for access to the BBS's web server|
+|HTTPS	        |443	|-	|Required for secure access to the BBS's web server using TLS|
 |NNTP	        |119	|-	|Allows BBS users to read and post messages using standard news readers/clients|
 |Gopher	        |70	|-	|Archaic protocol allows reading of messages and other BBS info|
 |IRC	        |6667	|-	|Allows Internet Relay Chat (IRC) clients to connect to your BBS|
-|Finger	        |79	|79	|Allows remote querying of BBS user info, who's online, and other BBS info|
+|Finger	        |79	|	|Allows remote querying of BBS user info, who's online, and other BBS info|
-|SYSTAT	        |11	|11	|Allows remote querying of who's online (aka Active Users)|
+|SYSTAT	        |11	|11	|Allows remote querying of who's online (aka Active Users) required for [[module:sbbsimsg|inter-BBS instant messaging]]|
-|QOTD	        |17	|17	|Allows remote querying of the current auto-message (aka Quote Of The Day)|
+|MSP	        |18	| 	|Allows incoming [[module:sbbsimsg|inter-BBS instant messages]]|
-|MSP	        |18	|18	|Allows incoming inter-BBS instant messages without SMTP connectivity|
+|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 |
+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.
@@ Line 203: / Line 222: @@
 [[http://www.ncftpd.com/ncftpd/doc/misc/ftp_and_firewalls.html|This document]] contains the technical details about how and why and the recommended solutions.
-**Note**: Most web browsers (e.g. //Microsoft Internet Explorer//) use passive FTP transfer mode by default.
+**Note**: Most web browsers use //passive// FTP transfer mode by default, though this may be configurable.
-**Note**: Some FTP clients (e.g. the Windows command-line FTP client, ''ftp.exe'') only support active mode transfers.
+**Note**: Some FTP clients (e.g. the Windows command-line FTP client, ''ftp.exe'') //only// support //active// mode transfers.
-Enabling the logging of FTP data channel activity can help diagnose these kinds of problems. This can be done by adding the ''DEBUG_DATA'' option to the ''Options'' value in the ''[FTP]'' section of your ''[[dir:ctrl]]/[[config:sbbs.ini]]'' file or by checking the //Data Channel Activity// checkbox in the //Log// tab of the FTP Server Configuration dialog in the Synchronet Control Panel for Win32.
+Enabling the logging of FTP data channel activity can help diagnose these kinds of problems. This can be done by adding the ''DEBUG_DATA'' option to the ''Options'' value in the ''[FTP]'' section of your ''[[dir:ctrl]]/[[config:sbbs.ini]]'' file or by checking the //Data Channel Activity// checkbox in the //Log// tab of the FTP Server Configuration dialog in the Synchronet Control Panel for Windows.
-If you're having problems with passive transfers and you're seeing
-  !UNSUPPORTED COMMAND from username: 'P@SW'
-in your FTP server log/window output, you're probably using an //SMC Barricade// router (see [[http://www.gbnetwork.co.uk/smcftpd/|this document]] for details). Upgrade to Synchronet v3.13a (FTP Server Revision 1.296) or later to work-around this problem with this device.
 If you're having problems with passive (PASV) transfers through your NAT/firewall device and you're running Synchronet v3.13a (FTP Server Revision 1.296) or later:
-If the remote client is attempting to connect to your [[#private IP]] address (your NAT device isn't translating the PASV response from the FTP server) and you have a static [[#public IP]] address, you can work-around this limitation of your NAT device by using the ''PasvIpAddress'' value in the ''[FTP]'' section of your ''[[dir:ctrl]]/[[config:sbbs.ini]]'' file to specify your [[#public IP]] address.
+If the remote client is attempting to connect to your [[#private IP]] address (your NAT device isn't translating the PASV response from the FTP server) and you have a static [[#public IP]] address, you can work-around this limitation of your NAT device by using the ''PasvIpAddress'' value in the ''[FTP]'' section of your ''[[dir:ctrl]]/[[config:sbbs.ini]]'' file to specify your IPv4 [[#public IP]] address.
 This problem can be identified (on the client) by finding a comma-separated [[#private IP]] address in the PASV response received from the FTP server (in response to a directory or file transfer request from the client).
@@ Line 236: / Line 251: @@
 If you have a dynamically-assigned IP address (via DHCP), then your IP address may change at some point, so setting the ''PasvIpAddress'' to a specific IP address may not be a long term solution for your FTP Server. In Synchronet v3.14a and later, you can enable the new //Lookup Passive IP// feature by checking the //Lookup// checkbox on the //Passive// tab of the FTP Server Configuration Dialog in [[monitor:SBBSCTRL]]-Win32, or by adding ''LOOKUP_PASV_IP'' to the Options value in the ''[FTP]'' section of your ''[[dir:ctrl]]/[[config:sbbs.ini]]'' file. This option instructs the Synchronet FTP Server to perform a DNS hostname lookup on your BBS's public hostname and use the resulting IP address (which should be your BBS's [[#public IP]] address) in passive responses.
-If your firewall cannot dynamically open/forward FTP PASV data ports for incoming passive FTP data connections, you can specifiy a limited range of TCP port numbers to use for passive transfers by modifying the PasvPortLow and PasvPortHigh values in the ''[FTP]'' section of your ''[[dir:ctrl]]/[[config:sbbs.ini]]'' file. You will of course need to configure your firewall device to open/forward these ports to your FTP server.
+If your firewall cannot dynamically open/forward FTP PASV data ports for incoming passive FTP data connections, you can specify a limited range of TCP port numbers to use for passive transfers by modifying the PasvPortLow and PasvPortHigh values in the ''[FTP]'' section of your ''[[dir:ctrl]]/[[config:sbbs.ini]]'' file. You will of course need to configure your firewall device to open/forward these ports to your FTP server.
+===== FTP HTML =====
+:?: **Question:**\\
+Why will a web browser not (no longer) render the HTML content sent by the Synchronet FTP Server (i.e. ''00index.html'' generated by ''ftp-html.js'')?
+:!: **Answer:**\\
+For security reasons, modern web browsers (e.g. Google Chrome) have stopped rendering HTML content served by protocols other than HTTP or HTTPS.
+  * [[https://www.bleepingcomputer.com/news/google/chrome-and-firefox-developers-aim-to-remove-support-for-ftp/]]
+Some web browsers (e.g. Microsoft Edge) are removing FTP support altogether.
+  * [[https://www.ghacks.net/2020/03/19/mozilla-will-remove-ftp-support-in-the-firefox-web-browser/]]
 ===== Bind =====
@@ Line 250: / Line 276: @@
 This usually means you have another TCP/IP server on your system that is already bound to (and is presumably already listening for incoming connections on) this port. This could be a pre-existing instance of Synchronet or any other Telnet/Web/Mail/FTP servers that you may have installed on your system. You can use utilities such as ''[[man>netstat]]'' (for Windows or Unix((e.g. 'netstat -naptu' as root user on Linux))) or [[http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx|TCPView]] (for Windows) to verify what programs (if any) have the TCP or UDP port in question already bound. If these utilities do not report any program is bound to (and listening) on this port, you can try Telnetting to the port in question and see if anything answers. If you're unable to connect to the port with a Telnet client and Synchronet cannot bind the port, your TCP/IP stack probably needs to be reset, so a system reboot may be in order.
-If you're running a Unix-like operating system (not Windows) and get bind errors only when recycling servers, 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 your ''[[dir:ctrl]]/[[config:sockopts.ini]]'' file:
-  REUSEADDR=1
 :!: **Answer:**\\
@@ Line 259: / Line 282: @@
 Error ''13'' means "access denied".
-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).
+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:**\\
+If you're running a Unix-like operating system (not Windows) and get bind errors //only// when recycling servers:
+  sbbs: term 0001 !ERROR 98 binding Telnet Server socket to port 23
+  sbbs: term 0001 Will retry in 15 seconds (1 of 2)
+... 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
 ===== Bandwidth =====
@@ Line 296: / Line 329: @@
 Yes, see [[howto:Block-Hackers]] for detailed instructions.
-===== SSH Kex Algo =====
+===== SSH Algo =====
 :?: **Question:**\\
 Why do some SSH clients (e.g. [[http://www.openssh.com/|OpenSSH]]) fail to connect to the Synchronet SSH Server?
+:!: **Answer:**\\
+SSH supports a variety of cryptographic algorithms for encryption (privacy), integrity (mac) and authentication (key-exchange). As stronger algorithms are introduced, older (less-strong) algorithms are deprecated. As a result, when using a newer version of any SSH client (especially OpenSSH), it may fail to connect to SSH servers which only support less-than-the-strongest (newest) algorithms. There is no permanent solution to this issue as cryptographic algorithms are constantly improving (becoming stronger) and older (weaker) algorithms are going out of favor.
+==== SSH Cipher Algo ====
+Should be fixed as of Fri Feb 14 07:37:04 2020 UTC. aes128-ctr and aes256-ctr support was added.
 Example:
   $ ssh vert.synchro.net
-  $ Received disconnect from 71.95.196.34: 2: Handshake failed
+  Unable to negotiate with vert.synchro.net port 22: no matching cipher found. Their offer: aes128-cbc,3des-cbc
-or:
+Workarounds for OpenSSH:
-  Unable to negotiate with legacyhost: no matching key exchange method found.
-  Their offer: diffie-hellman-group1-sha1
-:!: **Answer:**\\
+  $ ssh -c aes128-cbc user@yourbbs.com
+or in the ''~/.ssh/config'' file (OpenSSH v6):
-//**NOTE: This has been fixed in CVS now.**//
+  Host yourbbs.com
+  Ciphers aes128-cbc
+==== SSH Kex Algo ====
-Synchronet uses [[http://www.cs.auckland.ac.nz/~pgut001/cryptlib/|Cryptlib]], a cryptographic library, for SSH and TSL/SSL support in Synchronet. Cryptlib's v3.4.2 SSH support uses an older "Key Exchange Algorithm". OpenSSH has deprecated support for this older key exchange algorithm. Cryptlib v3.4.4, the currently latest version of Cryptlib now used by Synchronet, does not have this problem.
+Should be fixed as of Mon Jun 3 22:21:15 2019 UTC. diffie-hellman-group-exchange-sha256 and diffie-hellman-group14-sha256 support was added.
+Example:
+  $ ssh vert.synchro.net
+  Received disconnect from 71.95.196.34: 2: Handshake failed
+or:
+  Unable to negotiate with legacyhost: no matching key exchange method found.
+  Their offer: diffie-hellman-group1-sha1
 From the OpenSSH [[http://www.openssh.com/legacy.html|legacy page]]:
@@ Line 336: / Line 388: @@
 Note: Run ''ssh -V'' to see what version of OpenSSH you have.
-:!: **Answer:**\\
+==== SSH MAC Algo ====
+Should be fixed as of Mon Jun 3 22:21:15 2019 UTC. hmac-sha2-256 support was added.
 Another observed problem is with the negotiated Message Authentication Code (MAC) algorithm.
@@ Line 352: / Line 407: @@
 Rename/move or delete your ''[[dir:ctrl]]/cryptlib.key'' file.
+If you're using TLS for your other [[server:|Synchronet servers (e.g. web, mail, ftp, etc.)]], you may also need to rename/move or delete your ''[[dir:ctrl]]/ssl.cert'' file.
+These files (''cryptlib.key'' and ''ssl.cert'') are encrypted with the Synchronet //system password//, so if the system password is changed then these files must also be regenerated. The files are automatically recreated by //sbbs// upon startup if they do not already exist.
 ===== See Also =====
   * [[:server:|Servers]]

Trace:

Differences

Navigation

Search

Toolbox