RE: eth0 not starting on bootup

From: Wade Chandler (wchandler_at_redesetgrow.com)
Date: 10/29/03

  • Next message: Eldose Paul: "SNMP MIB-2 access from application"
    To: <redhat-list@redhat.com>
    Date: Wed, 29 Oct 2003 17:03:53 -0500
    
    

    Some times I find the simplest solution is to remove the configuration
    all together then add it back when things get very hairy. Use network
    configurator. Then if that doesn't work. Ask some more.

    Wade

    -----Original Message-----
    From: redhat-list-admin@redhat.com [mailto:redhat-list-admin@redhat.com]
    On Behalf Of MKlinke
    Sent: Wednesday, October 29, 2003 4:44 PM
    To: redhat-list@redhat.com
    Subject: Re: eth0 not starting on bootup

    On Wednesday 29 October 2003 20:32, Darryl W. DeLao Jr wrote:
    > I have my server configured to where the only network device that
    > activates on boot is eth0. This morning, I changed the name of my
    > server and rebooted. After that, the eth0 interface is now no longer
    > starting when the computer boots. Nor does it even go through the
    > "bringing up eth0 internface" that you normally see when Red Hat
    > starts. When I type in the command "ifconfig eth0 up" the interface
    > comes up, but does not have the statically defined address settings
    > that it has always had. I had to end up creating an new interface
    > eth0:1 which is a virual setup just so I could get connectivity. Now
    > that connectivity has been established and I have told this interface
    > to now start on bootup, red hat still does the same thing. None of
    > the interfaces that I have destined for startup will activate on boot.

    > Is there a startup file of some kind that I may need to modify or some

    > kind of script so that the interface will start on boot?
    >
    >
    >
    > Any help is greatly appreciated.
    >
    >
    >
    > Thanks,
    >
    > Darryl

    Are there conflicting ifcfg-eth0 files in the two directory trees?:

    /etc/sysconfig/networking.... /etc/sysconfig/network-scripts....

    Regards, Mike Klinke

    -- 
    redhat-list mailing list
    unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
    https://www.redhat.com/mailman/listinfo/redhat-list
    -- 
    redhat-list mailing list
    unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
    https://www.redhat.com/mailman/listinfo/redhat-list
    

  • Next message: Eldose Paul: "SNMP MIB-2 access from application"

    Relevant Pages

    • Re: 3620 boot from tftp
      ... DRAM configuration is 32 bits wide with parity disabled. ... 29K bytes of non-volatile configuration memory. ... Boot OK! ... interface FastEthernet0/0 ...
      (comp.dcom.sys.cisco)
    • Re: Is there a way to use Linux on the E450 ?
      ... have the brain damage of years of legacy crap (boot in first x cyls). ... configuration point for everything from display configuration to ... I know what some of the features are. ... probing of a given interface to delay until the device on that interface ...
      (comp.sys.sun.hardware)
    • Re: [SLE] CUPS and multiple enet ports
      ... A better alternative would seem to be to use "BrowseAddress ... I'll have to know the IP or URL of any network printer I need access to right? ... in Yast/Hardware/Printer (which brings up the Printer Configuration ... interface, so click on "Firewall details", make sure only that interface ...
      (SuSE)
    • Re: Cisco Switch/Router configuration help.
      ... a "show interface" will show the interface in full duplex mode, ... I've done some cisco configurations in the past without much issue. ... I am trying to setup a sample network, ... 32K bytes of flash-simulated non-volatile configuration memory. ...
      (comp.dcom.sys.cisco)
    • Re: [SLE] CUPS and multiple enet ports
      ... A better alternative would seem to be to use "BrowseAddress ... I'll have to know the IP or URL of any network printer I need access to right? ... in Yast/Hardware/Printer (which brings up the Printer Configuration ... interface, so click on "Firewall details", make sure only that interface ...
      (SuSE)