> try bumping net.inet.udp.sendspace by a bit (not loads - maybe 4x > default?)
Unfortunately, this has not done it. I tried bumping it to 64.000, still no difference. >> In my Unbound log on an OpenBSD router I see a lot of this: >> >> unbound: [3902:2] notice: sendto failed: Resource temporarily >> unavailable unbound: [3902:2] notice: remote address is 192.168.1.23 >> port 44318 unbound: [12836:0] notice: sendto failed: Resource >> temporarily unavailable unbound: [12836:0] notice: remote address is >> 192.168.1.23 port 45759 unbound: [65050:1] notice: sendto failed: >> Resource temporarily unavailable unbound: [65050:1] notice: remote >> address is 192.168.1.23 port 52747 unbound: [3902:2] notice: sendto >> failed: Resource temporarily unavailable unbound: [3902:2] notice: >> remote address is 192.168.1.23 port 34709 unbound: [12836:0] notice: >> sendto failed: Resource temporarily unavailable unbound: [12836:0] >> notice: remote address is 192.168.1.23 port 47520 unbound: [20311:3] >> notice: sendto failed: Resource temporarily unavailable unbound: >> [20311:3] notice: remote address is 192.168.1.23 port 38662 unbound: >> [65050:1] notice: sendto failed: Resource temporarily unavailable >> >> For different machines on the LAN, not just the one above. >> >> What exactly does this mean? >> >> All the machines query the router for an IP via DHCP and that works, >> and they query it for DNS and all outgoing traffic works too. >> >> Kind regards