DHCP does not run at boot (OpenSUSE 10.1, Toshiba A50)
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.
DHCP does not run at boot (OpenSUSE 10.1, Toshiba A50)
Hi all,
I've installed OpenSUSE 10.1 in a Toshiba A50 laptop, and everything is working OK (wireless with ipw2200, graphics, sound...) I have the network interface configured to connect to an specific ESSID, without using network manager.
The problem is that my computer does not get any IP address at startup from the router using DHCP (going through the syslog, I've found out some messages "DHCP client NOT running".
After that, when I attempt to restart the wlan interface, everything starts to work fine.
I cannot attach any message right now, but doing "iwconfig eth0", I guess I don't get any error (from the wlan perspective): ESSID OK, Access point OK, etc.)
What can be the problem? Is there any mean of having the dhcp daemon to be running at the beginning? If it already does without any action, could there be any problem related to the firewall, DHCP timeout (currently set to 9999999)...?
In case that it's suse but that doesn't matter at all.
There should be a file called ifcfg-devicename
and in this file should contain some lines like
the option ONBOOT=yes and BOOTPROTO=dhcp
In case that it's suse but that doesn't matter at all.
There should be a file called ifcfg-devicename
and in this file should contain some lines like
the option ONBOOT=yes and BOOTPROTO=dhcp
Thank you for your response.
But I was wondering if this file is being actually configured by using YasT (or other network-config tool) instructing the machine to activate the network card at boot time, and using DHCP to get IPs; even I did so, I got the same results: failed to connect at boot, but managed to connect manually later.
I don't like YET ANOTHER SETUP TOOL but this isn't my problem ;-)
modify the file by hand that will cause no problem.
If its a bug or not ? I don't belive it is one cause a lot people use 10.1
Finally, I reviewed that config file, and those parameters (onboot, bootproto) were ok, but still wouldn't get dhcp started at boot. I don't understand what could be the problem. Meanwhile, perhaps I should change to a fixed IP. That should be OK.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.