<div class="gmail_quote">On Tue, Jan 5, 2010 at 3:08 PM, Ashley M. Kirchner <span dir="ltr"><<a href="mailto:ashley@pcraft.com">ashley@pcraft.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Randall C Grimshaw wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
With this information I am going to join with Matt in suggesting the use of vlans to define a separate subnet.<br>
<br>
</blockquote></div>
Lovely, that would mean me having to go through the documentation for the switch (HP ProCurve 4000m) and figuring out the VLANs - something that was never done in the first place. When the switch was installed, they simply powered it up and plugged everyone in and called it done.<br>
<br>
Ok, I'll go that route and see if I can figure it out, but ... Once that's done, I still don't know how to configure DHCPd to tell what's what ...?<div><div></div><br></div></blockquote><div><br>It will get a bit complicated, but it will be worth setting up vlans in the end. As was mentioned you will have to configure routing between vlans. If you don't have a router that can handle multiple vlans and dhcprelay, then I would suggest looking in to setting up a box with pfsense as your router. It will handle vlans on a tagged port, or multiple ports, and it supports dhcprelay.<br>
<br>As for configuring dhcp, there is really nothing to learn. You just set up another subnet for it to hand out addresses on and it knows from the router's static address that it should return an address on that subnet.<br>
</div></div>