ESP32 DHCP hostname is not set correctly #1084
Comments
bettio
added a commit
that referenced
this issue
Mar 2, 2024
Fixed setting DHCP hostname in STA+AP mode. This PR fixes a bug that would cause the DHCP hostname to not get properly set when the device is configured in STA+AP mode. As a consequence, the default DHCP hostname (`espressif`) would be used, which would obviously be problematic on a network running multiple IoT devices. With this fix, the DCHP hostname is properly set, both in AP and STA modes, and in fact can be set differently in config, if desired. Closes #1084. These changes are made under both the "Apache 2.0" and the "GNU Lesser General Public License 2.1 or later" license terms (dual license). SPDX-License-Identifier: Apache-2.0 OR LGPL-2.1-or-later
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using AP+STA mode the logs report the correct hostname change, for example:
I (1220) network_driver: DHCP hostname set to atomvm-MACADDRESSBut the name cannot be resolved by the DHCP server, and running
hoston the assigned IP address shows the host name asespressif, if multiple AtomVM devices are connected to the network they all have the same default host name ofespressif.I have observed the same result with builds from all AtomVM supported versions of ESP-IDF (v4.4 through v5.1).
This behavior is not observed when the device is use only in STA mode.
The text was updated successfully, but these errors were encountered: