Project

General

Profile

Actions

Bug #1135

closed

Empty DHCP client hostname and client identifier in GUI not respected

Added by Joshua Colp about 13 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
12/27/2010
Due date:
% Done:

0%

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

Description

While replacing my telco router with pfSense I came across an issue where the telco DHCP server would not respond to my request. This ended up being because despite no hostname being configured in the GUI pfSense (actually the DHCP client program) was still sending the MAC address of the interface as the DHCP client identifier and the hostname as the hostname.

By explicitly configuring the DHCP hostname and client identifier in the configuration with empty values no hostname and client identifier was sent.

If this is expected behavior then some method to have it truly be empty and not present would be appreciated.

If this is not expected behavior then my change above would be applicable, although this would introduce a behavior change.

Actions #1

Updated by Chris Buechler over 9 years ago

  • Status changed from New to Rejected

dhclient's behavior is the same as OS X, Windows, Linux, iOS, Android, and nearly every router/firewall in existence. The blank field just allows overrides should one desire.

Actions

Also available in: Atom PDF