`<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 17, 2013 at 4:55 PM, Marion Hakanson <span dir="ltr"><<a href="mailto:hakansom@ohsu.edu" target="_blank">hakansom@ohsu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im"><br>
<a href="mailto:jesus@omniti.com">jesus@omniti.com</a> said:<br></div><div class="im">
> 2) using a browser remotely sounds painful... try ssh options to either<br>
> forward a port (-L) or act as a SOCKS proxy (-D) both *super* useful.<br>
<br>
</div>Perhaps painful is in the eye of the beholder. Using "ssh -X" or "ssh -Y"<br>
and running firefox on the remote server "just works". Maybe I'm missing<br>
something, but "ssh -L" for connecting to a Dell server's DRAC-Enterprise<br>
or other embedded webserver takes a fair amount of trial and error to suss<br>
out what ports, URL's, and/or hostnames their developers require in order<br>
to work. E.g. the DRAC-Enterprise, or SuperMicro BMC's often have some<br>
kind of remote KVM java app built into them, and those have their own<br>
obscure assumptions about connectivity, too.</blockquote><div><br></div><div style>You should look at -D</div><div style><br></div><div>Currently the SOCKS4 and SOCKS5 protocols are supported, and ssh will act as a SOCKS server. </div>
<div><br></div><div style>Makes ssh super for desktop apps (more than just browsers) to act as if they are in the DC.</div></div><div><br></div>-- <br>
<p>Theo Schlossnagle</p>
<p><a href="http://omniti.com/is/theo-schlossnagle" target="_blank">http://omniti.com/is/theo-schlossnagle</a></p>
</div></div>
`