u-boot.git/net/lwip, branch next

net: lwip: dhcp: fix DHCP fine timer interval

2026-08-12T12:23:14Z

dhcp_fine_tmr() was called every 10ms, but lwIP expects it to be called every DHCP_FINE_TIMER_MSECS (500ms). Since the fine timer ticks are currently 50 times faster than lwIP expects, the client burns through the bounded exponential backoff sequence for the DHCPREQUEST messages in 2.44 seconds rather than 122 seconds, after which it uses a new xid and returns to sending DHCPDISCOVER messages. If there is enough latency in the server, the client could receive an ACK response within DHCP_TIMEOUT_MS (10 seconds), but reject it because it has already moved on with another xid after 2.44 seconds. We have seen this occur with our boards. When our rack of 16 boards get powered on together, they all request for an address from the network switch's DHCP server in near lock-step and we see that only a few of the boards actually obtain a lease. Fixing the timing to 500ms allowed all of the boards to obtain a lease consistently. Fixes: 98ad145db61a ("net: lwip: add DHCP support and dhcp commmand") Signed-off-by: Luca Jones

net: lwip: handle chained pbufs in transmit path

2026-07-23T15:05:20Z

LwIP may pass a packet to the netif linkoutput callback as a chain of pbufs. In this case, p->len only describes the length of the first pbuf, while p->tot_len describes the length of the whole packet. The current transmit path only sends the first pbuf. This can truncate packets whose headers have already been generated for the full packet length, resulting in malformed frames on the wire. For example, the IP header may record a larger total length than the actual Ethernet frame length. Assemble chained pbufs into one aligned contiguous buffer before passing the packet to the Ethernet driver. Fixes: 98ad145db61a (net: lwip: add DHCP support and dhcp commmand) Signed-off-by: Weijie Gao Reviewed-by: Jerome Forissier

net: lwip: add tftpsrv command

2026-07-23T15:05:20Z

The legacy network stack supports tftpsrv, which listens for an incoming TFTP write request and receives the first file into memory. Despite the old command help wording, the command returns after receiving the file and does not boot it automatically. The lwIP stack already builds the lwIP TFTP application, but only wires it up for client-side tftpboot. Add a lwIP tftpsrv command and implement the server path with tftp_init_server(). Reuse the existing lwIP TFTP write callback and memory copy path so LMB checks, progress output, filesize/fileaddr updates and EFI bootdev handling stay consistent with tftpboot. Track receive timeout and write-failure state around the lwIP callbacks so a stalled or rejected receive is not reported as a successful close. Move CMD_TFTPSRV out of the legacy-only Kconfig block so it can be enabled with either network stack. Update the command help text and add usage documentation for the receive-only behavior. Add pytest coverage for tftpsrv using a generated host file and curl's TFTP upload support. Enable the command in qemu_arm64_lwip_defconfig so the test can be run with the existing lwIP QEMU build when the boardenv provides env__net_tftpsrv_file. Signed-off-by: James Hilliard [Jerome Forissier: remove trailing ':' after SPDX tag] Signed-off-by: Jerome Forissier Reviewed-by: Jerome Forissier

Merge branch 'next'

2026-07-07T00:26:12Z

Kconfig: net: restyle

2026-06-25T20:15:33Z

Restyle all Kconfigs for "net": Menu entries : no space left Menu attributes: 1 TAB Help text : 1 TAB + 2 spaces Replace '---help---' by 'help' Signed-off-by: Johan Jonker

net: lwip: introduce net_lwip_eth_stop() function

2026-06-23T11:13:16Z

Add a introduce net_lwip_eth_stop() function and use that to stop the network interface after each command that uses the network. This makes the behavior the same as the legacy net code and avoids potential issues with the network interface being left in an active state after a command finishes. The start/stop is reference-counted since there is at least one command (dhcp) that calls another command (tftp) to avoid starting and stopping the network interface multiple times in a single command. Signed-off-by: David Lechner Reviewed-by: Jerome Forissier

net: lwip: wget: return errno codes from wget_do_request()

2026-06-23T11:13:16Z

Change the return values of the lwip implementation of wget_do_request() to be errno codes instead of command return codes. wget_do_request() is not a command, so it does not make sense to return command return codes from it. Also, the legacy network implementation of wget_do_request() already returns errno codes so it is logical for the lwip implementation to do the same. This fixes a bug in try_load_from_uri_path() in efi_manager.c where it checks that the return value of wget_do_request() is < 0. Before this change, CMD_RET_FAILURE would not be considered an error since it has a value of 1. The value of ENODEV is used in places where there could actually be a number of different causes of failure and it isn't possible to discriminate (i.e. failing function returns NULL for all errors). Since all callers of wget_do_request() don't propagate the error code, it doesn't matter so much that this is not ideal, at least at this point in time. Fixes: 3c656c928bd7 ("net: lwip: add wget command") Reviewed-by: Jerome Forissier Signed-off-by: David Lechner

net: lwip: wget: fix error handling in wget_do_request()

2026-06-23T11:13:16Z

Split wget_do_request() into two functions to make error handling less error-prone. After a successful call to net_lwip_new_netif(), net_lwip_remove_netif() must always be called to prevent leaks. This was missed in the CACERT section of the code where we returned on error without cleaning up. Instead of adding more calls to net_lwip_remove_netif(), refactor the code into two functions. The outer function handles managing the netif lifecycle. The inner function no longer has to worry about cleaning up before returning on error. To keep things simple, the `path` local variable is removed during the refactoring. Instead, ctx.path is used directly everywhere. Fixes: 3c656c928bd7 ("net: lwip: add wget command") Reviewed-by: Jerome Forissier Acked-by: Ilias Apalodimas Signed-off-by: David Lechner

net: lwip/wget: don't print progress bar when silent

2026-05-06T09:07:22Z

When the EFI sub-system request to silence output, do not output a progress bar. Signed-off-by: Heinrich Schuchardt Reviewed-by: Jerome Forissier

net: lwip/wget: don't print content size twice

2026-05-06T09:07:22Z

If wget_info->silent is set, we should not print anything. If wget_info->silent we print the received content size. Printing the value of the Content-Length header is redundant For chunked transfer no Content-Length header is sent. The content length is returned as HTTPC_CONTENT_LEN_INVALID by the LwIP library. In this case we were incorrectly printing '4 GiB'. Signed-off-by: Heinrich Schuchardt Reviewed-by: Jerome Forissier