rndis connect cost long time (AEGHB-1361)

[yukunwu]

Answers checklist.

• I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
• I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
• I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

ENV
IDF:v5.5.1-875-g64726df15e-dirty

iot_usbh_rndis: v0.3.0
https://components.espressif.com/components/espressif/iot_usbh_rndis/versions/0.3.0/readme?language=en
iot_eth: 1.0.0
https://components.espressif.com/components/espressif/iot_eth/versions/1.0.0/readme

When upgrade the rndis and eth driver component to latest, it cost 15s to get ip.
But iot_usbh_rndis v0.2.0 and iot_eth 0.1.0m, it only cost 6s to get network connected.
Are all the components tested before release?
Can we be more cautious in the development to make the ecosystem more reliable?

[TDA-2030]

When we run the corresponding example, the IP address is obtained at a normal speed. You can use the example to test it. The time it takes to obtain the IP address is also highly dependent on the 4G module.

I (434) main_task: Calling app_main()
I (453) USBH_CDC: iot usbh cdc version: 3.0.0
I (486) usbh_rndis: IOT USBH RNDIS Version: 0.3.0
I (486) iot_eth: IoT ETH Version: 1.0.0
I (487) usbh_rndis: USB RNDIS network interface init success
I (492) RNDIS_4G_MODULE: IOT_ETH_EVENT_START
I (870) USBH_CDC: New device connected, address: 1
I (870) usbh_rndis: RNDIS device found: VID: 3505, PID: 0003, IFNUM: 0
I (872) cdc_descriptor: Found NOTIF endpoint: 7
I (877) cdc_descriptor: Found OUT endpoint: 12
I (882) cdc_descriptor: Found IN endpoint: 3
I (888) usbh_rndis: Max transfer packets: 0
I (892) usbh_rndis: Max transfer size: 0
I (897) usbh_rndis: rndis query OID_GEN_SUPPORTED_LIST success,oid num :22
I (908) usbh_rndis: rndis set OID_GEN_CURRENT_PACKET_FILTER success
I (911) usbh_rndis: rndis set OID_802_3_MULTICAST_LIST success
I (917) usbh_rndis: RNDIS connected success
I (922) iot_eth: Ethernet link up
I (926) RNDIS_4G_MODULE: IOT_ETH_EVENT_CONNECTED
I (931) iot_eth.netif_glue: Set MAC Address: 20:89:84:6A:96:AB
I (1943) RNDIS_4G_MODULE: GOT_IP
I (1943) Network Test: Ping task started
I (1944) iot_eth.netif_glue: netif "USB RNDIS0" Got IP Address
I (1943) Network Test: Network is connected, starting ping...
I (1947) iot_eth.netif_glue: ~~~~~~~~~~~
I (1958) iot_eth.netif_glue: ETHIP:192.168.10.100
I (1963) iot_eth.netif_glue: ETHMASK:255.255.255.0
I (1969) iot_eth.netif_glue: ETHGW:192.168.10.1
I (1947) 4g_router_server: ssid : Can't find in NVS!
I (1974) iot_eth.netif_glue: Main DNS: 192.168.10.2
I (1985) iot_eth.netif_glue: Backup DNS: 192.168.10.3
I (1991) iot_eth.netif_glue: ~~~~~~~~~~~
I (1995) 4g_router_server: password : Can't find in NVS!
I (2001) 4g_router_server: auth_mode : Can't find in NVS!
I (2007) 4g_router_server: channel : Can't find in NVS!
I (2013) 4g_router_server: hide_ssid : Can't find in NVS!
I (2019) 4g_router_server: bandwidth : Can't find in NVS!
I (2026) 4g_router_server: max_connection : Can't find in NVS!
I (2028) Network Test: 64 bytes from 8.8.8.8 icmp_seq=1 ttl=110 time=83 ms

[yukunwu]

When we run the corresponding example, the IP address is obtained at a normal speed. You can use the example to test it. The time it takes to obtain the IP address is also highly dependent on the 4G module.

I (434) main_task: Calling app_main()
I (453) USBH_CDC: iot usbh cdc version: 3.0.0
I (486) usbh_rndis: IOT USBH RNDIS Version: 0.3.0
I (486) iot_eth: IoT ETH Version: 1.0.0
I (487) usbh_rndis: USB RNDIS network interface init success
I (492) RNDIS_4G_MODULE: IOT_ETH_EVENT_START
I (870) USBH_CDC: New device connected, address: 1
I (870) usbh_rndis: RNDIS device found: VID: 3505, PID: 0003, IFNUM: 0
I (872) cdc_descriptor: Found NOTIF endpoint: 7
I (877) cdc_descriptor: Found OUT endpoint: 12
I (882) cdc_descriptor: Found IN endpoint: 3
I (888) usbh_rndis: Max transfer packets: 0
I (892) usbh_rndis: Max transfer size: 0
I (897) usbh_rndis: rndis query OID_GEN_SUPPORTED_LIST success,oid num :22
I (908) usbh_rndis: rndis set OID_GEN_CURRENT_PACKET_FILTER success
I (911) usbh_rndis: rndis set OID_802_3_MULTICAST_LIST success
I (917) usbh_rndis: RNDIS connected success
I (922) iot_eth: Ethernet link up
I (926) RNDIS_4G_MODULE: IOT_ETH_EVENT_CONNECTED
I (931) iot_eth.netif_glue: Set MAC Address: 20:89:84:6A:96:AB
I (1943) RNDIS_4G_MODULE: GOT_IP
I (1943) Network Test: Ping task started
I (1944) iot_eth.netif_glue: netif "USB RNDIS0" Got IP Address
I (1943) Network Test: Network is connected, starting ping...
I (1947) iot_eth.netif_glue: ~~~~~~~~~~~
I (1958) iot_eth.netif_glue: ETHIP:192.168.10.100
I (1963) iot_eth.netif_glue: ETHMASK:255.255.255.0
I (1969) iot_eth.netif_glue: ETHGW:192.168.10.1
I (1947) 4g_router_server: ssid : Can't find in NVS!
I (1974) iot_eth.netif_glue: Main DNS: 192.168.10.2
I (1985) iot_eth.netif_glue: Backup DNS: 192.168.10.3
I (1991) iot_eth.netif_glue: ~~~~~~~~~~~
I (1995) 4g_router_server: password : Can't find in NVS!
I (2001) 4g_router_server: auth_mode : Can't find in NVS!
I (2007) 4g_router_server: channel : Can't find in NVS!
I (2013) 4g_router_server: hide_ssid : Can't find in NVS!
I (2019) 4g_router_server: bandwidth : Can't find in NVS!
I (2026) 4g_router_server: max_connection : Can't find in NVS!
I (2028) Network Test: 64 bytes from 8.8.8.8 icmp_seq=1 ttl=110 time=83 ms

My case is that, the 4g module is powered on when the application is run.Are your case is the same? Or you power the module on before the esp32 application is running?