Dua For Babies Having Stomach Pain

Goodbye Ubuntu, Gnome

Peer-to-peer (P2P) connections from a private computer to another personal computer over the Internet thanks to accomplish today in almost all routers used NAT functionality not easy. On the side, the "play" server should still be the router configured to forward port ("port forwarding

"). The following figure illustrates the problem. If the port is not forwarded properly, can to connect the client with the server. The lower arrow, however, shows the connection with configured port forwarding.

However, there is sometimes the problem is that you can pass on that system either can not or that the port can not cope with the opposite configuration. Especially with a remote desktop connection in which you want help with a computer problem is that often the case. Although most such systems are already at ease with the house building a Reverse Connection (such as VNC), but you can still come across applications, where such a functionality is missing. Since it would be good if the entire connection can build backward, so that no one but the other self forward this port must.

It can be with simple command-line tools to build any connection backward. The most suitable is socat

: Socat is an excellent program that can combine different data streams together. This is exactly what you can do is quite simple: churning

Socat The client on the actual server side connects with both the actual server and with a Socat server on the client side. The client then connects to the server Socat. Since both instances Socat forward the data streams each (Input → Output and vice versa), client and server can now communicate as usual with one another:

But looks like from a practical implementation? First of all you have to leave on the client side, the port forward the router. In the following example, worked with Port 55 555. Now we start on the client side, the Socat server: socat TCP-LISTEN

: 55555 TCP-LISTEN: 8080

Socat The server now listens on ports 55 555

and 8080 (the client connects to later on that port) and connects them.

On the server side of the Socat client starts:

socat TCP: hostname: 55555 TCP: localhost: 8080 So there is a connection to Socat server is established (the

hostname must be modified accordingly be and must be known, of course, but the IP is simply a page, www.wieistmeineip.de

find out.), and this is connected to the local server (in this case the server listens on port therefore

8080, therefore the alternative HTTP port).

Last you need to connect only the client with the Socat server. This requires data only on the compound localhost and the corresponding port change (in the example

8080).

course is easy to see that the effort is not to be underestimated. But it may do in some situations paid off handsomely. And not as technically savvy users must be on the other hand, no longer a port forwarding and take care of its IP address. The command can also be easily transferred via Instant Messenger, so that the command will be copied only in a terminal needs. Of course, the approach is not for other application very useful.