Error adding tunnel to mgre interface

2018-08-01 Thread joe
Hi, I am trying to add a tunnel to an mgre interface. I can't get past the following error. $doas ifconfig mgre0 destroy $doas ifconfig mgre0 create $doas ifconfig mgre0 tunnel 192.0.2.1 192.0.2.1 ifconfig: SIOCSLIFPHYADDR: Invalid argument $ $ifconfig mgre mgre0: flags=8800 mtu 1476 ind

014_amdlfence.patch breaks OpenBSD VMs on AMD systems

2018-08-01 Thread Elmer Skjødt Henriksen
After installing the 014_amdlfence patch released yesterday for 6.3, my OpenBSD VM crashes on boot. It's running under KVM on a Linux box (Ubuntu 18.04 w/ kernel 4.15) on an AMD Ryzen 7 1700 (microcode 0x8001137). I suppose this would also happen on vmm(4) and bhyve, however I don't have any suc

Re: 014_amdlfence.patch breaks OpenBSD VMs on AMD systems

2018-08-01 Thread Bryan Steele
On Wed, Aug 01, 2018 at 03:46:25PM +0200, Elmer Skjødt Henriksen wrote: > After installing the 014_amdlfence patch released yesterday for 6.3, my > OpenBSD VM crashes on boot. It's running under KVM on a Linux box (Ubuntu > 18.04 w/ kernel 4.15) on an AMD Ryzen 7 1700 (microcode 0x8001137). > I sup

Re: 014_amdlfence.patch breaks OpenBSD VMs on AMD systems

2018-08-01 Thread Bryan Steele
On Wed, Aug 01, 2018 at 11:27:26AM -0400, Bryan Steele wrote: > On Wed, Aug 01, 2018 at 03:46:25PM +0200, Elmer Skjødt Henriksen wrote: > > After installing the 014_amdlfence patch released yesterday for 6.3, my > > OpenBSD VM crashes on boot. It's running under KVM on a Linux box (Ubuntu > > 18.04

nmap on routed ip4 networks, openbsd/pf or package/port issue?

2018-08-01 Thread Henrik Engmark
Hi. I very rarely post on these lists, so please go easy on me. Not sure on what list to post, since I don't know what causes the issue, so I thought I would start here and maybe get directed elsewhere. So I set up a new 6.3 with the sole purpose of nmapping, since my older OpenBSDs is coremapp

Re: 014_amdlfence.patch breaks OpenBSD VMs on AMD systems

2018-08-01 Thread Mike Larkin
On Wed, Aug 01, 2018 at 12:14:59PM -0400, Bryan Steele wrote: > On Wed, Aug 01, 2018 at 11:27:26AM -0400, Bryan Steele wrote: > > On Wed, Aug 01, 2018 at 03:46:25PM +0200, Elmer Skjødt Henriksen wrote: > > > After installing the 014_amdlfence patch released yesterday for 6.3, my > > > OpenBSD VM cr

Re: nmap on routed ip4 networks, openbsd/pf or package/port issue?

2018-08-01 Thread Luke A. Call
On 08-01 15:08, Henrik Engmark wrote: > So I set up a new 6.3 with the sole purpose of nmapping, since my older > OpenBSDs is coremapping on me with nmap. >[] > On to the problem, I scan my local LAN with the following: > nmap -Pn -A -v -v --send-eth -e em0 -stylesheet somestylesheet -oA > /

Re: nmap on routed ip4 networks, openbsd/pf or package/port issue?

2018-08-01 Thread Luke A. Call
On 08-01 10:54, Luke A. Call wrote: > On 08-01 15:08, Henrik Engmark wrote: > > So I set up a new 6.3 with the sole purpose of nmapping, since my older > > OpenBSDs is coremapping on me with nmap. > >[] > > On to the problem, I scan my local LAN with the following: > > nmap -Pn -A -v -v --sen

Re: 014_amdlfence.patch breaks OpenBSD VMs on AMD systems

2018-08-01 Thread Mike Larkin
On Wed, Aug 01, 2018 at 12:14:59PM -0400, Bryan Steele wrote: > On Wed, Aug 01, 2018 at 11:27:26AM -0400, Bryan Steele wrote: > > On Wed, Aug 01, 2018 at 03:46:25PM +0200, Elmer Skjødt Henriksen wrote: > > > After installing the 014_amdlfence patch released yesterday for 6.3, my > > > OpenBSD VM cr

Re: 014_amdlfence.patch breaks OpenBSD VMs on AMD systems

2018-08-01 Thread Bryan Steele
On Wed, Aug 01, 2018 at 01:07:33PM -0700, Mike Larkin wrote: > On Wed, Aug 01, 2018 at 12:14:59PM -0400, Bryan Steele wrote: > > On Wed, Aug 01, 2018 at 11:27:26AM -0400, Bryan Steele wrote: > > > On Wed, Aug 01, 2018 at 03:46:25PM +0200, Elmer Skjødt Henriksen wrote: > > > > After installing the 0

OpenBSD Guest under QEMU fails with pid 1 signal 11

2018-08-01 Thread Bill Zissimopoulos
I am trying to create OpenBSD images for use in Google Compute Engine using an expect script [1]. The expect script is able to drive the OpenBSD installation process successfully, but the created images fail to boot cleanly with a long stream of "Process (pid 1) got signal 11". To reproduce try