Zachery Bir  <zbir@urbanape.com> wrote:
+---------------
| "Stefan Schmiedl" <s@xss.de> said:
| > I have a web app running at a client site, where apache limits access
| > to the local network. So I usually ssh into the site and use lynx to
| > access the web app. Reconfiguring apache to allow access to my dynamically
| > allocate IP address is error prone.
| 
| Sounds like you want ssh tunneling. If the webapp runs on the machine 
| you ssh to, do this instead:
|   $ ssh -L 8080:web-app-host:80 client-host
| Then hit localhost:8080 in a browser of your choice and you get the webapp.
+---------------

Also note that OpenSSH 2.x provides the "-D port" option, which 
allows the SSH client to act as a SOCKS proxy forwarding to the
remote location. This can be useful when you want to look at the
world (the Internet) from the remote system's point of view. E.g.:

    $ ssh -D 8008 client-host

then set your browser to use localhost:8008 as a SOCKS proxy.
Now when you ask for "web-app-host" both the name lookup and
the data traffic occur over the tunnelled SOCKS proxy port.


-Rob

-----
Rob Warnock			<rpw3@rpw3.org>
627 26th Avenue			<URL:http://rpw3.org/>
San Mateo, CA 94403		(650)572-2607