Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
does anyone have any ideas why this might be or how to fix it? if it just happened at reboot I might have thought there was something stupid appended to a startup script that changes it back each time but it also happens after network restarts, as I said.
The file "/etc/sysconfig/network-scripts/ifcfg-eth0" is used by the RH network setup script to setup your network and remember the original settings. It is used by "/usr/bin/system-config-network" to setup your network. The file may be called a differnet name in RH9 but it would be very similar. Probably start with rh*
thanks for your replies. I'd already tried running the 'setup' program - and all that does is rewrite the ifcfg-eth0 file... which the network system then proceeds to take no notice of when I restart the network (or even restart the server). Any other ideas? I mean where might the thing be reading its config from if not from there anyway? :/
Originally posted by Michael Johnson Definitely no DHCP service running anywhere?
So I've been following this thread, and I have the same problem, but there is a DHCP server running on my network; I just don't want this computer to use it. However, the DHCP address aquisition seems automatic, and I can't figure out how to make it stop doing it. This is what my /etc/sysconfig/network-scripts/ifcfg-eth0 looks like:
Are there configuration options I'm missing? I've created this file both manually and with the 'setup' utility, rebooted, reset the network, all to no avail. /var/log/messages happily reports that it's finding a DHCP server and using it to configure my interface. What gives?
Oh, I forgot to mention, I did try re-installing the redhat-network RPMs as suggested, but that didn't do the trick. I feel like I'm probably missing some simple configuration step....
Last edited by heybrakywacky; 07-15-2005 at 10:53 PM.
Originally posted by Michael Johnson Do you use a broadband connection? If you do you can set the modem up to be a DHCP server and then use DHCP to setup your IP address and gateway server.
I'm afraid I don't understand how that benefits me. I have a DHCP server on my network, and the RedHat box sees it and configures to it properly, if that was a working paradigm for me. But this box will be functioning as a server, and as such needs to have a static IP address. I could probably work around it by either setting a ridiculously long lease expiration, or reserve an address at the DHCP server, etc. I just figured there must be a more straightforward way to configure a static IP address, and take the DHCP service out of the mix entirely for that particular network interface, since it's not necessary (or really desired, for that matter ).
Anyway, thanks for the response. I'll keep poking around to see what I can find.
I was wondering why you are setting a static IP instead of using DHCP.
The network setup tool should have set this to read the data from this file at startup. I am not sure it why it doesn't. More thought needed.
The last two had the proper settings for the static IP address, but the first one was still pointing to DHCP. I changed the networking/devices/ifcfg-eth0 file to mirror the other two, and restarting the network updated my interface properly. All's well that ends well, I suppose.