vgafb manpage is in wrong place, should I report it?

[IL Ka]

Hello,
I am pretty new to OpenBSD and not sure if I should report minor issue to
bugs@, but I just found that vgafb(4) device is supported only on macppc
and sparc64 (according to src/sys). It has nothing to do with i386 nor with
amd64.

But for some reason it's man page sits directly in /usr/share/man/man4
While other platform-specific mans live in  /usr/share/man/man4/${machine}
(lcd(4) is good example).

Ilya.

dmesg for edgerouter lite

[Sean Murphy]

Hello all,

Also upgraded the ERL to 6.3, dmesg to follow.

Secondary DNS server, backup router, and experiment box.

OpenBSD 6.3 (GENERIC.MP) #0: Sun Mar 25 19:59:39 UTC 2018
visa@octeon:/usr/src/sys/arch/octeon/compile/GENERIC.MP
real mem = 536870912 (512MB)
avail mem = 523862016 (499MB)
mainbus0 at root: board 20002 rev 2.18
cpu0 at mainbus0: CN50xx CPU rev 0.1 500 MHz, Software FP emulation
cpu0: cache L1-I 32KB 4 way D 16KB 64 way, L2 128KB 8 way
cpu1 at mainbus0: CN50xx CPU rev 0.1 500 MHz, Software FP emulation
cpu1: cache L1-I 32KB 4 way D 16KB 64 way, L2 128KB 8 way
clock0 at mainbus0: int 5
iobus0 at mainbus0
simplebus0 at iobus0: "soc"
octciu0 at simplebus0
cn30xxsmi0 at simplebus0
com0 at simplebus0: ns16550a, 64 byte fifo
com0: console
dwctwo0 at iobus0 base 0x118006800 irq 56
usb0 at dwctwo0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Octeon DWC2 root hub" rev
2.00/1.00 addr 1
octrng0 at iobus0 base 0x14000 irq 0
cn30xxgmx0 at iobus0 base 0x118000800
cnmac0 at cn30xxgmx0: RGMII, address 44:d9:e7:40:b5:c8
atphy0 at cnmac0 phy 7: AR8035 10/100/1000 PHY, rev. 2
cnmac1 at cn30xxgmx0: RGMII, address 44:d9:e7:40:b5:c9
atphy1 at cnmac1 phy 6: AR8035 10/100/1000 PHY, rev. 2
cnmac2 at cn30xxgmx0: RGMII, address 44:d9:e7:40:b5:ca
atphy2 at cnmac2 phy 5: AR8035 10/100/1000 PHY, rev. 2
/dev/ksyms: Symbol table not valid.
umass0 at uhub0 port 1 configuration 1 interface 0 "Lexar USB Flash
Drive" rev 2.10/11.00 addr 2
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0:  SCSI4
0/direct removable serial.05dca83aZB0L2W63LA4P
sd0: 30526MB, 512 bytes/sector, 62517248 sectors
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
boot device: sd0
root on sd0a (fb74a192b03ee90f.a) swap on sd0b dump on sd0b

dmesg for apu2 OpenBSD 6.3

[Sean Murphy]

Hello all,

Upgraded my apu2 to 6.3 tonight, here is the requisite dmesg.

This machine is my network's DHCP server and primary DNS server.

OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 1996152832 (1903MB)
avail mem = 1928654848 (1839MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x77fb7020 (7 entries)
bios0: vendor coreboot version "88a4f96" date 03/07/2016
bios0: PC Engines apu2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S2 S3 S4 S5
acpi0: tables DSDT FACP SSDT APIC HEST SSDT SSDT HPET
acpi0: wakeup devices PWRB(S4) PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4)
PBR8(S4) UOH1(S3) UOH3(S3) UOH5(S3) XHC0(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 GX-412TC SOC, 998.26 MHz
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,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1
cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB
64b/line 16-way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative
acpitimer0: recalibrated TSC frequency 998130097 Hz
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 1 (application processor)
cpu1: AMD GX-412TC SOC, 998.13 MHz
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,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1
cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB
64b/line 16-way L2 cache
cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: AMD GX-412TC SOC, 998.13 MHz
cpu2: 
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,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1
cpu2: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB
64b/line 16-way L2 cache
cpu2: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu2: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: AMD GX-412TC SOC, 998.13 MHz
cpu3: 
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,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1
cpu3: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB
64b/line 16-way L2 cache
cpu3: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu3: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 21, 24 pins
ioapic1 at mainbus0: apid 5 pa 0xfec2, version 21, 32 pins
, remapped to apid 5
acpihpet0 at acpi0: 14318180 Hz
acpihpet0: recalibrated TSC frequency 998130138 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PBR4)
acpiprt2 at acpi0: bus 1 (PBR5)
acpiprt3 at acpi0: bus 2 (PBR6)
acpiprt4 at acpi0: bus 3 (PBR7)
acpiprt5 at acpi0: bus -1 (PBR8)
acpicpu0 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS
acpicpu1 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS
acpicpu2 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS
acpicpu3 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS
acpibtn0 at acpi0: PWRB
cpu0: 998 MHz: speeds: 1000 800 600 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "AMD AMD64 16h Root Complex" rev 0x00
pchb1 at pci0 dev 2 function 0 "AMD AMD64 16h Host" rev 0x00
ppb0 at pci0 dev 2 function 2 "AMD AMD64 16h PCIE" rev 0x00: msi
pci1 at ppb0 bus 1
em0 at pci1 dev 0 function 0 "Intel I211" rev 0x03: msi, address
00:0d:b9:43:19:88
ppb1 at pci0 dev 2 function 3 "AMD AMD64 16h PCIE" rev 0x00: msi
pci2 at ppb1 bus 2
em1 at pci2 dev 0 function 0 "Intel I211" rev 0x03: msi, address
00:0d:b9:43:19:89
ppb2 at pci0 dev 

Re: pine64-lts - can't detect disk

[Jonathan Gray]

On Fri, Apr 13, 2018 at 11:05:06AM -0700, jungle Boogie wrote:
> On 13 April 2018 at 09:39, Jonathan Gray  wrote:
> > On Fri, Apr 13, 2018 at 09:19:23AM -0700, jungle Boogie wrote:
> >> On 13 April 2018 at 08:30, jungle Boogie  wrote:
> >> > Hi All,
> >> >
> >> > So between Peter Hessler's post here:
> >> > https://bsd.network/@phessler/99389809617980837
> >> >
> >> > And the install instructions for arm64:
> >> > https://ftp.openbsd.org/pub/OpenBSD/snapshots/arm64/INSTALL.arm64
> >> >
> >> > I have the pine64-lts:
> >> > https://www.pine64.org/?page_id=46823
> >>
> >>
> >> Forgot the dmesg:
> >>
> >> OpenBSD 6.3-current (RAMDISK) #235: Thu Apr 12 14:38:28 MDT 2018
> >> dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/RAMDISK
> >> real mem  = 2015993856 (1922MB)
> >> avail mem = 1915539456 (1826MB)
> >> mainbus0 at root: Pine64+
> >
> > The sopine U-Boot image does not currently include the sopine device
> > tree as there isn't a sopine device tree in U-Boot.
> >
> > Until that changes, on the msdos/efi partition create an 'allwinner'
> > directory, install the dtb port and copy
> > /usr/local/share/dtb/arm64/allwinner/sun50i-a64-sopine-baseboard.dtb
> > to
> > allwinner/sun50i-a64-pine64-plus.dtb
> >
> > or to a different path and change fdtfile in the U-Boot environment.
> >
> > Though it isn't clear if that is the appropriate device tree.
> >
> 
> Thanks for the reply. I think I'm closer, but there still seems to be
> some gaps...
> 
> my sd card:
> $ ls /mnt/allwinner/
> sun50i-a64-pine64-plus.dtb
> 
> 
> => run findfdt
> ## Error: "findfdt" not defined
> => load mmc 0:1 ${fdt_addr_r} allwinner/sun50i-a64-pine64-plus.dtb
> 12734 bytes read in 35 ms (354.5 KiB/s)
> => load mmc 0:1 ${kernel_addr_r} efi/boot/bootaa64.efi
> 98588 bytes read in 43 ms (2.2 MiB/s)
> => bootefi ${kernel_addr_r} ${fdt_addr_r}

You shouldn't have to explicitly run bootefi as the target supports what
U-Boot calls 'generic distro boot' which will load a dtb and run bootefi
automatically.

If you were to keep the original dtb name you would have to do something
like

setenv fdtfile allwinner/sun50i-a64-sopine-baseboard.dtb
saveenv
boot

Until such time that the U-Boot patch series for it gets merged/released:
https://patchwork.ozlabs.org/patch/885574/

Block device encryption

[Bogdan Kulbida]

Dear OpenBSD awesome community,

I tryed to find some information on block device encryption topic,
specifically about best practices in using it and did find some. But there
is not much I could find about what happens when my actual device contents
starting to consume more space than initially alocated. I know you can
resize a volume but what if for some reason that was not done what are the
ramifications of continuing using block device and adding even more data
onto it?

Thank you for all the hard work all and each of you have done to make it
such a great world class operating system.

Regards,
Bogdan
-- 

---
Best regards,
Bogdan Kulbida
CEO/CTO, Konstankino LLC 
+1.802.793.8295

Re: Audio stuttering on media playback with sndiod

[Robert Klein]

Hi Daniel,

On Wed, 4 Apr 2018 03:22:04 -0300
Daniel Bolgheroni  wrote:

> Hi,
> 
> audio is stuttering on media playback when run through sndiod. It's OK
> without it.

Maybe related.  Yesterday I disabled webcam and microphone in BIOS on
my X250.  Then Video playback (audio and video) was stuttering. I
didn't investigate further, as: reverting BIOS settings made it Ok
again.


Best regards
Robert

> 
> Here is an example of audio/cmus attaching to play a mp3 file:
> 
> x250$ doas sndiod -ddd
> snd0 pst=cfg.default: rec=0:1 play=0:1 vol=23170 dup
> helper(helper|ini): created
> worker(worker|ini): created
> listen(/tmp/aucat/aucat0|ini): created
> sock(sock|ini): created
> helper: recv: cmd = 0, num = 0, mode = 3, fd = -1
> helper: send: cmd = 3, num = 0, mode = 0, fd = 3
> sock,rmsg,widl: AUTH message
> sock,rmsg,widl: HELLO message
> sock,rmsg,widl: hello from , mode = 1, ver 7
> sock,rmsg,widl: using snd0 pst=cfg.default, mode = 1
> cmus0: overwritten slot 0
> snd0 pst=cfg: device requested
> worker: send: cmd = 0, num = 0, mode = 3, fd = -1
> worker: recv: cmd = 3, num = 0, mode = 0, fd = 6
> sio(rsnd/0|ini): created
> snd0 pst=ini: 48000Hz, s16le, play 0:1, rec 0:1, 8 blocks of 960
> frames cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: SETPAR message
> cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: playback channels 0:1 -> 0:1
> cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: 44100Hz sample rate, 882
> frame blocks cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: 13230 frame
> buffer cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: GETPAR message
> cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: GETPAR message
> cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: START message
> cmus0 vol=127,pst=ini,mmc=off: playing s16le -> s16le
> cmus0 vol=127,pst=ini,mmc=off: allocated 13230/20286 fr buffers
> cmus0 vol=127,pst=sta,mmc=off: 44100Hz, s16le, play 0:1, 15 blocks of
> 882 frames cmus0 vol=127,pst=sta,mmc=off,rmsg,widl: building SETVOL
> message, vol = 127 snd0 pst=ini: device started
> snd0 pst=run: started
> cmus0 vol=127,pst=run,mmc=off: attached at -7056, delta = 0
> cmap: nch = 2, ostart = 0, onext = 0, istart = 0, inext = 0
> resamp: 882/960
> cmus0 vol=127,pst=run,mmc=off: set weight: 23170/23170
> snd0 pst=run: rec hw xrun, rused = 5760/7680
> snd0 pst=run: play hw xrun, pused = 1920/7680
> snd0 pst=run: rec hw xrun, rused = 4800/7680
> snd0 pst=run: play hw xrun, pused = 2880/7680
> snd0 pst=run: rec hw xrun, rused = 3840/7680
> snd0 pst=run: play hw xrun, pused = 3840/7680
> snd0 pst=run: rec hw xrun, rused = 2880/7680
> snd0 pst=run: play hw xrun, pused = 4800/7680
> snd0 pst=run: rec hw xrun, rused = 1920/7680
> snd0 pst=run: play hw xrun, pused = 5760/7680
> snd0 pst=run: rec hw xrun, rused = 960/7680
> snd0 pst=run: play hw xrun, pused = 6720/7680
> snd0 pst=run: rec hw xrun, rused = 5760/7680
> snd0 pst=run: play hw xrun, pused = 1920/7680
> snd0 pst=run: rec hw xrun, rused = 4800/7680
> snd0 pst=run: play hw xrun, pused = 2880/7680
> snd0 pst=run: rec hw xrun, rused = 3840/7680
> snd0 pst=run: play hw xrun, pused = 3840/7680
> snd0 pst=run: rec hw xrun, rused = 2880/7680
> snd0 pst=run: play hw xrun, pused = 4800/7680
> snd0 pst=run: rec hw xrun, rused = 1920/7680
> snd0 pst=run: play hw xrun, pused = 5760/7680
> snd0 pst=run: rec hw xrun, rused = 960/7680
> snd0 pst=run: play hw xrun, pused = 6720/7680
> snd0 pst=run: rec hw xrun, rused = 5760/7680
> snd0 pst=run: play hw xrun, pused = 1920/7680
> snd0 pst=run: rec hw xrun, rused = 4800/7680
> snd0 pst=run: play hw xrun, pused = 2880/7680
> snd0 pst=run: rec hw xrun, rused = 3840/7680
> snd0 pst=run: play hw xrun, pused = 3840/7680
> 
> (... flood)
> 
> The same on a X220 gives me this (it's OK here):
> 
> x220$ doas sndiod -ddd
> snd0 pst=cfg.default: rec=0:1 play=0:1 vol=23170 dup
> helper(helper|ini): created
> worker(worker|ini): created
> listen(/tmp/aucat/aucat0|ini): created
> sock(sock|ini): created
> helper: recv: cmd = 0, num = 0, mode = 3, fd = -1
> helper: send: cmd = 3, num = 0, mode = 0, fd = 3
> sock,rmsg,widl: AUTH message
> sock,rmsg,widl: HELLO message
> sock,rmsg,widl: hello from , mode = 1, ver 7
> sock,rmsg,widl: using snd0 pst=cfg.default, mode = 1
> cmus0: overwritten slot 0
> snd0 pst=cfg: device requested
> worker: send: cmd = 0, num = 0, mode = 3, fd = -1
> worker: recv: cmd = 3, num = 0, mode = 0, fd = 6
> sio(rsnd/0|ini): created
> snd0 pst=ini: 48000Hz, s16le, play 0:1, rec 0:1, 8 blocks of 960
> frames cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: SETPAR message
> cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: playback channels 0:1 -> 0:1
> cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: 44100Hz sample rate, 882
> frame blocks cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: 13230 frame
> buffer cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: GETPAR message
> cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: GETPAR message
> cmus0 vol=127,pst=ini,mmc=off,rmsg,widl: START message
> cmus0 vol=127,pst=ini,mmc=off: playing s16le -> s16le
> cmus0 vol=127,pst=ini,mmc=off: 

Re: pine64-lts - can't detect disk

[jungle Boogie]

On 13 April 2018 at 11:05, jungle Boogie  wrote:

>
> Thanks for the reply. I think I'm closer, but there still seems to be
> some gaps...

It's working now! I had taken a shortcut earlier. At the installer
prompt, I incorrectly selected upgrade to take a shortcut. Now
thinking about it, openBSD wasn't installed so it didn't know the
partition layout.

Thanks for the the assistance, Jonathan. Thanks for Peter and all the
developers of openBSD.

dmesg of openBSD installed and running (not sure if it's different
than what's above):

pine64# dmesg
OpenBSD 6.3-current (GENERIC.MP) #69: Thu Apr 12 14:11:59 MDT 2018
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP
real mem  = 2021416960 (1927MB)
avail mem = 1927913472 (1838MB)
mainbus0 at root: SoPine with baseboard
cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4
efi0 at mainbus0: UEFI 2.7
efi0: Das U-Boot rev 0x0
psci0 at mainbus0: PSCI 0.2
agtimer0 at mainbus0: tick rate 24000 KHz
simplebus0 at mainbus0: "soc"
syscon0 at simplebus0: "syscon"
sxiccmu0 at simplebus0
sxipio0 at simplebus0: 103 pins
ampintc0 at simplebus0 nirq 224, ncpu 4 ipi: 0, 1: "interrupt-controller"
sxiccmu1 at simplebus0
sxipio1 at simplebus0: 13 pins
sxirsb0 at simplebus0
axppmic0 at sxirsb0 addr 0x3a3: AXP803
sximmc0 at simplebus0
sdmmc0 at sximmc0: 4-bit, sd high-speed, mmc high-speed, dma
ehci0 at simplebus0
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Generic EHCI root hub" rev
2.00/1.00 addr 1
ehci1 at simplebus0
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "Generic EHCI root hub" rev
2.00/1.00 addr 1
com0 at simplebus0: ns16550, no working fifo
com0: console
dwxe0 at simplebus0: address 02:ba:43:50:f0:a3
rgephy0 at dwxe0 phy 1: RTL8169S/8110S/8211 PHY, rev. 5
sxirtc0 at simplebus0
gpio0 at sxipio0: 32 pins
gpio1 at sxipio0: 32 pins
gpio2 at sxipio0: 32 pins
gpio3 at sxipio0: 32 pins
gpio4 at sxipio0: 32 pins
gpio5 at sxipio0: 32 pins
gpio6 at sxipio0: 32 pins
gpio7 at sxipio0: 32 pins
gpio8 at sxipio1: 32 pins
cpu1 at mainbus0 mpidr 1: ARM Cortex-A53 r0p4
cpu2 at mainbus0 mpidr 2: ARM Cortex-A53 r0p4
cpu3 at mainbus0 mpidr 3: ARM Cortex-A53 r0p4
scsibus0 at sdmmc0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0:  SCSI2 0/direct removable
sd0: 30436MB, 512 bytes/sector, 62333952 sectors
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
bootfile: sd0a:/bsd
boot device: sd0
root on sd0a (cada93f8e15fb69e.a) swap on sd0b dump on sd0b

Community-driven OpenBSD tutorials wiki?

[Jan Lambertz]

Before working with OpenBSD, I thought archlinux had good documenation, (
the wiki ). On OpenBSD I rarely need more things than the man pages, the
ports PKG docs and tailing the logfiles. But I can understand that
sometimes it feels good for short term benefits to be able to use an up and
running config for xy.
I've read the pf.conf manpage very often and still there is space for my
config to improve but I (believe) begin to understand how to configure it
properly and how it should be used. Never had that feeling with online
wikis. There I searched for xy, found an post that seems close to my
problem, copy paste, restart program and maybe it worked or not. Sometimes
this is faster but I definitely learned more with while reading manpages.
For my part I think it's not possible to build something better than the
manpages for its purpose. I do like other sources of information but this
is more about projects. Someone built xy with OpenBSD and wrote an article
about it. Share your stories via undeadly or whatever. Build an index that
lists cool OpenBSD Projects for everyone to find. And the rest is up to the
user and man(1)

Re: OpenBSD 6.3 kernel panic

[Mike Larkin]

On Thu, Apr 12, 2018 at 10:19:23PM -0500, Juan Morado wrote:
> Hi all,
> 
> I searched the mail archives briefly but couldn't find a related issue.
> Apologies if this is a duplicate.
> 
> Since upgrading to OpenBSD 6.3 on my amd64 laptop, it has been crashing
> whenever I touch the track pad.
> 
> Touching the track pad after X starts generally causes the machine to just
> hang, however, it also crashes during boot if the track pad is touched so I
> was able to get a dump from ddb.
> 
> Output from dmesg follows. I also have bsd.0.core, bsd.0, bounds, minfree
> files from the crash dump. If there is any interest in looking at these,
> please advise the best way to share them.
> 
> - JM
> 
> ---

Where's the panic string?

> 
> OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 4157906944 (3965MB)
> avail mem = 4024819712 (3838MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xeced0 (18 entries)
> bios0: vendor American Megatrends Inc. version "X541SA.301" date 09/14/2016
> bios0: ASUSTeK COMPUTER INC. X541SA
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP APIC FPDT FIDT ECDT MCFG SSDT SSDT SSDT UEFI LPIT
> TPM2 CSRT SSDT SSDT MSDM
> acpi0: wakeup devices BRC1(S0) XHC1(S4) HDEF(S4) PXSX(S4) RP01(S4) PXSX(S4)
> RP02(S4) PXSX(S4) RP03(S4) SLPB(S4)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Pentium(R) CPU N3710 @ 1.60GHz, 1680.32 MHz
> 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
> cpu0: 1MB 64b/line 16-way L2 cache
> acpitimer0: recalibrated TSC frequency 1599952018 Hz
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 80MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE
> cpu1 at mainbus0: apid 2 (application processor)
> cpu1: Intel(R) Pentium(R) CPU N3710 @ 1.60GHz, 1680.01 MHz
> 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
> cpu1: 1MB 64b/line 16-way L2 cache
> cpu1: smt 0, core 1, package 0
> cpu2 at mainbus0: apid 4 (application processor)
> cpu2: Intel(R) Pentium(R) CPU N3710 @ 1.60GHz, 1600.01 MHz
> cpu2:
> 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
> cpu2: 1MB 64b/line 16-way L2 cache
> cpu2: smt 0, core 2, package 0
> cpu3 at mainbus0: apid 6 (application processor)
> cpu3: Intel(R) Pentium(R) CPU N3710 @ 1.60GHz, 1600.01 MHz
> cpu3:
> 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
> cpu3: 1MB 64b/line 16-way L2 cache
> cpu3: smt 0, core 3, package 0
> ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 115 pins
> acpiec0 at acpi0
> acpimcfg0 at acpi0 addr 0xe000, bus 0-255
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 1 (RP01)
> acpiprt2 at acpi0: bus -1 (RP02)
> acpiprt3 at acpi0: bus 2 (RP03)
> acpiprt4 at acpi0: bus 3 (RP04)
> acpiec at acpi0 not configured
> acpicpu0 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
> C1(1000@1 mwait.1), PSS
> acpicpu1 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
> C1(1000@1 mwait.1), PSS
> acpicpu2 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
> C1(1000@1 mwait.1), PSS
> acpicpu3 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
> C1(1000@1 mwait.1), PSS
> acpipwrres0 at acpi0: ID3C, resource for ISP3
> acpipwrres1 at acpi0: CLK0
> acpipwrres2 at acpi0: CLK0
> acpipwrres3 at acpi0: CLK1
> acpipwrres4 at acpi0: USBC, resource for XHC1
> acpipwrres5 at acpi0: FN00, resource for FAN0
> acpitz0 at acpi0: critical temperature is 95 degC
> acpitz1 at acpi0: critical temperature is 94 degC
> "ATK3001" at acpi0 not configured
> "INTL9C60" at acpi0 not configured
> dwiic0 at acpi0: I2C4 addr 0x8141c000/0x1000 irq 35
> iic0 at dwiic0
> ihidev0 at iic0 addr 0x15 irq 0, vendor 0xb05 

Re: pine64-lts - can't detect disk

[jungle Boogie]

On 13 April 2018 at 09:39, Jonathan Gray  wrote:
> On Fri, Apr 13, 2018 at 09:19:23AM -0700, jungle Boogie wrote:
>> On 13 April 2018 at 08:30, jungle Boogie  wrote:
>> > Hi All,
>> >
>> > So between Peter Hessler's post here:
>> > https://bsd.network/@phessler/99389809617980837
>> >
>> > And the install instructions for arm64:
>> > https://ftp.openbsd.org/pub/OpenBSD/snapshots/arm64/INSTALL.arm64
>> >
>> > I have the pine64-lts:
>> > https://www.pine64.org/?page_id=46823
>>
>>
>> Forgot the dmesg:
>>
>> OpenBSD 6.3-current (RAMDISK) #235: Thu Apr 12 14:38:28 MDT 2018
>> dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/RAMDISK
>> real mem  = 2015993856 (1922MB)
>> avail mem = 1915539456 (1826MB)
>> mainbus0 at root: Pine64+
>
> The sopine U-Boot image does not currently include the sopine device
> tree as there isn't a sopine device tree in U-Boot.
>
> Until that changes, on the msdos/efi partition create an 'allwinner'
> directory, install the dtb port and copy
> /usr/local/share/dtb/arm64/allwinner/sun50i-a64-sopine-baseboard.dtb
> to
> allwinner/sun50i-a64-pine64-plus.dtb
>
> or to a different path and change fdtfile in the U-Boot environment.
>
> Though it isn't clear if that is the appropriate device tree.
>

Thanks for the reply. I think I'm closer, but there still seems to be
some gaps...

my sd card:
$ ls /mnt/allwinner/
sun50i-a64-pine64-plus.dtb


=> run findfdt
## Error: "findfdt" not defined
=> load mmc 0:1 ${fdt_addr_r} allwinner/sun50i-a64-pine64-plus.dtb
12734 bytes read in 35 ms (354.5 KiB/s)
=> load mmc 0:1 ${kernel_addr_r} efi/boot/bootaa64.efi
98588 bytes read in 43 ms (2.2 MiB/s)
=> bootefi ${kernel_addr_r} ${fdt_addr_r}


However, now it sees the sd card but can't use it:
Available disks are: sd0.
Which disk is the root disk? ('?' for details) [sd0]
sd0 is not a valid root disk.
Available disks are: sd0.
Which disk is the root disk? ('?' for details) [sd0]

Re: OpenBSD 6.3, pppoe and IPv6 - default route missing

[Daniel Gillen]

On 13.04.2018 18:54, Edmund Craske wrote:
> On Fri, Apr 13, 2018, at 9:31 AM, Stuart Henderson wrote:
>> Can you show your whole hostname.pppoe0 file? (mask your password of
>> course).  On Zen I'm using the following
>>
>> mtu 1500
>> inet 0.0.0.0 255.255.255.255 0.0.0.1 pppoedev em1 authproto chap 
>> authname "XXX@zen" authkey "XXX" up
>> inet6 -autoconfprivacy
>> inet6 autoconf
>> !/sbin/route add default -ifp pppoe0 0.0.0.1
>> !/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0 -priority 8
>>
>> and hostname.em1 has
>>
>> mtu 1508
>> up
>>
>> In my case, I'm using dhcpcd from packages to get addresses for my internal
>> networks, Zen don't statically route my v6 block unless I request it via
>> DHCPv6-PD, but you won't need that with A, you can just configure them
>> statically on the inside interfaces.
> 
> Of course, here is my /etc/hostname.pppoe0:
> inet 0.0.0.0 255.255.255.255 NONE mtu 1500 pppoedev em1 authproto chap 
> authname foo authkey bar up
> dest 0.0.0.1
> inet6 eui64
> !/sbin/route add default -ifp pppoe0 0.0.0.1
> !/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0
> 
> and my /etc/hostname.em1 is:
> inet 192.168.2.2 255.255.255.0 NONE mtu 1508
> 
> Which I think was just me attempting to make it so that I could talk to my 
> modem previously... Anyway the connection comes up and I can do 1500 byte 
> packets over it so all good in that respect.
> 
> My config is basically lifted almost verbatim from the first example on the 
> pppoe(4) man page, with the 1500 mtu modifications from the example lower 
> down... So either there is something really weird with my particular setup 
> which means that this example is no longer suitable, or the example does not 
> work like expected on 6.3.
> 
> As previously mentioned I also tried it with 'eui64' changed to 'autoconf',  
> but it didn't seem that SLAAC was seeing RAs from the remote end - maybe 
> that's not set up on A, or something else is configured wrong? I did try 
> opening up my pf ruleset a bit but it made no difference. However I used an 
> older version of the manpage example on my previous OpenBSD 5.8 router (i.e. 
> no SLAAC or other thing doing any v6 configuration) and it worked fine, so 
> something is seemingly altering the v6 route table in between the pppoe0 if 
> being brought up, and it actually establishing a session...
> 
> Thanks,
> Edmund
> 

Hi

Just upgraded to 6.3 and it works for me. Here is my config:

--- /etc/hostname.em1


llprio 1 mtu 1508 up

--- /etc/hostname.vlan35


vnetid 35 parent em1 mtu 1508 llprio 1 up

--- /etc/hostname.pppoe0
inet 0.0.0.0 255.255.255.255 NONE mtu 1500 llprio 1 \
pppoedev vlan35 \
authproto pap \
authname "foo" \
authkey "bar"
dest 0.0.0.1
inet6 autoconf
!/sbin/route add default -ifp pppoe0 0.0.0.1
!/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0

--- /etc/pf.conf
if_ext="pppoe0"
icmp6_types="{ 1, 2, 133, 134, 135, 136 }"
pass in quick on $if_ext inet6 proto icmp6 from any to { ($if_ext),
ff02::1/16 } icmp6-type $icmp6_types
pass in quick on $if_ext inet6 proto icmp6 from any to { ($if_ext),
ff02::1/16 } icmp6-type 3 code 0
pass in quick on $if_ext inet6 proto icmp6 from any to { ($if_ext),
ff02::1/16 } icmp6-type 3 code 1
pass in quick on $if_ext inet6 proto icmp6 from any to { ($if_ext),
ff02::1/16 } icmp6-type 4 code 0
pass in quick on $if_ext inet6 proto icmp6 from any to { ($if_ext),
ff02::1/16 } icmp6-type 4 code 1
pass in quick on $if_ext inet6 proto icmp6 from any to { ($if_ext),
ff02::1/16 } icmp6-type 4 code 2

You don't have to use a vlan as it seems from your config and won't need
the llprio stuff either. If your ISP supports SLAAC, this should work
for you too I guess.

Daniel

-- 
Unix _IS_ user friendly - it's just
selective about who its friends are!

Re: OpenBSD 6.3, pppoe and IPv6 - default route missing

[Edmund Craske]

On Fri, Apr 13, 2018, at 9:31 AM, Stuart Henderson wrote:
> Can you show your whole hostname.pppoe0 file? (mask your password of
> course).  On Zen I'm using the following
> 
> mtu 1500
> inet 0.0.0.0 255.255.255.255 0.0.0.1 pppoedev em1 authproto chap 
> authname "XXX@zen" authkey "XXX" up
> inet6 -autoconfprivacy
> inet6 autoconf
> !/sbin/route add default -ifp pppoe0 0.0.0.1
> !/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0 -priority 8
> 
> and hostname.em1 has
> 
> mtu 1508
> up
> 
> In my case, I'm using dhcpcd from packages to get addresses for my internal
> networks, Zen don't statically route my v6 block unless I request it via
> DHCPv6-PD, but you won't need that with A, you can just configure them
> statically on the inside interfaces.

Of course, here is my /etc/hostname.pppoe0:
inet 0.0.0.0 255.255.255.255 NONE mtu 1500 pppoedev em1 authproto chap authname 
foo authkey bar up
dest 0.0.0.1
inet6 eui64
!/sbin/route add default -ifp pppoe0 0.0.0.1
!/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0

and my /etc/hostname.em1 is:
inet 192.168.2.2 255.255.255.0 NONE mtu 1508

Which I think was just me attempting to make it so that I could talk to my 
modem previously... Anyway the connection comes up and I can do 1500 byte 
packets over it so all good in that respect.

My config is basically lifted almost verbatim from the first example on the 
pppoe(4) man page, with the 1500 mtu modifications from the example lower 
down... So either there is something really weird with my particular setup 
which means that this example is no longer suitable, or the example does not 
work like expected on 6.3.

As previously mentioned I also tried it with 'eui64' changed to 'autoconf',  
but it didn't seem that SLAAC was seeing RAs from the remote end - maybe that's 
not set up on A, or something else is configured wrong? I did try opening up 
my pf ruleset a bit but it made no difference. However I used an older version 
of the manpage example on my previous OpenBSD 5.8 router (i.e. no SLAAC or 
other thing doing any v6 configuration) and it worked fine, so something is 
seemingly altering the v6 route table in between the pppoe0 if being brought 
up, and it actually establishing a session...

Thanks,
Edmund

Re: 4-ports router under $150

[Stuart Henderson]

On 2018-04-13, Joel Wirāmu Pauling  wrote:
> Can they do 14MPPS aka 10GBIT ?
> That's what I am looking for in pretty much in anything I would vaguely
> consider to replace the n3160's I have as my target devices at the moment.

Not sure the current max performance but I think we're still a fair bit
of work away from that sort of speed on OpenBSD on any hardware.

Re: pine64-lts - can't detect disk

[Jonathan Gray]

On Fri, Apr 13, 2018 at 09:19:23AM -0700, jungle Boogie wrote:
> On 13 April 2018 at 08:30, jungle Boogie  wrote:
> > Hi All,
> >
> > So between Peter Hessler's post here:
> > https://bsd.network/@phessler/99389809617980837
> >
> > And the install instructions for arm64:
> > https://ftp.openbsd.org/pub/OpenBSD/snapshots/arm64/INSTALL.arm64
> >
> > I have the pine64-lts:
> > https://www.pine64.org/?page_id=46823
> 
> 
> Forgot the dmesg:
> 
> OpenBSD 6.3-current (RAMDISK) #235: Thu Apr 12 14:38:28 MDT 2018
> dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/RAMDISK
> real mem  = 2015993856 (1922MB)
> avail mem = 1915539456 (1826MB)
> mainbus0 at root: Pine64+

The sopine U-Boot image does not currently include the sopine device
tree as there isn't a sopine device tree in U-Boot.

Until that changes, on the msdos/efi partition create an 'allwinner'
directory, install the dtb port and copy
/usr/local/share/dtb/arm64/allwinner/sun50i-a64-sopine-baseboard.dtb
to
allwinner/sun50i-a64-pine64-plus.dtb

or to a different path and change fdtfile in the U-Boot environment.

Though it isn't clear if that is the appropriate device tree.

> cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4
> efi0 at mainbus0: UEFI 2.7
> efi0: Das U-Boot rev 0x0
> psci0 at mainbus0: PSCI 0.2
> agtimer0 at mainbus0: tick rate 24000 KHz
> simplebus0 at mainbus0: "soc"
> sxiccmu0 at simplebus0
> sxipio0 at simplebus0: 103 pins
> ampintc0 at simplebus0 nirq 224, ncpu 4: "interrupt-controller"
> sxiccmu1 at simplebus0
> sxipio1 at simplebus0: 13 pins
> sximmc0 at simplebus0
> sdmmc0 at sximmc0: 4-bit, sd high-speed, mmc high-speed, dma
> ehci0 at simplebus0
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 configuration 1 interface 0 "Generic EHCI root hub" rev
> 2.00/1.00 addr 1
> com0 at simplebus0: ns16550, no working fifo
> com0: console
> sxitwi0 at simplebus0
> iic0 at sxitwi0
> sxirtc0 at simplebus0
> dwxe0 at simplebus0: address 02:ba:43:50:f0:a3
> rgephy0 at dwxe0 phy 0: RTL8169S/8110S/8211 PHY, rev. 5
> rgephy1 at dwxe0 phy 1: RTL8169S/8110S/8211 PHY, rev. 5
> gpio0 at sxipio0: 32 pins
> gpio1 at sxipio0: 32 pins
> gpio2 at sxipio0: 32 pins
> gpio3 at sxipio0: 32 pins
> gpio4 at sxipio0: 32 pins
> gpio5 at sxipio0: 32 pins
> gpio6 at sxipio0: 32 pins
> gpio7 at sxipio0: 32 pins
> gpio8 at sxipio1: 32 pins
> bootfile: sd0a:/bsd
> boot device: lookup sd0a:/bsd failed
> root on rd0a swap on rd0b dump on rd0b
> 

Re: OpenBSD 6.3, pppoe and IPv6 - default route missing

[Stuart Henderson]

On 2018-04-13, Edmund Craske  wrote:
> Hi,
> I've just replaced my old OpenBSD 5.x-running router with a new one (Alix 
> APU2) running 6.3.
>
> Having copied over my old configuration and modified it where necessary, I've 
> got it bringing up my connections fine, IPv4 works, but IPv6 does not, 
> without having to manually add a default route after the connection is up.
>
> I already tripped over (and fixed) the fact that you have to put % 
> on the end of your inet6 route destinations now, but even having done that, 
> for some reason a default route does not get added correctly on boot with the 
> following line present in my /etc/hostname.pppoe0:
>
> !/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0
>
> Looking at the console output on boot it doesn't show any error running that 
> command (implying that the route should have been added just fine) but it's 
> definitely not there any more when doing a 'netstat -rn' once the ppp session 
> is established - is something removing it as part of establishing the 
> connection?
>
> Is there a completely different way that I should be doing this than the one 
> shown in  the pppoe(4) man page? I have already tried having 'inet6 autoconf' 
> instead of 'inet6 eui64' but for some reason I don't get a SLAAC 
> configuration and IPv6 doesn't come up that way. I don't know if anything has 
> to be explicitly enabled to make SLAAC work or if I am inadvertently blocking 
> something that I need to allow in my pf ruleset?
>
> I am in the UK, using a Draytek Vigor 130 VDSL modem with FTTC to Andrews & 
> Arnold (AAISP).
>
> Thanks in advance for any help :)
>
> Edmund
>
>

Can you show your whole hostname.pppoe0 file? (mask your password of
course).  On Zen I'm using the following

mtu 1500
inet 0.0.0.0 255.255.255.255 0.0.0.1 pppoedev em1 authproto chap authname 
"XXX@zen" authkey "XXX" up
inet6 -autoconfprivacy
inet6 autoconf
!/sbin/route add default -ifp pppoe0 0.0.0.1
!/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0 -priority 8

and hostname.em1 has

mtu 1508
up

In my case, I'm using dhcpcd from packages to get addresses for my internal
networks, Zen don't statically route my v6 block unless I request it via
DHCPv6-PD, but you won't need that with A, you can just configure them
statically on the inside interfaces.

Re: pine64-lts - can't detect disk

[jungle Boogie]

On 13 April 2018 at 08:30, jungle Boogie  wrote:
> Hi All,
>
> So between Peter Hessler's post here:
> https://bsd.network/@phessler/99389809617980837
>
> And the install instructions for arm64:
> https://ftp.openbsd.org/pub/OpenBSD/snapshots/arm64/INSTALL.arm64
>
> I have the pine64-lts:
> https://www.pine64.org/?page_id=46823


Forgot the dmesg:

OpenBSD 6.3-current (RAMDISK) #235: Thu Apr 12 14:38:28 MDT 2018
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/RAMDISK
real mem  = 2015993856 (1922MB)
avail mem = 1915539456 (1826MB)
mainbus0 at root: Pine64+
cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4
efi0 at mainbus0: UEFI 2.7
efi0: Das U-Boot rev 0x0
psci0 at mainbus0: PSCI 0.2
agtimer0 at mainbus0: tick rate 24000 KHz
simplebus0 at mainbus0: "soc"
sxiccmu0 at simplebus0
sxipio0 at simplebus0: 103 pins
ampintc0 at simplebus0 nirq 224, ncpu 4: "interrupt-controller"
sxiccmu1 at simplebus0
sxipio1 at simplebus0: 13 pins
sximmc0 at simplebus0
sdmmc0 at sximmc0: 4-bit, sd high-speed, mmc high-speed, dma
ehci0 at simplebus0
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Generic EHCI root hub" rev
2.00/1.00 addr 1
com0 at simplebus0: ns16550, no working fifo
com0: console
sxitwi0 at simplebus0
iic0 at sxitwi0
sxirtc0 at simplebus0
dwxe0 at simplebus0: address 02:ba:43:50:f0:a3
rgephy0 at dwxe0 phy 0: RTL8169S/8110S/8211 PHY, rev. 5
rgephy1 at dwxe0 phy 1: RTL8169S/8110S/8211 PHY, rev. 5
gpio0 at sxipio0: 32 pins
gpio1 at sxipio0: 32 pins
gpio2 at sxipio0: 32 pins
gpio3 at sxipio0: 32 pins
gpio4 at sxipio0: 32 pins
gpio5 at sxipio0: 32 pins
gpio6 at sxipio0: 32 pins
gpio7 at sxipio0: 32 pins
gpio8 at sxipio1: 32 pins
bootfile: sd0a:/bsd
boot device: lookup sd0a:/bsd failed
root on rd0a swap on rd0b dump on rd0b

Re: Xfce with the .xinitrc file

[Freddy Fisker]

I only use the following in the .xinitrc file to start Xfce: xfce4-session

Best regards
Freddy


On Friday, 13 April 2018 12:38:36 CEST, Olivier REGNIER wrote:

Hi,

After xfce was installed, I used the xinitrc file found in 
/usr/local/share/examples/xfce4-session.


It is very complete.

Xfce runs but ck-launch-session is not executed.

Here is the script related to ck-launch-session:

# run xfce4-session if installed
if which xfce4-session /dev/null 21; then

  # check if we start xfce4-session with ck-launch-session. this is only
   # required for starting from a console, not a login manager
   if test "$XFCE4_SESSION_WITH_CK" = "1"; then
 if which ck-launch-session /dev/null 21; then
   ck-launch-session xfce4-session
 else
   echo "You have tried to start Xfce with consolekit support, but"
   echo "ck-launch-session is not installed."
   echo "Aborted startup..."
   echo

   exit 1
 fi
   else
 # start xfce4-session normally
 xfce4-session
   fi

   exit 0
 fi

Thanks for your help.

pine64-lts - can't detect disk

[jungle Boogie]

Hi All,

So between Peter Hessler's post here:
https://bsd.network/@phessler/99389809617980837

And the install instructions for arm64:
https://ftp.openbsd.org/pub/OpenBSD/snapshots/arm64/INSTALL.arm64

I have the pine64-lts:
https://www.pine64.org/?page_id=46823

Booting to the installer, but the sd card disk cannot be located:
Available disks are: none.
Which disk is the root disk? ('?' for details) /dev/rd0a
no such disk
Available disks are: none.
Which disk is the root disk? ('?' for details) /dev/rd0
no such disk
Available disks are: none.
Which disk is the root disk? ('?' for details) ?
Available disks are: none.
Which disk is the root disk? ('?' for details)


Can anyone give some hints on how to have the installer detect the SD
card and for the installation to be completed?

disklabel rd0
# /dev/rrd0c:
type: rdroot
disk: rdroot
label:
duid: 6665228f9017b391
flags:
bytes/sector: 512
sectors/track: 480
tracks/cylinder: 2
sectors/cylinder: 960
cylinders: 16
total sectors: 15360
boundstart: 0
boundend: 0
drivedata: 0

3 partitions:
#size   offset  fstype [fsize bsize   cpg]
  a:153600  4.2BSD512  4096  1920
  c:153600  unused

Thanks!

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info

Re: Xfce with the .xinitrc file

[IL Ka]

 Hi,
So, does  xfce4-session start with out of console kit or does not start at
all?
Do you use display manager or startx?
Note that .xinitrc is used only by xinit (startx), not by xenodm/xdm.

ck-launch-session  is part of ConsoleKit, do you have it installed?


On Fri, Apr 13, 2018 at 1:38 PM, Olivier REGNIER 

Re: Migrating nginx config to OpenBSD's httpd

[Bogdan Kulbida]

Hi Carlos,

HAproxy project exists and serves much better as load balancer and reverse
proxy server. It is more efficient than engine X. Any concerns using it?

- Bogdan

On Fri, Apr 13, 2018 at 04:47 Pavel Korovin  wrote:

> Hi Carlos,
>
> There's no analog of proxy_pass in httpd(8). relayd(8) is your friend.
>
> On 04/13, C. L. Martinez wrote:
> >  I am trying to migrate nginx configuration to OpenBSD's httpd. All it is
> > working ok, except for some proxy reverse config that I use with nginx's
> > config, like for example:
> >
> > server {
> > listen 80;
> > server_name internal.w01.domain.org;
> >
> > location / {
> > proxy_pass http://192.168.30.4;
> > }
> > }
> >
> >  I don't see what is the option to use with httpd.conf or is it best
> > option to use relayd.conf for this type of configs?
>
> --
> With best regards,
> Pavel Korovin
>
> --

---
Best regards,
Bogdan Kulbida
CEO/CTO, Konstankino LLC 
+1.802.793.8295

Re: Xfce with the .xinitrc file

[Christophe Simon]

Hello,

Sorry for this silly question, but is consolekit installed ?

Additionally, how do you start your X session ? Using a login manager
(xenodm ?), or from the console using `startx` ?

The script below requires the variable `XFCE4_SESSION_WITH_CK` is set to
`1` to run the session through consolekit. If you use `startx`, could
you try to `export XFCE4_SESSION_WITH_CK=1` ?

Regards.

Christophe

Le 04/13/18 à 12:38, Olivier REGNIER a écrit :

Hi,

After xfce was installed, I used the xinitrc file found in 
/usr/local/share/examples/xfce4-session.


It is very complete.

Xfce runs but ck-launch-session is not executed.

Here is the script related to ck-launch-session:

# run xfce4-session if installed
if which xfce4-session /dev/null 21; then

   # check if we start xfce4-session with ck-launch-session. this is only
    # required for starting from a console, not a login manager
    if test "$XFCE4_SESSION_WITH_CK" = "1"; then
  if which ck-launch-session /dev/null 21; then
    ck-launch-session xfce4-session
  else
    echo "You have tried to start Xfce with consolekit support, but"
    echo "ck-launch-session is not installed."
    echo "Aborted startup..."
    echo

    exit 1
  fi
    else
  # start xfce4-session normally
  xfce4-session
    fi

    exit 0
  fi

Thanks for your help.

Re: Migrating nginx config to OpenBSD's httpd

[Pavel Korovin]

Hi Carlos,

There's no analog of proxy_pass in httpd(8). relayd(8) is your friend.

On 04/13, C. L. Martinez wrote:
>  I am trying to migrate nginx configuration to OpenBSD's httpd. All it is
> working ok, except for some proxy reverse config that I use with nginx's
> config, like for example:
> 
> server {
> listen 80;
> server_name internal.w01.domain.org;
> 
> location / {
> proxy_pass http://192.168.30.4;
> }
> }
> 
>  I don't see what is the option to use with httpd.conf or is it best
> option to use relayd.conf for this type of configs?

-- 
With best regards,
Pavel Korovin

Xfce with the .xinitrc file

[Olivier REGNIER]

Hi,

After xfce was installed, I used the xinitrc file found in 
/usr/local/share/examples/xfce4-session.


It is very complete.

Xfce runs but ck-launch-session is not executed.

Here is the script related to ck-launch-session:

# run xfce4-session if installed
if which xfce4-session /dev/null 21; then

  # check if we start xfce4-session with ck-launch-session. this is only
   # required for starting from a console, not a login manager
   if test "$XFCE4_SESSION_WITH_CK" = "1"; then
 if which ck-launch-session /dev/null 21; then
   ck-launch-session xfce4-session
 else
   echo "You have tried to start Xfce with consolekit support, but"
   echo "ck-launch-session is not installed."
   echo "Aborted startup..."
   echo

   exit 1
 fi
   else
 # start xfce4-session normally
 xfce4-session
   fi

   exit 0
 fi

Thanks for your help.

--
Regards,
Olivier REGNIER

Migrating nginx config to OpenBSD's httpd

[C. L. Martinez]

Hi all,

 I am trying to migrate nginx configuration to OpenBSD's httpd. All it is
working ok, except for some proxy reverse config that I use with nginx's
config, like for example:

server {
listen 80;
server_name internal.w01.domain.org;

location / {
proxy_pass http://192.168.30.4;
}
}

 I don't see what is the option to use with httpd.conf or is it best
option to use relayd.conf for this type of configs?

Thanks.

Re: Virtualbox vs latest snapshot

[Consus]

On 09:30 Fri 13 Apr, Boudewijn Dijkstra wrote:
> The point is not to go to court, the point is to bully people into
> paying up.

Well, this reminds me of Nigerian Emails. Have someone actually payed
them? Cause seriously, you can just reply them with a goatse picture
attached. Even goatse has more legal matter in it.

OpenBSD 6.3, pppoe and IPv6 - default route missing

[Edmund Craske]

Hi,
I've just replaced my old OpenBSD 5.x-running router with a new one (Alix APU2) 
running 6.3.

Having copied over my old configuration and modified it where necessary, I've 
got it bringing up my connections fine, IPv4 works, but IPv6 does not, without 
having to manually add a default route after the connection is up.

I already tripped over (and fixed) the fact that you have to put % 
on the end of your inet6 route destinations now, but even having done that, for 
some reason a default route does not get added correctly on boot with the 
following line present in my /etc/hostname.pppoe0:

!/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0

Looking at the console output on boot it doesn't show any error running that 
command (implying that the route should have been added just fine) but it's 
definitely not there any more when doing a 'netstat -rn' once the ppp session 
is established - is something removing it as part of establishing the 
connection?

Is there a completely different way that I should be doing this than the one 
shown in  the pppoe(4) man page? I have already tried having 'inet6 autoconf' 
instead of 'inet6 eui64' but for some reason I don't get a SLAAC configuration 
and IPv6 doesn't come up that way. I don't know if anything has to be 
explicitly enabled to make SLAAC work or if I am inadvertently blocking 
something that I need to allow in my pf ruleset?

I am in the UK, using a Draytek Vigor 130 VDSL modem with FTTC to Andrews & 
Arnold (AAISP).

Thanks in advance for any help :)

