Bug #7042
closed
DHCP client configures wrong address in some circumstances (setfirst support missing from ifconfig)
100%
Description
In certain circumstances a DHCP client interface gets configured with an incorrect address. The address that should be the interface address is found to be the broadcast address, and the interface address appears to be bogus along with the subnet mask.
We now know this is the result of the "setfirst" patch being removed. The /usr/local/sbin/pfSense-dhclient-script attempts to execute this line:
$IFCONFIG $interface setfirst $new_ip_address
Without the "setfirst" patch, that is taken as a hostname, which the client then attempts to resolve via DNS
If the upstream DNS does not properly return NXDOMAIN results, the bogus result is used for the interface IP address and the interface's real address becomes the broadcast address.
If a user's upstream DNS returns proper NXDOMAIN results and not bogus search page servers instead, there is no problem.
I'll push a workaround momentarily which comments out this line until we decide how best to proceed.
Updated by Jim Pingle over 7 years ago
Simplest way to reproduce this is to use a DNS Resolver override for "setfirst" and the firewall's domain, set to an obviously wrong address. Then all you have to do is unplug/replug the WAN cable, or reboot, and check the console menu or ifconfig output. It's easier to hit on SG-1000 for some reason, perhaps due to its lower speed.
Updated by Luiz Souza over 7 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Updated by Jim Pingle over 7 years ago
- Status changed from Feedback to Resolved
Seems to be solid all-around.