Re: snmpd dies

2024-01-07 Thread Nicolas Goy
On 07.01.24 09:37, Martijn van Duren wrote: On Sat, 2024-01-06 at 16:12 +0100, Nicolas Goy wrote: Unfortunately this isn't enough to give me a hint where the issue might be... Let's keep an eye out and hope that we can gather some more context next time, or that I can find something during

SATA slow/timeouts, AMD 600 Series AHCI, OpenBSD 7.4 amd64

2024-01-07 Thread blb8
Onboard SATA seems to require additional initialization on a Gigabyte B650 in OpenBSD 7.4 amd64; basic requests take minutes to complete and each block read takes 30 seconds. During boot, attached SSDs will block pending these requests; optical drives pass that boot step quickly but userland

Re: relayd forward with tls

2024-01-07 Thread Adriano Barbosa
On Sun, Jan 07, 2024 at 05:21:04AM -0800, Paul Pace wrote: > On 1/6/24 7:35 PM, Adriano Barbosa wrote: > > On Thu, Jan 04, 2024 at 06:57:10PM -0800, Paul Pace wrote: > > > On 1/4/24 10:22 AM, Adriano Barbosa wrote: > > > > Hi! > > > > I'm trying to use relayd with multiple FQDNs mixing remote

OneRNG TRNG issues on 7.4

2024-01-07 Thread Dylan D'Silva
Hello all, Trying to use the OneRNG TRNG to increase entropy on by OpenBSD 7.4 system. dmesg shows this. uonerng0 at uhub0 port 1 configuration 1 interface 0 "Moonbase Otago http://www.moonbaseotago.com/random 00" rev 2.00/0.09 addr 2 uonerng1 at uhub0 port 0 configuration 1 interface 1

Stalled nfs mount from disk in standby mode

2024-01-07 Thread Luis Mendes
Hi, I'm running a 7.4 amd64 NFS server that has a sd0 spinning disk. Its only partition is encrypted as sd3i. # mount | grep sd3 /dev/sd3i on /wd_4_tb type ffs (NFS exported, local) # cat /etc/exports /wd_4_tb -alldirs -maproot=root -network=192.168.1.0 -mask=255.255.255.0 At the Slackware

Re: relayd forward with tls

2024-01-07 Thread Paul Pace
On 1/6/24 7:35 PM, Adriano Barbosa wrote: On Thu, Jan 04, 2024 at 06:57:10PM -0800, Paul Pace wrote: On 1/4/24 10:22 AM, Adriano Barbosa wrote: Hi! I'm trying to use relayd with multiple FQDNs mixing remote servers with and without tls: relayd -- fqdn1 --> 127.0.0.1 (no tls) -- fqdn2

Re: bioctl: one key for multiple disks

2024-01-07 Thread Crystal Kolipe
On Sun, Jan 07, 2024 at 12:40:18PM +0100, Stefan Kreutz wrote: > You can indeed create multiple 1M RAID disklabel partitions per device Yes, you can. And that may be the most appropriate solution in this case, and in cases where you have several machines each with one softraid crypto partition

Re: ProtectLi w/ OpenBSD

2024-01-07 Thread Sven Wolf
On 1/3/24 12:17, Stuart Henderson wrote: On 2024-01-03, Kenneth Hendrickson wrote: Is there any newer information than this: https://OpenBsdMailBox.blogspot.com/2023/05/protectli-vp2420-with-dasharo.html That is exactly how a boot looks if you are on a device with serial console and don't

Re: bioctl: one key for multiple disks

2024-01-07 Thread Stefan Kreutz
You can indeed create multiple 1M RAID disklabel partitions per device (typically a USB stick), one partition per key. I've been using this setup for years. To save yourself some frustration, I suggest you backup the keydisks as described in the FAQ:

Re: Communication between hosts on different network interfaces

2024-01-07 Thread All
This is very much doable with DHCP one liner: add the following to your dhcpd.conf ((!) inside the block of your 192.168.2.0/24 network) option classless-static-routes 192.168.3.0/24 192.168.2.1; This will install static route into all machines in 192.168.2.0/24 network. When they will try to

bioctl: one key for multiple disks

2024-01-07 Thread 4
how to use one key for multiple disks? i naively believed that since bioctl does not have any keys for this, then a key on the specified key's partition will be used, and if it is not there, a new one will be created, and deleting the key it is the responsibility of the user, but in practice

Re: snmpd dies

2024-01-07 Thread Martijn van Duren
On Sat, 2024-01-06 at 16:12 +0100, Nicolas Goy wrote: > On 06.01.24 00:03, Martijn van Duren wrote: > > On Fri, 2024-01-05 at 13:09 +0100, Nicolas Goy wrote: > > My first assumption is it's a bug in libagentx. However, I don't have > > enough context to reproduce it. Can you reproduce it