mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrzej Krzysztofowicz <ankry@pg.gda.pl>
To: rhw@MemAlpha.CX (Riley Williams)
Cc: mra@pobox.com (Mark Atwood), linux-kernel@vger.kernel.org (Linux Kernel)
Subject: Re: How does "alias ethX drivername" in modules.conf work?
Date: Wed, 8 Aug 2001 10:41:09 +0200 (MET DST)	[thread overview]
Message-ID: <200108080841.KAA26569@sunrise.pg.gda.pl> (raw)
In-Reply-To: <Pine.LNX.4.33.0108080729480.12565-200000@infradead.org> from "Riley Williams" at Aug 08, 2001 07:40:56 AM

"Riley Williams wrote:"
>  > If I build a system with several identical (other than MAC)
>  > FooCorp PCI ethernics, they will number up in order of ascending
>  > MAC address.
>  >
>  > I take the same system, replace the FooCorp cards with BarInc
>  > NICs, they will number up in reverse MAC address.
>  >
>  > Replace them instead with Baz Systems NICs, and I get them in
>  > bus scan order (at which point I'm dependent on the firmware
>  > version of my PCI bridge too!).
>  >
>  > And if I elect to use Frob Networking NICs, I instead get them
>  > in the *random* order that their oncard processors won the race
>  > to power up.
>  >
>  > Gods and demons help me if I try putting several of all four
>  > brands in one box, or the firmware on my NICs or in my PCI
>  > bridges changes!
> 
> I dealt with this problem in a previous email, but will repeat it for
> your benefit. The ONLY provisos I will use are the following two:
> 
>  1. All ethernet interfaces in your machine have distinct MAC's.
> 
>  2. If the firmware in your NIC's changes, the MAC's do not.
> 
> Providing both of these are met, the enclosed BASH SHELL SCRIPT
> implements the `ifconfig` command with the port name replaced by its
> MAC address.

1. NFS-root needs to have RARP/NFS servers on eth0.
   How can you deal with it if you have two boards supported by a single
   driver and, unfortunately, the one you need is detected as eth1 ?
   Assume that you cannot switch them as they use different media type...

> With this change, it doesn't actually matter what port name a
> particular interface is given, because ALL of the other network config
> tools refer to the interface by its assigned IP address, not its port
> name. As a result, if its port name changes between boots, the routing
> automatically changes with it.

2. ipfwadm / ipchains / iptables may use interface names,
3. dhcpd may need interface names to be provided,
4. you may want to pass an interface name argument to tcpdump...

In 2.2+ you can deal with 2.-4. changing interface names using ip from
iproute2. But I doubt whether ifconfig based scripts would work properly
then. And problem 1. is still valid ...

-- 
=======================================================================
  Andrzej M. Krzysztofowicz               ankry@mif.pg.gda.pl
  phone (48)(58) 347 14 61
Faculty of Applied Phys. & Math.,   Technical University of Gdansk

  reply	other threads:[~2001-08-08  8:42 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-03 21:29 Mark Atwood
2001-08-04  1:21 ` Chris Wedgwood
2002-03-28  2:52   ` How to tell how much to expect from a fd Mark Atwood
2002-03-28 13:27     ` Eric Lammerts
2002-03-31  3:03     ` David Schwartz
2001-08-04  1:32 ` How does "alias ethX drivername" in modules.conf work? Thomas Duffy
2001-08-04  2:31   ` Chris Wedgwood
2001-08-04  4:39   ` Jim Roland
2001-08-04 19:35   ` Riley Williams
2001-08-06 19:59     ` Thomas Duffy
2001-08-06 22:56       ` Riley Williams
2001-08-06 23:46         ` Andrzej Krzysztofowicz
2001-08-07  7:04           ` Riley Williams
2001-08-07 10:49             ` Andrzej Krzysztofowicz
2001-08-07 19:04               ` Riley Williams
2001-08-07 21:46                 ` Mark Atwood
2001-08-07 22:33                   ` Tim Jansen
2001-08-07 23:06                     ` Josh Wyatt
2001-08-07 23:35                   ` Riley Williams
2001-08-08  0:04                     ` Josh Wyatt
2001-08-08  6:28                       ` Riley Williams
2001-08-08 10:59                         ` Alan Cox
2001-08-08  0:08                     ` Mark Atwood
2001-08-08  6:40                       ` Riley Williams
2001-08-08  8:41                         ` Andrzej Krzysztofowicz [this message]
2001-08-08 10:52                           ` Eric W. Biederman
2001-08-08 11:40                             ` Andrzej Krzysztofowicz
2001-08-08 22:04                             ` Riley Williams
2001-08-08 21:09                           ` Riley Williams
2001-08-08  0:11                     ` Mark Atwood
2001-08-08  6:47                       ` Riley Williams
2001-08-08  0:16                     ` Mark Atwood
2001-08-08 20:26                       ` Riley Williams
2001-08-08  9:30                     ` Andrzej Krzysztofowicz
2001-08-08 21:31                       ` Riley Williams
2001-08-08 21:42                         ` Alan Cox
2001-08-08 22:24                         ` Horst von Brand
2001-08-09 20:05                   ` Colonel
2001-08-10  6:32     ` Paul Gortmaker
2001-08-10 21:25       ` Riley Williams
2001-08-15  4:32         ` Paul Gortmaker
2001-08-04  4:33 ` Jim Roland
2001-08-04  4:48 ` Jim Roland
     [not found] ` <15SnZL-05h4nQC@fmrl06.sul.t-online.com>
2001-08-06 19:46   ` How to hack a network driver to use a specific ethX (was Re: How does "alias ethX drivername" in modules.conf work?) Mark Atwood
2001-08-07 20:51 How does "alias ethX drivername" in modules.conf work? Stuart Lynne
2001-08-08  2:36 ` Bill Nottingham
2001-08-08  5:45   ` Greg KH
2001-08-08 13:59 Matt_Domsch

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=200108080841.KAA26569@sunrise.pg.gda.pl \
    --to=ankry@pg.gda.pl \
    --cc=ankry@green.mif.pg.gda.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mra@pobox.com \
    --cc=rhw@MemAlpha.CX \
    /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

all inboxes | Powered by JetHome®