Issues in getting IP address (ip route table) after successfully WIFI STA CONNECT b/n host and esp32s3 in the esphosted fg implementation

[praveenm-itas]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

Issues in getting IP address (ip route table) after successfully WIFI STA CONNECT Between host and esp32s3 in the esphosted fg implementation.

1. Ported ESP32 Host side driver module code ,referred porting guide to Android based MYIR LT527 Allwinner board.

2. .SPI communication works fine , able to get esp32_spi: process_init_event: esp boot-up event processed message

3. using c-support hostcontrol test , using get_ap_scan_list -> getting all the AP list at host
   4 . STA_CONNECT is connecting to the pre-configured wifi AP configured with SSID and PWD in ctrl_config.h
   log on both esp32 side anf host side its show WIFI AP connected.- wifi:I (390942) slave_ctrl: connected to ap SSID:'ITAS-Air5',
   but when ping from Host to the IP address of AP its unreachable, and also not able to ping any external IP address.

Actual behavior (suspected bug)

when I ping from Host to the IP address of AP its unreachable, and also not able to ping any external IP address. can you please help what i am missing here after connection successful.

Logs attached for the following scenario ESP32 side and host side & c-support terminal log

esp32_connect.txt
esp32_init.txt
esp_app1.txt
esp_host_connect.txt
esp_host_init.txt

Error logs or terminal output

Steps to reproduce the behavior

Using c-support hostcontrol test , using get_ap_scan_list -> getting all the AP list at host
STA_CONNECT is connecting to the pre-configured wifi AP configured with SSID and PWD in ctrl_config.h
log on both esp32 side anf host side its show WIFI AP connected.- wifi:I (390942) slave_ctrl: connected to ap SSID:'ITAS-Air5',

but when ping from Host to the IP address of AP its unreachable, and also not able to ping any external IP address.

Project release version

ESP-Hosted-FG-release_0.0.5.tgz for rpi4b and ESP-Hosted-FG-release_0.0.5.tgz for esp32 s3 wroom 1

System architecture

ARM 64-bit (Apple M1/M2, Raspberry Pi 4/5)

Operating system

Linux

Operating system version

linux-5.15

Shell

ZSH

Additional context

No response

[mantriyogesh]

From what you've described, it seems you're connecting an external device to the ESP's SoftAP, and the ESP is also connecting to an external AP as a station. Now, you want to ping from the external device to the external AP. Is that correct?

If this is the issue, let me clarify, softap and sta interfaces are isolated; packets from SoftAP clients do not get routed automatically like this.
Simplest solution is Wi-Fi-NAT-router example: https://github.com/espressif/esp-idf/tree/master/examples/wifi/softap_sta

[praveenm-itas]

Just to describe what we are doing:
We are connecting Android based (MYIR LT527 Allwinner board) Host with ESP32S3 via SPI interface
Now we want to achieve the WIFI connectivity on this Android based Host.
(here the AP is our office wifi router)

"From what you've described, it seems you're connecting an external device to the ESP's SoftAP, and the ESP is also connecting to an external AP as a station. Now, you want to ping from the external device to the external AP. Is that correct?"

its like the ESP is also connecting to an external AP ( our office wifi router) as a station, and trying to ping from the host machine ( which is connected via SPI with ESP32) ,

[mantriyogesh]

I understand now.

you are using normal station mode.

After the station connects to the AP, we bring the network interface up, but do not run a DHCP client by default.

This is because the DHCP client is a high-level feature, and the specific client used (e.g., dhclient, udhcpd, etc.) varies across Linux distributions. Our code doesn't include dhcp client code (and sit should also not include in my opinion)

In the ESP-Hosted code:

After CONNECT_AP succeeds, we call up_sta_netdev()
(code link)
This brings up the ethsta0 interface and sets its MAC address, but does not assign an IP.

The Python support code provides a --set_dhcp flag
(code link)
This tries to run dhclient, assuming it's available.

After connecting, you can check with ifconfig or ip addr that the ethsta0 interface is up, with correct (non zero) MAC address.
You can manually run:

sudo dhclient -v ethsta0

to get IP on ethsta0 interface.

In case you wish to hook, you can add up system commands

system("sudo dhclient ethsta0 -r"); /* remove dhcp */
system("sudo dhclient ethsta0 -v"); /* perform dhcp client on staeth0 */

before this line,

esp-hosted/esp_hosted_fg/host/linux/host_control/c_support/test_utils.c

Line 531 in 61471c1

break;

Please do not hesitate to comment should you have any confusion.

Although, I understand we could have embedded above system commands (just the same way we did not python), with some config flag for USE_DHCP_CLIENT , by default enabled.

[praveenm-itas]

Hi @mantriyogesh ,
Below are the details after connecting from Host to ESp32 via esp32_test utils commands

(1) # ifconfig -a

ethsta0 Link encap:Ethernet HWaddr 24:ec:4a:7e:1b:90
inet6 addr: fe80::26ec:4aff:fe7e:1b90/64 Scope: Link
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:528 errors:0 dropped:1 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:55271 TX bytes:1368

ethap0 Link encap:Ethernet HWaddr 24:ec:4a:7e:1b:91
inet6 addr: fe80::26ec:4aff:fe7e:1b91/64 Scope: Link
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 TX bytes:936

user space test_util() log also shows below messages for MAC address.
MAC address 24:ec:4a:7e:1b:90 set to ethsta0 interface
ethsta0 interface up

(2) to get IP on ethsta0 interface:
I used dhcp client, currently I am running from terminal (busybox_arm64) , once this works i can integrate in code.
as below after connect.

./busybox_arm64 udhcpc -i ethsta0 -v

udhcpc: started, v1.31.1
udhcpc: executing /usr/share/udhcpc/default.script deconfig
udhcpc: entering listen mode: raw
udhcpc: created raw socket
udhcpc: sending discover
udhcpc: waiting 3 seconds
udhcpc: unrelated/bogus packet, ignoring
udhcpc: waiting 3 seconds
udhcpc: unrelated/bogus packet, ignoring
udhcpc: waiting 3 seconds
udhcpc: unrelated/bogus packet, ignoring
udhcpc: waiting 2 seconds
udhcpc: unrelated/bogus packet, ignoring
udhcpc: waiting 2 seconds
udhcpc: unrelated/bogus packet, ignoring
udhcpc: waiting 2 seconds
udhcpc: unrelated/bogus packet, ignoring
udhcpc: waiting 1 seconds
udhcpc: unrelated/bogus packet, ignoring
udhcpc: waiting 1 seconds
udhcpc: sending discover
udhcpc: waiting 3 seconds
udhcpc: unrelated/bogus packet, ignoring

Not obtaining the IP.

t527-demo-car:/ # ip addr show ethsta0
19: ethsta0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 24:ec:4a:7e:1b:90 brd ff:ff:ff:ff:ff:ff
inet6 fe80::26ec:4aff:fe7e:1b90/64 scope link
valid_lft forever preferred_lft forever

(3) checked logging in to router and this device is not listed even though its connected.

But the Esp32 Host side log shows/ lists what are the other laptops/devices connected to that router

03-21 14:41:10.179 0 0 I [ C0] esp32_spi: spi_data_ready_interrupt_handler: esp spi_data_ready_interrupt_handler
03-21 14:41:10.190 0 0 I [ C0] esp32_spi: spi_interrupt_handler: esp spi_interrupt_handler
03-21 14:41:10.198 2690 2690 D spi_rx : 00000000bd7d5a68: f6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
03-21 14:41:10.210 2690 2690 D spi_rx : 00000000230df70a: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
03-21 14:41:10.222 2690 2690 D spi_rx : 0000000036701b13: 00 00 3c 00 0c 00 94 09 00 00 00 00 24 ec 4a 7e ..<.........$.J~
03-21 14:41:10.222 0 0 I [ C0] esp32_spi: spi_interrupt_handler: esp spi_interrupt_handler
03-21 14:41:10.234 2690 2690 D spi_rx : 0000000034f799ca: 1b 90 00 17 61 12 8d 3d 08 06 00 01 08 00 06 04 ....a..=........
03-21 14:41:10.253 84 84 D rx : 000000005f5de02a: 00 00 68 00 0c 00 27 1d 00 00 00 00 24 ec 4a 7e ..h...'.....$.J~
03-21 14:41:10.264 84 84 D rx : 00000000460bb1cc: 1b 90 34 6f 24 eb dd 75 86 dd 60 00 80 fc 00 32 ..4o$..u..`....2
03-21 14:41:10.275 84 84 D rx : 00000000d552f53f: 11 01 fe 80 00 00 00 00 00 00 81 81 c4 95 53 51 ..............SQ
03-21 14:41:10.286 84 84 D rx : 000000006b05af9c: 79 db ff 02 00 00 00 00 00 00 00 00 00 00 00 00 y...............
03-21 14:41:10.297 84 84 D rx : 00000000ba939bae: 00 fb 14 e9 14 e9 00 32 72 4f 00 00 00 00 00 01 .......2rO......
03-21 14:41:10.308 84 84 D rx : 000000005cc71911: 00 00 00 00 00 00 06 44 45 45 50 41 4b 06 5f 64 .......DEEPAK._d
03-21 14:41:10.319 84 84 D rx : 00000000cccb31b1: 6f 73 76 63 04 5f 74 63 70 05 6c 6f 63 61 6c 00 osvc._tcp.local.
03-21 14:41:10.330 84 84 D rx : 00000000892e290f: 00 ff 00 01 ....
03-21 14:41:11.167 0 0 I [ C0] esp32_spi: spi_data_ready_interrupt_handler: esp spi_data_ready_interrupt_handler
03-21 14:41:11.177 0 0 I [ C0] esp32_spi: spi_interrupt_handler: esp spi_interrupt_handler
03-21 14:41:11.186 2690 2690 D spi_rx : 00000000704ac74a: f6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
03-21 14:41:11.197 2690 2690 D spi_rx : 00000000a360e4c8: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
03-21 14:41:11.210 0 0 I [ C0] esp32_spi: spi_interrupt_handler: esp spi_interrupt_handler
03-21 14:41:11.210 2690 2690 D spi_rx : 00000000b92864c7: 02 00 41 00 0c 00 00 17 10 00 00 00 01 08 00 63 ..A............c
03-21 14:41:11.230 2690 2690 D spi_rx : 00000000761424e0: 74 72 6c 45 76 6e 74 02 33 00 08 03 10 af 02 fa trlEvnt.3.......
03-21 14:41:11.241 66 66 D rx : 00000000b92864c7: 02 00 41 00 0c 00 00 17 10 00 00 00 01 08 00 63 ..A............c
03-21 14:41:11.252 66 66 D rx : 00000000761424e0: 74 72 6c 45 76 6e 74 02 33 00 08 03 10 af 02 fa trlEvnt.3.......
03-21 14:41:11.263 66 66 D rx : 000000007cefd6c2: 12 2b 12 09 49 54 41 53 2d 41 69 72 35 22 11 65 .+..ITAS-Air5".e
03-21 14:41:11.274 66 66 D rx : 00000000bc97215e: 65 3a 32 32 3a 66 34 3a 32 65 3a 35 63 3a 64 61 e:22:f4:2e:5c:da

(4) Just to validate this busybox/udhcpc utility , I tried this in my Linux Laptop (X86 based) which is connected to the same Wifi AP, below are the details and able to obtain the IP.
itas@itas-Latitude-5450:~/Downloads/Busybox-static-main$ sudo ./busybox_x86 udhcpc -i wlp0s20f3 -v
udhcpc: started, v1.31.1
udhcpc: executing /usr/share/udhcpc/default.script deconfig
udhcpc: entering listen mode: raw
udhcpc: created raw socket
udhcpc: sending discover
udhcpc: waiting 3 seconds
udhcpc: unrelated/bogus packet, ignoring
udhcpc: waiting 3 seconds
udhcpc: received a packet
udhcpc: sending select for 192.168.1.33
udhcpc: waiting 3 seconds
udhcpc: received a packet
udhcpc: lease of 192.168.1.33 obtained, lease time 86400
udhcpc: executing /usr/share/udhcpc/default.script bound
udhcpc: entering listen mode: none

itas@itas-Latitude-5450:~/Downloads/Busybox-static-main$ ip addr show wlp0s20f3
3: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 88:f4:da:53:87:89 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.33/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp0s20f3
valid_lft 82073sec preferred_lft 82073sec
inet6 fe80::48bc:a006:6194:331e/64 scope link noprefixroute
valid_lft forever preferred_lft forever

[mantriyogesh]

Hi @praveenm-itas,

Logs

To help debug the issue, could you please share:

• Full ESP32 logs from the beginning.
• Complete dmesg log from the host, also from the start.
• Commands fired and their output in terminal

This will help us check if Wi-Fi disconnected at any point, even if the ESP reports it's connected.

Static IP

To quickly verify whether it's just a DHCP issue, try assigning a static IP to the ethsta0 interface:

sudo ifconfig ethsta0 192.168.1.233
sudo route -n

and try to ping to router IP

ping 192.168.1.1

If the ping works, it means the ESP is connected to Wi-Fi and the DHCP client may be the issue.

Any manual changes either side?

Also, have there been any manual changes on the ESP or host side?
If yes, please share:

• The patch(es) applied (both sides)
• The base commit used (both sides)

This will help us understand any changes in behaviour or possible conflicts.

[mantriyogesh]

Please let us know once you have update @praveenm-itas.

In my opinion, it should have worked with the above steps. However, I understand it did not work as I expected.
I can check the above logs and come to a conclusion.

Also, similar to host logs, Would it be possible for you to enable slave side SPI level logs?
If so, it would be faster to locate the problem, if the request from host was reached or not.

[praveenm-itas]

Hi @mantriyogesh ,

Attached below 3 logs
Full ESP32 logs from the beginning.
Complete dmesg log from the host, also from the start.
Commands fired and their output in terminal

Static IP
127|t527-demo-car:/data/local/tmp # ifconfig ethsta0 192.168.1.233

t527-demo-car:/data/local/tmp # ip route show
192.168.1.0/24 dev ethsta0 proto kernel scope link src 192.168.1.233

t527-demo-car:/data/local/tmp # ping 192.168.1.1
connect: Network is unreachable

127|t527-demo-car:/data/local/tmp # ping -I ethsta0 192.168.1.1
PING 192.168.1.1 (192.168.1.1) from 192.168.1.233 ethsta0: 56(84) bytes of data.
From 192.168.1.233: icmp_seq=1 Destination Host Unreachable
From 192.168.1.233: icmp_seq=2 Destination Host Unreachable
From 192.168.1.233: icmp_seq=3 Destination Host Unreachable
From 192.168.1.233: icmp_seq=4 Destination Host Unreachable
From 192.168.1.233: icmp_seq=5 Destination Host Unreachable
From 192.168.1.233: icmp_seq=6 Destination Host Unreachable
From 192.168.1.233: icmp_seq=7 Destination Host Unreachable
From 192.168.1.233: icmp_seq=8 Destination Host Unreachable
From 192.168.1.233: icmp_seq=9 Destination Host Unreachable
From 192.168.1.233: icmp_seq=10 Destination Host Unreachable

Host_side_full_log.txt

ESP32_side_log.txt

commands_terminal_log.txt

After Static IP :
Now I can see that this device with IP is listed in the router list ( 192.168.1.233 and MAC , [24:ec:4a:7e:1b:90] )
attached the snap

[mantriyogesh]

What is currently happening,

I (855013) slave_ctrl: Stop Heatbeat
I (855013) slave_ctrl: Stopping HB timer
I (856668) wifi:<ba-add>idx:1 (ifx:0, ee:22:f4:2e:5c:da), tid:7, ssn:2, winSize:64
I (1089504) slave_ctrl: HB timer started for 20 sec

I (1090192) slave_ctrl: Wifi already configured earlier, ignore
I (1090192) slave_ctrl: Request successful
I (1090365) slave_ctrl: Get station mac address
I (1090365) slave_ctrl: mac [24:ec:4a:7e:1b:90] 
I (1091328) slave_ctrl: Get softap mac address
I (1091328) slave_ctrl: mac [24:ec:4a:7e:1b:91] 
I (1091576) slave_ctrl: Stop Heatbeat
I (1091577) slave_ctrl: Stopping HB timer

You are using stress.out, which is more of testing utility. This is more of to test if any inconsistencies while running the commands back to back. but in the same script it just runs the commands back to back ${\color{yellow} \text{blindly}}$

${\color{yellow} \text{It is just a demonstration}}$. So is the same and simplified in test.c, which creates test.out output, which could be used in following way described.

Can you just simply try these things:

1. load the kernel module (you would have done it already)

2. cd c_support/
   change ctrl_config.h with your desired SSID and Password along lines:
   

   esp-hosted/esp_hosted_fg/host/linux/host_control/c_support/ctrl_config.h

   Lines 84 to 85 in 61471c1

   	#define STATION_MODE_SSID "MyWifi"
   	#define STATION_MODE_PWD "MyWifiPass@123"

3. build the test.out with new changes

make test

3. connect station mode

sudo ./test.out sta_connect

This would show something like:

------ ESP-Hosted FW [FG-0.0.6.0.0] ------
Connect to AP[Yogesh]


Requested operation complete
Sleeping for some time just to showcase heartbeat
ctrl_app_parse_resp:503 Info: Connect band_mode is 0
ethsta0 interface down
MAC address XXXXXXXXX set to ethsta0 interface
ethsta0 interface up

4. Once the interface up with MAC address like above, then either invoke dhcp client or static ip

sudo dhclient -v ethsta0
ping 8.8.8.8

logs at my side to refer

ym2@rpi2 ~/h/e/h/l/h/c_support [1]> vim ctrl_config.h
ym2@rpi2 ~/h/e/h/l/h/c_support> make test
gcc -C -Wall --sysroot= -I/home/ym2/h2_old_18jan/esp_hosted_fg/host/linux/host_control/c_support/../../../../common/protobuf-c -I/home/ym2/h2_old_18jan/esp_hosted_fg/host/linux/host_control/c_support/../../../../common/include -I/home/ym2/h2_old_18jan/esp_hosted_fg/host/linux/host_control/c_support/../../../control_lib/include -I/home/ym2/h2_old_18jan/esp_hosted_fg/host/linux/host_control/c_support/../../../control_lib/src/include -I/home/ym2/h2_old_18jan/esp_hosted_fg/host/linux/host_control/c_support/../../../virtual_serial_if/include -I/home/ym2/h2_old_18jan/esp_hosted_fg/host/linux/host_control/c_support/../../../components/include -I/home/ym2/h2_old_18jan/esp_hosted_fg/host/linux/host_control/c_support/../../port/include -I. /home/ym2/h2_old_18jan/esp_hosted_fg/host/linux/host_control/c_support/../../../../common/protobuf-c/protobuf-c/protobuf-c.c /home/ym2/h2_old_18jan/esp_hosted_fg/host/linux/host_control/c_support/../../../../common/esp_hosted_config.pb-c.c /home/ym2/h2_old_18jan/esp_hosted_fg/host/linux/host_control/c_support/../../../control_lib/src/ctrl_core.c /home/ym2/h2_old_18jan/esp_hosted_fg/host/linux/host_control/c_support/../../../control_lib/src/ctrl_api.c /home/ym2/h2_old_18jan/esp_hosted_fg/host/linux/host_control/c_support/../../../virtual_serial_if/src/serial_if.c /home/ym2/h2_old_18jan/esp_hosted_fg/host/linux/host_control/c_support/../../../components/src/esp_queue.c /home/ym2/h2_old_18jan/esp_hosted_fg/host/linux/host_control/c_support/../../port/src/platform_wrapper.c ./test_utils.c -lpthread -lrt test.c -o test.out
ym2@rpi2 ~/h/e/h/l/h/c_support> sudo ./test.out sta_connect
Enable heartbeat with duration 20
Heartbeat operation successful
------ ESP-Hosted FW [FG-0.0.6.0.0] ------
Connect to AP[Yogesh]


Requested operation complete
Sleeping for some time just to showcase heartbeat
ctrl_app_parse_resp:503 Info: Connect band_mode is 0
ethsta0 interface down
MAC address 40:4c:ca:4a:a8:50 set to ethsta0 interface
ethsta0 interface up

^C
Clean-up and exit
Disable Heartbeat
Heartbeat operation successful
ym2@rpi2 ~/h/e/h/l/h/c_support [1]>
ym2@rpi2 ~/h/e/h/l/h/c_support [1]> ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.162.0.2  netmask 255.255.255.0  broadcast 192.162.0.255
        inet6 fe80::2dcc:635f:d6ec:cc6  prefixlen 64  scopeid 0x20<link>
        ether dc:a6:32:33:6d:7c  txqueuelen 1000  (Ethernet)
        RX packets 3872  bytes 404695 (395.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3183  bytes 976328 (953.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ethsta0: flags=67<UP,BROADCAST,RUNNING>  mtu 1500
        ether 40:4c:ca:4a:a8:50  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 23  bytes 2469 (2.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 23  bytes 2469 (2.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether dc:a6:32:33:6d:7d  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ym2@rpi2 ~/h/e/h/l/h/c_support> sudo dhclient -v ethsta0
Internet Systems Consortium DHCP Client 4.4.3-P1
Copyright 2004-2022 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/ethsta0/40:4c:ca:4a:a8:50
Sending on   LPF/ethsta0/40:4c:ca:4a:a8:50
Sending on   Socket/fallback
DHCPDISCOVER on ethsta0 to 255.255.255.255 port 67 interval 8
DHCPOFFER of 172.20.10.5 from 172.20.10.1
DHCPREQUEST for 172.20.10.5 on ethsta0 to 255.255.255.255 port 67
DHCPACK of 172.20.10.5 from 172.20.10.1
bound to 172.20.10.5 -- renewal in 1631 seconds.
ym2@rpi2 ~/h/e/h/l/h/c_support>
ym2@rpi2 ~/h/e/h/l/h/c_support> ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=115 time=62.2 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=115 time=43.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=115 time=54.0 ms
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 43.819/53.325/62.170/7.506 ms

[mantriyogesh]

ESP logs at my side to refer

ESP-ROM:esp32c6-20220919
Build:Sep 19 2022
rst:0x1 (POWERON),boot:0x1e (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:2
load:0x40875730,len:0x173c
load:0x4086b910,len:0xe9c
--- 0x4086b910: esp_bootloader_get_description at /Users/yogesh/esp-idf/components/esp_bootloader_format/esp_bootloader_desc.c:39 (discriminator 1)

load:0x4086e610,len:0x30ec
--- 0x4086e610: esp_flash_encryption_enabled at /Users/yogesh/esp-idf/components/bootloader_support/src/flash_encrypt.c:89

entry 0x4086b91a
--- 0x4086b91a: call_start_cpu0 at /Users/yogesh/esp-idf/components/bootloader/subproject/main/bootloader_start.c:25

I (23) boot: ESP-IDF v5.5-dev-2303-gc864ee3701-dirty 2nd stage bootloader
I (24) boot: compile time May  7 2025 15:15:23
I (24) boot: chip revision: v0.0
I (26) boot: efuse block revision: v0.1
I (29) boot.esp32c6: SPI Speed      : 80MHz
I (33) boot.esp32c6: SPI Mode       : DIO
I (37) boot.esp32c6: SPI Flash Size : 4MB
I (41) boot: Enabling RNG early entropy source...
I (45) boot: Partition Table:
I (48) boot: ## Label            Usage          Type ST Offset   Length
I (54) boot:  0 nvs              WiFi data        01 02 00009000 00004000
I (61) boot:  1 otadata          OTA data         01 00 0000d000 00002000
I (67) boot:  2 phy_init         RF data          01 01 0000f000 00001000
I (74) boot:  3 ota_0            OTA app          00 10 00010000 00180000
I (80) boot:  4 ota_1            OTA app          00 11 00190000 00180000
I (87) boot: End of partition table
I (90) esp_image: segment 0: paddr=00010020 vaddr=420c0020 size=25bc8h (154568) map
I (126) esp_image: segment 1: paddr=00035bf0 vaddr=40800000 size=0a428h ( 42024) load
I (136) esp_image: segment 2: paddr=00040020 vaddr=42000020 size=ba9b4h (764340) map
I (277) esp_image: segment 3: paddr=000fa9dc vaddr=4080a428 size=158c4h ( 88260) load
I (297) esp_image: segment 4: paddr=001102a8 vaddr=4081fcf0 size=03cc4h ( 15556) load
I (308) boot: Loaded app from partition at offset 0x10000
I (309) boot: Disabling RNG early entropy source...
I (318) cpu_start: Unicore app
I (327) cpu_start: Pro cpu start user code
I (327) cpu_start: cpu freq: 160000000 Hz
I (327) app_init: Application information:
I (327) app_init: Project name:     network_adapter
I (332) app_init: App version:      FG-0.0.6.0.0
I (336) app_init: Compile time:     May  7 2025 15:15:15
I (341) app_init: ELF file SHA256:  3e8fba45d...
I (345) app_init: ESP-IDF:          v5.5-dev-2303-gc864ee3701-dirty
I (351) efuse_init: Min chip rev:     v0.0
I (355) efuse_init: Max chip rev:     v0.99
I (359) efuse_init: Chip rev:         v0.0
I (363) heap_init: Initializing. RAM available for dynamic allocation:
I (369) heap_init: At 408297F0 len 00052E20 (331 KiB): RAM
I (374) heap_init: At 4087C610 len 00002F54 (11 KiB): RAM
I (380) heap_init: At 50000000 len 00003FE8 (15 KiB): RTCRAM
I (386) spi_flash: detected chip: generic
I (389) spi_flash: flash io: dio
W (392) spi_flash: Detected size(8192k) larger than the size in the binary image header(4096k). Using the size in the binary image header.
I (404) sleep_gpio: Configure to isolate all GPIO pins in sleep state
I (410) sleep_gpio: Enable automatic switching of GPIO sleep configuration
I (417) coexist: coex firmware version: e727207
I (435) coexist: coexist rom version 5b8dcfa
I (436) main_task: Started on CPU0
I (436) main_task: Calling app_main()
I (436) NETWORK_ADAPTER: *********************************************************************
I (443) NETWORK_ADAPTER:                 ESP-Hosted Firmware version :: FG-0.0.6.0.0
I (450) NETWORK_ADAPTER:                 Transport used :: SPI only
I (458) NETWORK_ADAPTER: *********************************************************************
I (467) NETWORK_ADAPTER: Supported features are:
I (471) NETWORK_ADAPTER: - WLAN over SPI
I (474) ESP_BT: - BT/BLE
I (477) ESP_BT:    - HCI Over SPI
I (480) ESP_BT:    - BLE only
I (482) NETWORK_ADAPTER: capabilities: 0xe8
I (498) BLE_INIT: Using main XTAL as clock source
I (498) BLE_INIT: ble controller commit:[7ead2d2]
W (503) BLE_INIT: BLE modem sleep is enabled
I (504) BLE_INIT: Bluetooth MAC: 40:4c:ca:4a:a8:52
I (504) phy_init: phy_version 330,4af1121,Feb  6 2025,14:39:13
I (557) phy: libbtbb version: 99f6adc, Feb  6 2025, 14:39:27
I (558) NETWORK_ADAPTER: ESP Bluetooth MAC addr: 40:4c:ca:4a:a8:52
I (558) SPI_DRIVER: Using SPI interface
I (561) gpio: GPIO[3]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (569) gpio: GPIO[4]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (577) SPI_DRIVER: SPI Ctrl:1 mode: 2, GPIOs: MOSI: 7, MISO: 2, CS: 10, CLK: 6 HS: 3 DR: 4

I (586) SPI_DRIVER: TX Queues:10
I (589) SPI_DRIVER: RX Queues:10
I (592) gpio: GPIO[10]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (600) gpio: GPIO[10]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (610) pp: pp rom version: 5b8dcfa
I (612) net80211: net80211 rom version: 5b8dcfa
I (617) wifi:wifi driver task: 40846c60, prio:23, stack:6656, core=0
I (629) wifi:wifi firmware version: 3a3aca644
I (629) wifi:wifi certification version: v7.0
I (630) wifi:config NVS flash: enabled
I (633) wifi:config nano formatting: disabled
I (637) wifi:mac_version:HAL_MAC_ESP32AX_761,ut_version:N, band mode:0x1
I (644) wifi:Init data frame dynamic rx buffer num: 60
I (649) wifi:Init static rx mgmt buffer num: 5
I (653) wifi:Init management short buffer num: 32
I (657) wifi:Init dynamic tx buffer num: 40
I (661) wifi:Init static tx FG buffer num: 2
I (665) wifi:Init static rx buffer size: 1700 (rxctrl:92, csi:512)
I (672) wifi:Init static rx buffer num: 40
I (675) wifi:Init dynamic rx buffer num: 60
I (679) wifi_init: rx ba win: 32
I (682) wifi_init: accept mbox: 6
I (685) wifi_init: tcpip mbox: 32
I (688) wifi_init: udp mbox: 6
I (691) wifi_init: tcp mbox: 6
I (693) wifi_init: tcp tx win: 5760
I (697) wifi_init: tcp rx win: 5760
I (700) wifi_init: tcp mss: 1440
I (703) wifi_init: WiFi IRAM OP enabled
I (706) wifi_init: WiFi RX IRAM OP enabled
I (710) wifi_init: WiFi SLP IRAM OP enabled
W (715) wifi:ACK_TAB0   :0x   90a0b, QAM16:0x9 (24Mbps), QPSK:0xa (12Mbps), BPSK:0xb (6Mbps)
W (722) wifi:CTS_TAB0   :0x   90a0b, QAM16:0x9 (24Mbps), QPSK:0xa (12Mbps), BPSK:0xb (6Mbps)
W (731) wifi:(agc)0x600a7128:0xd2097b08, min.avgNF:0xce->0xd2(dB), RCalCount:0x96, min.RRssi:0xb08(-79.50)
W (740) wifi:(TB)WDEV_PWR_TB_MCS0:19
W (743) wifi:(TB)WDEV_PWR_TB_MCS1:19
W (746) wifi:(TB)WDEV_PWR_TB_MCS2:19
W (750) wifi:(TB)WDEV_PWR_TB_MCS3:19
W (753) wifi:(TB)WDEV_PWR_TB_MCS4:19
W (756) wifi:(TB)WDEV_PWR_TB_MCS5:19
W (760) wifi:(TB)WDEV_PWR_TB_MCS6:18
W (763) wifi:(TB)WDEV_PWR_TB_MCS7:18
W (766) wifi:(TB)WDEV_PWR_TB_MCS8:17
W (769) wifi:(TB)WDEV_PWR_TB_MCS9:15
W (773) wifi:(TB)WDEV_PWR_TB_MCS10:15
W (776) wifi:(TB)WDEV_PWR_TB_MCS11:15
I (780) wifi:11ax coex: WDEVAX_PTI0(0x55777555), WDEVAX_PTI1(0x00003377).

I (786) wifi:mode : null
I (789) NETWORK_ADAPTER: Initial set up done
I (793) slave_ctrl: event ESPInit
I (796) main_task: Returned from app_main()
I (3424) slave_ctrl: HB timer started for 20 sec

I (3434) wifi:mode : sta (40:4c:ca:4a:a8:50)
I (3435) wifi:enable tsf
I (3435) slave_ctrl: station mode set
I (3435) slave_ctrl: Get station mac address
I (3437) slave_ctrl: mac [40:4c:ca:4a:a8:50]
W (3442) wifi:Password length matches WPA2 standards, authmode threshold changes from OPEN to WPA2
I (3469) wifi:(he)max.RxAMPDULenExponentExtension:3, max.RxAMPDUpre-EOFpaddingBytes:8388607(0x7fffff)
I (3469) wifi:(mac)omc_ul_mu_data_disable_rx:0
I (3471) wifi:(phy)ppe_thresholds_present:1, nominal_packet_padding:3
I (3477) wifi:(phy)dcm tx(constellation:0, nss:0), dcm rx(constellation:0, nss:0)
I (3485) wifi:(phy)rx_mcs_map:0xfff5, tx_mcs_map:0xfff5, stbc_tx:0, bfmer(su:0, mu:0), ldpc:1, max_rate:172
I (3494) wifi:(phy)nsts:2, ru_index_bitmap:0x7(242:1, 484:1, 996:1, 2*996:0)
I (3501) wifi:(phy)threshold_bits:36, nsts_num:2, ru_num:3, he_cap->len:28, ppe_threshold_len:6(6,11,4)
I (3510) wifi:(ppe)RU242, NSTS0, PPE16:0, PPE8:7, nominal_packet_padding:2
I (3517) wifi:(opr)len:7, TWT Required:0, VHT Opr Info Present:0, 6GHz Opr Info Present:0, Co-Hosted BSS:0(max_indicator:0), Basic MCS and NSS:0xfffc
I (3530) wifi:(opr)len:7, Default PE Duration:4, TXOP RTS Threshold:0(0 us), ER-SU-Disable:0
I (3538) wifi:(opr)len:7, BSS Color:0, disabled:0, Partial BSS Color:0
I (5857) wifi:new:<6,0>, old:<1,0>, ap:<255,255>, sta:<6,0>, prof:1, snd_ch_cfg:0x0
I (5858) wifi:(connect)dot11_authmode:0x3, pairwise_cipher:0x3, group_cipher:0x3
I (5861) wifi:state: init -> auth (0xb0)
I (5870) wifi:state: auth -> assoc (0x0)
I (5876) wifi:(assoc)RESP, Extended Capabilities length:9, operating_mode_notification:0
I (5876) wifi:(assoc)RESP, Extended Capabilities, MBSSID:0, TWT Responder:0, OBSS Narrow Bandwidth RU In OFDMA Tolerance:0
I (5887) wifi:Extended Capabilities length:9, operating_mode_notification:1
I (5894) wifi:(he)max.RxAMPDULenExponentExtension:3, max.RxAMPDUpre-EOFpaddingBytes:8388607(0x7fffff)
I (5902) wifi:(mac)omc_ul_mu_data_disable_rx:0
I (5906) wifi:(phy)ppe_thresholds_present:1, nominal_packet_padding:3
I (5913) wifi:(phy)dcm tx(constellation:0, nss:0), dcm rx(constellation:0, nss:0)
I (5920) wifi:(phy)rx_mcs_map:0xfff5, tx_mcs_map:0xfff5, stbc_tx:0, bfmer(su:0, mu:0), ldpc:1, max_rate:172
I (5929) wifi:(phy)nsts:2, ru_index_bitmap:0x7(242:1, 484:1, 996:1, 2*996:0)
I (5936) wifi:(phy)threshold_bits:36, nsts_num:2, ru_num:3, he_cap->len:28, ppe_threshold_len:6(6,11,4)
I (5945) wifi:(ppe)RU242, NSTS0, PPE16:0, PPE8:7, nominal_packet_padding:2
I (5952) wifi:(opr)len:7, TWT Required:0, VHT Opr Info Present:0, 6GHz Opr Info Present:0, Co-Hosted BSS:0(max_indicator:0), Basic MCS and NSS:0xfffc
I (5965) wifi:(opr)len:7, Default PE Duration:4, TXOP RTS Threshold:0(0 us), ER-SU-Disable:0
I (5973) wifi:(opr)len:7, BSS Color:0, disabled:0, Partial BSS Color:0
I (5979) wifi:state: assoc -> run (0x10)
I (5983) wifi:(he)ppe_thresholds_present:1, nominal_packet_padding(rx:3, cfg:2)
I (5990) wifi:(trc)phytype:CBW20-SGI, snr:39, maxRate:172, highestRateIdx:0
W (5997) wifi:(trc)band:2G, phymode:3, highestRateIdx:0, lowestRateIdx:11, dataSchedTableSize:14
I (6005) wifi:(trc)band:2G, rate(S-MCS7, rateIdx:0), ampdu(rate:S-MCS7, schedIdx(0, stop:8)), snr:39, ampduState:wait operational
I (6016) wifi:ifidx:0, rssi:-46, nf:-85, phytype(0x3, CBW20-SGI), phymode(0x7, 11ax), max_rate:172, he:1, vht:0, ht:1
I (6027) wifi:(ht)max.RxAMPDULenExponent:3(65535 bytes), MMSS:6(8 us)
I (6049) wifi:(extcap)mbssid:0, enhanced_mbssid_advertise:0, complete_nontxbssid_profiles:0, twt_responder: 0
I (6049) wifi:connected with Yogesh, aid = 1, channel 6, BW20, bssid = 36:a2:64:36:92:12
I (6055) wifi:security: WPA2-PSK, phy:11ax, rssi:-46, cipher(pairwise:0x3, group:0x3), pmf:0,
I (6064) wifi:pm start, type: 1, twt_start:0

I (6068) wifi:pm start, type:1, aid:0x1, trans-BSSID:36:a2:64:36:92:12, BSSID[5]:0x12, mbssid(max-indicator:0, index:0), he:1
I (6079) wifi:dp: 1, bi: 102400, li: 3, scale listen interval from 307200 us to 307200 us
I (6087) wifi:set rx beacon pti, rx_bcn_pti: 10, bcn_timeout: 25000, mt_pti: 10, mt_time: 10000
I (6095) wifi:[ADDBA]TX addba request, tid:0, dialogtoken:1, bufsize:32, A-MSDU:0(not supported), policy:1(IMR), ssn:0(0x0)
I (6106) wifi:[ADDBA]TX addba request, tid:7, dialogtoken:2, bufsize:32, A-MSDU:0(not supported), policy:1(IMR), ssn:0(0x20)
I (6117) wifi:[ADDBA]TX addba request, tid:5, dialogtoken:3, bufsize:32, A-MSDU:0(not supported), policy:1(IMR), ssn:0(0x0)
I (6128) wifi:AP's beacon interval = 102400 us, DTIM period = 1
I (6134) wifi:[ADDBA]RX addba response, status:0, tid:0/tb:1(0xa1), bufsize:32, batimeout:0, txa_wnd:32
I (6142) wifi:[ADDBA]RX addba response, status:0, tid:7/tb:1(0xa1), bufsize:32, batimeout:0, txa_wnd:32
I (6152) wifi:[ADDBA]RX addba response, status:0, tid:5/tb:1(0xa1), bufsize:16, batimeout:0, txa_wnd:16
I (6161) slave_ctrl: Manual Wi-Fi connected, no event raised
I (6166) slave_ctrl: connected to ap SSID:'Yogesh', password:'PlantMoreTrees123'
I (6173) slave_ctrl: req_connect_ap_handler:655 Set resp to Success
I (13549) slave_ctrl: Stop Heatbeat
I (13550) slave_ctrl: Stopping HB timer
W (35199) wifi:<ba-add>idx:0, ifx:0, tid:6, TAHI:0x1001292, TALO:0x3664a236, (ssn:0, win:64, cur_ssn:0), CONF:0xc0006005
W (39279) wifi:<ba-add>idx:1, ifx:0, tid:0, TAHI:0x1001292, TALO:0x3664a236, (ssn:2, win:64, cur_ssn:2), CONF:0xc0000005

<Note: nothing else ahead in esp side log, after 'connected', which is significant difference in your and mine log >

[praveenm-itas]

Ok Yogesh I will try with test.out and check

Just before that wanted to confirm from you.
I (855013) slave_ctrl: Stop Heatbeat
I (855013) slave_ctrl: Stopping HB timer
I (856668) wifi:idx:1 (ifx:0, ee:22:f4:2e:5c:da), tid:7, ssn:2, winSize:64
I (1089504) slave_ctrl: HB timer started for 20 sec

I (1090192) slave_ctrl: Wifi already configured earlier, ignore
I (1090192) slave_ctrl: Request successful
I (1090365) slave_ctrl: Get station mac address
I (1090365) slave_ctrl: mac [24:ec:4a:7e:1b:90]
I (1091328) slave_ctrl: Get softap mac address
I (1091328) slave_ctrl: mac [24:ec:4a:7e:1b:91]
I (1091576) slave_ctrl: Stop Heatbeat
I (1091577) slave_ctrl: Stopping HB timer

The above log displayed because from terminal, i did following sequence of operations

get_ap_scan_list
sta_connect
enable_wifi

let me know if any particular sequence if differ from above , i will try with test.out and update you soon with details

[mantriyogesh]

ESP-Hosted: Documentation & Usage Notes

📚 Recommended Documentation

• Low-Level RPC APIs (Host–Slave Communication)
  Control APIs Documentation

• Higher-Level User-Space APIs
  Easier-to-use APIs can be found in test.h and used directly in your application once the demo is working.

• Control Path Design
  Control Path Overview

---

🚦 Using enable_wifi() and Related Functions

• enable_wifi(), disable_wifi(), and get_ap_scan_list() are not required for a basic Wi-Fi connection.
• Wi-Fi and Bluetooth are enabled by default at boot. Some users needed to manually disable, that was the reason 'disable_xxx()' and 'enable_xxx()' for Wi-Fi and Bluetooth was introduced.
• To connect to an AP, use sta_connect() directly — it sets up the mode, performs scan, and connects.

⚠️ Current Behavior (Bug?)

• Calling enable_wifi() clears previous Wi-Fi state, even if Wi-Fi is already enabled.
• After calling enable_wifi(), you must call sta_connect() again to reconnect.
• This behavior is expected to improve in future releases (e.g., enable_wifi() becoming idempotent).

---

🔔 Event Subscription

You can register and handle asynchronous Wi-Fi events such as disconnects.

• Events documentation:
  Control Path Events

• For example:
  On station disconnect, you can trigger an asynchronous RPC request to reconnect.

---

🔁 Synchronous vs Asynchronous Requests

• RPC (or Control) Responses and Events are 'Asynchronous' in nature.
• Only RPC Requests could be Synchronous or Asynchronous.
• Request becomes asynchronous if response callback was provided in the Request.
• If response callback is not populated, it remains NULL. it would be trated as Synchronous request.
• Any Request is by default Synchronous.
• Synchronous Request is called 'synchronous' because it blocks for the response.
• Asynchronous Request is called 'asynchronous' because it **does not ** block for the response.

Source Context	Send Sync RPC Request	Send Async RPC Request
Synchronous Thread	✅ Supported	✅ Supported
Asynchronous Thread	❌ Not Supported	✅ Supported

• Event callbacks are invoked from the RX thread, which must remain:
  • Non-blocking
  • Fast
• Async response callback also are called from RX thread, which must remain:
  • Non-blocking
  • Fast

[praveenm-itas]

I tried building with test.c and tried as per the steps you mentioned ,
Only triggered connect command this time ( SSID & pwd in .h file)

1|t527-demo-car:/data/local/tmp # ./esp32_wifi_control_test sta_connect

------ ESP-Hosted FW [FG-0.0.6.0.0] ------
Connect to AP[ITAS-Air5]ctrl_app_send_req -> req.msg_id :107
4. Protobuf msg size4. Protobuf msg size tx_len = 36
5. Allocate protobuf msg
6. Assign response callback
7. Start timeout for response for async only
8. Pack in protobuf and send the request
Serial connection: transport_pserial_send
Serial handle available
before serial_drv_write
serial_drv_write, .... just before ko write
serial_drv_write SUCCESS
9. Free hook for application
10. Cleanup

Requested operation complete
Sleeping for some time just to showcase heartbeat
ctrl_app_parse_resp:505 Info: Connect band_mode is 0
ethsta0 interface down
MAC address 24:ec:4a:7e:1b:90 set to ethsta0 interface
ethsta0 interface up
^C

After this assigned Static IP
t527-demo-car:/data/local/tmp # ifconfig ethsta0 192.168.1.233
t527-demo-car:/data/local/tmp # ip route show
192.168.1.0/24 dev ethsta0 proto kernel scope link src 192.168.1.233
t527-demo-car:/data/local/tmp # ping 192.168.1.1
connect: Network is unreachable
2|t527-demo-car:/data/local/tmp # ping -I ethsta0 192.168.1.1
PING 192.168.1.1 (192.168.1.1) from 192.168.1.233 ethsta0: 56(84) bytes of data.
From 192.168.1.233: icmp_seq=12 Destination Host Unreachable
From 192.168.1.233: icmp_seq=13 Destination Host Unreachable
From 192.168.1.233: icmp_seq=14 Destination Host Unreachable
^C
--- 192.168.1.1 ping statistics ---
17 packets transmitted, 0 received, +3 errors, 100% packet loss, time 16420ms
pipe 3
127|t527-demo-car:/data/local/tmp # ping 8.8.8.8
connect: Network is unreachable
2|t527-demo-car:/data/local/tmp # ping -I ethsta0 8.8.8.8
PING 8.8.8.8 (8.8.8.8) from 192.168.1.233 ethsta0: 56(84) bytes of data.
From 192.168.1.233: icmp_seq=1 Destination Host Unreachable
From 192.168.1.233: icmp_seq=2 Destination Host Unreachable
From 192.168.1.233: icmp_seq=3 Destination Host Unreachable
^C
--- 8.8.8.8 ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5092ms
pipe 4

[praveenm-itas]

DHCP client:

1|t527-demo-car:/data/local/tmp # ./busybox_arm64 udhcpc -i ethsta0 -v
udhcpc: started, v1.31.1
udhcpc: executing /usr/share/udhcpc/default.script deconfig
udhcpc: entering listen mode: raw
udhcpc: created raw socket
udhcpc: sending discover
udhcpc: waiting 3 seconds
udhcpc: unrelated/bogus packet, ignoring
udhcpc: waiting 2 seconds
udhcpc: unrelated/bogus packet, ignoring
udhcpc: waiting 1 seconds
udhcpc: sending discover
udhcpc: waiting 3 seconds
udhcpc: received a packet
udhcpc: xid a929a87f (our is 6f1a4884), ignoring packet
udhcpc: waiting 3 seconds
udhcpc: unrelated/bogus packet, ignoring
udhcpc: waiting 1 seconds
udhcpc: unrelated/bogus packet, ignoring
udhcpc: sending discover
udhcpc: waiting 3 seconds
udhcpc: unrelated/bogus packet, ignoring
udhcpc: waiting 3 seconds
udhcpc: unrelated/bogus packet, ignoring
udhcpc: waiting 3 seconds
udhcpc: unrelated/bogus packet, ignoring
udhcpc: waiting 1 seconds
udhcpc: executing /usr/share/udhcpc/default.script leasefail

[mantriyogesh]

I am not understanding why this should fail !

Let me think and come back on this.