Projects tagged ‘port’ and ‘tunnel’

Allows you to port forward with Remote Desktop, in the same way that ssh has been able to for years.

Allow you to socksify outgoing connections by using a TUN device. Similar to SocksCap except it intercepts the TCP/IP data at network layer 3 instead of at network layer 4.

Socks via HTTP is a program converting SOCKS requests into HTTP requests and tunnelling them through HTTP proxies if needed. The SOCKS protocol allows programs to traverse firewalls on any port number ... [More] and is used by many popular programs, like Napster, MSN Messenger, CRT(telnet client) and many others. Many companies restrict firewall traversals only to HTTP requests, disabling SOCKS proxy. Socks via HTTP provides a miniature SOCKS server for the SOCKS client, performing its connection through an HTTP proxy to a remote server, which establishes the real connection. Please read carefully the INSTALL and DOCUMENTATION files. You can always get the last version of the program, and some documentation at http://cqs.dyndns.org Please send your feedback to socksviahttp@cqs.dyndns.org Thank you Florent CUETO & Sebastien LEBRETON socksviahttp@cqs.dyndns.org [Less]

Socks via HTTP is a program converting SOCKS requests into HTTP requests and tunnelling them through HTTP proxies if needed.The SOCKS protocol allows programs to traverse firewalls on any port number ... [More] and is used by many popular programs, like Napster, MSN Messenger, CRT(telnet client) and many others. Many companies restrict firewall traversals only to HTTP requests, disabling SOCKS proxy. Socks via HTTP provides a miniature SOCKS server for the SOCKS client, performing its connection through an HTTP proxy to a remote server, which establishes the real connection. Socks via HTTP is 100% Java, and can run on any OS. I - How it works II - As the program is 100% Java, you can use any OS combinaison you want: Server part 2b on Linux, Client part 2a on Windows. Both Server part and client part on Linux. Both Server part and client part on Windows. Server part 2b on Windows, Client part 2a on Linux. III - IV - Advanced description:1.The client part The client part of Socks via HTTP acts as a socks server. Your program (IRC, Telnet or whatever) connects to this socks server, thinking it is speaking with a real socks server. The socks via HTTP client communicates the socks via HTTP server using HTTP protocol. # The HTTP packets are zipped on the fly to speed up network transfer. 2 - Server part The server parts manages the real connections. As you know, HTTP is a disconnected protocol, ie you create a request, send it, and you got a response. There is no connection context (I suppose here that the proxy you have to bypass does not support keep alive). As a consequence, the context handling is the job of the Socks via HTTP server part. The server part manages a HashTable containing all the opened connections. Each connection has an unique id. This id is sended by the Socks via HTTP client part for each request. [Less]

See http://github.com/coderrr/rtunnel for latest version INSTALL on server and local machine: gem install rtunnel If you don't have root access on server, you can use either the ... [More] rtunnel_server_linux binary (only works with linux), or extract the .tar.gz and use rtunnel_server.rb (all function the same) USAGE on server (myserver.com): rtunnel_server on your local machine: rtunnel_client -c myserver.com -f 4000 -t 3000 This would reverse tunnel myserver.com:4000 to localhost:3000 so that if you had a web server running at port 3000 on your local machine, anyone on the internet could access it by going to http://myserver.com:4000 News 0.3.6 released, new protocol created gem for easier installation 0.2.1 released, minor bugfix, cmdline options change 0.2.0 released, much simpler 0.1.2 released Created rtunnel_server binary for linux so you don't need Ruby installed on the host you want to reverse tunnel from 0.1.1 released Added default control port of 19050, no longer have to specify this on client or server unless you care to change it RTunnel? This client/server allow you to reverse tunnel traffic. Reverse tunneling is useful if you want to run a server behind a NAT and you do not have the ability use port forwarding. The specific reason I created this program was to reduce the pain of Facebook App development on a crappy internet connection that drops often. ssh -R was not cutting it. How does reverse tunneling work? tunnel_client makes connection to tunnel_server (through NAT) tunnel_server listens on port X internet_user connects to port X on tunnel server tunnel_server uses existing connection to tunnel internet user's request back to tunnel_client tunnel_client connects to local server on port Y tunnel_client tunnels internet users connection through to local server or: establish connection: tunnel_client --NAT--> tunnel_server reverse tunnel: internet_user -> tunnel_server --(NAT)--> tunnel_client -> server_running_behind_nat How is this different than normal tunneling? With tunneling, usually your connections are made in the same direction you create the tunnel connection. With reverse tunneling, you tunnel your connections the opposite direction of which you made the tunnel connection. So you initiate the tunnel with A -> B, but connections are tunneled from B -> A. Why not just use ssh -R? The same thing can be achieved with ssh -R, why not just use it? A lot of ssh servers don't have the GatewayPorts sshd option set up to allow you to reverse tunnel. If you are not in control of the server and it is not setup correctly then you are SOL. RTunnel does not require you are in control of the server. ssh -R has other annoyances. When your connection drops and you try to re-initiate the reverse tunnel sometimes you get an address already in use error because the old tunnel process is still laying around. This requires you to kill the existing sshd process. RTunnel does not have this problem. [Less]