Edmund

Re: Virtualbox vs latest snapshot

[Boudewijn Dijkstra]

Op Thu, 12 Apr 2018 15:47:18 +0200 schreef Consus :

On 08:28 Thu 12 Apr, Nick Holland wrote:

Another "failure mode" of VirtualBox people should be aware of:
I understand through good sources, Oracle monitors the IP addresses that
it's downloaded from, and if they can trace it back to a commercial IP
(i.e., not a home address), and if they see you download (or update) the
"not for unrestricted free use" parts, their lawyers will contact you
and send you a bill...and they really don't care about "for work" or
"not for work related" uses.

I'd really recommend removing this product from your computers.


This won't stand in court. You sources are so high on crack it's not
even funny.


The point is not to go to court, the point is to bully people into paying  
up.



--
Gemaakt met Opera's e-mailprogramma: http://www.opera.com/mail/

Re: Virtualbox vs latest snapshot

[Boudewijn Dijkstra]

Op Thu, 12 Apr 2018 14:28:14 +0200 schreef Nick Holland  
:

Another "failure mode" of VirtualBox people should be aware of:
I understand through good sources, Oracle monitors the IP addresses that
it's downloaded from, and if they can trace it back to a commercial IP
(i.e., not a home address), and if they see you download (or update) the
"not for unrestricted free use" parts, their lawyers will contact you
and send you a bill...and they really don't care about "for work" or
"not for work related" uses.


