Oh ok, I thought you were saying on the same Ethernet card (NIC).
You''re
meaning the same network aren''t you.
Yes, you could have that on two different machines, no problem there. The
aliasing is done on the machine, not the network. Just because an IP is an
alias on one of your machines means nothing really to the outside world,
it''s treated like any other.
Aliases are per-interface too, not just per machine. You could in theory
have 4 Ethernet cards in one machine and alias 1000 IPs to each of them..
Every interface would have an alias 1, 2, 3, and so on.. There wouldn''t
be
any problem there.
The most I''ve ever had on a single interface would have probably been
about
200. But I had absolutely no trouble with it at that (small) number..
To my knowledge there is no limit to the number of aliases you can have as
such. If there is, I''m sure it''s a very, very big number.
- Mitch
----- Original Message -----
From: Jeff Halper <jeff@ihot.com>
To: <redhat-secure-server@redhat.com>
Sent: Wednesday, September 08, 1999 1:25 PM
Subject: Re: virtual host limitations
> Maybe this question was pretty vague - I''m trying to determine if
there is
a> finite # of eth0:1 through eth0:9999999, and if each use of a
eth0:somenumber> needs to be unique for the entire ethernet.
>
> If I have this entry in rc.local on server 1 for www.domain1.com at
> 207.211.187.24
>
> /sbin/ifconfig eth0:24 207.211.187.24 netmask 255.255.255.255 broadcast
> 207.211.187.255
>
> Can I have THIS entry in server 2 for www.domain2.com at 207.211.187.98
> /sbin/ifconfig eth0:24 207.211.187.98 netmask 255.255.255.255 broadcast
> 207.211.187.255
>
> Both servers on same ethernet.
>
>
> > > Using Multiple servers on the same ethernet - is it possible to
> > > ifconfig eth0:24 on server 2 if server 1 already has someone on
it''s
> > > etho:24?
> > >
> >
> > Huh?
> >
>
>
> --
> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> http://www.redhat.com http://archive.redhat.com
> To unsubscribe: mail redhat-secure-server-request@redhat.com with
> "unsubscribe" as the Subject.
>
>