Double interface can fail DNS resolution: dns_clear_servers called twice (IDFGH-4440)

[arnoutdekimo]

Hi,

In the v4.2 but also in the 4.3-dev, the https_request_example allows in the sdkconfig to enable both ethernet and wifi. (CONFIG_EXAMPLE_CONNECT_ETHERNET and CONFIG_EXAMPLE_CONNECT_WIFI)
Both will then run a dhcp client and the example will wait until both interfaces are up and have an IP.

However, in the case that one of the two interfaces does not get a DNS server through its DHCP lease, it is possible for no DNS servers to be configured at all, causing all subsequent name resolutions to fail.

What seems to happen is that esp_netif_dhcpc_start_api is called for every interface. In this function all dns servers are cleared. If the slower interface does not restore another dns server, the system will be without any dns server, which is clearly undesired.

(Tested on ESP32-WROOM-32)

Kind regards,
Arnout

[AxelLin]

This is a common issue for dual-interface use cases.
e.g. In STA + PPP case, when PPP is down the dns server settings are clear.
i.e. STA then fail to do DNS resolution.

The problem is lwIP does not support DNS per netif.
There is a patch available to support dns servers per netif, see
https://savannah.nongnu.org/bugs/?func=detailitem&item_id=58571#options

Maybe esp-lwip can test and pickup this patch.

@david-cermak

[david-cermak]

@arnoutdekimo @AxelLin Thanks for the report and the pointers. Will check the issue and see if we can cherry-pick the patch.

[sguitton]

Hi, I am working on the release v4.3 and I still have this issue. (LWIP version is 2.1.2)
Is there a patch working on the v4.3?
Is there a release planned which is solving this issue?

Thank you,

[xueyunfei998]

hi @sguitton

I provided a pacth of 4.3, which distinguishes the dns of each netif. If you have any more questions, please feel free to ask them.

As for the official patch of lwip, that patch has changed too much for idf, and it will take some time to change it.

[xueyunfei998]

dns_lwip.txt
4.3_dns.txt