Re: RFC: new network config (was: Re: network configuration)
On Sun, Feb 07, 1999 at 04:08:37PM +1000, Anthony Towns wrote:
> > (alternatively, if you want to handle ip_alias ifconfig in netbase,
> > that's fine too. would be nice to have some extra data in your
> > /etc/interfaces file, though...to avoid duplication of config data.)
> What I was thinking of was something like:
> eth0 220.127.116.11 # This is my real IP
> eth1 192.168.200.1 # But I'm also a masq g/w for this network
> eth0:0 18.104.22.168 # I also run a virtual ftp server on this
> # address
i'm against hardcoding the eth0:n alias number into a config file. it
gets clumsy when you've got a few hundred aliases on a machine. let a
script count it.
i.e. ip-aliases should have their own config file, rather than clutter
up the main /etc/interfaces. whether this is done in netbase or a
virtual-services package doesn't really matter.
> www.freakystuff.com apache,analog
> ftp.freakystuff.com proftpd
i was thinking more of something like:
and have ftp.freakystuff.com be a CNAME for www.freakystuff.com - if
they're both running on the same machine, there's no need to waste two
ip addresses for them.
if one machine is handling ftp services and another is handling www
services, then they can each have config files like so:
one other thing that occurs to me is that there should be a flag for
"no_ip_alias", to support name-based virtual hosting with apache. i.e.
where you use CNAMEs to point to one IP address, and apache uses the
HTTP "Host: " header to figure out which virtual is being requested.
http doesn't really need a dedicated IP anymore (except to support older
browsers). ftp and pop and other services do.
> 22.214.171.124 ftp.freakystuff.com
> 126.96.36.199 www.freakystuff.com
excessive use of /etc/hosts is evil :-)
either install bind or rely on an existing name server on the LAN