DHCP additional pool gateway='none' is ignored; and empty means MAIN pool setting not default
-
Pfsense 2.5.2 and 2.6.0: Setting gateway='none' for a DHCP additional pool is permitted but the setting appears to be ignored and is treated the same as an empty setting.
In addition, an empty setting for the gateway in an additional pool is documented to mean the same thing as in the main pool setting, but the documentation is incorrect: an empty gateway in an additional pool does not mean "send the Pfsense address as the gateway," it means "follow the setting of the MAIN pool." I think this is appropriate behavior, but the documentation is incorrect.
Setting an explicit IP in the gateway of the additional pool works as expected. A setting of 'none' on the main pool works as expected.
My use case at the moment is trying to refrain from giving one client a gateway (it's a management host which might jump onto the subnet for administrative purposes but shouldn't get a gateway). The way I really want to (and in my opinion should be able to) do this is with a static lease entry for the management host which overrides the gateway setting with 'none.' For reasons I don't understand, however, 'none' is not a permitted setting for the gateway in a static lease. OK I accept that, so I put the administrative host's MAC in the main pool 'deny mac' and create an additional pool of size 1 and the MAC in 'allow.' The administrative host gets the single IP of the pool as expected, but the pool's gateway 'none' is ignored.