это от 10.0.0.12
tracepath 192.168.1.26
1: 10.0.0.12 0.109ms pmtu 1500
1: 10.0.0.100 0.471ms
1: 10.0.0.100 0.369ms
2: 10.0.0.100 0.416ms pmtu 1476
2: 192.168.10.10 4.588ms
3: 192.168.1.26 6.438ms reached
Resume: pmtu 1476 hops 3 back 62
tracepath 192.168.0.22
1: 10.0.0.12 0.057ms pmtu 1500
1: 10.0.0.100 0.405ms
1: 10.0.0.100 0.408ms
2: 10.0.0.100 0.307ms pmtu 1476
2: 192.168.10.2 52.746ms
3: 192.168.0.22 54.215ms reached
Resume: pmtu 1476 hops 3 back 62
это от 192.168.1.26
tracepath 192.168.0.22
1: 192.168.1.26 0.230ms pmtu 1500
1: 192.168.1.1 0.952ms
1: 192.168.1.1 0.984ms
2: 192.168.1.1 2.362ms pmtu 1476
2: 192.168.10.5 9.109ms
3: 192.168.0.22 10.988ms reached
Resume: pmtu 1476 hops 3 back 62
tracepath 10.0.0.12
1: 192.168.1.26 0.276ms pmtu 1500
1: 192.168.1.1 1.011ms
1: 192.168.1.1 0.964ms
2: 192.168.1.1 0.984ms pmtu 1476
2: 192.168.10.9 6.200ms
3: 10.0.0.12 5.313ms reached
Resume: pmtu 1476 hops 3 back 62
от 192.168.1.26 спокойно подключаюсь по ssh на 10.0.0.12, обратно не хочет, при этом обратно по тому же vnc или по rdp цеплется легко.
вот cat /etc/ssh/
moduli ssh_host_dsa_key.pub ssh_host_rsa_key.pub
ssh_config ssh_host_ecdsa_key ssh_import_id
sshd_config ssh_host_ecdsa_key.pub
ssh_host_dsa_key ssh_host_rsa_key
root@ogni-voshod-06:~# cat /etc/ssh/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
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes
# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 768
# Logging
SyslogFacility AUTH
LogLevel INFO
# Authentication:
LoginGraceTime 120
PermitRootLogin yes
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