From: "James A. Crippen" <james@UnLambda.COM>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] multiple MAC addresses from one network card
Date: Fri, 06 Apr 2001 22:43:37 +0000 [thread overview]
Message-ID: <marc-lartc-98659706014114@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98659466008892@msgid-missing>
On Fri, 6 Apr 2001, Alexey Marinichev wrote:
> On Fri, Apr 06, 2001 at 02:10:00PM -0800, James A. Crippen wrote:
> [...]
> > DON'T USE IFCONFIG AND fooN:M ALIASES IF YOU CAN HELP IT.
> [...]
>
> Why? What exactly is the difference between using aliases from ifconfig
> and from ip?
> Why? Just curious. BSD uses ifconfig and route just fine, so does
> SunOS.
Right, and the Linux version used to work perfectly well too. But there
have been so many changes to the underlying network subsystem (under
kernel 2.4 particularly) that ifconfig and route aren't totally in sync
with the system. Aliases are a good example. They don't really exist
anymore as network devices. Instead there's a clear separation now
between the hardware device and its driver and the network stack and
addresses assigned to a device. The old ifconfig way was to create fake
devices like eth0:0 to hang other IP addresses on. The new way that the
'ip' tool works is to assign an arbitrary number of addresses to *one*
real device. If you create an alias with ifconfig as an eth0:0 type of
device then you can see it attached to the real device using 'ip'.
However if you allocate a number of addresses and attach them to eth0,
say, then you won't see any except the first with ifconfig. This is
because ifconfig doesn't understand the new alias mechanism. Then you
start to get out of sync, and you have the problem of your device going
down when you try to remove an alias. It's just not good to use for
anything more than the old single-address, single-device metaphor.
Anything more complicated is better done with 'ip'. And if you've learned
how to use 'ip' you'll find that it's so convenient that you want to just
throw ifconfig and route away.
'james
--
James A. Crippen <james@unlambda.com> ,-./-. Anchorage, Alaska,
Lambda Unlimited: Recursion 'R' Us | |/ | USA, 61.2069 N, 149.766 W,
Y = \f.(\x.f(xx)) (\x.f(xx)) | |\ | Earth, Sol System,
Y(F) = F(Y(F)) \_,-_/ Milky Way.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-04-06 22:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-06 22:03 [LARTC] multiple MAC addresses from one network card Alexey Marinichev
2001-04-06 22:10 ` James A. Crippen
2001-04-06 22:16 ` Terry L. Ridder
2001-04-06 22:26 ` Alexey Marinichev
2001-04-06 22:35 ` James A. Crippen
2001-04-06 22:43 ` James A. Crippen [this message]
2001-04-06 22:45 ` Alexey Marinichev
2001-04-06 22:53 ` Terry L. Ridder
2001-04-06 22:59 ` James A. Crippen
2001-04-06 23:12 ` Breen Mullins
2001-04-06 23:48 ` Guy Van Den Bergh
2001-04-06 23:50 ` James A. Crippen
2001-04-07 0:24 ` Ingram Leedy
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=marc-lartc-98659706014114@msgid-missing \
--to=james@unlambda.com \
--cc=lartc@vger.kernel.org \
/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