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

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

net: lwip/wget: missing linefeed in diagnostic output

2026-05-06T09:07:22Z

With NET_LWIP wget produces this output with an overlong line and missing white space: => wget $kernel_addr_r http://example.com/ ################################################# 4 GiB540 bytes transferred in 2 ms (263.7 KiB/s) Bytes transferred = 540 (21c hex) Removing the condition on inserting a line feed yields: => wget $kernel_addr_r http://example.com/ ################################################# 4 GiB 540 bytes transferred in 2 ms (263.7 KiB/s) Bytes transferred = 540 (21c hex) Signed-off-by: Heinrich Schuchardt Reviewed-by: Jerome Forissier

net: lwip: tftp: update image_load_addr after successful transfer

2026-03-31T14:54:49Z

do_tftpb() parses the load address into a local variable laddr but never updates the global image_load_addr. Commands that rely on image_load_addr as their default address (e.g. 'bmp info') therefore operate on the wrong address when called without an explicit argument after tftpboot. Update image_load_addr to laddr only on a successful transfer, so that it accurately reflects where data was actually loaded. Fixes: 4d4d7838127e ("net: lwip: add TFTP support and tftpboot command") Signed-off-by: Pranav Sanwal Reviewed-by: Jerome Forissier

net: lwip: nfs: fix buffer overflow when using symlinks

2026-03-31T14:43:28Z

When resolving a symlink, nfs_path points into a heap allocated buffer which is just large enough to hold the original path with no extra space. If the symlink target name is longer than the original filename, the write goes beyond the end of the buffer corrupting heap memory. Fix this by ensuring nfs_path always points to a buffer large enough to accommodate the resolved symlink path. Fixes: 230cf3bc2776 ("net: lwip: nfs: Port the NFS code to work with lwIP") Signed-off-by: Pranav Tilak Acked-by: Jerome Forissier Reviewed-by: Jerome Forissier

net: lwip: wget: rework the '#' printing

2026-02-06T15:42:45Z

Currently, the LWIP wget command prints excessive amount of progress indicator '#' for very long file downloads, limit this to one line that scales according to transfer size. The HTTP server does report the size of the entire file in protocol headers, which are received before the actual data transfer. Cache this information and use it to adaptively print progress indicator '#' until it fills one entire line worth of '#', which indicates the transfer has completed. This way, long transfers don't print pages of '#', but every transfer will print exactly one line worth of '#'. The algorithm for '#' printing is the same as TFTP tsize one. Signed-off-by: Marek Vasut Acked-by: Jerome Forissier

net: lwip: tftp: add support of tsize option to client

2026-02-06T15:42:37Z

The TFTP server can report the size of the entire file that is about to be received in the Transfer Size Option, this is described in RFC 2349. This functionality is optional and the server may not report tsize in case it is not supported. Always send tsize request to the server to query the transfer size, and in case the server does respond, cache that information locally in tftp_state.tsize, otherwise cache size 0. Introduce new function tftp_client_get_tsize() which returns the cached tftp_state.tsize so clients can determine the transfer size and use it. Update net/lwip/tftp.c to make use of tftp_client_get_tsize() and avoid excessive printing of '#' during TFTP transfers in case the transfer size is reported by the server. Submitted upstream: https://savannah.nongnu.org/patch/index.php?item_id=10557 Signed-off-by: Marek Vasut Acked-by: Jerome Forissier