unbound eats up buffer space

[Marko Cupać]

Hi,

I have 5.8 i386 box as my home network gateway, with unbound as a
resolver for local LAN. I am getting these in my log:

Mar  8 08:21:42 kerber unbound: [24074:0] notice: sendto failed: No
buffer space available
Mar  8 08:21:42 kerber unbound: [24074:0] notice: remote address is
192.168.33.1 port 60829

Any advices? Thank you in advance.
--
Before enlightenment - chop wood, draw water.
After  enlightenment - chop wood, draw water.

Marko Cupać
https://www.mimar.rs/

Re: BGPD not adding routes

[Claudio Jeker]

On Mon, Mar 07, 2016 at 11:29:48AM -0500, Matt Schwartz wrote:
> Thank you much, Claudio! That was the ticket. I had put my depend on mpe0
> in the wrong place. I was mostly using your mpls example. Dumb questions:
> Why do you not create a default route in rdomain 1 on the 2nd PE in your
> mpls example network? Why do you not have network 0.0.0.0/0 on the 2nd PE?
> Thanks for helping me with my understanding gaps.
> 

>From the top of my memory the idea is that the 2nd PE gets the default
route from the 1st PE similar to a client connecting via MPLS VPN to a
ISP. Does this make sense?

-- 
:wq Claudio

Re: OpenBSD 5.8, -static, and -nopie

[Philip Guenther]

On Tue, Mar 1, 2016 at 10:39 PM, Kristaps Dzonsons  wrote:
> I'm having a strange issue on 5.8 regarding compiling -static binaries.
>  In short, unless I specify -nopie for a particular statically-linked
> binary, it segfaults.  Am I making a mistake, maybe, in my compilation?
...
> Then I try the same, but linking with -static:
>
> % cc -static -L/usr/local/lib -o admin ...
>
> Now,
>
> % ./admin
> Segmentation fault (core dumped)
>
> % gdb ./admin
...
> (gdb) run
> Starting program: ./admin
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0f92a5b46ced in _dl_boot_bind ()
> (gdb) bt
> #0  0x0f92a5b46ced in _dl_boot_bind ()
> #1  0x0f92a5b468e9 in __start ()
> #2  0x in ?? ()

Well that's not good.  First, what's the output of
readelf -edr admin

That covers the data used by _dl_boot_bind() to relocate the static
PIE process.  Next, can you run it under gdb like that and after it
gets a SEGV can you get the output of both 'bt' (like you did above)
and 'info reg'?  As is it looks like an R_X86_64_RELATIVE relocation
for a bogus location, but the readelf output should clarify that.


Phliip Guenther

bgpd network connected

[Tony Sarendal]

Is there any chance of getting "network inet connected" fixed to 5.9 ?

Regards Tony

Re: some problems with disks

[dan mclaughlin]

On Tue, 8 Mar 2016 00:20:08 +0100 arrowscr...@mail.com wrote:
> I'm having some problems with disks. Probably because I still don't
> understand enough of how BSD manage them:
> 
> 1. I was going to install -current on a USB flash drive. I did the
> install media using install59.fs and booted. I scape from installer to
> shell because I wanted to wipe the drive using dd(1) and to create a
> RAID partition (for FDE). I could not find the disk on /dev/, however.
> The system print on screen that the disk is located at "sd5" interface
> ("dmesg | grep sd" confirm this), but I cound not find it using "disklabel
> /dev/sd5". The only interfaces there was sd0 and wd0, none was my disk.
> How can I find it? The ./install script can find the sd5 normally, but I
> can't find it manually.

# (cd /dev && ./MAKEDEV sd5)

> 
> 2. I gave up of the FDE idea temporarily and I just did the install
> normally. No problem to install, but the speed of the system was too
> slow... at the point that it was basically unusable (>4 hours to install
> 10 packages and ~4 minutes to startx).
> The device, a USB flash drive, have about 10MB/s write speed. It's kinda
> slow, but I don't think this was the cause of the slowliness. I checked
> the signature of the snapshot and the installed sets had no problem with
> SHA256 too, so it's not a problem with corrupted snapshot.
> 

