On Tue, 28 Mar 2000, Haines Brown wrote about, Re: network configuration does not
stick:
> Richard,
>
> Another follow up to your message. To recall the problem: I'm tracking
> down why some of my network configuration does not survive a
> reboot. Following a reboot I have to run ifconfig eth0 192.168.1.1 to
> activate my Ethernet card.
>
> When I do that and run ifconfig without argument, I see that in fact
> the Ethernet card is active:
>
> eth0 Link encap: Ethernet HWadd ...
> inet addr:192.168.1.6 Bcast ...
> UP BROADCAST RUNNING MULTICAST MTU ...
> rxpackets ...
> lo Link encap ...
>
> Among helpful suggestions was that I inspect
> /etc/sysconf/network-scripts/ifcfg-eth0. However, while there's a
> ifcfg-lo, there's no ifcfg-eth0.
I belive you need to define global things in /etc/sysconfig/network
and interface stuff in /etc/sysconfig/network-scripts
ifcfg-eth0 should also contain something like
NETWORKING=yes
I belive i said it was in the network file in my last message.
> It therefore seems that while ifconfig configures my hardware, it does
> not write the configuration to a file that can be accessed at the next
> reboot. I tried to create the ifcfg-eth0 file based on another machine
> running linux, but that might not be a good idea. I've not tried to
> reboot to see if it works. Anyone have any insight as to why ifcfg
> might be able to configure the card but not write the configuration to
> file?
If no one else has answered your question by the weekend i will be able to
tell you exachtly as i have to do a redhat install here Friday.
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
