Date: Thu, 30 Nov 2000 22:32:57 -0500 (EST) From: Jim Durham <durham@w2xo.pgh.pa.us> To: David Banning <david@www3.pacific-pages.com> Cc: tim hobbs <uniquely_tim@yahoo.com>, questions@FreeBSD.ORG Subject: Re: web hosting with a dynamic IP address question Message-ID: <Pine.BSF.4.21.0011302214250.42314-100000@shazam.int> In-Reply-To: <20001125224059.A607@www3.pacific-pages.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 25 Nov 2000, David Banning wrote: > Thanks for your response - > > Before I do all that - is it possible to find out what my running > IP address currently is, and access my computer by typing > http://123.456.7.8/myfiles.html > > or some such thing in my browser? > > > On Sat, Nov 25, 2000 at 09:54:35AM -0800, tim hobbs wrote: > > Hi David, > > > > > > > I would like to call into my computer and access it > > > like a web host > > > from somewhere else on the web. My thought is that > > > this should be possible > > > if my IP address is known. > > > > This is how I am doing it, if this helps: > > Interesting! I have been wondering about dynamic dns. What do they do about caching name servers? I find that changing the DNS entry takes a couple days to propagate.. Here's how I do it.. I have an "outside" server on a fixed IP. Perhaps you could do this at work, if you have a T1. This server is where the domain points. You can sell it to your boss because only the mouse clicks of the web user go through the outside server. The web pages go out through your dynamic IP's connection. At my house, I have a "local" server, where the web page actually runs. I have some processes running a ham radio mail service on radios that requires that the web server run on the same machine as the radios are connected to. This machine has a dynamic IP. I establish an SSH connection to the "outside" server and then use port redirection to forward port 80 from the "outside" server to the "local" server, where Apache runs. This is really easy with SSH. An added benefit is that you can always connect directly to your home machine if you want to from anywhere, because you can log into the "outside" server and do a "netstat -a" and see who's connected to port 22. Then, you can ssh or (less securly) telnet or ftp into your "local" machine from anywhere. You can write a little expect script to test the line occasionally in case your ISP goes down like mine does once in a while, so that the "tunnel" re-establishes itself on failure. The "outside" machine can be an old 486. Works for me... Jim Durham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0011302214250.42314-100000>