* Re: Network device aliases
[not found] <200108100327.EAA22951@mauve.demon.co.uk.suse.lists.linux.kernel>
@ 2001-08-10 20:05 ` Andi Kleen
0 siblings, 0 replies; 2+ messages in thread
From: Andi Kleen @ 2001-08-10 20:05 UTC (permalink / raw)
To: Ian Stirling; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Network device aliases
@ 2001-08-10 3:27 Ian Stirling
0 siblings, 0 replies; 2+ messages in thread
From: Ian Stirling @ 2001-08-10 3:27 UTC (permalink / raw)
To: l
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?
Any pointers would be most welcome.
Many thanks.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-08-10 20:05 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <200108100327.EAA22951@mauve.demon.co.uk.suse.lists.linux.kernel>
2001-08-10 20:05 ` Network device aliases Andi Kleen
2001-08-10 3:27 Ian Stirling
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox