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 just upgraded to SUSE 9.3 professional doing a fresh install from SUSE 9.2. When I tried to start the DHCPD server, it keeps stating "No subnet declaration". I had the DHCPD server running under SUSE 9.2. I have even used the example dhcpd.conf file that comes with SUSE but it keeps giving me the same error. I have tried the most basic setup. I have swapped both my NIC cards but still no luck.
I've been googling around but haven't found anybody with my problem. I've been running a dhcpd server since SUSE 9.1. and have never encountered this problem before.
I run rcdhcpd start -t to test the file and it's OK but when I run it, I get the error. But then if I go back with rcdhcpd start -t, I will get the error.
I have the same problem. dhcpd.conf setting have gone amiss.
I am running Fedora Core 3. Last night I ran updates. After that, dhcp ceased to function. I receive the message that I have not provided a subnet for my public (internet) interface (eth1). My ip is static (assigned by ISP). I don't know what the subnet should be for my ISP assigned address.
dhcp is (was) configured to provide addresses on eth0 (internal interface). Anyone have any suggestions?
Should I enter an Options section that lists my assigned ip but ending with .0 (as in 123.123.123.0 if my assigned ip was 123.123.123.4?)
I received those errors too but haven't found a solution. I'm reloading SUSE 9.2. and starting from there. I've tried everything else like uninstalling then reinstalling the dhcp(d) software but nothing seems to work.
I'll let you know what happens. However, both my son's teams are wrapping up their baseball seasons by being in the playoffs and I won't be able to get to it for a few days at least.
Yes I did downgrade, temporarily anyway. The file I was using is the same one that I've been using since SUSE 9.1. It worked perfectly for 9.1. and 9.2. When I upgraded to SUSE 9.3, I started having all types of problems.
I even tried using the example dhcpd.conf that came with SUSE 9.3 (modified with the correct addresses).
I should be able to test it within the next few days when my son's little league baseball is over with.
I finally figured out my goof. I must have done something when I upgraded from suse 9.2 to 9.3 because when I configured my second card again with the IP address I had assigned it in the dhcpd.conf file originally, the dhcpd server started working again. Somehow, I had wiped out the configuration for the second card and didn't realize it. This was causing the "No subnet declaration" message.
Basically, I have a machine with two NIC cards. One card is configured with the static IP address of my ISP. On my second NIC card, I assign it the IP address that I had set in the dhcpd.conf file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.