On Wed, Apr 30, 2025 at 09:33:56AM +0300, Kapetanakis Giannis wrote:
> On 29/04/2025 22:19, Otto Moerbeek wrote:
> > If you looks more closely you'll see that resuseport and UDP do not
> > work well together for the multithreaded case. Alls packets end up in
> > one thread.
>
> Yes, so in you co
On 29/04/2025 22:19, Otto Moerbeek wrote:
> If you looks more closely you'll see that resuseport and UDP do not
> work well together for the multithreaded case. Alls packets end up in
> one thread.
Yes, so in you comment bellow I believe you meant "does *NOT* handle ...
multi-threaded case very
On Tue, Apr 29, 2025 at 09:35:11PM +0300, Kapetanakis Giannis wrote:
> talked too soon... seems it's only using now only one thread...
>
> unbound-control stats_noreset | grep num.queries=
> thread0.num.queries=0
> thread1.num.queries=0
> thread2.num.queries=0
> thread3.num.queries=32416
> total.
On Tue, Apr 29, 2025 at 07:19:22PM +0300, Kapetanakis Giannis wrote:
> On 29/04/2025 18:34, Otto Moerbeek wrote:
> > On Tue, Apr 29, 2025 at 06:23:34PM +0300, Kapetanakis Giannis wrote:
> >
> > > On 29/04/2025 18:11, Otto Moerbeek wrote:
> > > > On Tue, Apr 29, 2025 at 04:32:01PM +0300, Kapetanak
On Tue, Apr 29, 2025 at 09:24:24PM +0300, Kapetanakis Giannis wrote:
> ok, I've managed to use multiple threads without errors by setting
> so-reuseport: yes
>
> Although the manual says that it's on by default it's not. It is only
> enabled on Linux and Dragonfly.
> Does it make sense to report
talked too soon... seems it's only using now only one thread...
unbound-control stats_noreset | grep num.queries=
thread0.num.queries=0
thread1.num.queries=0
thread2.num.queries=0
thread3.num.queries=32416
total.num.queries=32416
wtf
G
On 29/04/2025 21:24, Kapetanakis Giannis wrote:
ok, I've
ok, I've managed to use multiple threads without errors by setting
so-reuseport: yes
Although the manual says that it's on by default it's not. It is only
enabled on Linux and Dragonfly.
Does it make sense to report this upstream and enable REUSEPORT_DEFAULT
on OpenBSD as well?
Other findings
On 29/04/2025 18:34, Otto Moerbeek wrote:
On Tue, Apr 29, 2025 at 06:23:34PM +0300, Kapetanakis Giannis wrote:
On 29/04/2025 18:11, Otto Moerbeek wrote:
On Tue, Apr 29, 2025 at 04:32:01PM +0300, Kapetanakis Giannis wrote:
Can it be related to this: dropped due to no socket?
IIRC OpenBSD doe
On Tue, 29 Apr 2025 17:23:34 +0200,
Kapetanakis Giannis wrote:
>
> On 29/04/2025 18:11, Otto Moerbeek wrote:
> > On Tue, Apr 29, 2025 at 04:32:01PM +0300, Kapetanakis Giannis wrote:
> >
> >> Can it be related to this: dropped due to no socket?
> > IIRC OpenBSD does handle sending to a non-blocki
On Tue, Apr 29, 2025 at 06:23:34PM +0300, Kapetanakis Giannis wrote:
> On 29/04/2025 18:11, Otto Moerbeek wrote:
> > On Tue, Apr 29, 2025 at 04:32:01PM +0300, Kapetanakis Giannis wrote:
> >
> > > Can it be related to this: dropped due to no socket?
> > IIRC OpenBSD does handle sending to a non-bl
On 29/04/2025 18:11, Otto Moerbeek wrote:
On Tue, Apr 29, 2025 at 04:32:01PM +0300, Kapetanakis Giannis wrote:
Can it be related to this: dropped due to no socket?
IIRC OpenBSD does handle sending to a non-blocking socket in the
multi-threaded case very well. If multiple threads try to do that
Network was down only while reboot.
Indeed those broadcast drops are also strange. I temporarily pf blocked
224/4 as well as all (local) broadcast addresses but still the numbers
of "dropped due to no socket" continued to increase (both lines).
I've also played with net.inet.udp.sendspace but
On Tue, Apr 29, 2025 at 04:32:01PM +0300, Kapetanakis Giannis wrote:
> Can it be related to this: dropped due to no socket?
IIRC OpenBSD does handle sending to a non-blocking socket in the
multi-threaded case very well. If multiple threads try to do that
simulteneously, some of them will get a EA
I found instead interesting the "broadcast/multicast datagrams" that let me
think that
that your dest network was probably missing for a while. I dont think it like
an unbound problem.
As if the resource, ie. the dns server, is unreachable unbound doesn't cache.
Apr 29, 2025 15:34:48 Kapetanak
Can it be related to this: dropped due to no socket?
# netstat -ss|grep -A7 ^udp
udp:
819120 datagrams received
15494 with no checksum
22621 dropped due to no socket
170569 broadcast/multicast datagrams dropped due to no socket
625930 delivered
64973
Hi,
I'm having this busy router with multiple private networks behind which is also
doing dns caching services.
vlans and carp are also involved.
I'm getting this almost every second on my logs from multiple/different vlans
and IPs (had it also on 7.6 as well on 7.7 now).
Apr 29 15:11:49 unbou
16 matches
Mail list logo
