From: Andi Kleen <ak@suse.de>
To: Ian Stirling <root@mauve.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Network device aliases
Date: 10 Aug 2001 22:05:28 +0200 [thread overview]
Message-ID: <oupd763istz.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <200108100327.EAA22951@mauve.demon.co.uk.suse.lists.linux.kernel>
In-Reply-To: Ian Stirling's message of "10 Aug 2001 05:46:42 +0200"
Ian Stirling <root@mauve.demon.co.uk> writes:
> I think I've more or less worked out how network devices are initiated,
> and configured, with the help of the htmlised sources, but am not
> finding anything on how aliases (eth0:1 ...) work.
> Do they have an entire device structure that only differs in name and
> IP address?
In 2.0 they had. In 2.2+ they are just another entry on a per interface
address list. The notion of alias interfaces is just emulated for
compatibility, they really do not exist anymore.
-Andi
next parent reply other threads:[~2001-08-10 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200108100327.EAA22951@mauve.demon.co.uk.suse.lists.linux.kernel>
2001-08-10 20:05 ` Andi Kleen [this message]
2001-08-10 3:27 Network device aliases Ian Stirling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=oupd763istz.fsf@pigdrop.muc.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=root@mauve.demon.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox