On Wed, 28 Feb 2001, Luigi Rizzo wrote:
> the source of confusion is just the fact that when you ifconfig an
> interface, you really give two distinct pieces of information:
> 1. an ip address that the machine recognises as its own
> 2. an address for a subnet connected to that interface.
> With aliases you can assign multiple instances of 1 and 2, as long
> as they are distinct. In your example the subnet address that
> you try to set with the alias is the same as the one you have
> already set with the primary ip, so the info is already there and
> you get the warning/error.
Luigi,
Can you be more specific please? Is it just a harmless warning
message or a true error? In other words, will anything break if I use
a.b.c.2/24 alias on the interface with the a.b.c.1/24 primary address?
I hate to admit, but this thread is very confusing to me --
several people are claiming opposite things with confidence.
Unfortunately, I cannot simply ignore the discussion. For benchmarking
purposes, we routinely use thousands of IP aliases that belong to the
same subnet on one interface without any known problems. I want to
know if we are doing something wrong.
I do not care about the ifconfig warning by itself. We do not
even use ifconfig to manage aliases. I care about the actual run-time
code that handles the addresses. Could you please clarify whether
there is anything wrong with using, say, 10.0.0-3.1-250/16 aliases on
the same interface?
Thanks a lot,
Alex.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
