Xshell proxy settings

Keywords: xshell proxy; xshell setting proxy

The client of the customer node can connect to the middle node middle. The middle node middle can connect to many other service nodes, such as A1 and A2. However, the client and service nodes A, B, and C cannot communicate with each other.

At this point, I want to directly connect to service nodes A1 and A2 on the customer node, such as accessing the Web Services on node A, using SSH to directly log on to node A, and display the image interface to xmanager. In this case, you need to set a proxy to complete these functions. The detailed settings are as follows:

Create an intermediate node on the client of the customer NodeMiddleSelect connection --> SSH --> tunneling, add under the TCP/IP forwarding option, type is dynamic (socks4/5), and listen port is1080Save the connection, for example, middle.

 

Create a connection to service node A1 on the client of the customer node. The host is the IP address of the A1 node. Make the following settings in the proxy server item (under the connection item: click the browser button and add a proxy on the pop-up interface. Select SOCKS5 for type, which is assumed to be prox1 and hostLocalhost, Port1080, Which corresponds to the port number set in the intermediate node. Save the connection. For example, the connection name is A1.

 

After setting, log on to the intermediate node middle through the middle connection on the client. After the connection is successful, you will see this proxy in xshell, in the forwarding rules on the bottom panel, the proxy status is open.

Then, log on to the service node A1 by connecting A1 on the customer node. If you want to log on to the service node A1, select forward X11 connections to: xmanager under SSH --> tunneling of connection.

If you want to access the Web server on service node A1 through a browser on the Client client, you only need to set the browser proxy. In Firefox, you can set tools, options, advanced, and network, set and manually configure the proxy. EnterLocalhost, Port
1080Other items are not required. OK. Use http: // A1: 8080 directly after setting.

 

 

 

If service node A1 is connected to other nodes, such as B1, B2, and B3, but the intermediate node cannot be connected to them (b1, b2), we can continue to configure the proxy, this allows the customer machine to directly access B1 and B2. In this case, you only need to set the xshell A1 connection (the connection created when A1 is connected), add a proxy, localhost: 10801 (set different port numbers, the same steps as above ). After that, use xshell to create a connection to B1 (the same as above). The proxy selects the newly created proxy localhost: 10801, assuming the name is prox1. After completion,First, log on to the intermediate node and then log on to the A1 node (ensure that the two nodes are successfully logged on and the proxy is created successfully)Then you can directly connect to the B1 node through B1. In this way, the client-to-B connection is completed through multi-layer proxy.

 

 

 

In this case, if you need to directly access the URL on the B1 node in the web browser, you can set the Firefox proxy, which is the same as the method above, but the port number is set to 10801. At this time, you can still directly access the URL (?) on B1 (?).

 

Principle:

After successfully logging on to the intermediate node using the middle connection,
Xshell creates a proxy: localhost: 1080, which is local to the client. Then, when the client connects to service node A to log on to service node A, it will access service a through this proxy.