Websocket connection has timeout too frequently

RE: Websocket connection has timeout too frequently

Håkon Alseth — Mon, 08 Sep 2025 13:07:06 GMT

Hi,

You're looking at the overall timing process, from boot until socket connected, correct?

[quote user=""]While it was developed through Linux drivers and such rather than with NCS/VS-Code/etc., we determined it can connect to WiFi, connect to socket, and send a little data all comfortably in <10sec. So I'm expecting similar performance.[/quote]

A linux device has more processing power for the WPA supplicant part than a nRF5-device has, and there will be a difference between the linux net based application implementation, as compared to the zephyr net implementation.

The crypto cpu processing part will take around 3-4 seconds for WPA2 as an example. You can see the difference by setting up test AP's with WPA2 / WPA3 and "open" security.

The below tests are from a complete cold boot (ie. power off, wait, power on), which is also why the logs are missing the first boot sequence logs (ie. "booting nRF connect SDK" etc)

WPA2 (nRF52840DK + nRF7002EK):

[00:00:01.631,896] <inf> sta: Static IP address (overridable): 192.168.1.99/255.255.255.0 -> 192.168.1.1
[00:00:03.296,081] <inf> wifi_mgmt_ext: Connection requested
[00:00:03.296,142] <inf> sta: Connection requested
[00:00:08.471,496] <inf> sta: Connected
[00:00:08.697,570] <inf> sta: Waiting for DHCP to be bound
[00:00:13.485,076] <inf> net_dhcpv4: Received: 192.168.32.163
[00:00:13.485,290] <inf> net_config: IPv4 address: 192.168.32.163
[00:00:13.485,321] <inf> net_config: Lease time: 36000 seconds
[00:00:13.485,351] <inf> net_config: Subnet: 255.255.255.0
[00:00:13.485,412] <inf> net_config: Router: 192.168.32.1
[00:00:13.485,809] <inf> sta: Try to open as client
[00:00:14.093,872] <inf> sta: Connected
[00:00:14.108,062] <inf> wifi_supplicant: Network interface 1 (0x20001140) down
[00:00:14.108,306] <inf> sta: Interface down

Open security:

[00:00:01.630,187] <inf> sta: Static IP address (overridable): 192.168.1.99/255.255.255.0 -> 192.168.1.1
[00:00:01.642,333] <inf> wifi_mgmt_ext: Connection requested
[00:00:01.642,364] <inf> sta: Connection requested
[00:00:06.731,109] <inf> sta: Connected
[00:00:06.743,713] <inf> sta: Waiting for DHCP to be bound
[00:00:06.748,962] <inf> net_dhcpv4: Received: 192.168.32.163
[00:00:06.749,145] <inf> net_config: IPv4 address: 192.168.32.163
[00:00:06.749,176] <inf> net_config: Lease time: 36000 seconds
[00:00:06.749,206] <inf> net_config: Subnet: 255.255.255.0
[00:00:06.749,267] <inf> net_config: Router: 192.168.32.1
[00:00:06.749,694] <inf> sta: Try to open as client
[00:00:07.369,934] <inf> sta: Connected
[00:00:07.383,911] <inf> wifi_supplicant: Network interface 1 (0x20001140) down
[00:00:07.384,155] <inf> sta: Interface down

Looking into the implementation, there will be a timing variation on both these testing vectors, as dhcp is udp based and the zephyr dhcp client has randomness on sending the request on the first boot.

There is a random delay between 1 to 10 seconds in the initial dhcp client sequence, required as per RFC2131 4.4.1, which you can set with CONFIG_NET_DHCPV4_INITIAL_DELAY_MAX=2 (value of '2' is min at this time).

Here are the configurations that I added:

CONFIG_NRF_WIFI_PS_EXIT_EVERY_TIM=y
CONFIG_NET_SHELL=n
CONFIG_SHELL=n
CONFIG_NET_DHCPV4_INITIAL_DELAY_MAX=2

PS: If you want to test with no delay on initial dhcp request, you can set the "true -> false" in this function call:

https://github.com/nrfconnect/sdk-zephyr/blob/v3.7.99-ncs3/subsys/net/lib/dhcpv4/dhcpv4.c#L1816

