I deployed two changes in my PF config.
(1) Bigger Queue
I rearranged some queues and gave the queue holding the DNS traffic more
bandwidth and a higher qlimit on the affected interface.
bnd_flows = "1024"
bnd_qlimit = "1024"
guest_local = "850M"
queue guest_local parent guest_root bandwidth $
sd.org On Behalf Of Stuart
Henderson
Sent: Friday, 17 April 2020 3:05 PM
To: misc@openbsd.org
Subject: Re: Unbound Notice: "sendto failed: No buffer space available"
On 2020-04-16, William Ahern wrote:
> I'm no network administrator, but a 3% failure rate would be very high
>
On 2020-04-16, William Ahern wrote:
> I'm no network administrator, but a 3% failure rate would be very high on a
> physical interface. vlan4 is presumably the interface your Apple device
> passes through, right? Investigate why all the dropped packets. Start with
> your queuing rules: examine/ena
On Thu, Apr 16, 2020 at 10:28:55AM +0200, Ben wrote:
> > AFAIU, ENOBUFS happens when the NIC transmit queue is full. Have you looked
> > at the interface statistics to see if there are many dropped packets? Try,
> > e.g.,
> >
> > $ netstat -ni
>
> NameMtu Network Address I
> AFAIU, ENOBUFS happens when the NIC transmit queue is full. Have you looked
> at the interface statistics to see if there are many dropped packets? Try,
> e.g.,
>
> $ netstat -ni
NameMtu Network Address Ipkts IfailOpkts
Ofail Colls
lo0 32768
On Wed, Apr 15, 2020 at 10:53:49PM +0200, Ben wrote:
> I have exactly one device - an Apple smartphone - within one of the
> subnets, that Unbound is not able to send "some" data. The log tells us
> "sendto failed: No buffer space available". Beside the error message,
> the device seems to work wi
PROBLEM: only one specific device continuously triggers Unbound notice
VERSION: OpenBSD 6.6
FLAVOR: stable
LATEST PATCH: "024: SECURITY FIX: April 7, 2020"
DMESG: attached as "dmesg.txt"
UNBOUND LOG: attached as "unbound.log"
Dear community.
After studying what I could find on this topic, it see
7 matches
Mail list logo
