-
Notifications
You must be signed in to change notification settings - Fork 13.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hostname not set for DISCOVER packets - DHCP client hostname not present on some routers #8247
Comments
duplicate This will be addressed soon |
@ilium007 I've tested the fix on a Mikrotik router with a custom script like here: |
Issue #8223 references "OPTION: 61 ( 7) Client-identifier" This issue I have raised is about OPTION 12 Hostname. |
Edit: @1e1 I had been using the script from this thread to register the static DNS name but the issue I have is the missing hostname from the DISCOVER packet, the hostame is not available so this line doesn't work:
Yes, the scripts creates a static DNS entry in the form of a-b-c-d.domain but this is of no use to me. |
Different option, reopening |
@d-a-v @ilium007 What I get is what you see below (OPTION 12 & OPTION 51):
|
So it is not duplicate but is adressed by the same fix right ? |
Yes, I opened another PR for the Client Identifier, this one is for Hostname. |
I had noticed client identifier as well as hostname is missing from the Mikrotik DHCP lease table. It would be good to have both included in the DHCP DISCOVER and REQUEST packets. |
@ilium007 it's merging d-a-v/esp82xx-nonos-linklayer#51 |
@ilium007 and @1e1 Can you try the unofficial alpha release v0.0.2 (https://d-a-v.github.io/esp8266/Arduino/) ? |
Hi @d-a-v |
I'll need to reinstate a different router to test |
closing via #8319 |
Basic Infos
Platform
Settings in IDE
Problem Description
The hostname is not being set in the DISCOVER packet sent by the ESP8266. Some routers (Mikrotik definitely) reject the DHCP 'Option 12 - hostname' field in the REQUEST packet if it has not been sent in the DISCOVER packet previously.
This same issue has been fixed for the ESP32 in this commit: espressif/esp-lwip@13665c1
MCVE Sketch
N/A
Debug Messages
N/A
Detailed explanation and packet captures in this ESPHome issue: esphome/issues#2069 (comment)
The text was updated successfully, but these errors were encountered: