更新
- 所以我测试了另一台计算机，我可以外部连接到 SSH。所以看起来我在 Ubuntu 服务器网络配置中遇到了路由问题。有人能帮我找出是什么原因导致 Ubuntu 服务器只接受来自私有 IP 而不接受外部 IP 的连接吗？- 防火墙已被验证已禁用，所以我认为这一定是路由问题。
我正在尝试设置 SSH，以便可以远程管理我的家庭网络。我能够在连接到 LAN 时进行连接，包括指定我的外部 IP 地址。我在路由器上启用了端口转发，并在我的服务器上验证了端口转发正在与 TCP dump 配合使用：
sudo tcpdump -i enp2s0f0 port 22 -n -Q inout
23:52:13.322036 IP [REDACTED].7754 > 192.168.1.230.22: Flags [S], seq 2665018728, win 65535, options [mss 1388,sackOK,TS val 361680193 ecr 0,nop,wscale 9], length 0
23:52:14.242965 IP [REDACTED].7754 > 192.168.1.230.22: Flags [S], seq 2665018728, win 65535, options [mss 1388,sackOK,TS val 361681194 ecr 0,nop,wscale 9], length 0
23:52:16.240930 IP [REDACTED].7754 > 192.168.1.230.22: Flags [S], seq 2665018728, win 65535, options [mss 1388,sackOK,TS val 361683210 ecr 0,nop,wscale 9], length 0
当我连接到 LAN 并运行相同的命令时，我看到服务器响应并且能够连接。
这是我的 sshd_config 的副本：
# Package generated configuration file
# See the sshd_config(5) manpage for details
# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
HostKey /etc/ssh/ssh_host_ed25519_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes
# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 1024
# Logging
SyslogFacility AUTH
LogLevel INFO
# Authentication:
LoginGraceTime 120
PermitRootLogin prohibit-password
StrictModes yes
RSAAuthentication yes
PubkeyAuthentication yes
#AuthorizedKeysFile %h/.ssh/authorized_keys
# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
#IgnoreUserKnownHosts yes
# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no
# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no
# Change to no to disable tunnelled clear text passwords
#PasswordAuthentication yes
# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no
#MaxStartups 10:30:60
#Banner /etc/issue.net
# Allow client to pass locale environment variables
AcceptEnv LANG LC_*
Subsystem sftp /usr/lib/openssh/sftp-server
# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication. Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes
我还确保防火墙已被禁用：
sudo ufw disable
Firewall stopped and disabled on system startup
任何帮助都将不胜感激，我第一次无法找到解决方案。
谢谢！