-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Default hostname non-compliant with rfc952 (again) #6130
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
Comments
It is even explicilty stated as such in: https://arduino-esp8266.readthedocs.io/en/2.5.2/esp8266wifi/station-class.html "Function returns String type. Default hostname is in format ESP_24xMACwhere 24xMAC are the last 24 bits of module’s MAC address." |
(edit: version fixed - was 2.1.x vs 2.2.x, is 2.2.1 vs 2.2.2) @philbowles Bug was fixed in (not default) sdk-2.2.2 which you can enable with arduino ide menu when using generic esp8266 board. About local copies of other firmwares (including default 2.2.1), we haven't binary-patched them. |
We can do that for a following release. It's just a matter of replacing 1 byte in the sdk lib. |
@d-a-v I'm confused: Does this not mean I AM using sdk-2.2.x ?: SDK:2.2.1(cfd48f3)/Core:2.5.2=20502000/lwIP:STABLE-2_1_2_RELEASE/glue:1.1-7-g82abda3/BearSSL:a143020 If so, it is absolutely NOT fixed, hence the post. What am I missing? |
Sorry my mistake. |
Thanks! Originally I thought that for some bizarre reason it might be causing an exception in my code, but the code has moved on and I now can't replicate the exception (thankfully!). Hence it's not a "showstopper", more a "FYI" so I will close it now. Thanks for rapid response and keep up the great work. |
Basic Infos
Platform
SDK:2.2.1(cfd48f3)/Core:2.5.2=20502000/lwIP:STABLE-2_1_2_RELEASE/glue:1.1-7-g82abda3/BearSSL:a143020
Settings in IDE
N/A : applies to all
Problem Description
The default WiFi chosen by the system is non-compliant with RFC952. This has been mentioned in the past (e.g. espressif/ESP8266_NONOS_SDK#208, #4415 )
Has it regressively crept back in or was it decided to ignore it back then?
The text was updated successfully, but these errors were encountered: