In message <[email protected]>, Gleb Smirnoff writes: > On Tue, Oct 07, 2025 at 09:25:20PM -0700, Cy Schubert wrote: > C> Without more context in the upstream commit log message it's difficult we > C> must surmise that the wait for ARP/NDP resolution could be due to a very > C> busy unbound service combined with latency in ARP/NDP resolution. I haven' > t > C> found any upstream Github issues that document this problem. > > When a system can't send UDP packets due to no ARP/NDP entry for the next hop > , > the packets are not stored in the send buffer. Or does unbound do this for > the TCP socket?
That didn't make sense to me either. Giving upstream the benefit of the doubt I took it (the commit log entry) to mean TCP instead of UDP. -- Cheers, Cy Schubert <[email protected]> FreeBSD UNIX: <[email protected]> Web: https://FreeBSD.org NTP: <[email protected]> Web: https://nwtime.org e**(i*pi)+1=0
