help with dhcpd.config file to assign address's to clients on another subnet
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.
help with dhcpd.config file to assign address's to clients on another subnet
Am having problems with my dhcpd.conf file assigning address on another subnet on the same network. The one that I have all of my server's and networking gear is on a 172.16.0.0 wtih an netmask of 255.255.248.0. I would like to assign all of the client computers a 172.16.8.0 subnet with a netmask of 255.255.248.0. I have both subnet's declared in the file and the ranges I want to assign (172.16.8.1-172.16.15.254) dhcpd will start but will not assign the correct address. Maybe I should use a shared network declaration or group declaration. Not sure which. Running on RedHat Linux 3.x Enterprise. Thanks for any input.
You know that on the router between those subnets, you have to run a dhcprelay? Because otherwise the dhcp client requests will never reach the dhcp server.
If this is not the cause of the problem, then you might want to post your dhcpd.conf file. You don't want a shared-network declaration, since that does not apply to your network topology, and a group declaration would make little sense (but maybe your dhcpd.conf file will show the sense of that).
Then again, I might interpret your question falsely, and you mean you have only one physical network segment, and want to use two separate IP subnets on it? In which case you should use a shared-network declaration.
This is for a WISP setup, I have two NIC's in my DHCP server. I am running a SonicWall firewall and want my clients on the DMZ side of the firewall (2nd subnet), and all of my networking/server's on the other (1st) subnet. The clients need to obtain authorization from a server on the other (1st) subnet, and yet have full internet access on the (2nd subnet) DMZ. (I have the LAN side running a content filter and IDS, and Managed A/V protection). The DMZ is wide open. From what you stated, I can see two fix's for this. 1. Assign 1 IP on the same subnet to eth0 and plug it into my DMZ Switch and use it to assign DHCP, and then build a route in RedHat to eth1, which is on the other subnet. Or, do some routing in the SonicWall appliance from the DMZ to the LAN. What do you think? Thanks so much for the reply. You have been a great help. I was able to get the DHCP working on my DMZ Switch with the current DHCP.confg. It did assign the correct IP's and subnet, DNS servers etc...now seems like all I need is to work on my routing. Any ideas would be great...and again thanks a million.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.