On 2026/02/24 11:36, Kirill A. Korinsky wrote:
> On Tue, 24 Feb 2026 07:35:41 +0100,
> Klemens Nanni <kn@openbsd.org> wrote:
> > 
> > 23.02.2026 00:44, Kirill A. Korinsky пишет:
> > > On Sat, 21 Feb 2026 18:30:14 +0100,
> > > Klemens Nanni <kn@openbsd.org> wrote:
> > 
> >      -w seconds
> >              Wait for seconds for the remote server to connect before giving
> >              up.
> > 
> > This should be the equivalent to curl(1)'s --connect-timeout, although I
> > did not see which default value they provide.

curl's --connect-timeout default is 5 minutes. this includes DNS (which
can be quite long if you have a few NS listed) and TLS (in particular,
the handshake can stall if you have MTU issues). I believe ftp(1) just
uses this on the connect call which would not be equivalent.

> But issue is not only connect timeout, but when IP address is changed when
> it downloading something. As far as I understand code, we haven't got non
> connect timeout at all.

only implicit timeouts from TCP keepalives, if enabled.

btw, if that is a common issue on a machine, you might like:

net.inet.tcp.keepidle=300
net.inet.tcp.always_keepalive=1

also useful if you are on a network with fast NAT state timeouts.