RE: Configure multiple ethernet interfaces

From: Ow Mun Heng (ow.mun.heng_at_wdc.com)
Date: 05/07/04

  • Next message: Martijn Moret: "Re: Fedora on SUN Ultra sparc10" 
    Date: Fri, 7 May 2004 14:55:21 +0800
To: "For users of Fedora Core releases" <fedora-list@redhat.com>

    > -----Original Message-----
    > From: Demyanovich, Craig - Apogent [mailto:cdemyanovich@apogent.com]
    > Sent: Friday, May 07, 2004 4:59 AM
    > To: 'fedora-list@redhat.com'
    > Subject: Configure multiple ethernet interfaces
    >
    >
    > Greetings,
    >
    > I can't recreate the configuration of network interfaces after a FC1
    > install. eth0 (built-in) has been identified and configured
    > correctly.
    > However, eth1 (built-in) and eth2-5 (a 4-port card) are a mess. Kudzu
    > doesn't detect everything properly at boot time. Furthermore, despite
    > deleting all devices (via the GUI config tool),
    > /etc/sysconfig/hwconf still
    > lists eth4 and eth5. Yet, /etc/sysconfig/network-scripts
    > lists only eth0
    > and lo (good), and /etc/modules.conf lists only eth0 (good).
    > What gives?
    >

    What about removing kudzu??

    Or.. try pulling the card out and maybe kudzu will complain that it's
    not around anymore and offer you the choice of removing it??

    > What I want to be able to do is to keep the config for eth0
    > and start fresh
    > with eth1-5. For example, first I'd configure eth1 and test.
    > Then, I'd try
    > to configure the 4-port card (eth2-5). Still very new to linux
    > administration, I've been struggling to find a good resource on how to
    > accomplish my goal. I would greatly appreciate any pointers
    > on the proper
    > way to tell FC1 exactly what I want the details (card,
    > driver, assigned to
    > ethX, etc.) of the remaining interfaces to be.

    What sort of system has 2 built in net-cards??

    /curious 

    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Martijn Moret: "Re: Fedora on SUN Ultra sparc10"

    Relevant Pages

    • Re: Part 2; COM issues
      ... The COM configuration defines how the object ... Yes but these differences are as you wanted, a seperate concern. ... completely encapsulated by this object factory. ... another spin on this lies in the nature of interfaces. ...
      (comp.object)
    • Re: Part 2; COM issues
      ... The COM configuration defines how the object ... It is that composition of behavior that I ... The fact that a networking service is ... another spin on this lies in the nature of interfaces. ...
      (comp.object)
    • Network/IPMP configuration difficulties
      ... I have 8 interfaces on each machine, ... My intended configuration will be e1000g0 and e1000g2 as one ... netmask + broadcast + group interchange up ...
      (SunManagers)
    • [SLE] SuSE 9.0 Channel Bonding broken, fix and Mini-Howto
      ... It looks like the default compile of ifenslave included with SuSE 9.0 ... The good news is that the proper version of ifenslave now also supports ... NETWORK INTERFACE TEAMING USING KERNEL-BASED CHANNEL BONDING IN SUSE 9.0 ... Use Yast to configure both Ethernet interfaces as DHCP clients. ...
      (SuSE)
    • SUMMARY: IPMP Questions
      ... interfaces) is due to a series of problems from configuring the "service" ... Bootparamd didn't behave very well with such configuration. ... This correspondence is for the intended recipient only. ... Any views expressed in this message are those of the individual sender, ...
      (SunManagers)