Jump to content

Talk:Dynamic Host Configuration Protocol

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 203.206.162.148 (talk) at 02:03, 6 September 2018 (→Client ID is starting to replace MAC address). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Merge

Closing per a WP:ANRFC request.
The result of the discussion was no consensus. Armbrust The Homunculus 05:46, 10 July 2014 (UTC)[reply]

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

I'm proposing the merge because DHCP snooping is a DHCP-related feature akin to DHCP relaying and we don't have a separate article for DHCP relaying. Spoofing is an attack technique and so is not a feature of the protocol and so arguably deserves a separate article. ~KvnG 14:22, 10 July 2013 (UTC)[reply]

The security section looks like the target for this proposed merge. Much of the material is already here so I don't think we'd be increasing the size of the article substantially. When you discount the tables, the article is not actually that large. ~KvnG 23:51, 7 November 2013 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

What is the "CHADDR (Client hardware address)"?

Is that the same thing as the "MAC address"? I know in my router's settings, IP addresses are assigned based on MAC address. But the term "MAC address" isn't used in this article, but a term I've never heard before "client hardware address" is used. Are these two things the same? Or is this yet another address which is associated with your computer? Benhut1 (talk) 01:37, 17 April 2015 (UTC)[reply]

Hello! In contemporary (Ethernet) networks, that's almost always a MAC address. However, not all networks are Ethernet, let's just remember TokenRing, for example, in which physical addresses are still six bytes long but aren't called "MAC addreses". Thus, the RFC uses CHADDR as a more universal term. — Dsimic (talk | contribs) 01:45, 17 April 2015 (UTC)[reply]
There are other fields that are labelled but not defined. The XID field, for example. What is it for and how is its value determined? Likewise the SECS and FLAGS fields. Mention of what the magic cookie is for would be helpful too. 83.104.249.240 (talk) 20:43, 23 August 2015 (UTC)[reply]

DHCP disabled?

In the first paragraph (Overview) the explanation for manual DHCP begins with: 

"The DHCP server is disabled and"

Which is clearly wrong and should be deleted.

Of course the DHCP-server is enabled. I assume the person who wrote this wanted to say, that the DHCP-server is not giving leases to clients which are not listed in the DHCP-configuration with a MAC-address and an according IP-address. — Preceding unsigned comment added by 212.149.48.42 (talk) 09:22, 11 August 2016 (UTC)[reply]

1234 Mahdiaziz (talk) 21:47, 29 December 2017 (UTC)[reply]

Hello fellow Wikipedians,

I have just modified one external link on Dynamic Host Configuration Protocol. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 08:19, 26 July 2017 (UTC)[reply]

Client ID is starting to replace MAC address

And this article is still assuming that the client is presenting a MAC address. I've pushed in some qualifications, but haven't provided any RFC's or references.

Most of the documentation on the web still assumes that clients will be presenting either EUI-48 or EUI-64 identifiers, but that's no longer the case: current Linux distributions (including Ubuntu) are presenting to DHCP machine ID's that do not include hardware-level identifiers at all.

The reason described for this change is that a machine with wired and wireless connections should by default present and acquire the same identification on both channels. This is not true if the hardware-level id's are bound to application-level ids, which happens if hardware-level id's are bound to IP address.

I notice that a comment about this was made on the talk page in 2007, so the technology is not new, but it's becoming more widespread — Preceding unsigned comment added by 203.206.162.148 (talk) 01:59, 6 September 2018 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:Dynamic_Host_Configuration_Protocol&oldid=858276247"