Setting NIC to eth0/eth1

Robert Dege rdege at cse.Buffalo.EDU
Fri Dec 21 12:37:05 EST 2001


This might help:

http://www.vortech.net/rrlinux/Multiple-Ethernet.txt

-or-

http://www.linuxdoc.org/LDP/solrhe/Securing-Optimizing-Linux-RH-Edition-v1.3/chap8sec88.html

It's not a copy-n-paste answer, but should solve the problem, without
lowering yourself to modules ;)

-Rob

> Redhat 7.2, I was loading the NIC I wanted as eth1 as a module in the
> past. I think it strange that it would detect the PCI nic as eth0 and
> the on-board as eth1, but stranger things have happened. ;) Yes, the
> onboard does show up later on the pci bus, probably to keep it away from
> any conflicts. I will just go back to the good old module again :>
>
> Thanks for all the help.
>
> -----Original Message-----
> From: owner-nflug at nflug.org [mailto:owner-nflug at nflug.org] On Behalf Of
> Robert Dege
> Sent: Friday, December 21, 2001 12:16 PM
> To: nflug at nflug.org
> Subject: RE: Setting NIC to eth0/eth1
>
>
> Not that I know of.  I don't know how you're previous kernel was setup.
> Did you check the lilo.conf file to see if any parameters were passed at
> boot time?  Are the NIC drivers loaded via modules, or built into the
> kernel?
>
> Perhaps the older kernel detected 1 NIC first over the other.  Can be
> how
> the PCI bus is queried during boot.  You can do lspci, or cat /proc/pci
> do
> see what devices are detected.  Maybe there's an order?
>
> What flavor of linux are we talking here?  What version kernels?
>
> -Rob
>
> > Any idea why it would have changed? Does it have anything to do with
> the
> > order in which you select things when building the kernel?
> >
> > -----Original Message-----
> > From: owner-nflug at nflug.org [mailto:owner-nflug at nflug.org] On Behalf
> Of
> > Robert Dege
> > Sent: Friday, December 21, 2001 12:03 PM
> > To: nflug at nflug.org
> > Subject: RE: Setting NIC to eth0/eth1
> >
> >
> > In that case, you can probably pass them as kernel parameters at the
> > lilo
> > prompt or something similar.
> >
> > I'm not sure of the syntax, but that's the only other place that I can
> > think of to do that.
> >
> > -Rob
> >
> > > Also, I am hard-coding the drivers in (not loading as modules, so I
> > > don't think 'alias eth0 3c59x' etc will work)..
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: owner-nflug at nflug.org [mailto:owner-nflug at nflug.org] On Behalf
> > Of
> > > Joe Bielli
> > > Sent: Friday, December 21, 2001 11:48 AM
> > > To: nflug at nflug.org
> > > Subject: Setting NIC to eth0/eth1
> > >
> > > Does anybody know how to set which NIC becomes eth0/eth1 when the
> > driver
> > > loads up? I know its kind of a trivial question, but I am developing
> a
> > > solution for a customer, and I notice that this time around, my
> NIC's
> > > have swapped. How can I set which one to be eth0 or eth1? If I boot
> to
> > > the old kernel, they are like they were. I'm sure some kernel params
> > can
> > > be passed, but how can I compile it this way?
> > >
> > > Thanks,
> > >
> > > Joe Bielli
> > > Software Development
> > > Computer SOS, Inc.
> > > 1505 Cleveland Drive
> > > Buffalo, NY 14225
> > >
> > >
> >
> >
> >
> > Dege
> >
> > Inside some of us is a thin person struggling to get out, but
> > they can usually be sedated with a few pieces of chocolate cake.
> >
> >
>
>
>
> Dege
>
> Inside some of us is a thin person struggling to get out, but
> they can usually be sedated with a few pieces of chocolate cake.
>
>



Dege

Inside some of us is a thin person struggling to get out, but
they can usually be sedated with a few pieces of chocolate cake.



More information about the nflug mailing list