-
Notifications
You must be signed in to change notification settings - Fork 7.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
inappropriate IPv4 address offered by DHCP server (IDFGH-8574) #10024
Comments
@xueyunfei998 / "I can receive 10 addresses for the test here" |
hi xueyunfei998, |
Yes, the subnet mask you set has no effect on idf. |
@xueyunfei998 |
0001-lwip-bugfix-softap-excedes-the-range-of-subnet.txt |
Hi xueyunfei998, static void dhcps_poll_set(u32_t ip)
} |
sorry, to enter even though your question was @xueyunfei998, but I'm on hold waiting for a support to test the fix (please, see comment on Nov 19th. Thank you. |
Hi, just loaded ESP-IDF 5.0 I'll test the patch soon. |
Hi, the issue is still there :(
} |
@xueyunfei998 |
dhcpserver.txt Sorry for not replying in time. The above is a complete pacth based on version 4.4. |
Please, let me know what to test in IDF v5.0 Is the file dhcpserver.txt also relevant for IDF v5.0? |
@xueyunfei998 This bug is also in v4.3: cab17c7, please backport the fix for v4.3. |
@xueyunfei998 v4.3.5 still has this bug. |
The dhcp address pool allocation algorithm has been revised again. Please use the master version to test it. hi @AxelLin dhcp server's new memory pool allocation algorithm has been backport to 4.3.please test |
I have a question regarding the change in espressif/esp-lwip@4f24c9b , Does this commit fix any issue? |
Answers checklist.
General issue report
Hope this problem has not been previously flagged.
Based on AP networking configuration
IP4_ADDR(&ipInfo.ip, 192,168,200,9);
IP4_ADDR(&ipInfo.gw, 192,168,200,9);
IP4_ADDR(&ipInfo.netmask, 255,255,255,248);
the addresses 192.168.200.8 and 192.168.200.15 should be reserved
Vice versa the HDCP server of the ESP32 AP tried to assign it. The STA does not answer and does not associate.
Note that only three IP addresses has been assigned on 5 available:
I (743059) esp_netif_lwip: DHCP server assigned IP to a station, IP is: 192.168.200.15
D (743059) event: no handlers have been registered for event IP_EVENT:2 posted to loop 0x3ffbdc18
D (744349) esp_netif_lwip: esp_netif_get_ip_info esp_netif:0x3ffbeb44
D (744489) esp_netif_lwip: esp_netif_get_ip_info esp_netif:0x3ffbeb44
I (744489) esp_netif_lwip: DHCP server assigned IP to a station, IP is: 192.168.200.15
D (744499) event: no handlers have been registered for event IP_EVENT:2 posted to loop 0x3ffbdc18
D (745739) esp_netif_lwip: esp_netif_get_ip_info esp_netif:0x3ffbeb44
D (745929) esp_netif_lwip: esp_netif_get_ip_info esp_netif:0x3ffbeb44
I can't clarify the reason why the AP's DHCP svr does not consider the two addresses 192.168.200.10 and .11 (usually they are assigned as expected)
The wireshark trace reports, similarly to lwip's log. a DHCP offer of the 192.168.200.15 address. The STA does not answer to AP's HDCP MSGs
The text was updated successfully, but these errors were encountered: