uhidpp expanded support

2021-12-21 Thread jwinnie
Hello OpenBSD developers, I am interested in contributing to improve the uhidpp(4) (Logitech Unifying Reciever) support in OpenBSD. Currently, the uhidpp(4) driver only handles detecting certain sensors, but I would like more robust support for these devices, including: * pairing and unpairing

Re: Recommendations on Buffer Space for Busy Unbound Resolver Service for a network

2021-12-21 Thread Tom Smyth
THanks Dirk Ill give that a go Cheers, Tom Smyth On Wed, 22 Dec 2021 at 00:30, Dirk Coetzee wrote: > Hi Tom, > > I would recommend debugging using "unbound-control stats_noreset" and > referencing the unbound configuration documentation at >

Re: Recommendations on Buffer Space for Busy Unbound Resolver Service for a network

2021-12-21 Thread Dirk Coetzee
Hi Tom, I would recommend debugging using "unbound-control stats_noreset" and referencing the unbound configuration documentation at https://www.nlnetlabs.nl/documentation/unbound/unbound.conf/ -Original Message- From: owner-m...@openbsd.org On Behalf Of Tom Smyth Sent: Wednesday,

Disk partition not recognized

2021-12-21 Thread Rob Whitlock
I have two disks, one an MBR partitioned 1TB external SSD, and the other a GPT partitioned 5TB external HDD. Both have a single ExFAT partition on them and both have the same contents. Both show up as sd1 under "sysctl hw.disknames" (when plugged in one at a time, that is). I am able to mount the

Re: Recommendations on Buffer Space for Busy Unbound Resolver Service for a network

2021-12-21 Thread Tom Smyth
Sorry forgot to say running OpenBSD on an amd64, and hosted in a KVM environment, Thanks Tom Smyth On Tue, 21 Dec 2021 at 21:15, Tom Smyth wrote: > Recommendations on Buffer Space for Busy Unbound Resolver Service for a > network serving a 3000, customers > > Thanks > > -- > Kindest

Recommendations on Buffer Space for Busy Unbound Resolver Service for a network

2021-12-21 Thread Tom Smyth
Recommendations on Buffer Space for Busy Unbound Resolver Service for a network serving a 3000, customers Thanks -- Kindest regards, Tom Smyth.

Re: NAT fails to work from internal to external network

2021-12-21 Thread Stuart Henderson
On 2021-12-20, beebeet...@posteo.de wrote: > > pass out on egress from trunk:network to any nat-to egress > > pass out on egress > > Looks like you (incorrectly) assumed that first matching rule wins? I suggest changing this to a "match ... nat-to" rule. You might want to add "inet" unkess you