On Mon, 3 Apr 2000, Timothy Reaves wrote:
> I've read the Ethernet howto, and it states that linux assigns eth0
> to the first network card it finds, and eth1 to the second. The problem
> is I need what RH says is eth0 to be eth1 and eth1 to be eth0. I have
> two PCI nics; one 10mB/s and one 100mB/s. It is this that makes me need
> them in a particular order.
>
> I'm using RoadRunner, and it will only assign a DHCP address to
> eth0; I can't change that - at least that's what the docs say.
Ha! That's almost funny! Who's docs?
Think about it. How does the cable company know anything about your
machine, whether a card that is connected to its network is "eth0" or
"eth1" or a doze box, or ...?
You DO need to know which one is going to be eth0 and which eth1
in order to configure them and the assignment must be consistent
everytime you reboot. BUT, it doesn't matter which one is
used to connect to RoadRunner, as long as you know which one and you
configure it to run the dhcp client (either pump or dhcpcd). In the case
of your cards, there are two different type cards, so there's two different
modules loading, right? In this case, it's much easier to figure out
which card is which device than the case where you have two identical cards,
loading the same module.
>
> I assume I could change the I/O address to make the 10mB/s first (it
> already has a lower IRQ), but I'm not sure how to do that, because the
> Ehternet howto states this is assigned by the BIOS.
>
> Any ideas?
There are ways to "zero out" the ethernet card parameters assigned by
the BIOS and control the assignment by modifying lilo boot parameters,
but you certainly don't need or want to to something complicated
if you don't have to.
Your linux system detects and configures both cards, right?
You should have entries in the file:
/etc/conf.modules:
alias eth0 your_10/100_driver_module_name
alias eth1 your 10_driver_module_name
In /etc/sysconfig/network-scripts, you should have:
ifcfg-eth0
ifcfg-eth1
ifcfg-eth0 should look like:
DEVICE="eth0"
BOOTPROTO="manual"
ONBOOT="yes"
IPADDR="192.168.1.1" (assuming you use subnet 192.168.1.x for your LAN)
NETMASK="255.255.255.0"
...
ifcfg-eth1:
DEVICE="eth1"
BOOTPROTO="dhcp"
ONBOOT="yes"
IPADDR=""
NETMASK=""
...
Now, if the startup of eth1 fails on system startup, you know that pump
(your default dhcp client on your linux box), isn't working with the
RoadRunner line. I sent to this list detailed instructions on how to
troublshoot this dhcp client set up a couple of days ago. Either
check the archives (http://www.moongroup.com/redhat.phtml), or send me
private reply and I'll send you the step-by-step troubleshooting
instructions. In some cases, creating a simple /etc/pump.conf configuration
file for the dhcp client (pump) to give it a longer time out works,
sometimes, the line isn't working properly, or the cable company's dhcp
server isn't working correctly. Sometimes, you need to try a different
dhcp client (dhcpcd).
***************************************************************************
Jerry Winegarden OIT/Technical Support Duke University
[EMAIL PROTECTED] http://www-jerry.oit.duke.edu
***************************************************************************
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
