mirror of
https://github.com/espressif/esp-idf.git
synced 2026-09-22 13:01:16 +03:00
553d969c4f
The NAN-started handler brought the netif up via esp_netif_action_connected() using the NAN-started event's base/event_id/data. Feeding a "connected" action from a "started" event and handing it an unrelated event payload is fragile: it would misbehave if the action handler ever interpreted data (which is not a wifi_event_sta_connected_t here). esp_netif_up() is private to the esp_netif component, so keep the public esp_netif_action_connected() but pass NULL base, 0 event_id, NULL data. This is safe because the NAN netif is not a DHCP client: the handler only calls esp_netif_up() and never reads the event args.