[lug] NIC loses static IP config on reboot

[Paul E Condon]

On Fri, Apr 23, 2004 at 09:41:32AM -0600, Nate Duehr wrote:
> David Anselmi wrote:
> 
> >Tim Stephenson wrote:
> >
> >>Dave,
> >>I checked as suggested.
> >>When reboot and NIC is down ifconfig eth0 shows
> >
> >
> >>Link encap:Ethernet Hwaddr 00:40:XX:XX:XX:XX:XX
> >>UP Broadcast Multicast MTU 1500 Metric 1
> >>RX Packets:851 errors: 0 dropped: 0 overruns:0 frame: 0
> >>TX Packets: 19 errors: 0 dropped: 0 overruns:0 frame: 0
> >>Collisions: 0 txqueuelen: 100
> >
> >
> >No surprise there, no IP address but it looks like you've got the 
> >right driver and the cable is plugged in...
> >
> >>It shows same for eth1 except packet quantity - no errors
> >>
> >>When I enter ifup eth0
> >>I get
> >>Determining IP info for eth0 - failed
> >>Ping 10.0.0.1
> >>Doesn't get response
> >
> >
> >Are those last two lines output of ifup, or something else you tried?
> >
> >>We then put the machine on another network and booted. It pulled down 
> >>a DHCP
> >>address and was able to ping other boxes on the network.
> >
> >
> >So it looks like your card is using DHCP.  I did some looking and 
> >found that one system I have is using:
> >
> >/etc/sysconfig/networking/profiles/default/ifcfg-eth0
> >
> >rather than:
> >
> >/etc/sysconfig/network-scripts/ifcfg-eth0
> >
> >The former is used the the RH "network administration tool" according 
> >to the docs.  I don't use that and somehow both config files on my 
> >system are the same.  But maybe you need to check both of them.
> >
> >BTW, if you want to see what /etc/sysconfig/network-scripts/ifup is 
> >doing, you can add a "set -x" line at the top of it and it will show 
> >you just what files it uses.  Look just below the line that says 
> >"need_config eth0".
> 
> Oh goodie... I totally forgot about RH's stupid "profiles" thing. 
> 
> What a mess they made of a relatively simple process.... (sigh).
> 
> We've been chatting off-list about Tim's network issues, but seeing your 
> note about profiles just makes me even more leery about this thing... 
> uggh.  If someone did something to turn *that* mess on... all bets are 
> off.  That's some really horrible code.
> 
> Comment back to the group -- Tim's just trying to get the machine to 
> stop doing DHCP and to use a static address.  Somehow I missed that in 
> my reply.  Perhaps it's just time to suggest he completely remove the 
> DHCP clients altogether?  Then we'd KNOW it wasn't trying to DHCP!  ;-)  
> (I'm half-joking about this.)
> 

If he were using Debian, removing a package in order to stop a service
would be a reasonable suggestion. Quick, easy, guaranteed to work, and
easy to undo, if you change your mind.


-- 
Paul E Condon           
pecondon at mesanetworks.net