<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Thanks for everyone's recommendations. What I didn't realize at the time of the initial post was there is a Satellite modem/router that sits in between the sshd and internet and performs NAT. Nobody knows how or wants to touch this satellite modem thingy.<br><br>Obviously, this makes things more difficult to reach the sshd directly from the internet.<br><br>Also, what I didn't realize was that there are a few other computers on this network. And that it is okay to require some level of user-interaction (in Haiti) to initiate a remote session.<br><br>As a result, I set up uVNC SC (http://uvnc.com/addons/singleclick.html) on a windows machine in the Haiti network that points to a DynDns VNC listener host. Voila! The person on the Haiti network just double-clicks the uVNC icon and starts a VNC session to California. Then the
engineer can startup Putty on the Haiti windows computer and connect to the embedded sshd device.<br><br>So, again, thanks for all your suggestions. Although the engineers in California would rather just have remote access on demand directly to the embedded sshd device, this method works well enough.<br><br>-Chaz<br><br><br>--- On <b>Fri, 11/21/08, Justin Krejci <i><jus@krytosvirus.com></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">From: Justin Krejci <jus@krytosvirus.com><br>Subject: RE: ssh reverse connection<br>To: chaz_meister_rock@yahoo.com, openbsd-newbies@sfobug.org<br>Date: Friday, November 21, 2008, 6:12 AM<br><br><pre>I have written a perl script that will try to determine your public IP<br>address if you are using NAT. In a nutshell what it does is make an HTTP<br>call to various websites that will reply with your source IP. It then tracks<br>changes to
your IP. You can call the script regularly from cron. When it<br>notices a change it generates an email with the IP address info.<br><br>A previous method I used was for a simple HTTP request to go to my personal<br>web server to some non-existent file (gets a 404) then I had a cgi on the<br>web server that would parse the log for requests to that URL and return the<br>log entry to the browser.<br><br>Email me directly if you're interested.<br><br></pre></blockquote></td></tr></table><br>