problems with iproute in lfs 6.0

Schafer Frank Frank.Schafer at
Wed Jan 5 06:43:06 PST 2005

Due to the docs in /usr/share/doc/iproute*/

	# Ip addr add dev eth0 label eth0:1

should work for ip-aliasing with iproute2.

I can't proove this now because I've replaced iproute2 by the (formerly
used) net-tools. That's not because I don't know how to work with ``ip''
to set up interfaces. I need the netstat command or a replacement and I
didn't find anything appropriate within iproute2.


-----Original Message-----
From: lfs-support-bounces at
[mailto:lfs-support-bounces at] On Behalf Of Kevin P.
Sent: Wednesday, January 05, 2005 3:24 PM
To: LFS Support List
Subject: Re: problems with iproute in lfs 6.0

Stephan wrote:

> the book says in configuring the network scripts:
> This directory should contain files in the form of, where
> is a network interface name (such as eth0 or eth0:1).

That is an error in the book; interface aliases are no longer supported
by the tools included in LFS. Please enter a bug in the LFS Bugzilla to
get this corrected.

> but if i want to use eth0:1 it doesnt work at all, because ip cant 
> find that interface. i dont know if that "bug" is known but how can i 
> change the ifup/ifdown-scripts to keep track of a second ip-address
for an interface?

You do not need to change those scripts, you need to read them and learn
how they work. Adding additional IPV4 addresses to an interface is very
easy to do with these scripts, and an LFS builder should be able to read
and understand the scripts involved (it is, after all, "from scratch",
not "from helpers" <G>).
Unsubscribe: See the above information page

More information about the lfs-support mailing list