Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am facing a strange problem with DHCP. At the boot time, the DHCP takes more then 30 secs to determine IP address when network service is starting up. However, after booting, I am able to stop and then start network service in couple of seconds. Any idea what might be causing this delay (Which almost doubles the boot time)?
Try this: Check how long it takcs for DHCP to stop on its own when the cable is not connected vs. when it is, that may tell us something. If you don't need internet you can hit CTRL+C while the daemon is starting to abort. I know it takes my Deb system 30-45 seconds to boot DHCP if there is no connection available (I removed it from initscripts since I'm on a laptop, and just start it manually), but it's up in a couple seconds if there is one.
Another thought would be for you to either do it manually on startup or on login. A possible fix would be to move DHCP later in the initscripts. If you could give more details on distro & hardware it might help me/others help you more.
>Try this: Check how long it takcs for DHCP to stop on its own when the cable is not connected vs. when it is, that may tell >us something. If you don't need internet you can hit CTRL+C while the daemon is starting to abort. I know it takes my >Deb system 30-45 seconds to boot DHCP if there is no connection available (I removed it from initscripts since I'm on a >laptop, and just start it manually), but it's up in a couple seconds if there is one.
With cable removed, network service throws an error without taking much time. Just to make clear, I am not trying to start dhcp server service, but rather using dhcp for configuring network on my machine as client.
>Another thought would be for you to either do it manually on startup or on login. A possible fix would be to move DHCP >later in the initscripts. If you could give more details on distro & hardware it might help me/others help you more.
I have tried moving network service later in the order, It did not help.
I am using Fedora core 4
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.