[Beowulf] Linux NIC order : (ether)boots from eth1 but Linux says it's eth0

[Yaroslav Halchenko]

In general you can rename interfaces the way you want

Package: ifrename
Description: Rename network interfaces based on various static criteria
 Ifrename allow the user to decide what name a network interface will have.
 Ifrename can use a variety of selectors to specify how interface names match
 the network interfaces on the system, the most common selector is the
 interface MAC address

but in your case it is just a matter of order in which this interfaces
got acknowleged by the kernel. So if both drivers are compiled as
modules, then the one loaded first gets eth0.

so you just need to make sure in the right sequence of module loads

-- 
Yarik


On Tue, Mar 29, 2005 at 08:23:47PM -0500, Nelson Castillo wrote:
> Hi.

> I'm booting a diskless cluster. Some nodes boot from eth0, others
> from eth1 or eth2. All nodes are identical.

> n at mdk:~$ lspci  | grep Ethernet
> 0000:02:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro
> 100] (rev 08)
> 0000:02:08.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX
> [Cyclone] (rev 34)
> 0000:02:09.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX
> [Cyclone] (rev 34)

> The etherboot image of the nodes that boot from eth0 have support
> only for Ethernet Pro 100. They work fine.

> The nodes that boot from eht1 have support for 3c90x and  they work
> fine. I tell etherboot to boot from the first nic found. But I have an issue.

> Linux kernel 2.6.8 sees eth1  (3com) as eth0! only when they boot from
> the etherboot image. I don't know why they inherit the etherboot order.

> Kernel log reads (Root over NFS / get ip from DHCP):

> IP-Config: Complete
>  device=eth0, addr=10.0.1.31, mask=255.255.255.0, gw=10.0.1.1,
>  host=10.0.1.31, domain=mydomain.com, nis-domain=(none),
>  bootserver=10.0.1.1, rootserver=10.0.1.1, rootpath=

> (note! : device=eth0)

> ******
> My question is: can i override this and tell Linux to call this interface eth1?
> ******

> Linux names it eth0.
> eth0      Link encap:Ethernet  HWaddr 00:50:DA:CE:07:7F

> I also would like to know why Linux does this.

> Regards,
> Nelson.-
-- 
                                  .-.
=------------------------------   /v\  ----------------------------=
Keep in touch                    // \\     (yoh@|www.)onerussian.com
Yaroslav Halchenko              /(   )\               ICQ#: 60653192
                   Linux User    ^^-^^    [175555]


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://www.scyld.com/pipermail/beowulf/attachments/20050331/ecade423/attachment.bin