>> Looking at a 2.0.3-release system, it appears that dhcpd and dhcrelay are both from ISC DHCPD 4.2.4. Both daemons support binding to specific interfaces, and as long as they don't overlap, ISC does support running both simultaneously. It's possible (although insane) to have dhcrelay listen on interface #1 and forward the requests to dhcpd listening on interface #2.
(Disclaimer: IIRC I've done this under Linux and OpenBSD. I've never tried it on FreeBSD, so YMMV.) pfSense, on the other hand, has a bunch of checks to make sure this doesn't happen. (Is this left over from when dnsmasq was used for DHCP?) It would likely be non-trivial to allow both to run simultaneously, and might require a complete redesign of the two GUI areas involved (.../services_dhcp.php & .../services_dhcp_relay.php) to avoid pathological coupling. Hey! Even better, I *can* make pfSense do this as long as I shut off the DHCP server, enable the DHCP relay on some interfaces, and *then* (re-)enable the DHCP server on some non-conflicting interfaces. I'm pretty sure that's a bug, though :-). -Adam Thompson [email protected] >> Looking at M0N0wall I see they are using ISC DHCP Server 3.0.5, and this setup is working perfectly for me at a few installations. I know it might be old school to have clients and servers on separate VLANS/subnets, but sometimes it makes sense. When you have decided to have clients and servers on separate subnets, you will often choose to have more VLANS/subnets for "other stuff", like industrial equipment, and having a DHCP server on those subnets is often requested. While I have no skills to contribute with this, I guess this is a feature request from me. I will be happy to do testing, documentation or anything (almost)..:-) Med venlig hilsen, Best regards Ulrik Lunddahl _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
