[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: configuring multiple NIC's at boot

I have 5 nics in a box, ISA 3Com units with pnp disabled.  When you are
using the same driver for multiple NICs, they get allocated to interfaces
with the lowest MAC address getting eth0, etc. up the line.  At least this
is the way the 3Com driver works on ISA NICs.

Once you know the MAC address of each card, you can line them up in the
slots in interface order which makes it easy to know which connector is
which interface.

NICs on PCI busses using the same driver may be ordered on which slot they
are found in.  It may take a few cycles of booting to find out.


David Smead

On Sat, 20 Apr 2002, Osamu Aoki wrote:

> This is based on my vague memory and guess ...
> On Sat, Apr 20, 2002 at 04:39:42PM +0000, Pollywog wrote:
> > On 2002.04.20 16:30 Sean 'Shaleh' Perry wrote:
> > >
> > >On 20-Apr-2002 Pollywog wrote:
> > >> When I got DSL, I had a problem with my two NICS's.  Things would
> > >usually
> > >> end up with the NIC's being assigned the wrong addresses.  What I
> > >> did to correct this mess was to have the DSL modem's NIC get
> > >> configured in /etc/init.d/local.
> > >>
> > >>
> > >> What is the best way to avoid this type of problem?  BTW, the
> > >> internal network's NIC is a 3Com and I compiled the kernel with
> > >> support for that
> > >
> > >> NIC, but the DSL NIC is a Kingston card and uses the Tulip driver,
> > >which I
> > >> did not compile into the kernel (this is the card that gets
> > >> configured from /etc/init.d/local
> > >>
> > >
> > >the way this works is the first driver to be loaded gets eth0.  So
> > >the 3Com you compiled into the kernel SHOULD be setup as eth0.
> >
> > It does now, but when I had support for both cards compiled into the
> > kernel, the 3Com card did not get eth0, it got eth1 and the DSL's NIC
> > got eth0 and I could not think of a way to control this.  That is why
> > I now have only the 3Com card's support built into the kernel, so it
> > gets configured first.  If I add another NIC later, I will probably
> > have to also compile it as a module and have it get configured in
> > /etc/init.d/local after the Kingston NIC's config lines.  I just don't
> > know if that is the correct way or the best way to do it.
> I am thinking of dealing this just by /etc/modules and hardware reconfig ...
> First, swapping PCI slot made difference in eth0 and eth1, I kind of
> remember for my system with 2 NICs with same driver.
> Also I thought you can specify which eth? for each driver by the
> command line option which can be specified through /etc/modules.
> Vague memory.  Maybe un-true.
> I am also guessing /etc/modutils/alias may include lines like
>  alias eth0 tulip
> which may specify eth0 and eth1 if each use different driver.
> Just a thought.

To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: