Project

General

Profile

Actions

Bug #7042

closed

DHCP client configures wrong address in some circumstances (setfirst support missing from ifconfig)

Added by Jim Pingle over 7 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Interfaces
Target version:
Start date:
12/27/2016
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4
Affected Architecture:
All

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.

Actions

Also available in: Atom PDF