The file to edit is /etc/sysconfig/network-scripts/ifcfg-eth0
It should look something like this. You should edit it with your settings
DEVICE=eth0 BOOTPROTO=static BROADCAST=xxx.xxx.xx.255 HWADDR=xx:xx:xx:xx:xx:xx IPADDR=xxx.xx.xx.xxx NETMASK=255.255.255.0 NETWORK=xxx.xxx.xx.0 ONBOOT=yes TYPE=Ethernet
Thom van der Boon E-Mail: Thom.van.der.Boon@vdb.nl
=====
Thom.H. van der Boon b.v. Havens 563 Jan Evertsenweg 2-4 NL-3115 JA Schiedam Tel.: +31 (0)10 4272727 Fax: +31 (0)10 4736620 E-Mail: info@vdb.nl Home Page: http://www.vdb.nl/
scott.heisler@huntleighusa.com 10.06.2005 22:52:34 >>>
Centos 4.0 P4 Dual Xeon 2gig Ram One 100mb NIC
The problem is that the nic won't hold a fixed IP address. What I mean is that if I refresh it, after booting up by typing "ifdown eth0" and then "ifup eth0" - it then reflects the correct IP address. However, it won't 'have' and IP address upon boot. Also, it seems to hang on the logger service starting up. It sits there attempting to start logger for like 3-4 minutes (timed!). I suspect this problem is most likely related to the IP problem.
I've tried moving the network connection to a dedicated HUB and still no luck.
What is the correct config file to edit to set the IP address correctly? I tried editing the one in /etc/sysconfig/network-scripts - but that didn't fix my problem.
Thanks. Scott _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Fri, 2005-06-10 at 18:10, Thom van der Boon wrote:
The file to edit is /etc/sysconfig/network-scripts/ifcfg-eth0
It should look something like this. You should edit it with your settings
DEVICE=eth0 BOOTPROTO=static BROADCAST=xxx.xxx.xx.255 HWADDR=xx:xx:xx:xx:xx:xx IPADDR=xxx.xx.xx.xxx NETMASK=255.255.255.0 NETWORK=xxx.xxx.xx.0 ONBOOT=yes TYPE=Ethernet
Note that if you have ever used the GUI network tool to configure the network, you will also have: /etc/sysconfig/networking/profiles/default/ containing files that override the ones in /etc/sysconfig/network-scripts. Also if the HWADD is specified but doesn't match the NIC, at some OS update level it will be ignored. It is probably best to either always use the GUI network tool or get rid of these files.
-
Les Mikesell -
Thom van der Boon