I suppose this only works if you have your own netblock. Otherwise they  
cannot know the legal entity behind an IP-address. Except in totalitarian  
states I guess.



I'd really recommend removing this product from your computers.


By which you mean the Oracle VM VirtualBox Extension Pack, presumably.


--
Gemaakt met Opera's e-mailprogramma: http://www.opera.com/mail/

Re: net-snmpd extend and doas : a tty is required

[Martijn van Duren]

On 04/12/18 23:13, Joel Carnat wrote:
>> Le 12 avr. 2018 à 21:10, Stuart Henderson  a écrit :
>>
>> On 2018-04-12, Joel Carnat > wrote:
>>> Hi,
>>>
>>> I want net-snmpd to run a script via the extend directive.
>>> This script has to run a command using doas to get temporary root 
>>> permission.
>>>
>>> The script is run on snmpcmd call but the doas command returns:
>>> doas: a tty is required
>>>
>>> Is there a way to run doas from net-snmpd ?
>>> I already have doas running from collectd-exec without issues.
>>>
>>> Thanks.
>>>
>>> # More infos on configuration and commands
>>>
>>> # grep extend /etc/snmp/snmpd.conf
>>> extend test /home/scripts/test.sh
>>>
>>> # grep snmpd /etc/doas.conf
>>> permit nopass _snmpd as root
>>
>> Net-SNMP runs as _netsnmp, but you're giving nopass access to _snmpd
>> (base snmpd's uid, which doesn't execute anything anyway).
> 
> Of course…
> Using "permit nopass _netsnmp as root" makes it run as expected.

Please add "cmd  args ..." to that line to prevent more root-
exposure than required.
> 
> Thanks a lot!
>