Skip to content
This repository has been archived by the owner on Dec 8, 2022. It is now read-only.

Fix DHCP option Client-identifier #1696

Merged
merged 1 commit into from Jan 21, 2020

Conversation

shubhamkulkarni97
Copy link
Contributor

Description

DHCP option 61 i.e. Client-Identifier consist of type-value pairs. In FreeRTOS TCP stack, value is assigned, while the type is missing.

Hence, type is added in Client-identifier option, which has value 0x1. 0x1 corresponds to Ethernet.

Checklist:

  • I have tested my changes. No regression in existing tests.
  • My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@mahavirj
Copy link
Contributor

This is per 9.14 section of RFC at https://tools.ietf.org/html/rfc2132 and observed in the context of espressif/esp-idf#4060

@htibosch
Copy link
Contributor

Hi Shubham, thank you for this PR. I tested the changes in one of my boards and indeed it looks good, and conform the RFC.
In fact you repaired a bug that has gone unnoticed for many years.
Hein

@gordonwang0
Copy link
Contributor

/bot run checks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants