[SLE] NICs changing names by themselves?

From: Anders Norrbring (lists_at_norrbring.se)
Date: 03/14/05

  • Next message: Sandy Drobic: "Re: [SLE] routing / forwarding ergent help" 
    To: <suse-linux-e@suse.com>
Date: Mon, 14 Mar 2005 12:45:38 +0100

    I have a box with 2 NICs in it. SuSE 9.2 Pro.

    One Realtek that starts up as eth0, and a Broadcom that starts up as eth1.
    So far, so good.

    But suddenly after a reboot, they've changed places? The Realtek is then
    eth1 and the Broadcom is eth0.

    A couple of reboots later, they've changed places again! How can I control
    this? I need static naming since I have apps that depends on the correct
    name/network.

    Anders. 

    -- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
  • Next message: Sandy Drobic: "Re: [SLE] routing / forwarding ergent help"

    Relevant Pages

    • Forcing modules aliases on install
      ... I have a system running varius versions of RHEL (it started on RHEL4 U2, ... 04:00.0 Ethernet controller: Realtek Semiconductor Co., ... Even if the Broadcom device has a lower PCI address, ... detected as eth1 while eth0 is assigned to the Realtek. ...
      (RedHat)
    • RE: Kernel upgrade 2.4.18-14 -> 2.4.23 (rh8)
      ... I suspect there is a bcmxxxx.o under your old kernel ... Broadcom Gigabit Ethernet Driver bcm5700 with Broadcom NIC Extension ... eth0: Broadcom BCM5701 Integrated Copper transceiver found ... eth1: Broadcom BCM5701 Integrated Copper transceiver found ...
      (RedHat)
    • Re: Forcing modules aliases on install
      ... 04:00.0 Ethernet controller: Realtek Semiconductor Co., ... Even if the Broadcom device has a lower PCI address, ... detected as eth1 while eth0 is assigned to the Realtek. ... another Broadcom card; no, I cannot use Realtek as eth0 (I need Gigabit ...
      (RedHat)
    • eth0 and eth1 failure on boot
      ... One is Intel Kenai 32 + Realtek 8201, ... The boot log shows failure on eth0 and eth1. ...
      (alt.os.linux.suse)
    • Re: eth0 - eth1 confusion vs. local network
      ... The udev rules and dmesg output concur.. ... So 3com is eth0 and realtek is eth1 after boot and udev renames them ...
      (Debian-User)