RFC2131 ch 4.4.1 (https://www.rfc-editor.org/rfc/rfc2131.html#section-4.4) uses the wording "should" indicating that this initial delay is optional, which I will take up internally with our networking team.

Kind regards,

Håkon

RE: Websocket connection has timeout too frequently

esmart-engineering — Fri, 05 Sep 2025 18:17:18 GMT

I tested your code, along with the websocketd server, and was able to reproduce a similar log. However, the original problem is still there – the overall time to perform this operation is taking too long. It’s just that we have narrowed down the source of the delay to be when the nRF is waiting for DHCP (which your latest log also shows as well).

Why is this happening? As mentioned before, and as your sales rep is aware, we had previous projects using the nRF7002. We tested these with the same router and same Linux host as this current project, yet they did not experience this issue. These previous projects had the nRF code developed through Linux drivers, not through NCS/Zephyr. So perhaps this is something to do with the Zephyr drivers?

RE: Websocket connection has timeout too frequently

Håkon Alseth — Fri, 05 Sep 2025 07:56:34 GMT

Hi,

This seems to be due to timing between the connected event vs. when the DHCP is bound. Could you try to wait for the DHCP to be bound?

Here's a proposed diff:

diff --git a/src/main.c b/src/main.c
index 7a6f4fe..c675d6c 100644
--- a/src/main.c
+++ b/src/main.c
@@ -37,6 +37,9 @@ LOG_MODULE_REGISTER(sta, CONFIG_LOG_DEFAULT_LEVEL);
 #include <zephyr/net/websocket.h>
 #define SERVER_PORT 3001
 #define SERVER_ADDR4  CONFIG_NET_CONFIG_PEER_IPV4_ADDR
+^M
+static K_SEM_DEFINE(dhcp_bound, 0, 1);^M
+^M
 static int setup_socket(sa_family_t family, const char *server, int port,
                        int *sock, struct sockaddr *addr, socklen_t addr_len)
 {
@@ -333,6 +336,7 @@ static void net_mgmt_event_handler(struct net_mgmt_event_callback *cb,
 {
        switch (mgmt_event) {
        case NET_EVENT_IPV4_DHCP_BOUND:
+               k_sem_give(&dhcp_bound);^M
                print_dhcp_ip(cb);
                break;
        default:
@@ -437,6 +441,8 @@ int start_app(void)
                }
 
                if (context.connected) {
+                       LOG_INF("Waiting for DHCP to be bound");^M
+                       k_sem_take(&dhcp_bound, K_FOREVER);^M
                        cmd_wifi_status();
 
                        int err = connect_to_server();

File:

devzone.nordicsemi.com/.../51427.main.c

Log:

*** Booting nRF Connect SDK v2.9.1-60d0d6c8d42d ***
*** Using Zephyr OS v3.7.99-ca954a6216c9 ***
[00:00:00.637,329] <inf> net_config: Initializing network
[00:00:00.637,329] <inf> net_config: Waiting interface 1 (0x20000dc8) to be up...
[00:00:00.637,481] <inf> net_config: IPv4 address: 192.168.1.99
[00:00:00.637,542] <inf> net_config: Running dhcpv4 client...
[00:00:00.638,366] <inf> sta: Starting nrf7002dk with CPU frequency: 64 MHz
[00:00:00.640,014] <inf> wifi_supplicant: wpa_supplicant initialized
[00:00:01.638,549] <inf> sta: Static IP address (overridable): 192.168.1.99/255.255.255.0 -> 192.168.1.1
[00:00:03.185,943] <inf> wifi_mgmt_ext: Connection requested
[00:00:03.185,974] <inf> sta: Connection requested
[00:00:03.186,035] <inf> sta: ==================
[00:00:03.186,065] <inf> sta: State: SCANNING
[00:00:03.486,206] <inf> sta: ==================
[00:00:03.486,236] <inf> sta: State: SCANNING
[00:00:03.786,346] <inf> sta: ==================
[00:00:03.786,376] <inf> sta: State: SCANNING
[00:00:04.086,486] <inf> sta: ==================
[00:00:04.086,517] <inf> sta: State: SCANNING
[00:00:04.386,627] <inf> sta: ==================
[00:00:04.386,657] <inf> sta: State: SCANNING
[00:00:04.686,828] <inf> sta: ==================
[00:00:04.686,859] <inf> sta: State: SCANNING
[00:00:04.986,968] <inf> sta: ==================
[00:00:04.986,999] <inf> sta: State: SCANNING
[00:00:05.287,139] <inf> sta: ==================
[00:00:05.287,170] <inf> sta: State: SCANNING
[00:00:05.587,280] <inf> sta: ==================
[00:00:05.587,310] <inf> sta: State: SCANNING
[00:00:05.887,451] <inf> sta: ==================
[00:00:05.887,481] <inf> sta: State: SCANNING
[00:00:06.187,591] <inf> sta: ==================
[00:00:06.187,622] <inf> sta: State: SCANNING
[00:00:06.487,731] <inf> sta: ==================
[00:00:06.487,762] <inf> sta: State: SCANNING
[00:00:06.787,902] <inf> sta: ==================
[00:00:06.787,933] <inf> sta: State: SCANNING
[00:00:07.088,043] <inf> sta: ==================
[00:00:07.088,073] <inf> sta: State: SCANNING
[00:00:07.388,214] <inf> sta: ==================
[00:00:07.388,244] <inf> sta: State: SCANNING
[00:00:07.688,385] <inf> sta: ==================
[00:00:07.688,415] <inf> sta: State: SCANNING
[00:00:07.988,555] <inf> sta: ==================
[00:00:07.988,586] <inf> sta: State: AUTHENTICATING
[00:00:08.288,726] <inf> sta: ==================
[00:00:08.288,757] <inf> sta: State: AUTHENTICATING
[00:00:08.373,504] <inf> sta: Connected
[00:00:08.588,836] <inf> sta: Waiting for DHCP to be bound
[00:00:12.395,080] <inf> net_dhcpv4: Received: 192.168.32.198
[00:00:12.395,263] <inf> net_config: IPv4 address: 192.168.32.198
[00:00:12.395,294] <inf> net_config: Lease time: 36000 seconds
[00:00:12.395,324] <inf> net_config: Subnet: 255.255.255.0
[00:00:12.395,355] <inf> net_config: Router: 192.168.32.1
[00:00:12.395,477] <inf> sta: DHCP IP address: 192.168.32.198
[00:00:12.401,916] <inf> sta: ==================
[00:00:12.401,947] <inf> sta: State: COMPLETED
[00:00:12.401,947] <inf> sta: Interface Mode: STATION
[00:00:12.401,977] <inf> sta: Link Mode: WIFI 6 (802.11ax/HE)
[00:00:12.402,008] <inf> sta: SSID: OpenWrt
[00:00:12.402,038] <inf> sta: BSSID: FC:34:97:0B:F6:DC
[00:00:12.402,069] <inf> sta: Band: 5GHz
[00:00:12.402,069] <inf> sta: Channel: 44
[00:00:12.402,099] <inf> sta: Security: WPA2-PSK
[00:00:12.402,099] <inf> sta: MFP: Optional
[00:00:12.402,130] <inf> sta: RSSI: -61
[00:00:12.402,130] <inf> sta: Try to open as client
[00:00:12.474,487] <inf> sta: Connected
[00:00:12.488,708] <inf> sta: Interface down

Best regards,

Håkon

RE: Websocket connection has timeout too frequently

esmart-engineering — Fri, 05 Sep 2025 01:50:40 GMT

To make it even more clear - here is the project source showing the main problem. I'm not even calling send_data_to_server() at all anymore, as it's not the main problem. The main problem is with connect_to_server().

devzone.nordicsemi.com/.../wifi_5F00_station_5F00_w_5F00_sockets_5F00_v2.zip

RE: Websocket connection has timeout too frequently

esmart-engineering — Fri, 05 Sep 2025 01:41:30 GMT

My lead had me look into the 2 suggestions you had:

Connect once and send data once
- I have attached an updated project zip, with these changes.
- devzone.nordicsemi.com/.../wifi_5F00_station_5F00_w_5F00_sockets_5F00_v1.zip
- It is still sometimes unable to connect to the server. Whether it was using my server script, your server script, or websocketd, none of them affected this result.
Use websocketd for testing
- I followed the instructions on the website link:
  - I prepared a Linux host machine, with the 3001 port ready for use.
  - I downloaded websocketd using the following command
    - ```
    $ wget 'https://github.com/joewalnes/websocketd/releases/download/v0.3.0/websocketd-0.3.0-linux_amd64.zip'
    $ unzip websocketd-0.3.0-linux_amd64.zip
```
- I ran the command to start the program
  - ```
  $ ./websocketd --port=3001 cat
```
- I have attached an example of the output from websocketd. This shows multiple attempts of powering on the nRF’s and having it send just 1 message.
  - (will upload later; DevZone is reporting errors when I try uploading)
- Note that the Linux host we used is an AWS server that we have been using for multiple other products, for many years. Other than whatever else websocketd sets up, the Linux host and its settings absolutely should not be an issue when it comes to hosting servers.

Both of these suggestions did not work. Not only that, but again they were for addressing other parts of the project that are not the main problem we’re facing – why is it sometimes taking too long to connect to the server? Please address this directly. We will no longer waste time addressing other suggestions like this that lead us down different paths.

RE: Websocket connection has timeout too frequently

esmart-engineering — Wed, 03 Sep 2025 15:51:55 GMT

Can we have someone w/ more knowledge about this to support us? Obvioously, Hakon is trying to drag out this issue.

RE: Websocket connection has timeout too frequently

Håkon Alseth — Wed, 03 Sep 2025 07:04:44 GMT

Hi,

[quote user="esmart-engineering"]The constant "Cannot connect to 192.168.32.166:3001 (err -113)" is not the issue I am talking about[/quote]

Your logs show both -113 and -116.

[quote user="esmart-engineering"]Please carefully re-examine the exact problem I am talking about. Also pay attention to the other details I've shared; for example, the problem occasionally (roughly 50% of the time) occurs.[/quote]

According to the logs that you posted, you are still running in a for-loop. If you look into what the websocket library does, it will create a new socket for each try. This means that you will exhaust the amount of sockets available if you hammer on.

[quote user="hkn"]However, if you only run the function send_data_to_server() once, it will show:[/quote]

To debug an issue, please take in one step at the time, then adjust when you're seeing issues.

This includes trying different scripts, specifically those intended to work with the sample itself, ie. websocketd for instance.

Kind regards,

Håkon

RE: Websocket connection has timeout too frequently

esmart-engineering — Tue, 02 Sep 2025 21:52:59 GMT

Apologies for the late response.

The constant "Cannot connect to 192.168.32.166:3001 (err -113)" is not the issue I am talking about. My issue is seeing "Cannot connect to IPv4 remote (-116)" which is coming from connect_to_server(). Please carefully re-examine the exact problem I am talking about. Also pay attention to the other details I've shared; for example, the problem occasionally (roughly 50% of the time) occurs.

Your Python server is set up to receive 1 message, which is not my intention. It should connect to the nRF, receive multiple messages, then require user to Ctrl+C and rerun the server whenever the nRF needs to be run again. I've attached my script and an example of what you should see.

devzone.nordicsemi.com/.../server.py devzone.nordicsemi.com/.../server_5F00_log.txt

I went ahead and tried your configurations anyway, but it did not help with my issue.

RE: Websocket connection has timeout too frequently

Håkon Alseth — Mon, 18 Aug 2025 12:34:43 GMT

Hi,

This is the log that I am seeing:

*** Booting nRF Connect SDK v2.9.2-4ab7b98fc76f ***
*** Using Zephyr OS v3.7.99-aa34a5632971 ***
[00:00:00.688,720] <inf> net_config: Initializing network
[00:00:00.688,751] <inf> net_config: Waiting interface 1 (0x20001290) to be up...
[00:00:00.688,903] <inf> net_config: IPv4 address: 192.168.32.99
[00:00:00.688,964] <inf> net_config: Running dhcpv4 client...
[00:00:00.689,788] <inf> sta: Starting nrf7002dk with CPU frequency: 64 MHz
[00:00:00.691,467] <inf> wifi_supplicant: wpa_supplicant initialized
[00:00:01.689,971] <inf> sta: Static IP address (overridable): 192.168.32.99/255.255.255.0 -> 192.168.32.1
[00:00:03.239,898] <inf> wifi_mgmt_ext: Connection requested
[00:00:03.239,929] <inf> sta: Connection requested
[00:00:03.239,990] <inf> sta: ==================
[00:00:03.240,020] <inf> sta: State: SCANNING
[00:00:03.540,161] <inf> sta: ==================
[00:00:03.540,191] <inf> sta: State: SCANNING
[00:00:03.840,332] <inf> sta: ==================
[00:00:03.840,362] <inf> sta: State: SCANNING
[00:00:04.140,502] <inf> sta: ==================
[00:00:04.140,533] <inf> sta: State: SCANNING
[00:00:04.440,673] <inf> sta: ==================
[00:00:04.440,704] <inf> sta: State: SCANNING
[00:00:04.740,844] <inf> sta: ==================
[00:00:04.740,875] <inf> sta: State: SCANNING
[00:00:05.041,015] <inf> sta: ==================
[00:00:05.041,015] <inf> sta: State: SCANNING
[00:00:05.341,186] <inf> sta: ==================
[00:00:05.341,186] <inf> sta: State: SCANNING
[00:00:05.641,326] <inf> sta: ==================
[00:00:05.641,357] <inf> sta: State: SCANNING
[00:00:05.941,528] <inf> sta: ==================
[00:00:05.941,558] <inf> sta: State: SCANNING
[00:00:06.241,668] <inf> sta: ==================
[00:00:06.241,699] <inf> sta: State: SCANNING
[00:00:06.541,870] <inf> sta: ==================
[00:00:06.541,900] <inf> sta: State: SCANNING
[00:00:06.842,041] <inf> sta: ==================
[00:00:06.842,041] <inf> sta: State: SCANNING
[00:00:07.142,211] <inf> sta: ==================
[00:00:07.142,242] <inf> sta: State: SCANNING
[00:00:07.442,352] <inf> sta: ==================
[00:00:07.442,382] <inf> sta: State: SCANNING
[00:00:07.742,523] <inf> sta: ==================
[00:00:07.742,553] <inf> sta: State: SCANNING
[00:00:08.042,724] <inf> sta: ==================
[00:00:08.042,755] <inf> sta: State: AUTHENTICATING
[00:00:08.342,895] <inf> sta: ==================
[00:00:08.342,926] <inf> sta: State: AUTHENTICATING
[00:00:08.452,941] <inf> sta: Connected
[00:00:12.475,097] <inf> net_dhcpv4: Received: 192.168.32.198
[00:00:12.475,280] <inf> net_config: IPv4 address: 192.168.32.198
[00:00:12.475,280] <inf> net_config: Lease time: 36000 seconds
[00:00:12.475,341] <inf> net_config: Subnet: 255.255.255.0
[00:00:12.475,372] <inf> net_config: Router: 192.168.32.1
[00:00:12.475,463] <inf> sta: DHCP IP address: 192.168.32.198
[00:00:12.657,257] <inf> sta: ==================
[00:00:12.657,287] <inf> sta: State: COMPLETED
[00:00:12.657,318] <inf> sta: Interface Mode: STATION
[00:00:12.657,348] <inf> sta: Link Mode: WIFI 6 (802.11ax/HE)
[00:00:12.657,379] <inf> sta: SSID: OpenWrt
[00:00:12.657,409] <inf> sta: BSSID: FC:34:97:0B:F6:DC
[00:00:12.657,409] <inf> sta: Band: 5GHz
[00:00:12.657,440] <inf> sta: Channel: 44
[00:00:12.657,440] <inf> sta: Security: WPA2-PSK
[00:00:12.657,470] <inf> sta: MFP: Optional
[00:00:12.657,470] <inf> sta: RSSI: -60
[00:00:13.657,562] <inf> sta: Try to open as client
[00:00:13.740,417] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:13.740,417] <err> sta: No IPv4 connectivity
[00:00:13.740,905] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:13.740,905] <err> sta: No IPv4 connectivity
[00:00:13.741,363] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:13.741,363] <err> sta: No IPv4 connectivity
[00:00:13.741,821] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:13.741,851] <err> sta: No IPv4 connectivity
[00:00:13.742,309] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:13.742,309] <err> sta: No IPv4 connectivity
[00:00:13.742,767] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:13.742,797] <err> sta: No IPv4 connectivity
[00:00:13.743,255] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:13.743,255] <err> sta: No IPv4 connectivity
[00:00:13.743,713] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:13.743,713] <err> sta: No IPv4 connectivity
[00:00:13.744,201] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:13.744,201] <err> sta: No IPv4 connectivity
[00:00:13.744,659] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:13.744,659] <err> sta: No IPv4 connectivity
[00:00:13.766,021] <inf> sta: Interface down
[00:00:13.766,143] <inf> wifi_supplicant: Network interface 1 (0x20001290) down

On the server side, I am running a small py script just to setup a server on port 3001:

#! /usr/bin/python
# a simple tcp server
import socket,os
sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
sock.bind(('192.168.32.166', 3001))
sock.listen(5)
while True:
    connection,address = sock.accept()
    buf = connection.recv(1024)
    print(buf)
    connection.send(buf)     
    connection.close()

Which prints this each time I connect:

b'GET / HTTP/1.1\r\nHost: 192.168.32.166\r\nOrigin: http://foobar\r\nSec-WebSocket-Key: lm0W7zOrdWFToQCN8Kkcmg==\r\nUpgrade: websocket\r\nConnection: Upgrade\r\nSec-WebSocket-Version: 13\r\n\r\n'

Running the websocketd as described here:

https://docs.zephyrproject.org/latest/samples/net/sockets/websocket_client/README.html#running-websocket-server-in-linux-host

Shows similar issues as before, ie. that the log spits out:

[00:00:13.955,291] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:13.955,291] <err> sta: No IPv4 connectivity
[00:00:14.078,338] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:14.078,338] <err> sta: No IPv4 connectivity
[00:00:14.178,863] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:14.178,894] <err> sta: No IPv4 connectivity
[00:00:14.279,449] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:14.279,449] <err> sta: No IPv4 connectivity
[00:00:14.380,004] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:14.380,035] <err> sta: No IPv4 connectivity
[00:00:14.480,621] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:14.480,651] <err> sta: No IPv4 connectivity
[00:00:14.581,207] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:14.581,237] <err> sta: No IPv4 connectivity
[00:00:14.681,793] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:14.681,793] <err> sta: No IPv4 connectivity
[00:00:14.782,348] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:14.782,379] <err> sta: No IPv4 connectivity
[00:00:14.882,934] <err> sta: Cannot connect to 192.168.32.166:3001 (err -113)
[00:00:14.882,934] <err> sta: No IPv4 connectivity

However, if you only run the function send_data_to_server() once, it will show:

*** Booting nRF Connect SDK v2.9.2-4ab7b98fc76f ***
*** Using Zephyr OS v3.7.99-aa34a5632971 ***
[00:00:00.638,793] <inf> net_config: Initializing network
[00:00:00.638,793] <inf> net_config: Waiting interface 1 (0x20000d98) to be up...
[00:00:00.638,977] <inf> net_config: IPv4 address: 192.168.32.99
[00:00:00.639,007] <inf> net_config: Running dhcpv4 client...
[00:00:00.639,953] <inf> sta: Starting nrf7002dk with CPU frequency: 64 MHz
[00:00:00.641,845] <inf> wifi_supplicant: wpa_supplicant initialized
[00:00:01.640,136] <inf> sta: Static IP address (overridable): 192.168.32.99/255.255.255.0 -> 192.168.32.1
[00:00:03.560,089] <inf> wifi_mgmt_ext: Connection requested
[00:00:03.560,119] <inf> sta: Connection requested
[00:00:03.560,180] <inf> sta: ==================
[00:00:03.560,211] <inf> sta: State: SCANNING
[00:00:08.062,774] <inf> sta: ==================
[00:00:08.062,774] <inf> sta: State: SCANNING
[00:00:08.362,945] <inf> sta: ==================
[00:00:08.362,976] <inf> sta: State: AUTHENTICATING
[00:00:08.663,116] <inf> sta: ==================
[00:00:08.663,146] <inf> sta: State: AUTHENTICATING
[00:00:08.730,682] <inf> sta: Connected
[00:00:12.988,555] <inf> sta: ==================
[00:00:12.988,586] <inf> sta: State: COMPLETED
[00:00:12.988,616] <inf> sta: Interface Mode: STATION
[00:00:12.988,647] <inf> sta: Link Mode: WIFI 6 (802.11ax/HE)
[00:00:12.988,647] <inf> sta: SSID: OpenWrt
[00:00:12.988,677] <inf> sta: BSSID: FC:34:97:0B:F6:DC
[00:00:12.988,708] <inf> sta: Band: 5GHz
[00:00:12.988,708] <inf> sta: Channel: 44
[00:00:12.988,739] <inf> sta: Security: WPA2-PSK
[00:00:12.988,769] <inf> sta: MFP: Optional
[00:00:12.988,769] <inf> sta: RSSI: -55
[00:00:13.752,960] <inf> net_dhcpv4: Received: 192.168.32.198
[00:00:13.753,143] <inf> net_config: IPv4 address: 192.168.32.198
[00:00:13.753,173] <inf> net_config: Lease time: 36000 seconds
[00:00:13.753,204] <inf> net_config: Subnet: 255.255.255.0
[00:00:13.753,234] <inf> net_config: Router: 192.168.32.1
[00:00:13.753,356] <inf> sta: DHCP IP address: 192.168.32.198
[00:00:13.988,830] <inf> sta: Try to open as client
[00:00:14.059,570] <err> sta: 12
[00:00:14.069,183] <inf> sta: Websocket 13 for IPv4 connected.
[00:00:14.069,183] <inf> sta: Websocket IPv4 13

I added these configurations to maximize the amount of sockets / net contexts:

CONFIG_ZVFS_OPEN_MAX=20
CONFIG_NET_SOCKETS_POLL_MAX=20
CONFIG_NET_CONFIG_NEED_IPV6=n
CONFIG_NET_IPV6=n
CONFIG_NET_MAX_CONTEXTS=20

Could you try the same and see if it runs accordingly?

Kind regards,

Håkon

RE: Websocket connection has timeout too frequently

esmart-engineering — Thu, 14 Aug 2025 22:36:54 GMT

Could be a RAM issue, but I also tested on an nRF7002DK (using nRF53 which has 2x RAM as nRF52) and saw the same issue.

I've attached the whole project here you can use. Please build based off the build configuration presets I have for the nRF52+nRF70, as well as the nRF7002DK I just tried.

devzone.nordicsemi.com/.../wifi_5F00_station_5F00_w_5F00_sockets.zip

RE: Websocket connection has timeout too frequently

Håkon Alseth — Thu, 14 Aug 2025 09:31:32 GMT

Hi,

[quote user="esmart-engineering"]My log is from before making the change,[/quote]

It is important that you disclose such information when posting, to avoid any confusion, such is the scenario right now.

[quote user="esmart-engineering"]It has been a week since the posting and we've only gotten small suggestions that are not helping whatsoever. Please look into this more in depth and give us a solid concrete solution for us to try.[/quote]

I understand that this issue is blocking your evaluation and development, and I aim to help you with this. However, I am going to stress this as much as I can, please do not truncate any information that you share on devzone. Logs show warnings and errors, and leaving them out makes it hard to be able to help you.

Can you please share your configurations and settings, so I can recreate this in the STA sample?

You are combining the nRF52840 with the nRF7002, which is a tight fit wrt. RAM, meaning that it needs to be optimized quite heavily.

Kind regards,

Håkon

RE: Websocket connection has timeout too frequently

esmart-engineering — Wed, 13 Aug 2025 20:17:01 GMT

It has been a week since the posting and we've only gotten small suggestions that are not helping whatsoever. Please look into this more in depth and give us a solid concrete solution for us to try.

RE: Websocket connection has timeout too frequently

esmart-engineering — Wed, 13 Aug 2025 18:02:02 GMT

As I already mentioned, the issue was resolved with CONFIG_NET_PKT_TX_COUNT. My log is from before making the change, but the log does not differ much with or without the change. And again it does not resolve my primary issue.

I also tried CONFIG_NET_BUF_DATA_SIZE (to 256, 512, and 4096) and none of these fixed the packet allocation issues like CONFIG_NET_PKT_TX_COUNT did.

If by "NET_PKT configuration", you mean KConfig flags related to "NET_PKT", then I have CONFIG_NET_PKT_RX_COUNT=8 and CONFIG_NET_PKT_TX_COUNT=16 explicitly stated in my "prj.conf" file. The following is what I see in my build output ".config" file:

CONFIG_NET_PKT_RX_COUNT=8
CONFIG_NET_PKT_TX_COUNT=16
...
# CONFIG_NET_PKT_TXTIME is not set
# CONFIG_NET_PKT_TIMESTAMP is not set
...
# CONFIG_NET_CONTEXT_NET_PKT_POOL is not set
...
CONFIG_NET_PKT_BUF_RX_DATA_POOL_SIZE=4096
CONFIG_NET_PKT_BUF_TX_DATA_POOL_SIZE=4096
CONFIG_NET_PKT_BUF_USER_DATA_SIZE=4
...
# CONFIG_NET_PKT_RXTIME_STATS is not set
# CONFIG_NET_PKT_TXTIME_STATS is not set
...
# CONFIG_NET_PKT_LOG_LEVEL_OFF is not set
# CONFIG_NET_PKT_LOG_LEVEL_ERR is not set
# CONFIG_NET_PKT_LOG_LEVEL_WRN is not set
# CONFIG_NET_PKT_LOG_LEVEL_INF is not set
# CONFIG_NET_PKT_LOG_LEVEL_DBG is not set
CONFIG_NET_PKT_LOG_LEVEL_DEFAULT=y
CONFIG_NET_PKT_LOG_LEVEL=3
# CONFIG_NET_DEBUG_NET_PKT_ALLOC is not set
CONFIG_NET_DEBUG_NET_PKT_EXTERNALS=0
# CONFIG_NET_DEBUG_NET_PKT_NON_FRAGILE_ACCESS is not set
...
# CONFIG_NET_PKT_FILTER is not set

-------

EDIT #1 - Here's another log, with complete output and with the CONFIG_NET_PKT_TX_COUNT=16 fix.

devzone.nordicsemi.com/.../websocket_5F00_log2.txt

RE: Websocket connection has timeout too frequently

Håkon Alseth — Wed, 13 Aug 2025 14:02:35 GMT

Hi,

You still have packet allocation issues, based on your latest log.

[00:00:09.321,838] <wrn> net_tcp: net_pkt alloc failure
[00:00:09.626,037] <wrn> net_tcp: net_pkt alloc failure
[00:00:09.930,236] <wrn> net_tcp: net_pkt alloc failure

What NET_PKT configuration did you end up using?

Kind regards,

Håkon

RE: Websocket connection has timeout too frequently

esmart-engineering — Tue, 12 Aug 2025 15:55:43 GMT

Server reports it connected to nRF with an IP 192.168.101.x

Log only had the following removed. Apologies. Initially it was to avoid confusion on when the nRF connected to the socket, but looking at it now it could be relevant:

...

[00:00:09.321,838] <wrn> net_tcp: net_pkt alloc failure
[00:00:09.626,037] <wrn> net_tcp: net_pkt alloc failure
[00:00:09.930,236] <wrn> net_tcp: net_pkt alloc failure
[00:00:10.864,440] <inf> net_dhcpv4: Received: 192.168.101.143
[00:00:10.864,654] <inf> net_config: IPv4 address: 192.168.101.143
[00:00:10.864,685] <inf> net_config: Lease time: 86400 seconds
[00:00:10.864,715] <inf> net_config: Subnet: 255.255.255.0
[00:00:10.864,776] <inf> net_config: Router: 192.168.101.1
[00:00:10.864,898] <inf> sta: DHCP IP address: 192.168.101.143
[00:00:10.951,232] <err> sta: Cannot connect to IPv4 remote (-116)
[00:00:10.951,232] <err> sta: Cannot create HTTP connection.
[00:00:12.052,185] <wrn> net_tcp: net_pkt alloc failure
[00:00:15.052,337] <err> sta: Cannot connect to IPv4 remote (-116)
[00:00:15.052,337] <err> sta: Cannot create HTTP connection.
...

Regardless, logs indicate 3sec in this particular case between attempting to connect to socket, and receiving the 192.168.101.x IP address. This seems too long.

RE: Websocket connection has timeout too frequently

Håkon Alseth — Tue, 12 Aug 2025 11:47:57 GMT

Hi,

Can you confirm that you're receiving an IP within 192.168.101.x range? Or with a netmask of 255.255.0.0 if in the 192.168.x.x range?

Could you please share the full log, and do not take out any of the lines? Feel free to redact the SSID for instance.

Kind regards,

Håkon

RE: Websocket connection has timeout too frequently

esmart-engineering — Tue, 12 Aug 2025 09:04:34 GMT

I already have CONFIG_NET_DHCPV4=y. In addition, I had these which probably explain the IP's/masks in the log:

CONFIG_NET_CONFIG_MY_IPV4_ADDR="192.168.1.99"
CONFIG_NET_CONFIG_MY_IPV4_NETMASK="255.255.255.0"
CONFIG_NET_CONFIG_MY_IPV4_GW="192.168.1.1"

RE: Websocket connection has timeout too frequently

Håkon Alseth — Tue, 12 Aug 2025 08:47:58 GMT

Hi,

You're connecting to a server on 192.168.101.x, have you enabled DHCPv4 on the nRF side?

If not, it will default to this IP and mask:

....[00:00:01.774,780] <inf> sta: Static IP address (overridable): 192.168.1.99/255.255.255.0 -> 192.168.1.1

Kind regards,

Håkon

RE: Websocket connection has timeout too frequently

esmart-engineering — Tue, 12 Aug 2025 07:58:10 GMT

Socket is created and a connection is established in connect_to_server().

I will try those KConfig flags when I get in the office next. I previously increased CONFIG_NET_PKT_TX_COUNT from 8 to 16, and this removed those "alloc failure" messages. But the problem still persists.

RE: Websocket connection has timeout too frequently

Håkon Alseth — Tue, 12 Aug 2025 07:24:07 GMT

Hi,

Where is your socket created?

The log lines here indicate that the network stack isn't able to allocate data:

[00:00:09.321,838] <wrn> net_tcp: net_pkt alloc failure
[00:00:09.626,037] <wrn> net_tcp: net_pkt alloc failure
[00:00:09.930,236] <wrn> net_tcp: net_pkt alloc failure

You can try to adjust the buf size via "CONFIG_NET_BUF_DATA_SIZE", or you can switch do a variable data size buffer for the net stack via "CONFIG_NET_BUF_VARIABLE_DATA_SIZE=y".

Kind regards,

Håkon

RE: Websocket connection has timeout too frequently

esmart-engineering — Sat, 09 Aug 2025 03:10:39 GMT

I tested closing my socket after use but it did not help.

Here's the relevant code:

int sock4 = -1;

static int wifi_connect(void) { // same definition as WiFi station example }

static int wifi_shutdown(void)
{   // based off NCS v2.9.1 (nrf/samples/wifi/shutdown)
	int ret;
	struct net_if *iface = net_if_get_default();

	if (!net_if_is_admin_up(iface)) {
		return 0;
	}

	ret = net_if_down(iface);
	if (ret) {
		LOG_ERR("Cannot bring down iface (%d)", ret);
		return ret;
	}

	LOG_INF("Interface down");

	return 0;
}

int connect_to_server(void)
{   // based off Websocket client example
    
	struct sockaddr_in addr4;
	size_t amount;
	int ret = -1;

	LOG_INF("Try to open as client");
	while (ret < 0) {
		if (IS_ENABLED(CONFIG_NET_IPV4)) {
			ret = connect_socket(AF_INET, SERVER_ADDR4, SERVER_PORT,
						&sock4, (struct sockaddr *)&addr4,
						sizeof(addr4));
		}
		if (sock4 < 0 || ret < 0) {
			LOG_ERR("Cannot create HTTP connection.");
			k_sleep(K_SECONDS(1));
		}
	}
}

int send_data_to_server(void)
{   // based off Websocket client example

	/* Just an example how to set extra headers */
	const char *extra_headers[] = {
		"Origin: http://foobar\r\n",
		NULL
	};
	int websock4 = -1;
	int32_t timeout = 150;	// units [ms]

	if (sock4 >= 0 && IS_ENABLED(CONFIG_NET_IPV4)) {
		struct websocket_request req;

		memset(&req, 0, sizeof(req));

		req.host = SERVER_ADDR4;
		req.url = "/";
		req.optional_headers = extra_headers;
		req.cb = connect_cb;
		req.tmp_buf = temp_recv_buf_ipv4;
		req.tmp_buf_len = sizeof(temp_recv_buf_ipv4);

		websock4 = websocket_connect(sock4, &req, timeout, "IPv4");
		if (websock4 < 0) {
			LOG_ERR("Cannot connect to %s:%d (err %d)",
				SERVER_ADDR4, SERVER_PORT,
				websock4);
			// close(sock4);
		}
	}
	if (websock4 < 0) {
		LOG_ERR("No IPv4 connectivity");
		return -2;
	}
	LOG_INF("Websocket IPv4 %d", websock4);
}

int start_app(void)
{       // main() calls this; my main() has same definition as main() from WiFi station example
	LOG_INF("Static IP address (overridable): %s/%s -> %s",
		CONFIG_NET_CONFIG_MY_IPV4_ADDR,
		CONFIG_NET_CONFIG_MY_IPV4_NETMASK,
		CONFIG_NET_CONFIG_MY_IPV4_GW);
		
	while (1) {
	    wifi_connect();

		while (!context.connect_result) {
			cmd_wifi_status();
			k_sleep(K_MSEC(STATUS_POLLING_MS));
		}

		if (context.connected) {
			cmd_wifi_status();

			connect_to_server();
			
			// Send data multiple times
			for (uint8_t i = 0; i < 10; i ++) {
			    send_data_to_server();
			}
			
			// Close socket
			    // NOTE - didn't try with websock4, since I see "No IPv4 connectivity" log output
			if (sock4 >= 0) {
			    close(sock4);
			}

			wifi_shutdown();
			k_sleep(K_SECONDS(1));

			sys_poweroff();
		}
	}
}

Here's the log I get:
devzone.nordicsemi.com/.../websocket_5F00_log.txt

Again, for context:

I call connect() multiple times because there's a timeout in trying to connect; it's confirmed on my server too that no connection is established.
I see the attempt to connect to socket will timeout if I see "Cannot connect to IPv4 remote (-116)"
The data arrives on the server if I see " Cannot connect to 192.168.101.98:3001 (err -113)". The message is misleading but my server does receive data.

RE: Websocket connection has timeout too frequently

Håkon Alseth — Thu, 07 Aug 2025 12:57:03 GMT

Hi,

[quote user=""]

Functionally my code is working: able to connect to WiFi, connect to socket, and send some data. For sending data, I'm having it repeatedly call websocket_connect(); it will return with an error but my server still gets the data (which is acceptable at this time of evaluation).

However, once my code gets to the connect() call as part of connect_socket(), it will occasionally (roughly 50% of the time) timeout after the default 3sec. I modified it to repeatedly call connect() until it succeeds, and noticed it may take 2-3 tries to connect. But this means that it's taking almost 10sec at most just to simply connect to a socket.

[/quote]

Can you share logs and relevant code for this procedure?

Are you closing your sockets after use?

If you are already connected via a socket, you should not run connect() multiple times.

[quote user=""]Note that I also tried one of Nordic's official networking samples - the HTTPS client one (NCS v2.9.1, nrf/samples/net/https_client).[/quote]

This sample does not have support for the board combination that you're using:

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/net/https_client/README.html#requirements

Kind regards,

Håkon