You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, setting network.hostname() does not actually set a hostname that gets picked up in DHCP. I have not done a packet dump to investigate why, but I assume the WIZNET5K driver used in MicroPython ignores the setting when sending DHCP requests. Other MicroPython implementations of the W5500 exists where DHCP is handled outside of the built-in driver, likely fixing the issue, but developing an entire W5500 driver just for DHCP hostnames seems a bit extreme.
It doesn't seem like there's a register in the W5500 that stores a hostname, so any use of the hostname would have to be done in software, likely requiring the efforts like in the above example.
Currently, setting
network.hostname()does not actually set a hostname that gets picked up in DHCP. I have not done a packet dump to investigate why, but I assume the WIZNET5K driver used in MicroPython ignores the setting when sending DHCP requests. Other MicroPython implementations of the W5500 exists where DHCP is handled outside of the built-in driver, likely fixing the issue, but developing an entire W5500 driver just for DHCP hostnames seems a bit extreme.It doesn't seem like there's a register in the W5500 that stores a hostname, so any use of the hostname would have to be done in software, likely requiring the efforts like in the above example.