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 running Slackware 10 with 3 nics. I get dhcp from my isp on eth0. I want to run DHCPD on eth1 and eth2 (wired and wireless). DHCPD runs without errors, and has given addresses in the past, but it will now not give out addresses on either interface.
Have you tried to start it w/ just using "/usr/sbin/dhcpd" with out adding eth1 and eth2 to it? If I try to add an interface as an arguement to mine it will not work. With your config file setup how it is, adding eth1 and eth2 is redundant.
Well that was easy. Thank you. Is there a reason it would not work with the arguments? When I run it without the arguments it gives me an error about eth0, but says it is listening and sending on the other two.
Does it say something like "No subnet declaration for eth0"? That's not so much an error as it is just a warning.
I'd say it just isn't written to accept interfaces as an arguement like that since you use the config file to tell it which subnets you want it to work on.
Yeah thas all it is. I figured it was fine, just telling me what its not doing, which is good I guess. So if it is written that way, why would it have the option to put interfaces? Maybe if you have 2 interfaces on the same subnet and only want it to go on one? I can't think of any other reason for working that way.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.