Closed 0xFEEDC0DE64 closed 1 year ago
This might be the same issue as reported in https://github.com/espressif/esp-idf/issues/10559.
@0xFEEDC0DE64 Could you please always show the esp-idf version (git describe --tags output) in your issue report?
@0xFEEDC0DE64 The fix is in master(4f0732c), v5.0 (392533f) and v4.4 (109eec403334), please check if it fixed your issue.
you please always show the esp-idf version (git describe --tags output) in y
https://github.com/0xFEEDC0DE64/esp-idf
i will check if the latest master has it fixed
@0xFEEDC0DE64 Do you still hit the issue?
no it seems the latest idf has this fixed, thank you
hi @0xFEEDC0DE64 The latest idf has fixed this problem.
Since our latest esp-idf rebase the DHCP server on the AP interface stopped working, we have had a quite unusual ip address range to avoid conflicts of customer's smart phones simulaniusly connected to multiple networks (cellular network and home networks).
Our selected AP ip range was 10.128.250.181 (255.255.255.0).
The error log in question:
I can avoid this error by commenting out a line of code in esp-idf (but I would like to discuss some other solution, maybe sdkconfig?)