Re: Putting together a server/network...

[Chuck Yerkes <chuck@snew.com>]

Quoting Mike Ayers (mike.ayers@earthling.net):
> 	Please read the posts before answering them.
> Chuck Yerkes wrote:
> > You CAN do it.  It's not that hard either.
> > You DO NOT NEED A PUBLIC IP FOR EACH WEB SERVER.
> <SNIP/>
> > > >Local Union 824 wrote: 
> <SNIP/>
> > > > > DNS server.  I want more that using apache's virtual
> > > > > hosting as i want telnet, ssh, ftp, http, mail and a
> > > > > future bbs to hit the box when keyed in.
> > > > > I only have one public IP from the ADSL so all internal
> > > > > boxes will be internal IP's using NAT.
> <SNIP/>
> 	Virtual hosting does not support anything but HTTP.  An IP per external
> host is necessary to support the other services.
> 
> Mike

Damn you for reading ALL the words.
Ok, mail and web are easy.  ftp, ssh and perhaps BBS (old earth
term) require a unique IP address.  How important are these?

FTP can just use different directories (many OpenBSD repositories
also house /pub/NetBSD/).

ssh - well, if you have an ssh population, you can either
forward different ports back to the machines or have them start
from one machine.

BBS?  This is perhaps an nntp server and a web front end?

I forbid the use of telnet.  By you, by anyone.  Just say "no,
thank you"

It's unlikely that you'll jump at getting IPv6 up, since you'd
get millions of addresses when you attach the the 6bone.
Somehow, I don't see telling the local 824 guys that they have
to have IPv6 to get to the BBS as a successfull endeavor.  (tho
I have told sales guys that they can only ftp from my server
via IPv6 - it keeps the requests down:)