Re: relayd and stateless UDP traffic

[Martin]

TCP conns works excellent using relayd.

The final goal is to make OpenVPN UDP connection as below:

PC 10.0.20.3 -> relayd -> NAT to egress (IPsec) -> Internet

But UDP redirection rule seems to work only for incoming UDP connections. I'm 
not sure about this.

I've tried:

redirect udp-pass {
  listen on 10.0.20.1 udp port 1:65535
  forward to nat lookup
}

# rcctl -d restart relayd
returns config error.

Any suggestions how to redirect UDP stateless from PC in local network to 
system wide NAT to egress (IPsec).

Martin

‐‐‐ Original Message ‐‐‐
On Sunday, November 22, 2020 2:54 PM, Stuart Henderson  
wrote:

> On 2020-11-22, Martin martin...@protonmail.com wrote:
>
> > I'm looking for a solution to handle stateless UDP traffic by relayd from 
> > various apps which use UDP. For now relayd configured to forward TCP 
> > connections only.
> > The goal is to use OpenVPN UDP connection trough relayd proxy.
> > Any suggestions/examples for would help find a solution.
> > Martin
>
> See relayd.conf(5), the second paragraph of the PROTOCOLS section.

samba macos epic fail

[Lyndon Nerenberg]

Somebody please tell me what the hell I am doing wrong here.

OpenBSD 6.8, samba 4.9.18 via pkg_add, MacOS 10.15.7 fully patched.

My main goal is to get Time Machine backups running, but I keep getting
all sorts of inscrutable errors about file permissions.  The backup manages
to create a few directories before it blows up:

  : root@broken:/dump/tm; find . -ls
  27641856   32 drwxr-xr-x3 lyndon   wheel 512 Nov 22 13:27 .
  276418570 -rwxr--r--1 lyndon   wheel   0 Nov 22 13:27 
./.com.apple.timemachine.supported-d865743e-fb2-4a68-b0e7-10857c459e5c
  276418580 -rwxr--r--1 lyndon   wheel   0 Nov 22 13:27 
./.com.apple.timemachine.supported-64bebc6e-ed10-4c41-9f21-301de558be49
  27641859   32 drwx--3 lyndon   wheel 512 Nov 22 13:27 
./30228818-9C9E-5DBF-8F9B-36F186FA68BF.sparsebundle
  27641860   32 -rw-r--r--1 lyndon   wheel 502 Nov 22 13:27 
./30228818-9C9E-5DBF-8F9B-36F186FA68BF.sparsebundle/Info.plist
  27641861   32 -rw-r--r--1 lyndon   wheel 502 Nov 22 13:27 
./30228818-9C9E-5DBF-8F9B-36F186FA68BF.sparsebundle/Info.bckup
  27641862   32 drwx--2 lyndon   wheel 512 Nov 22 13:27 
./30228818-9C9E-5DBF-8F9B-36F186FA68BF.sparsebundle/bands
  276418630 -rwx--1 lyndon   wheel   0 Nov 22 13:27 
./30228818-9C9E-5DBF-8F9B-36F186FA68BF.sparsebundle/token
  : root@broken:/dump/tm; ls -ld
  drwxr-xr-x  3 lyndon  wheel  512 Nov 22 13:27 .
  : root@broken:/dump/tm; 

There's nothing magic about the /dump mount:
  
  fd71e51011d0eabf.c /dump ffs rw,softdep,nodev,nosuid 0 2

Below is my smbd.conf in full.  I'm hoping somebody can point out the
stupidly obvious mistake I'm making :-P  Note that by now I have tried
every sample smbd.conf that exists on the web, so I'd really like to
hear from somebody who *actually has this working*.

--lyndon

---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---

[global]
  min protocol =  SMB2
  ea support = yes
  inherit acls = yes
  #create mask = 0640
  #directory mask = 0750
  workgroup = BITSEA
  server role = standalone server
  log file = /var/log/samba/smbd.%m
  max log size = 200

# Shares
[homes]
   comment = Home Directories
   browseable = no
   writable = yes

[public]
   comment = Public Stuff
   path = /pub
   public = yes
   writable = no
   printable = no

# Time Machine
[timemachine]
  comment = Time Machine Backups
  path = /dump/tm
  browseable = yes
  writeable = yes
  vfs objects = catia fruit streams_xattr
  fruit:aapl = yes
  fruit:time machine = yes
  fruit:metadata = stream
  fruit:model = MacSamba
  fruit:posix_rename = yes 
  fruit:veto_appledouble = no
  fruit:advertise_fullsync = true

Re: sndiod -F does not switch to device

[Jan Stary]

On Nov 22 21:31:38, mih...@gmail.com wrote:
> https://marc.info/?l=openbsd-misc=158436621701274=2

I'm not trying to combine two devices as they discuss there.
I'm trying to have sndiod -F rsnd/1 switch to audio1.

(Is it related, though, to the webcam
not having a playback channel?)

Re: sndiod -F does not switch to device

[Mihai Popescu]

https://marc.info/?l=openbsd-misc=158436621701274=2

sndiod -F does not switch to device

[Jan Stary]

This is current/amd64 (dmesg below),
running /usr/bin/sndiod -f rsnd/0 -F rsnd/1

While the -F feature works with most USB audio devices I have tried,
it does not make the switch to use the -F device
with this USB camera with a builtin microphone.
It's an Audom AF640 and it attaches as follows:

uvideo0 at uhub0 port 1 configuration 1 interface 0 "Sunplus IT Co Full HD 
webcam" rev 2.00/0.05 addr 2
video0 at uvideo0
uaudio0 at uhub0 port 1 configuration 1 interface 3 "Sunplus IT Co Full HD 
webcam" rev 2.00/0.05 addr 2
uaudio0: class v1, high-speed, sync, channels: 0 play, 1 rec, 2 ctls
audio1 at uaudio0

I can confirm that both the camera and the mike themselves work.
After plugging it in, sndioctl says

input.level=0.000
input.mute=1
output.level=0.980
output.mute=0
server.device=0
app/rec0.level=1.000

Notice the server.device=0, meaning it is still using snd/0.
Notice the zero input level and the muted input.
Is this intended?

If I plug a Sennheiser haedset instead, sndioctl says

input.level=0.800
input.mute=0
output.level=0.800
output.mute=0
server.device=1
app/rec0.level=1.000

switching to the USB device plugged in.

Is it because the camera's mike has no output channels?
"channels: 0 play, 1 rec, 2 ctls" - indeed, it only
records mono and has no playback capabilities.

According to the manpage

-F device
Specify an alternate device to use.  If it doesn't work,
the one given with the last -f or -F options will be used.
For instance, specifying a USB device following a PCI device
allows sndiod to use the USB one preferably when it's
connected and to fall back to the PCI one when it's
disconnected. Alternate devices may be switched with the
server.device control of the sndioctl(1) utility.

Is the -F device required to have at least one playback
and pne record channel to "work"?

Switching with a manual "sndioctl server.device=1"
doesn't work either: sndioctl still shows server.device=0

Is this intended?
How can I further debug this?

Jan



OpenBSD 6.8-current (GENERIC.MP) #0: Sun Nov 22 17:22:47 CET 2020
h...@lenovo.stare.cz:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8463781888 (8071MB)
avail mem = 8191975424 (7812MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (80 entries)
bios0: vendor LENOVO version "7UET94WW (3.24 )" date 10/17/2012
bios0: LENOVO 64741EG
acpi0 at bios0: ACPI 3.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT ASF! SSDT TCPA SSDT 
SSDT SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2(S4) 
EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB3(S3) USB5(S3) EHC0(S3) EHC1(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2261.40 MHz, 06-17-06
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu0: 3MB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges
cpu0: apic clock running at 266MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2.1.3, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2261.01 MHz, 06-17-06
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu1: 3MB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins, remapped
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (AGP_)
acpiprt2 at acpi0: bus 2 (EXP0)
acpiprt3 at acpi0: bus 3 (EXP1)
acpiprt4 at acpi0: bus -1 (EXP2)
acpiprt5 at acpi0: bus 5 (EXP3)
acpiprt6 at acpi0: bus 13 (EXP4)
acpiprt7 at acpi0: bus 21 (PCI1)
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
acpicmos0 at acpi0
tpm0 at acpi0 TPM_ addr 0xfed4/0x5000, device 0x10208086 rev 0x6
acpibat0 at acpi0: BAT0 model "92P1137" serial57 type LION oem "SANYO"
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0: version 1.0
"PNP0C14" at acpi0 not configured
acpicpu0 at acpi0: !C3(100@57 mwait.3@0x30), !C2(500@1 mwait.1@0x10), C1(1000@1 
mwait.1), PSS
acpicpu1 at acpi0: !C3(100@57 mwait.3@0x30), !C2(500@1 mwait.1@0x10), C1(1000@1 
mwait.1), PSS
acpipwrres0 at acpi0: PUBS, resource for USB0, USB3, USB5, EHC0, EHC1
acpitz0 at acpi0: critical temperature is 127 degC
acpitz1 at 

Re: softraid0 errors after 6.8 upgrade

[Nick Holland]

On 2020-11-22 06:04, Leo Unglaub wrote:
> Hi,
> i upgraded my desktop to the latest 6.8 release. I uses sysupgrade to do 
> the upgrade and everything worked fine. But now i noticed in my dmesg 
> the following error messages:
> 
>> softraid0: sd6: i/o error 5 @ CRYPTO block 475440376
>> softraid0: sd6: i/o error 5 @ CRYPTO block 475440376
>> softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
>> softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
>> softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
>> softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
>> softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
>> softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
>> softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
>> softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
>> softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
>> softraid0: sd6: i/o error 5 @ CRYPTO block 477298832

sure sounds to me like your disk has issues.  Doesn't look related
to the upgrade process.

> This only happens when i want to read certain files in /home. I checked 
> with fsck but it reports the partition to be fine. Has this something 
> todo with the upgrade? I did not find anything in the changelog.

sounds even more like your disk isn't good.

fsck checks file *system* integrity.  It does NOT check every sector
on the disk for suitability to store data.  The percentage of the
disk that fsck reads in the process of doing its job is very small.

If you want to test your backing disk, I'd do a:
# dd if=/dev/rsdXc of=/dev/null bs=1m
where "X" is your physical disk.  If you want to see it's progress
while running:
# pkill -info dd
will tell you how much has been read so far.

IF that comes up bad, you MAY be able to "fix" your problem by
deleting the files that are bad, then write a very large file to
the entire partition where those damaged files were -- the disk
will typically read-after-write verify that the data landed on the
disk properly, and if it finds a bad spot, it will lock it out and
put the failed write on a good spot (after you fill the disk,
delete the "filler" file, of course).  But be aware, your disk may
not not healthy -- yes, bad spots and reallocated space is a normal
thing for disks, but new bad spots, not so much.

Nick.

relayd and stateless UDP traffic

[Martin]

I'm looking for a solution to handle stateless UDP traffic by relayd from 
various apps which use UDP. For now relayd configured to forward TCP 
connections only.

The goal is to use OpenVPN UDP connection trough relayd proxy.

Any suggestions/examples for would help find a solution.

Martin

Re: MJPEG in video(1)

[Jan Stary]

ping

On Sep 24 15:21:26, h...@stare.cz wrote:
> Hello Laurie,
> 
> On Sep 21 17:54:40, lau...@tratt.net wrote:
> > However, there's a probably deeper point here. IMHO, video(1) isn't really a
> > sensible tool for viewing or recording video
> 
> I find it nice that a base tool exists
> for viewing and recording video, even
> if not the compressed formats.
> 
> > as it can't access a camera's
> > MJPEG mode (assuming the camera has one!) without ld tricks.
> 
> Can you elaborate please? I was under the impression that
> video(1) can only do the video -e encodings, namely:
> 
> Valid arguments are ‘uyvy’, ‘yuy2’ and ‘yv12’.  The default
> is ‘yuy2’ unless file is being used and only supports ‘uyvy’,
> in which case ‘uyvy’ will be used by default.
> 
> What "ld tricks" would make video(1) recognize the mjpeg modes?

Re: softraid0 errors after 6.8 upgrade

[James Cook]

On Sun, Nov 22, 2020 at 12:04:29PM +0100, Leo Unglaub wrote:
> Hi,
> i upgraded my desktop to the latest 6.8 release. I uses sysupgrade to do the
> upgrade and everything worked fine. But now i noticed in my dmesg the
> following error messages:
> 
> > softraid0: sd6: i/o error 5 @ CRYPTO block 475440376
> > softraid0: sd6: i/o error 5 @ CRYPTO block 475440376
> > softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
> > softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
> > softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
> > softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
> > softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
> > softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
> > softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
> > softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
> > softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
> > softraid0: sd6: i/o error 5 @ CRYPTO block 477298832
> 
> This only happens when i want to read certain files in /home. I checked with
> fsck but it reports the partition to be fine. Has this something todo with
> the upgrade? I did not find anything in the changelog.

Could this happen if there's a problem with the disk blocks backing the
content of those files? I don't think fsck tries to read blocks that
only store file content.

-- 
James

Re: relayd and stateless UDP traffic

[Stuart Henderson]

On 2020-11-22, Martin  wrote:
> I'm looking for a solution to handle stateless UDP traffic by relayd from 
> various apps which use UDP. For now relayd configured to forward TCP 
> connections only.
>
> The goal is to use OpenVPN UDP connection trough relayd proxy.
>
> Any suggestions/examples for would help find a solution.
>
> Martin
>
>

See relayd.conf(5), the second paragraph of the PROTOCOLS section.

Re: Advice on using intrusion detection

[Peter Nicolai Mathias Hansteen]

> 22. nov. 2020 kl. 02:02 skrev Predrag Punosevac :

> OpenBSD is all about prevention and exploit mitigation. Code simplicity,
> correctness, and code audit are all examples of intrusion prevention
> methods. They don't sound very sexy :-) If you are super new to OpenBSD
> Peter just gave a really nice virtual talk which can be found on the net
> 
> https://home.nuug.no/~peter/openbsd_and_you/#12

Thanks for pointing to that one :)

This OpenBSD Journal (aka undeadly.org) entry has a link to the video and the 
slides: https://undeadly.org/cgi?action=article;sid=20201109055713 


All the best,
Peter


—
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

softraid0 errors after 6.8 upgrade

[Leo Unglaub]

Hi,
i upgraded my desktop to the latest 6.8 release. I uses sysupgrade to do 
the upgrade and everything worked fine. But now i noticed in my dmesg 
the following error messages:



softraid0: sd6: i/o error 5 @ CRYPTO block 475440376
softraid0: sd6: i/o error 5 @ CRYPTO block 475440376
softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
softraid0: sd6: i/o error 5 @ CRYPTO block 473833936
softraid0: sd6: i/o error 5 @ CRYPTO block 477298832


This only happens when i want to read certain files in /home. I checked 
with fsck but it reports the partition to be fine. Has this something 
todo with the upgrade? I did not find anything in the changelog.


This setup uses OpenBSD 6.8 x64 on an AMD Ryzen processor with a full 
disc encryption setup.



# mount
/dev/sd6a on / type ffs (local, softdep)
/dev/sd6k on /home type ffs (local, nodev, nosuid, softdep)
/dev/sd6d on /tmp type ffs (local, nodev, nosuid, softdep)
/dev/sd6f on /usr type ffs (local, nodev, softdep)
/dev/sd6g on /usr/X11R6 type ffs (local, nodev, softdep)
/dev/sd6h on /usr/local type ffs (local, nodev, wxallowed, softdep)
/dev/sd6j on /usr/obj type ffs (local, nodev, nosuid, softdep)
/dev/sd6i on /usr/src type ffs (local, nodev, nosuid, softdep)
/dev/sd6e on /var type ffs (local, nodev, nosuid, softdep)
/dev/sd8a on /mnt type ffs (local)


I now switched to the latest snapshot and there there, but the error 
still exists.



OpenBSD stormwind.wow-data.net 6.8 GENERIC.MP#173 amd64


What is the best way to fix this? Reinstall the entire machine?

Thanks so much for your help.
Greetings from Vienna
Leo


# uname -a
OpenBSD stormwind.foo.bar 6.8 GENERIC.MP#173 amd64
stormwind# dmesg 
OpenBSD 6.8-current (GENERIC.MP) #173: Mon Nov  9 19:07:05 MST 2020

dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17105850368 (16313MB)
avail mem = 16572129280 (15804MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe6cf0 (59 entries)
bios0: vendor American Megatrends Inc. version "1.NV" date 11/29/2019
bios0: Micro-Star International Co., Ltd. MS-7A32
acpi0 at bios0: ACPI 6.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT SSDT SSDT SSDT MCFG HPET SSDT UEFI IVRS 
SSDT CRAT CDIT SSDT SSDT WSMT
acpi0: wakeup devices GPP0(S4) GPP1(S4) GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) 
GPP7(S4) GPP8(S4) GPP9(S4) GPPA(S4) GPPB(S4) GPPC(S4) GPPD(S4) GPPE(S4) 
GPPF(S4) GP17(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Ryzen 7 1700X Eight-Core Processor, 3400.60 MHz, 17-01-01
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu0: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 
8-way L2 cache, 16MB 64b/line 16-way L3 cache
cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: AMD Ryzen 7 1700X Eight-Core Processor, 3400.03 MHz, 17-01-01
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu1: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 
8-way L2 cache, 16MB 64b/line 16-way L3 cache
cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: AMD Ryzen 7 1700X Eight-Core Processor, 3400.03 MHz, 17-01-01
cpu2: