Project

General

Profile

Actions

Correction #8852

closed

Clarify purpose of "Client Identifier" in DHCP static mapping

Added by Jared Dillard over 5 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
DHCP
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:

Description

Page: https://docs.netgate.com/pfsense/en/latest/services/dhcp/ipv4.html

Feedback: I am unclear about "Client Identifier" in a static mapping. Am I expected to figure out what the DHCP Client wants to call itself -- and populate that field with the value? Or am I to leave it blank and expect that when the DHCP Client is on-line, pfSense will take notice and populate the value for me?

Actions #1

Updated by Jim Pingle over 3 years ago

  • Description updated (diff)
Actions #2

Updated by Jim Pingle over 1 year ago

  • Subject changed from [feedback form] Unclear about "Client Identifier" in a static mapping to Clarify purpose of "Client Identifier" in DHCP static mapping
  • Start date deleted (08/29/2018)
Actions #3

Updated by Chris W over 1 year ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 50

Merge request liking to RFC for explanation:
https://gitlab.netgate.com/docs/pfSense-docs/-/merge_requests/47/

Actions #4

Updated by Jim Pingle over 1 year ago

  • Status changed from Feedback to Pull Request Review
Actions #5

Updated by Jim Pingle over 1 year ago

  • Status changed from Pull Request Review to Resolved
  • % Done changed from 50 to 100

Merged and deployed.

Actions

Also available in: Atom PDF