[Sluglug] IDE HD transfer and crossover cables.

[cerise at armory.com]

DynDNS is short for Dynamic DNS.  Basically, dyndns.org (for example) runs
DNS for a number of domains.  So you can run a client which pings them and
reports your new address and your preferred domain.  So if you have
myserver.gotdns.com through them, you turn your system on, it runs dhcp,
gets a random address, and you run your client pinging them to report
the new address of myserver.gotdns.com.

Your friends go to myserver.gotdns.com and everything just works.

Apache will run https (which is just like http, but secure.  It also has
a well established port on 443).  You could just keep your box on port 81,
but that means that anyone accessing your page would have to type
http://your-server-ip-here:81 every time.  That's kind of annoying.  8)

The campus has nothing against dyndns AFAIK, aside from possibly making it
even easier to cost the university tons of cash by making it easier to have
xfers off campus.  I'd be surprised if anyone was bothered by it, but booloo
could do a much better job of answering about campus policy than I can 8)  
After all, he works there ; )

Oh, and re: his job posting.  It wasn't half bad when I had that job 8)

-Phil/CERisE

On Thu, Oct 06, 2005 at 01:48:58PM -0700, Erich wrote:
> I've never even heard of dyndns - and will Apache run an https service?
> Honestly, the only thing the page is for is for friends on the campus to be
> able to upload/download to a CVS (actually an SVN), and for me to keep a
> little blog. I've got the apache bit set up, running on port 81... But it
> seems the wireless computers can't see it? I don't know, I've tested it on
> my wireless laptop and the server itself, the server can connect to it's own
> IP, but the laptop just works until it times out. Would dyndns fix that? Is
> dyndns legal on this campus? Isn't https overkill for this purpose?
> 
> Thanks!
> 
> -Erich