on quick way to check to check if it is the drive itself is to use dd:

# dd if=/dev/zero of=/mnt/testfile bs=1M count=20

but if the install was not slow that is unlikely to be the problem.

Re: Shoudn't full disk encryption be a option on installer?

[Stuart Henderson]

On 2016-03-07, arrowscr...@mail.com  wrote:
> I'm using softraid_crypto for full disk encryption for about one year
> now. I used this on a low end Core2Duo and noticed absolutely *no*
> performance hit. I also use this on a newer platform and, again, no
> performance problems. It's stable too, no issues on booting.
> I know some high intensive servers/routers and old machines with old hard
> drivers can have serious performance decrease due to this, but this
> could be at least a option on installer, I think.
> The developers have any arguments against this? Why not? I think this is
> a great security improvement, specially for a notebook user.

This mailing list strips attachments, please re-send with the diff inline.

Re: Shoudn't full disk encryption be a option on installer?

[Jiri B]

On Tue, Mar 08, 2016 at 12:32:16AM +0100, arrowscr...@mail.com wrote:
> I'm using softraid_crypto for full disk encryption for about one year
> now. I used this on a low end Core2Duo and noticed absolutely *no*
> performance hit. I also use this on a newer platform and, again, no
> performance problems. It's stable too, no issues on booting.
> I know some high intensive servers/routers and old machines with old hard
> drivers can have serious performance decrease due to this, but this
> could be at least a option on installer, I think.
> The developers have any arguments against this? Why not? I think this is
> a great security improvement, specially for a notebook user.

Probably nobody has yet sent good solution for the installer.
You got the source, read it, understand it, get idea how autoinstall
works, check archives which kind of "improvements" were discussed or
rejected, then... maybe cook a diff.

j.

Shoudn't full disk encryption be a option on installer?

[arrowscript]

I'm using softraid_crypto for full disk encryption for about one year
now. I used this on a low end Core2Duo and noticed absolutely *no*
performance hit. I also use this on a newer platform and, again, no
performance problems. It's stable too, no issues on booting.
I know some high intensive servers/routers and old machines with old hard
drivers can have serious performance decrease due to this, but this
could be at least a option on installer, I think.
The developers have any arguments against this? Why not? I think this is
a great security improvement, specially for a notebook user.

Re: some problems with disks

[Jiri B]

tl;dr...

> 3. When procceding to wipe the disk on my desktop (openbsd -current too)
> I cound not do this. This time I could find sd5 using disklabel, but:
> 
>   # dd if=/dev/arandom of=/dev/sd5 bs=4096
> 
>   /: write failed, filesystem is full
>   dd: /dev/sd5: No space left on device

see man disklabel, you need to put 'c' for whole disk, otherwise
you created new file in /dev.

> The same happen on rsd5. When trying to wipe just one partition:
> 
>   # dd if=/dev/arandom of=/dev/rsd5c
>   Operation not permitted
> 
> The message show after just some seconds (the disk has 7.2GB) and the
> partitions still there, so I know that dd did not work. 
> I thought it was something to do with my kern.securelevel, but when to
> down from 2 -> 1 got the same permission problem: 
> 
>   # sysctl kern.securelevel=1
>   sysctl: kern.securelevel: Operationg not permitted

man securelevel, you cannot decrease securelevel. in this case 'raw
disks are always read-only'.

welcome on the board, just do man help, man hier, man afterboot...

j.

some problems with disks

[arrowscript]

I'm having some problems with disks. Probably because I still don't
understand enough of how BSD manage them:

1. I was going to install -current on a USB flash drive. I did the
install media using install59.fs and booted. I scape from installer to
shell because I wanted to wipe the drive using dd(1) and to create a
RAID partition (for FDE). I could not find the disk on /dev/, however.
The system print on screen that the disk is located at "sd5" interface
("dmesg | grep sd" confirm this), but I cound not find it using "disklabel
/dev/sd5". The only interfaces there was sd0 and wd0, none was my disk.
How can I find it? The ./install script can find the sd5 normally, but I
can't find it manually.

