Feature #11927
closed
Allow DHCP not to serve a gateway - small fix
0%
Description
Currently pfSense cannot serve dual homed machine on DHCP without giving both interfaces a default gateway as leaving the default gateway field empty means pfSense will send the firewall interface as default gateway. As jimp suggested either a checkbox to suppress sending a gateway or entering the word "none" into the gateway box to prevent the gateway from being supplied to clients will be an easy and adequate solution for dual or multi homed machines. More information can be found on: https://forum.netgate.com/topic/52221/how-to-configure-dhcp-server-to-not-assign-a-default-gateway
Updated by Jori Huisman almost 4 years ago
To add some clarity. The "none" option is available in the general config. However it is not on the static mapping page.
Updated by Marcos M almost 4 years ago
https://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xhtml
Router aka Gateway is DHCP option 3. You can override what's sent under Additional BOOTP/DHCP Options by specifying an empty string for option 3.
I don't see this as necessitating a specific GUI option given that there may be edge cases for many more DHCP options that get sent by default.
Updated by Steve Wheeler over 3 years ago
- Status changed from New to Feedback
This appears to be complete in 2.5.2.
A new feature request should be opened for similar function in Static Mappings if the dhcp option workaround is insufficient. That does work though:
https://forum.netgate.com/post/1017778
Updated by Alhusein Zawi almost 3 years ago
- Status changed from Feedback to Resolved
resolved
22.05-RELEASE (amd64)
built on Wed Jun 22 18:56:13 UTC 2022
FreeBSD 12.3-STABLE