DHCP block unknown - MAC wildcard not allowed?
-
Is there a way to replace isc dhcpd w/ dnsmasq for dhcp?
<rant />
We just keep running into so many limitations with isc.. which then makes everyone else wonder why we're trying to migrate all of these things into pfsense..Every. (click save, wait)
Single. (click save, wait)
Thing. (click save, wait)
Can. (click save, wait)
Only. (click save, wait)
Be. (click save, wait)
Done. (click save wait)
With. (click save, wait)
The. (click save, wait)
Browser. (click save, wait)Or via xml scripting; don't forget to escape, or make any mistakes
The "end of this", seems we are expecting too much (dhcp wise), and assumed too much was already integrated and that our use cases were typical.
This whole rant would be incorrectly formatted and been removed.. with out any indication where the problem is..
<rant />We have thousands of devices (chromebooks for students) almost a dozen buildings.. with dnsmasq we could do this:
dhcp-host=d8:f3:bc:df::
dhcp-host=d8:f3:bc:e3::
dhcp-host=d8:f3:bc:e4::
dhcp-host=d8:f3:bc:e5::
dhcp-host=d8:f3:bc:e6::
dhcp-host=dc:8b:28:72::
dhcp-host=e0:9d:31:72::
dhcp-host=e0:9d:31:73::
dhcp-host=f0:42:1c:b8::
dhcp-host=f0:77:c3:cf::And the magic all starts with this one line..
dhcp-ignore=tag:!known
I understand there might not be any gui for the dnsmasq dhcpd.. but are there correct ways to disable isc and enable dnsmasq correctly?
Thanks in advance..
-
@mystique_ said in DHCP block unknown - MAC wildcard not allowed?:
dnsmasq
pfSense still has dnsmasq, as it can be used as a DNS forwarder, for those who want to forward to a remote DNS resolver.
If the pfSense-dnsmasq can be used as a DHCP server, I have my doubts.edit : Is this looks like what you want ?
