Shulou(Shulou.com)06/03 Report--

Case 1:

A: public network IP (129.28.X.X)

B: private IP (192.168.X.X)

Without considering the firewall and other reasons, B can SSH to A remotely, but A cannot SSH to B (because B is a private network IP).

For some reason, An is now required to access B, (you can guess what to do first, is it OK? I don't know.)

Description: as long as other people can access A (public network IP), they can also access B through A.

Do the following:

# execution of host B (then enter the password of A):

Ssh-R 6121VR 127.0.0.1 Nf 22 129.28.X.X-Nf

Parameter description:

-R forwarding

The port to be opened by 6121 A server

127.0.0.1 forwarding target (this test is a B host, which can also be replaced with other hosts that B can access, so that A can access other hosts through B)

: 22 Port of the forwarding destination

-enable Nf backend, do not open shell

Test: connect to local port 6121 on server A

# Host An executes (then enter B's password):

Ssh localhost-p 6121

Scenario: a has a virtual machine on his own computer and a virtual machine on computer B, but they are not in the same network segment. Through the appeal method, as long as they can access the same server (often on the public network), then they can communicate. If you are interested, you can fix it by yourself.

Note: if an error Permission denied (publickey,gssapi-keyex,gssapi-with-mic) is reported when ssh, add a line PasswordAuthentication yes to the / etc/ssh/sshd_config file

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.