Telnet非交互式连接异常解析：TCP RST原因及交互模式必要性

Let's walk through both scenarios and clear up the confusion around Telnet's behavior and interactive requirements—this is stuff I've dug into many times when debugging network connectivity.

Scenario 1: Non-interactive Telnet throws "connection closed by foreign host" #

When you run a basic telnet host_ip port without entering any interactive input (or run it in a non-interactive context like a script without feeding input), the most common cause is the Telnet server's idle timeout or authentication requirements. Here's the play-by-play:

1. Your client completes the TCP three-way handshake with the server (so the connection is established initially).
2. Many Telnet servers are configured to expect an interactive login (username/password prompt) immediately after connection. If no input is received within a set timeout window, the server will send a TCP FIN packet to gracefully close the connection.
3. Your Telnet client receives this FIN, interprets it as the server terminating the link, and outputs the "connection closed by foreign host" message.

Scenario 2: telnet host_ip port < /dev/null with client-side RST #

This one's all about how Telnet handles standard input (stdin). Let's break down exactly what happens here:

1. The telnet command starts, initiates the TCP three-way handshake, and successfully connects to the server—hence the output: Trying host_ip... Connected to host_ip. Escape character is '^]'.
2. But since you've redirected stdin to /dev/null, the client immediately detects that there's no input coming (stdin hits EOF right away).
3. Depending on your Telnet client implementation (common in many Unix-like systems), when stdin is closed unexpectedly without any interactive session setup, the client will send a TCP RST packet instead of a graceful FIN. This is a "hard close" that tells the server to terminate the connection immediately.
4. The server receives the RST and closes the connection, which triggers the client to print "Connection closed by foreign host"—even though the client initiated the RST, the message reflects the server's side of the closure.

Does Telnet have to run in interactive mode? #

Absolutely not. Telnet is perfectly capable of non-interactive use cases, though you need to account for client/server behavior:

• Port testing: The most common non-interactive use is just checking if a port is open (e.g., telnet google.com 80—you don't need to send any data, just confirm the connection is established).
• Scripted commands: You can pipe input to Telnet for automated tasks. For example:

  echo "GET / HTTP/1.1\r\nHost: example.com\r\n\r\n" | telnet example.com 80
  

  This sends an HTTP GET request via Telnet without any interaction.
• Client flags: Many Telnet clients support flags to tweak non-interactive behavior. For example, -l to specify a username upfront, or -e to change the escape character if needed.

The key gotcha is that different Telnet implementations handle stdin closure (like the /dev/null case) differently—some send RST, some send FIN, but that's just implementation-specific behavior, not a requirement for interactive mode.

内容的提问来源于stack exchange，提问作者pepero