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.
When a DHCP server is down, is it possible for a client machine to bypass the LONG delay in waiting for an IP and carry on and boot up. It currently takes about 2-3 minutes for it to work out that the DHCP server is not available.
I have a PC that has a DHCP server running that I sometimes don't want to turn on (it's upstairs), but just want to just go into my PC downstairs.
Sorry if this doesn't make sense, its a bit hard to explain.
well it naturally depends which dhcp client you are using. if you're on pump, you should edit (or create) an /etc/pump.conf containing a suitable timeout= line. check the manpage for more info. I've been trying to suss out quickly how to do it with dhcpcd, but the manpage doesn't mention a config file to edit. you can specify a timeout on a command line iwth the -t option. you might want to look at the /sbin/ifup script to find out what's going on. (the dhcp client will be called from inside there. in there there are options to use the dhcpcd timeout from a preset environment varible, but i'm not really sure where that's meant to have come from. you could always just hardcode the value inside that script, or i guess you could add it to /etc/rc.sysinit or something...
Yeah, but the DOS based windows have to be rebooted to configure it with a static as its not really compliant with the RFC for dhcp, but really runs off of BOOTP. Also, you might want to change your /etc/sysconfig/network-scripts/ifcg-eth0 file and take it off dhcp. You can invoke the client from the command line easily enough with dhcpcd, or put that in rc.local, which runs last, and if you check the man page on dhcpcd, I'm pretty certain there's an option you can pass it to shorten the time-out wait period to something reasonable like 10 seconds instead of the default... 60 I think?
I first tried putting DHCP_TIMEOUT=10 in the ifcfg.eth0 file, but it had no effect.
I then had a browse at the /etc/rc.sysinit file (which I think is similar to the autoexec.bat / config.sys files), and I noticed a section dealing with DHCP. One line seemed to have options that are passed to the called DHCPCD command, so I added:
to set a time-out of 10 seconds, and hey-presto it worked !!
One quick ?, is there a similar command like WINIPCFG or IPCONFIG that I can run to check out the IP address in RHLinux?
If you want to see all the information retrieved by the dhcpc then there should be a file in the /etc/dhcpc directory called dhcpcd-<interface>.info
The name depends on how things are configured but just look around and I'm sure you'll find it.
ifconfig does a similar job to WINIPCFG or IPCONFIG on windows.
You can normally only run it as root though, and it does a load more stuff than either of the windows utils - so be careful!
Running it without command line arguments should be safe enough - it brings up a list of all your network adaptors, so on a typical machine it would bring up eth0, ppp0 (if you're dialed up to the net) and lo0 (the loopback adaptor) - and along with the list - you get all the info about each adaptor, including the IP address.