2. I gave up of the FDE idea temporarily and I just did the install
normally. No problem to install, but the speed of the system was too
slow... at the point that it was basically unusable (>4 hours to install
10 packages and ~4 minutes to startx).
The device, a USB flash drive, have about 10MB/s write speed. It's kinda
slow, but I don't think this was the cause of the slowliness. I checked
the signature of the snapshot and the installed sets had no problem with
SHA256 too, so it's not a problem with corrupted snapshot.

3. When procceding to wipe the disk on my desktop (openbsd -current too)
I cound not do this. This time I could find sd5 using disklabel, but:

# dd if=/dev/arandom of=/dev/sd5 bs=4096

/: write failed, filesystem is full
dd: /dev/sd5: No space left on device


The same happen on rsd5. When trying to wipe just one partition:

# dd if=/dev/arandom of=/dev/rsd5c
Operation not permitted

The message show after just some seconds (the disk has 7.2GB) and the
partitions still there, so I know that dd did not work. 
I thought it was something to do with my kern.securelevel, but when to
down from 2 -> 1 got the same permission problem: 

# sysctl kern.securelevel=1
sysctl: kern.securelevel: Operationg not permitted

dmesg:

penBSD 5.9-beta (GENERIC.MP) #1864: Mon Jan 25 19:11:29 MST 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16481857536 (15718MB)
avail mem = 15978151936 (15237MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe98e0 (94 entries)
bios0: vendor American Megatrends Inc. version "1601" date 11/27/2013
bios0: ASUSTeK COMPUTER INC. P8H61-M LX2 R2.0
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT MCFG SSDT BGRT SSDT SSDT DMAR
acpi0: wakeup devices P0P1(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4)
PEGP(S4) PEG0(S4) PEG1(S4) PEG2(S4) PEG3(S4) PXSX(S4) RP04(S4) PXSX(S4)
RP03(S4) PS2K(S4) PS2M(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) Core(TM) i5-3470 CPU @ 3.20GHz, 3200.47 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 100MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz, 3200.03 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz, 3200.03 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz, 3200.03 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, 

No sound through headphones on laptop (HP 9480m)

[Simon McFarlane]

Hi,

I'm running today's snapshot on an HP EliteBook 9480m. Everything works 
great, aside from the audio. I get no sound when I plug my headphones 
in, though the internal speakers work when the headphones are not 
plugged in (they mute themselves when the headphones are inserted).


I'm good to test patches if anybody has any ideas that might help fix this.

Output of mixerctl -va:
inputs.dac-0:1=126,126
inputs.dac-2:3=126,126
record.adc-2:3_mute=off  [ off on ]
record.adc-2:3=124,124
record.adc-0:1_mute=off  [ off on ]
record.adc-0:1=124,124
inputs.mix_source=mic2  { mic2 }
inputs.mix_mic2=120,120
inputs.mix2_source=dac-0:1,mix  { dac-0:1 mix }
inputs.mix3_source=dac-2:3,mix  { dac-2:3 mix }
inputs.mic=85,85
outputs.spkr_source=mix3  [ mix2 mix3 ]
outputs.spkr_mute=on  [ off on ]
outputs.spkr_eapd=on  [ off on ]
outputs.hp_source=mix2  [ mix2 mix3 ]
outputs.hp_mute=off  [ off on ]
outputs.hp_boost=off  [ off on ]
outputs.hp_eapd=on  [ off on ]
outputs.mic2_source=mix2  [ mix2 mix3 ]
outputs.mic2_mute=off  [ off on ]
inputs.mic2=85,85
outputs.mic2_dir=input-vr80  [ none output input input-vr0 input-vr50 
input-vr80 input-vr100 ]

outputs.mic2_boost=off  [ off on ]
record.adc-0:1_source=mic  [ mic2 mix mic ]
record.adc-2:3_source=mic2  [ mic2 mix ]
outputs.hp_sense=plugged  [ unplugged plugged ]
outputs.mic2_sense=unplugged  [ unplugged plugged ]
outputs.spkr_muters=hp,mic2  { hp mic2 }
outputs.master=126,126
outputs.master.mute=off  [ off on ]
outputs.master.slaves=dac-0:1,dac-2:3,spkr,hp  { dac-0:1 dac-2:3 spkr hp 
mic2 }

record.volume=124,124
record.volume.mute=off  [ off on ]
record.volume.slaves=adc-2:3,adc-0:1  { adc-2:3 adc-0:1 mic mic2 }

Two knobs change when the headphones are removed:
outputs.spkr_mute=off  [ off on ]
outputs.hp_sense=unplugged  [ unplugged plugged ]

output of audioctl:
name=azalia1
encodings=slinear_le:16:2:1,slinear_le:20:4:1,slinear_le:24:4:1
properties=full_duplex,independent
hiwat=8
mode=
rate=48000
precision=16
bps=2
msb=1
encoding=slinear_le
pause=1
active=0
block_size=960
play.channels=2
play.bytes=0
play.errors=0
record.channels=2
record.bytes=0
record.errors=0

and a dmesg:
OpenBSD 5.9-current (GENERIC.MP) #1905: Sun Mar  6 19:13:08 MST 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 7945580544 (7577MB)
avail mem = 7700443136 (7343MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x8be3f000 (32 entries)
bios0: vendor Hewlett-Packard version "M85 Ver. 01.32" date 07/20/2015
bios0: Hewlett-Packard HP EliteBook Folio 9480m
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC MCFG SSDT SSDT SLIC MSDM FPDT BGRT 
SSDT SSDT SSDT SSDT ASF! DMAR
acpi0: wakeup devices LANC(S5) EHC1(S3) XHC_(S3) PCIB(S5) RP03(S5) 
NIC_(S5) RP04(S5) WNIC(S5) HST1(S5)

acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz, 1995.65 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,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT

cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz, 1995.38 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,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT

cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz, 1995.38 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,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT

cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz, 1995.38 MHz
cpu3: 

Re: SIP Client

[Jiri B]

On Mon, Mar 07, 2016 at 05:12:58PM +0100, Solne Rapenne wrote:
> Hello,
> 
> Is there a SIP client working on OpenBSD ?
> I was using Jitsi or Ekiga but they don't seem working on OpenBSD.

...doesn't seem working is not very good issue report.

I'm not using Jitsi myself but usually java apps are shipped with
native libs. Try to find for *.so in Jitsi and check if they are
Linux native libs.

Another tip could be to get Jitsi source and grep for Linux or
FreeBSD in it, maybe you will find some conditional blocks where
they define support only for specific OS. Then, submit a diff or
just bug report for Jitsi.

j.

Re: SIP Client

[Mihai Popescu]

pjsua - audio only, works fine
baresip - audio and video, works fine

Both are in ports, I was using them with iptel.org as free provider.

Re: OpenBSD on AMD Embedded G-Series T40E APU?

[Chris Cappuccio]

Alan McKay [alan.mc...@gmail.com] wrote:
> Next question ... do they make them with 4 or more NIC ports?
> 
> I only see them with 3 ports on that site.

Nope. You might want a Supermicro X11SBA-LN4F or maybe Netgate's
RCC-VE 2440 if you need 4 ports.

Re: OpenBSD on AMD Embedded G-Series T40E APU?

[Alan McKay]

Next question ... do they make them with 4 or more NIC ports?

I only see them with 3 ports on that site.

Re: OpenBSD on AMD Embedded G-Series T40E APU?

[Karel Gardas]

I think Daniel just questioned support for e.g. ECC in the board's
BIOS providing details from manufacturer's website. There was no
single word or rumour about OpenBSD support on the board. Also since
manufacturer is honest and clearly notes that ECC is not *yet*
supported and yet it sells ECC equipped board, there is still hope
they are still working on their piece of software to get it right.

For OpenBSD ECC should be pretty transparent, shouldn't it?

On Mon, Mar 7, 2016 at 8:44 PM, Theo de Raadt  wrote:
>
> It is very strange behaviour to jump onto threads and create rumours
> that OpenBSD doesn't work on something.

Re: OpenBSD on AMD Embedded G-Series T40E APU?

[Noth]

On 03/07/16 20:07, Daniel Ouellet wrote:

On 3/7/16 1:55 PM, Theo de Raadt wrote:

On 3/7/16 12:43 PM, Noth wrote:

On 03/07/16 02:04, Theo de Raadt wrote:

Hey folks,

The website does not seem to have a lot of info on what CPUs are
supported.  I'm looking at this box for a home firewall with OpenBSD

http://www.corpshadow.biz/bizstore/apu1d-red-combo-kit-p-345.html?cPath=51


All of them work.


PC Engines APU models 1D & D4 and 2C2 & 2C4 are fully supported,
although you need -CURRENT or the upcoming 5.9 release to get the
correct identity of the thermal sensor. They're very good boxes for home
& SMB usage.

Not sure about the APU2b and c series yet.

The APU1* yes no issue, the 2* based on their own site it is not fully
working yet.

http://pcengines.ch/apu2b4.htm

But I do not have one for the 2* series to test, i have the previous
version.

Their site does show this clearly:

  BIOS is not feature complete yet, in particular -

• No boot from SD card.
• ECC not working yet.
• iPXE module not included yet.

So, this may need to be confirmed to be sure at 100%.

Do you have one of these boxes?

The original question was as to whether the cpu works.

Daniel, you are wrong.  The CPU works fine.  Furthermore, these
machines being talked about WORK COMPLETELY FINE.

Please stop the factless rumour mongering about hardware you don't have.

Not a rumor. That's why I asked as I said I didn't have one to test and
I can only go with what their site said. That's why I asked.

Sorry if that created confusion, but I am glad to know it is working.

I've beta tested the APU2 since November, and which features are 
complete, work flawlessly in OpenBSD.

Re: SIP Client

[Roderick]

Is there a SIP client working on OpenBSD ?


I used with OpenBSD 4.8:

http://www.pjsip.org/pjsua.htm

Perhaps still works.

Rodrigo

Re: OpenBSD on AMD Embedded G-Series T40E APU?

[Theo de Raadt]

> > http://www.corpshadow.biz/bizstore/apu1d-red-combo-kit-p-345.html?cPath=51
> >
>  All of them work.
> 
> >>> PC Engines APU models 1D & D4 and 2C2 & 2C4 are fully supported,
> >>> although you need -CURRENT or the upcoming 5.9 release to get the
> >>> correct identity of the thermal sensor. They're very good boxes for home
> >>> & SMB usage.
> >>
> >> Not sure about the APU2b and c series yet.
> >>
> >> The APU1* yes no issue, the 2* based on their own site it is not fully
> >> working yet.
> >>
> >> http://pcengines.ch/apu2b4.htm
> >>
> >> But I do not have one for the 2* series to test, i have the previous
> >> version.
> >>
> >> Their site does show this clearly:
> >>
> >>  BIOS is not feature complete yet, in particular -
> >>
> >> • No boot from SD card.
> >> • ECC not working yet.
> >> • iPXE module not included yet.
> >>
> >> So, this may need to be confirmed to be sure at 100%.
> >>
> >> Do you have one of these boxes?
> > 
> > The original question was as to whether the cpu works.
> > 
> > Daniel, you are wrong.  The CPU works fine.  Furthermore, these
> > machines being talked about WORK COMPLETELY FINE.
> > 
> > Please stop the factless rumour mongering about hardware you don't have.
> 
> Not a rumor. That's why I asked as I said I didn't have one to test and
> I can only go with what their site said. That's why I asked.
> 
> Sorry if that created confusion, but I am glad to know it is working.

It is very strange behaviour to jump onto threads and create rumours
that OpenBSD doesn't work on something.

Re: OpenBSD on AMD Embedded G-Series T40E APU?

[Theo de Raadt]

> On 3/7/16 12:43 PM, Noth wrote:
> > On 03/07/16 02:04, Theo de Raadt wrote:
> >>> Hey folks,
> >>>
> >>> The website does not seem to have a lot of info on what CPUs are
> >>> supported.  I'm looking at this box for a home firewall with OpenBSD
> >>>
> >>> http://www.corpshadow.biz/bizstore/apu1d-red-combo-kit-p-345.html?cPath=51
> >>>
> >> All of them work.
> >>
> > PC Engines APU models 1D & D4 and 2C2 & 2C4 are fully supported,
> > although you need -CURRENT or the upcoming 5.9 release to get the
> > correct identity of the thermal sensor. They're very good boxes for home
> > & SMB usage.
> 
> Not sure about the APU2b and c series yet.
> 
> The APU1* yes no issue, the 2* based on their own site it is not fully
> working yet.
> 
> http://pcengines.ch/apu2b4.htm
> 
> But I do not have one for the 2* series to test, i have the previous
> version.
> 
> Their site does show this clearly:
> 
>  BIOS is not feature complete yet, in particular -
> 
> • No boot from SD card.
> • ECC not working yet.
> • iPXE module not included yet.
> 
> So, this may need to be confirmed to be sure at 100%.
> 
> Do you have one of these boxes?

The original question was as to whether the cpu works.

Daniel, you are wrong.  The CPU works fine.  Furthermore, these
machines being talked about WORK COMPLETELY FINE.

Please stop the factless rumour mongering about hardware you don't have.

Re: OpenBSD on AMD Embedded G-Series T40E APU?

[Daniel Ouellet]

On 3/7/16 12:43 PM, Noth wrote:
> On 03/07/16 02:04, Theo de Raadt wrote:
>>> Hey folks,
>>>
>>> The website does not seem to have a lot of info on what CPUs are
>>> supported.  I'm looking at this box for a home firewall with OpenBSD
>>>
>>> http://www.corpshadow.biz/bizstore/apu1d-red-combo-kit-p-345.html?cPath=51
>>>
>> All of them work.
>>
> PC Engines APU models 1D & D4 and 2C2 & 2C4 are fully supported,
> although you need -CURRENT or the upcoming 5.9 release to get the
> correct identity of the thermal sensor. They're very good boxes for home
> & SMB usage.

Not sure about the APU2b and c series yet.

The APU1* yes no issue, the 2* based on their own site it is not fully
working yet.

http://pcengines.ch/apu2b4.htm

But I do not have one for the 2* series to test, i have the previous
version.

Their site does show this clearly:

 BIOS is not feature complete yet, in particular -

• No boot from SD card.
• ECC not working yet.
• iPXE module not included yet.

So, this may need to be confirmed to be sure at 100%.

Do you have one of these boxes?

Re: OpenBSD on AMD Embedded G-Series T40E APU?

[Daniel Ouellet]

On 3/7/16 1:55 PM, Theo de Raadt wrote:
>> On 3/7/16 12:43 PM, Noth wrote:
>>> On 03/07/16 02:04, Theo de Raadt wrote:
> Hey folks,
>
> The website does not seem to have a lot of info on what CPUs are
> supported.  I'm looking at this box for a home firewall with OpenBSD
>
> http://www.corpshadow.biz/bizstore/apu1d-red-combo-kit-p-345.html?cPath=51
>
 All of them work.

>>> PC Engines APU models 1D & D4 and 2C2 & 2C4 are fully supported,
>>> although you need -CURRENT or the upcoming 5.9 release to get the
>>> correct identity of the thermal sensor. They're very good boxes for home
>>> & SMB usage.
>>
>> Not sure about the APU2b and c series yet.
>>
>> The APU1* yes no issue, the 2* based on their own site it is not fully
>> working yet.
>>
>> http://pcengines.ch/apu2b4.htm
>>
>> But I do not have one for the 2* series to test, i have the previous
>> version.
>>
>> Their site does show this clearly:
>>
>>  BIOS is not feature complete yet, in particular -
>>
>> • No boot from SD card.
>> • ECC not working yet.
>> • iPXE module not included yet.
>>
>> So, this may need to be confirmed to be sure at 100%.
>>
>> Do you have one of these boxes?
> 
> The original question was as to whether the cpu works.
> 
> Daniel, you are wrong.  The CPU works fine.  Furthermore, these
> machines being talked about WORK COMPLETELY FINE.
> 
> Please stop the factless rumour mongering about hardware you don't have.

Not a rumor. That's why I asked as I said I didn't have one to test and
I can only go with what their site said. That's why I asked.

Sorry if that created confusion, but I am glad to know it is working.

patch for faq14 : newfs and raw/block device

[Daniel Jakots]

Hi,

>From newfs(8):
The special file should be a raw device, for example /dev/rsd0a; if a
relative path like sd0a is specified, the corresponding raw device is
used.

Right now:
# newfs /dev/sd5m
newfs: /dev/sd5m: block device
# newfs /dev/rsd5m
/dev/rsd5m: blah blah works as expected

So I guess it's either a relative path and a block device is fine, or
if you use the absolute path, you must pick the raw device.

Cheers,
Daniel

Index: faq/faq14.html
===
RCS file: /cvs/www/faq/faq14.html,v
retrieving revision 1.296
diff -u -p -r1.296 faq14.html
--- faq/faq14.html  28 Feb 2016 07:24:37 -  1.296
+++ faq/faq14.html  7 Mar 2016 17:55:39 -
@@ -917,7 +917,7 @@ Re-type passphrase:
 softraid0: CRYPTO volume attached as sd1
 # dd if=/dev/zero of=/dev/rsd1c bs=1m count=1
 # disklabel -E sd1 (create an "i" partition, see above for more info)
-# newfs /dev/sd1i
+# newfs /dev/rsd1i
 # mkdir -p /mnt/secretstuff
 # mount /dev/sd0i /mnt/secretstuff
 # mv planstotakeovertheworld.txt /mnt/secretstuff/

Re: OpenBSD on AMD Embedded G-Series T40E APU?

[Noth]

On 03/07/16 02:04, Theo de Raadt wrote:

Hey folks,

The website does not seem to have a lot of info on what CPUs are
supported.  I'm looking at this box for a home firewall with OpenBSD

http://www.corpshadow.biz/bizstore/apu1d-red-combo-kit-p-345.html?cPath=51

All of them work.

PC Engines APU models 1D & D4 and 2C2 & 2C4 are fully supported, 
although you need -CURRENT or the upcoming 5.9 release to get the 
correct identity of the thermal sensor. They're very good boxes for home 
& SMB usage.


Cheers,

Noth

Re: {obsd,pf}-faq.txt are greatly missed

[Ingo Schwarze]

Hi,

Vasily Kolobkov wrote on Mon, Mar 07, 2016 at 05:20:56PM +0200:

> as of not long ago the plain text versions of the faqs went missing 
> from http://www.openbsd.org/faq/{obsd,pf}-faq.txt
> 
> wonder if that's for good?

Yes.  They were deleted to reduce maintenance burden and to avoid
the risk of getting outdated.  We'd rather have developers focus
on improving the system and the authoritative documentation than
maintaining multiple copies of auxiliary documentation.

> those where really handy at times.

A package like converters/html2text should to the trick for you
whenever you need a plain text version.

Yours,
  Ingo

Re: BGPD not adding routes

[Matt Schwartz]

Thank you much, Claudio! That was the ticket. I had put my depend on mpe0
in the wrong place. I was mostly using your mpls example. Dumb questions:
Why do you not create a default route in rdomain 1 on the 2nd PE in your
mpls example network? Why do you not have network 0.0.0.0/0 on the 2nd PE?
Thanks for helping me with my understanding gaps.

Matt

SIP Client

[Solène Rapenne]

Hello,

Is there a SIP client working on OpenBSD ?
I was using Jitsi or Ekiga but they don't seem working on OpenBSD.

Kind regards

{obsd,pf}-faq.txt are greatly missed

[Vasily Kolobkov]

as of not long ago the plain text versions of the faqs went missing 
from http://www.openbsd.org/faq/{obsd,pf}-faq.txt

wonder if that's for good? those where really handy at times.

Re: OT: Looking for email host with qmail like minus-addressing for custom domain

[Craig Skinner]

On 2016-03-05 Sat 21:56 PM |, Stuart Henderson wrote:
> 
> Besides qmail, this is easy to setup with Postfix (my preferred option
> for these)

Default:
$ postconf -d recipient_delimiter
recipient_delimiter =

Set this to your favourite character in /etc/postfix/main.cf:
$ postconf recipient_delimiter
recipient_delimiter = +

Cheers.
-- 
It's hard to drive at the limit,
but it's harder to know where the limits are.
-- Stirling Moss

mirror port, span

[Kapetanakis Giannis]

Hi,

I'd like to mirror my ext_if which has 802.1q VLANs on to a remote 
server for traffic analysis.


I've created bridge0 with
add $ext_physical_int
addspan $mirror_port

which seems to work just fine :)

is that all? anything else I should have in mind?
How would this affect box performance on more that gigabit traffic?

regards,

G

Supermicro X11SSL-F freezes probing USB 3

[Paul B. Henson]

I just put together a new server with a Supermicro X11SSL-F motherboard
and a Xeon E3-1240L v5 processor, and was trying to install openbsd 5.8
on it. The install cd freezes while booting after it probes the USB 3
devices:

>>> xhci probe won
xhci0 at pci0 dev 20 function 0 "Intel 100 Series xHCI" rev 0x31: msi
>>> probing for usb*
>>> usb probe returned 1
>>> usb probe won
usb0 at xhci0: USB revision 3.0
>>> probing for uhub*
>>> uhub probe returned 10
>>> uhub probe won
uhub0 at usb0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
[system freezes here]


I also tried the latest snapshot install cd, same problem. If I disable
xhci, the installer boots successfully, although I haven't actually
tried installing yet. I don't really need usb on this box, so I'm not
really concerned if it's not going to work. It's not going into
production for a few weeks though, so if anybody's interested in looking
at why it's broken I could provide further details or test possible
fixes. Here's a dmesg of the snapshot install kernel booted without
xhci:

OpenBSD 5.9-current (RAMDISK_CD) #1737: Sun Mar  6 19:18:13 MST 2016
   
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
   
real mem = 16976416768 (16189MB)
   
avail mem = 16460062720 (15697MB)   
   
User Kernel Config  
   
UKC> do\^H \^Hiso\^H \^Hable xhci   
   
 98 xhci* disabled  
   
 UKC> quit  

 Continuing...  

 mainbus0 at root   

 bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7fb95000 (59 entries)   

 bios0: vendor American Megatrends Inc. version "1.0b" date
 12/29/2015  
 bios0: Supermicro Super Server 

 acpi0 at bios0: rev 2  

 acpi0: tables DSDT FACP APIC FPDT FIDT SPMI MCFG HPET SSDT LPIT
 SSDT SSDT SSDT DBGP DBG2 SSDT SSDT UEFI SSDT DMAR EINJ ERST BERT
 HEST 
 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat   

 cpu0 at mainbus0: apid 0 (boot processor)  

 cpu0: Intel(R) Xeon(R) CPU E3-1240L v5 @ 2.10GHz, 2100.73 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,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT

 cpu0: 256KB 64b/line 8-way L2 cache

 cpu0: apic clock running at 24MHz  

 cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1, IBE   

 cpu at mainbus0: not configured

 cpu at mainbus0: not configured

 cpu at mainbus0: not configured

 cpu at mainbus0: not configured

 cpu at mainbus0: not configured

 cpu at mainbus0: not configured

 cpu at mainbus0: not configured

 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins 

 acpiprt0 at acpi0: bus 0 (PCI0)

 acpiprt1 at acpi0: bus 1 (PEG0)

 acpiprt2 at acpi0: bus -1 (PEG1)   

 acpiprt3 at acpi0: bus -1 (PEG2)   

 acpiprt4 at acpi0: bus 2 (RP09)

 acpiprt5 at acpi0: bus 3 (RP10)  

Re: Why?Add vmm(4). It is disabled by default.

[Peter Hessler]

On 2016 Mar 06 (Sun) at 04:52:29 + (+), freeu...@ruggedinbox.com wrote:
:Add vmm(4). It is disabled by default.
:How do I enable the /dev/vmm0 on OpenBSD5.9?
:
:config -e -f /bsd
:config -e -f /bsd.mp
:
:now we could comment out any line and compile GENERIC|GENERIC.MP kernel.
:

vmm(4) is not yet ready to be enabled.  There has been quite a bit of
work done, but there are still a few things pending.

Once vmm(4) is considered ready, it will be enabled.


-- 
When all other means of communication fail, try words.