Date: Tue, 07 Oct 2025 21:25:20 -0700 From: Cy Schubert <Cy.Schubert@cschubert.com> To: Jose Luis Duran <jlduran@gmail.com>, Cy Schubert <Cy.Schubert@cschubert.com>, jlduran+freebsd@freebsd.org, Cy Schubert <cy@FreeBSD.org>, src-committers@freebsd.org, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org Subject: Re: git: b2efd602aea8 - main - unbound: Vendor import 1.24.0 Message-ID: <20251008042520.C47BA3AB@slippy.cwsent.com> In-Reply-To: <aOXN8ySmTaQL3tBA@amaryllis.le-fay.org> References: <202510071524.597FOTr3063628@gitrepo.freebsd.org> <CAPwQLcep1-Pt4P1QHiJpnZrMXXicG5Bc_tpxa6MtjVZT%2BvpJmg@mail.gmail.com> <20251007221221.22BCC29E@slippy.cwsent.com> <20251007230048.64C8F39B@slippy.cwsent.com> <CAPwQLcd8cuttgT4tYcExcQraWYisRECfe49_XkCyvrZ3pW=ZDw@mail.gmail.com> <aOXN8ySmTaQL3tBA@amaryllis.le-fay.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <aOXN8ySmTaQL3tBA@amaryllis.le-fay.org>, Lexi Winter writes:
>
>
> --fsIKWKOqZus1STs3
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> Jose Luis Duran wrote in <CAPwQLcd8cuttgT4tYcExcQraWYisRECfe49_XkCyvrZ3pW=
> =3DZDw@mail.gmail.com>:
> > > > > This means so-sndbuf is now 4m. Which triggers a warning, detailed =
> in
> > > > > upstream commit 713b5db5 ("- Fix to print warning for when so-sndbuf
> > > > > setsockopt is not granted.").
>
> > > > > I wonder if we should revert back to using "so-sndbuf: 0" as the
> > > > > default for FreeBSD? Or is there a better solution/workaround?
> =20
> > If we configure it with "so-sndbuf: 0" the warning goes away.
> > But, nevermind if I'm the only one seeing these warnings. It was just
> > a basic local_unbound test.
>
> it's not just you, a user on IRC also reported this issue on a system
> with 256GB memory. i would be inclined to add so-sndbuf: 0 to the
> default configuration, but i haven't looked at the actual problem
> here in detail (i don't use local_unbound myself).
Thinking out loud:
Without more context in the upstream commit log message it's difficult we
must surmise that the wait for ARP/NDP resolution could be due to a very
busy unbound service combined with latency in ARP/NDP resolution. I haven't
found any upstream Github issues that document this problem.
Maybe there's a pattern waiting to be discovered. Let's open a PR for this
to gather more information. I'd also be inclined to open an upstream Github
issue for this problem.
Questions I have are:
1. What is similar about the systems with this problem?
2. What was upstream *really* trying to solve? Was it a Linux-only problem
or
more, i.e. affecting FreeBSD also?
There is no default configuration file shipped with FreeBSD. Though we
should probably include one. That would be the simplest, least intrusive
mitigation of upstream's mitigation.
As my machine here that does use local_unbound has had no such warnings I'm
unable to reproduce the problem locally.
--
Cheers,
Cy Schubert <Cy.Schubert@cschubert.com>
FreeBSD UNIX: <cy@FreeBSD.org> Web: https://FreeBSD.org
NTP: <cy@nwtime.org> Web: https://nwtime.org
e**(i*pi)+1=0
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20251008042520.C47BA3AB>