Re: Potential grep bug?

[Demi M. Obenour]

On 2020-06-23 22:29, Jordan Geoghegan wrote:
> Hello,
> 
> I was working on a couple POSIX regular expressions to search for and 
> validate IPv4 and IPv6 addresses with optional CIDR blocks, and encountered 
> some strange behaviour from the base system grep.
> 
> I wanted to validate my regex against a list of every valid IPv4 address, so 
> I generated a list with a zsh 1 liner:
> 
>  for i in {0..255}; do; echo $i.{0..255}.{0..255}.{0..255} ; done | tr 
> '[:space:]' '\n' > IPv4.txt
> 
> My intentions were to test the regex by running it with 'grep -c' to confirm 
> there was indeed 2^32 addresses matched, and I also wanted to benchmark and 
> compare performance between BSD grep, GNU grep and ripgrep. The command I 
> used:
> 
>    grep -Eoc 
> "((25[0-5]|(2[0-4]|1{0,1}[[:digit:]]){0,1}[[:digit:]])\.){3,3}(25[0-5]|(2[0-4]|1{0,1}[[:digit:]]){0,1}[[:digit:]])(/[1-9]|/[1-2][[:digit:]]|/3[0-2])?"
> 
> My findings were surprising. Both GNU grep and ripgrep were able get through 
> the file in roughly 10 and 20 minutes respectively, whereas the base system 
> grep took over 20 hours! What interested me the most was that the base system 
> grep when run with '-c' returned '0' for match count. It seems that 'grep -c' 
> will have its counter overflow if there are more than 2^32-1 matches 
> (4294967295) and then the counter will start counting from zero again for 
> further matches.

Does OpenBSD use an NFA/DFA regular expression implementation, or a
backtracking one?  If it uses the latter, then your regex is probably
causing catastrophic backtracking.

> Regards,
> 
> Jordan

Sincerely,

Demi



signature.asc
Description: OpenPGP digital signature

Re: Issue with relayd and redirections

[Gabri Tofano]

Here:

LAB1-LB1$ relayctl sh sum
Id  TypeName   Avlblty Status
1   redirecthttp   active
1   table   web_servers:80 active (1 hosts)
1   host172.16.101.31  4.87%   up
2   table   nc_servers:80  active (1 hosts)
2   host172.16.101.32  4.86%   up
2   redirecthttps  down
3   table   web_servers:443empty
3   host172.16.101.31  0.00%   down
4   table   nc_servers:443 empty
4   host172.16.101.32  0.00%   down

The low availability is due too the web servers were turned off.

Thanks!

On 2020-07-10 17:41, Sebastian Benoit wrote:

Gabri Tofano(ga...@tofanos.com) on 2020.07.07 15:38:17 -0400:

When using redirections, no listening ports are open (I guess due to
relayd using pf nat rules)


correct


and I'm unable to reach both backend servers.


show the output of "relayctl sh sum".

Re: Unbound Configuration

[Ken.Hendrickson]

--- I said:
> Thinking that an absolutely empty unbound.conf file would be the
> simplest, I tried it.  It doesn't work.

Nope.  That is not true.
I don't know how it happened, but my box wound up without a default route.

An absolutely empty unbound.conf works just fine.

Thanks,
Ken



  

CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of 
the intended recipient and may contain material that is proprietary, 
confidential, privileged or otherwise legally protected or restricted under 
applicable government laws. Any review, disclosure, distributing or other use 
without expressed permission of the sender is strictly prohibited. If you are 
not the intended recipient, please contact the sender and delete all copies 
without reading, printing, or saving.

Re: sysupgrade failure due to boot.conf

[Brian Brombacher]

> On Jul 10, 2020, at 7:31 PM, Alfred Morgan  wrote:
> 
> 
>> 
>> You claimed sysupgrade does this.
>> sysupgrade does nothing like that.  It placed a /bsd.upgrade file, and
> that is the end of the story.
>> You told boot (via commands in boot.conf) to do something, so it did,
> before discovering the file.
> 
> Theo,
> When I mentioned sysupgrade I was referring to the full sysupgrade
> procedure all the way through to completion. Sorry for not being specific
> enough. Thank you, you brought focus to boot which is really where my
> suggestion will be focused on.
> 
> So, how can I explicitly tell boot to act normally to boot /bsd.upgrade and
> if that doesn't exist then boot /bsd? I would expect # echo boot >
> /etc/boot.conf to do just that.
> 

(echo boot /bsd.upgrade; echo boot) > /etc/boot.conf

Re: Issue with relayd and redirections

[Brian Brombacher]

> On Jul 10, 2020, at 9:15 PM, Gabri Tofano  wrote:
> 
> Here:
> 
> LAB1-LB1$ relayctl sh sum
> Id  TypeName   Avlblty Status
> 1   redirecthttp   active
> 1   table   web_servers:80 active (1 hosts)
> 1   host172.16.101.31  4.87%   up
> 2   table   nc_servers:80  active (1 hosts)
> 2   host172.16.101.32  4.86%   up
> 2   redirecthttps  down
> 3   table   web_servers:443empty
> 3   host172.16.101.31  0.00%   down
> 4   table   nc_servers:443 empty
> 4   host172.16.101.32  0.00%   down
> 

Does http work with redirects?  It wasn’t clear if it did or not in your first 
post.  Indications from your pf anchor rules and the down status above, and the 
check http attribute on the https forward to directives tell me relayd isn’t 
liking your check http configuration for port 443.

Start by switching to check icmp or check tcp or something else, see if it 
works, unless you can fix the check http based on logs or otherwise.

> The low availability is due too the web servers were turned off.
> 
> Thanks!
> 
>> On 2020-07-10 17:41, Sebastian Benoit wrote:
>> Gabri Tofano(ga...@tofanos.com) on 2020.07.07 15:38:17 -0400:
>>> When using redirections, no listening ports are open (I guess due to
>>> relayd using pf nat rules)
>> correct
>>> and I'm unable to reach both backend servers.
>> show the output of "relayctl sh sum".
> 

Re: Unbound Configuration

[Ken.Hendrickson]

I said:
> Thinking that an absolutely empty unbound.conf file
> would be the simplest, I tried it.  It doesn't work.

However, unbound-checkconf likes it just fine.

$ unbound-checkconf /var/unbound/etc/unbound.conf
unbound-checkconf: no errors in /var/unbound/etc/unbound.conf



  

CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of 
the intended recipient and may contain material that is proprietary, 
confidential, privileged or otherwise legally protected or restricted under 
applicable government laws. Any review, disclosure, distributing or other use 
without expressed permission of the sender is strictly prohibited. If you are 
not the intended recipient, please contact the sender and delete all copies 
without reading, printing, or saving.

Re: Unbound Configuration

[Ken.Hendrickson]

--- I asked:
> What I would like to do now is make the *simplest
> possible* unbound.conf file and get it working.

Thinking that an absolutely empty unbound.conf file
would be the simplest, I tried it.  It doesn't work.

Can anybody help me with the simplest possible
unbound.conf file???

Thanks,
Ken


  

CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of 
the intended recipient and may contain material that is proprietary, 
confidential, privileged or otherwise legally protected or restricted under 
applicable government laws. Any review, disclosure, distributing or other use 
without expressed permission of the sender is strictly prohibited. If you are 
not the intended recipient, please contact the sender and delete all copies 
without reading, printing, or saving.

Unbound Configuration

[Ken.Hendrickson]

Thanks for all of the help so far, but I am completely failing.
Nothing I have tried will make unbound work.

What I would like to do now is make the *simplest possible*
unbound.conf file and get it working.

Then I want to add more and more stuff, to get the point I want.

I have searched for such a tutorial on the internet, but can't find
one.

Can anybody help me out with the *simplest possible* unbound.conf file,
just to get it working???

Thanks,
Ken



  

CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of 
the intended recipient and may contain material that is proprietary, 
confidential, privileged or otherwise legally protected or restricted under 
applicable government laws. Any review, disclosure, distributing or other use 
without expressed permission of the sender is strictly prohibited. If you are 
not the intended recipient, please contact the sender and delete all copies 
without reading, printing, or saving.

Re: Unbound Configuration

[Steve Litt]

On Fri, 10 Jul 2020 21:29:02 +
 wrote:

> --- I asked:
> > What I would like to do now is make the *simplest
> > possible* unbound.conf file and get it working.  
> 
> Thinking that an absolutely empty unbound.conf file
> would be the simplest, I tried it.  It doesn't work.
> 
> Can anybody help me with the simplest possible
> unbound.conf file???

You can make an empty unbound.conf with instructions at:

http://troubleshooters.com/linux/unbound_nsd/unbound.htm#helloworld

You can slowly transition to a real, practical unbound.conf by
following the instructions below that section.

SteveT

Steve Litt 
May 2020 featured book: Troubleshooting Techniques
 of the Successful Technologist
http://www.troubleshooters.com/techniques

Re: msyscall error during boot

[mabi]

‐‐‐ Original Message ‐‐‐
On Friday, July 10, 2020 10:18 PM, Jurjen Oskam  wrote:

> Did you update your packages? I ran into the same issue when I forgot to 
> update
> the packages after upgrading the system.

Yes, I did run a "pkg_add -u". I have found more details and actually it is the 
"rake" command, part of the ruby-2.5.8 which outputs this error message at boot 
because I am starting a Ruby rack web server for an API using "rake" command in 
/etc/rc.local.

Re: sysupgrade failure due to boot.conf

[Jordan Geoghegan]

On 2020-07-10 15:37, Alfred Morgan wrote:

Please, I have had this problem for several versions now and it still isn't
working right.
I have this on all three of my servers:
echo boot > /etc/boot.conf

I have this boot.conf because openbsd fails to boot (on all three servers)
because it hangs on the boot> prompt because of some ghost input (I have no
keyboard plugged in). So I was told that putting "boot" in my boot.conf
would solve the problem and it did the trick. BUT, sysupgrade now fails
trying to upgrade 6.6 -> 6.7. So what can I put in my boot.conf that will
ignore the ghost input in the boot> prompt and allow sysupgrade to succeed?

I feel that it's a bug in sysupgrade that it doesn't behave the same having
"boot" in the boot.conf. Any help?

-alfred



Relevant xkcd? https://xkcd.com/1172/

Re: sysupgrade failure due to boot.conf

[Theo de Raadt]

Alfred Morgan  wrote:

> > You claimed sysupgrade does this.
> > sysupgrade does nothing like that.  It placed a /bsd.upgrade file, and
> that is the end of the story.
> > You told boot (via commands in boot.conf) to do something, so it did,
> before discovering the file.
> 
> Theo,
> When I mentioned sysupgrade I was referring to the full sysupgrade
> procedure all the way through to completion. Sorry for not being specific
> enough. Thank you, you brought focus to boot which is really where my
> suggestion will be focused on.
> 
> So, how can I explicitly tell boot to act normally to boot /bsd.upgrade and
> if that doesn't exist then boot /bsd? I would expect # echo boot >
> /etc/boot.conf to do just that.

The code is in sys/stand/boot.c

devboot(bootdev, cmd.bootdev);
strlcpy(cmd.image, kernelfile, sizeof(cmd.image));
cmd.boothowto = 0;
cmd.conf = "/etc/boot.conf";
cmd.addr = (void *)DEFAULT_KERNEL_ADDRESS;
cmd.timeout = boottimeout;

if (upgrade()) {
strlcpy(cmd.image, "/bsd.upgrade", sizeof(cmd.image));
printf("upgrade detected: switching to %s\n", cmd.image);
isupgrade = 1;
}

st = read_conf();

Figure out how to build and install.  It is not hard to test.

Re: sysupgrade failure due to boot.conf

[Alfred Morgan]

> You claimed sysupgrade does this.
> sysupgrade does nothing like that.  It placed a /bsd.upgrade file, and
that is the end of the story.
> You told boot (via commands in boot.conf) to do something, so it did,
before discovering the file.

Theo,
When I mentioned sysupgrade I was referring to the full sysupgrade
procedure all the way through to completion. Sorry for not being specific
enough. Thank you, you brought focus to boot which is really where my
suggestion will be focused on.

So, how can I explicitly tell boot to act normally to boot /bsd.upgrade and
if that doesn't exist then boot /bsd? I would expect # echo boot >
/etc/boot.conf to do just that.

-alfred

Re: sysupgrade failure due to boot.conf

[Theo de Raadt]

Alfred Morgan  wrote:

> Theo, right on point and I agree with the workarounds statement. I would love 
> to send
> my server in for someone to look at it. I have 3 different machines (2 are 
> similar) all
> experiencing the same problem with the ghost keyboard at the boot prompt.
> 
> What my issue is that the bootloader seems to act differently if the prompt 
> times out
> or if the "boot" command is given. I would expect the boot command with no 
> arguments to
> do the same thing as a timeout at the prompt.
> 
> the boot(8) man page says:
> "prompt, which means you are in interactive mode and may enter commands. If 
> you do not,
> boot will proceed to load the kernel with the current parameters after the 
> timeout
> period has expired."
> 
> and boot(8) also says:
> "If device or image are omitted, values from boot variables will be used."
> 
> (I find a discrepancy between "current parameters" and "boot variables" but I 
> take it
> to mean the same thing.)
> 
> sysupgrade(8) says:
> "The bootloader will automatically choose /bsd.upgrade"
> 
> I'm either missing something or one of these statements doesn't seem to be 
> entirely
> true. I feel stuck with no options.

You claimed sysupgrade does this.

sysupgrade does nothing like that.  It placed a /bsd.upgrade file, and that
is the end of the story.

You told boot (via commands in boot.conf) to do something, so it did, before
discovering the file.

Re: sysupgrade failure due to boot.conf

[Alfred Morgan]

Theo, right on point and I agree with the workarounds statement. I would
love to send my server in for someone to look at it. I have 3 different
machines (2 are similar) all experiencing the same problem with the ghost
keyboard at the boot prompt.

What my issue is that the bootloader seems to act differently if the prompt
times out or if the "boot" command is given. I would expect the boot
command with no arguments to do the same thing as a timeout at the prompt.

the boot(8) man page says:
"prompt, which means you are in interactive mode and may enter commands. If
you do not, boot will proceed to load the kernel with the current
parameters after the timeout period has expired."

and boot(8) also says:
"If device or image are omitted, values from boot variables will be used."

(I find a discrepancy between "current parameters" and "boot variables" but
I take it to mean the same thing.)

sysupgrade(8) says:
"The bootloader will automatically choose /bsd.upgrade"

I'm either missing something or one of these statements doesn't seem to be
entirely true. I feel stuck with no options.

-alfred


On Fri, Jul 10, 2020 at 3:43 PM Theo de Raadt  wrote:

> Alfred Morgan  wrote:
>
> > Please, I have had this problem for several versions now and it still
> isn't
> > working right.
> > I have this on all three of my servers:
> > echo boot > /etc/boot.conf
> >
> > I have this boot.conf because openbsd fails to boot (on all three
> servers)
> > because it hangs on the boot> prompt because of some ghost input (I have
> no
> > keyboard plugged in). So I was told that putting "boot" in my boot.conf
> > would solve the problem and it did the trick. BUT, sysupgrade now fails
> > trying to upgrade 6.6 -> 6.7. So what can I put in my boot.conf that will
> > ignore the ghost input in the boot> prompt and allow sysupgrade to
> succeed?
> >
> > I feel that it's a bug in sysupgrade that it doesn't behave the same
> having
> > "boot" in the boot.conf. Any help?
>
> sysupgrade has nothing to do with this.  the bootblocks decide to do
> bsd.upgrade
> instead, but if you've supplied it commands it does that instead.
>
> everything is working *precisely* as designed.
>
> As to what makes your keyboard controller do something wrong?  That's
> the real issue and needs a fix (who knows what), so the workaround is
> causing you harm.
>
> But that's not really news, is it?  There is always a cost associated
> with workarounds
>

Re: Unbound Configuration

[Daniel Jakots]

On Fri, 10 Jul 2020 21:21:00 +, 
wrote:

> Can anybody help me out with the *simplest possible* unbound.conf
> file, just to get it working???

The default config should be fine.

Also posting to multiple mailing lists at the same time is considered a
bad practice.

Cheers,
Daniel

Re: sysupgrade failure due to boot.conf

[Theo de Raadt]

Alfred Morgan  wrote:

> Please, I have had this problem for several versions now and it still isn't
> working right.
> I have this on all three of my servers:
> echo boot > /etc/boot.conf
> 
> I have this boot.conf because openbsd fails to boot (on all three servers)
> because it hangs on the boot> prompt because of some ghost input (I have no
> keyboard plugged in). So I was told that putting "boot" in my boot.conf
> would solve the problem and it did the trick. BUT, sysupgrade now fails
> trying to upgrade 6.6 -> 6.7. So what can I put in my boot.conf that will
> ignore the ghost input in the boot> prompt and allow sysupgrade to succeed?
> 
> I feel that it's a bug in sysupgrade that it doesn't behave the same having
> "boot" in the boot.conf. Any help?

sysupgrade has nothing to do with this.  the bootblocks decide to do bsd.upgrade
instead, but if you've supplied it commands it does that instead.

everything is working *precisely* as designed.

As to what makes your keyboard controller do something wrong?  That's
the real issue and needs a fix (who knows what), so the workaround is
causing you harm.

But that's not really news, is it?  There is always a cost associated
with workarounds

Re: supermicro - A2SDV-8C-LN8F

[Jonathan Matthew]

On Sat, Jul 11, 2020 at 12:13:34AM +0200, Hrvoje Popovski wrote:
> Hi all,
> 
> does anyone have experience or dmesg of this motherboard
> https://www.supermicro.com/en/products/motherboard/A2SDV-8C-LN8F
> 
> is it stable? i'm most interested in network performance and network
> cards. in motherboard manual i couldn't find what "Quad LAN with Intel®
> C3000 SoC" means ?  is it i350 em(4)?

I can't comment on anything else as I don't have any hardware like this,
but that'll be X553 ix(4), supported since 6.7.

sysupgrade failure due to boot.conf

[Alfred Morgan]

Please, I have had this problem for several versions now and it still isn't
working right.
I have this on all three of my servers:
echo boot > /etc/boot.conf

I have this boot.conf because openbsd fails to boot (on all three servers)
because it hangs on the boot> prompt because of some ghost input (I have no
keyboard plugged in). So I was told that putting "boot" in my boot.conf
would solve the problem and it did the trick. BUT, sysupgrade now fails
trying to upgrade 6.6 -> 6.7. So what can I put in my boot.conf that will
ignore the ghost input in the boot> prompt and allow sysupgrade to succeed?

I feel that it's a bug in sysupgrade that it doesn't behave the same having
"boot" in the boot.conf. Any help?

-alfred

supermicro - A2SDV-8C-LN8F

[Hrvoje Popovski]

Hi all,

does anyone have experience or dmesg of this motherboard
https://www.supermicro.com/en/products/motherboard/A2SDV-8C-LN8F

is it stable? i'm most interested in network performance and network
cards. in motherboard manual i couldn't find what "Quad LAN with Intel®
C3000 SoC" means ?  is it i350 em(4)?


Thank you ..

Re: Issue with relayd and redirections

[Sebastian Benoit]

Gabri Tofano(ga...@tofanos.com) on 2020.07.07 15:38:17 -0400:
> When using redirections, no listening ports are open (I guess due to
> relayd using pf nat rules)

correct

> and I'm unable to reach both backend servers.

show the output of "relayctl sh sum".

Re: Unbound Configuration

[Jordan Geoghegan]

On 2020-07-10 14:29, ken.hendrick...@l3harris.com wrote:

--- I asked:

What I would like to do now is make the *simplest
possible* unbound.conf file and get it working.

Thinking that an absolutely empty unbound.conf file
would be the simplest, I tried it.  It doesn't work.

Can anybody help me with the simplest possible
unbound.conf file???

Thanks,
Ken


   


CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of 
the intended recipient and may contain material that is proprietary, 
confidential, privileged or otherwise legally protected or restricted under 
applicable government laws. Any review, disclosure, distributing or other use 
without expressed permission of the sender is strictly prohibited. If you are 
not the intended recipient, please contact the sender and delete all copies 
without reading, printing, or saving.




This FAQ page should be a useful starting point:

https://www.openbsd.org/faq/pf/example1.html#dns

Re: Installation in a Xen guest (pvgrub)

[Demi M. Obenour]

On 2020-07-09 05:06, Markus Kolb wrote:
> Hi,
> 
> is there a possibility to install/boot OpenBSD in a Xen guest which is booted 
> by pvgrub1 or pvgrub2? The pvgrub is configured to use a /boot/grub/grub.cfg 
> of the guest in the 1st partition.
> 
> In a non-Xen-grub there is a bsd-module which can boot the installer bsd.rd, 
> but this bsd-module is not available in the xenhost-builds of grub.
> There is also no chain-module for chainloader configs.
> 
> Any ideas?
> 
> Thanks
> Markus

For me, OpenBSD boots fine in HVM mode (with an I/O emulator).
I have not tried PVH mode and would not expect it to work.  PV mode
definitely won’t work, and should be avoided anyway for both security
and performance reasons.

Is HVM mode okay, or do you need PVH?

Sincerely,

Demi

Re: Missing description of the default proposals in iked.conf

[Tobias Heider]

On Fri, Jul 10, 2020 at 01:17:38PM +0300, Антон Касимов wrote:
> The descriptions of the ikesa and childsa options contain the following
> statements:
> 
> Possible values for auth, enc, prf, group, and the* default proposals* are
> described below in CRYPTO TRANSFORMS. If omitted, iked(8) will use the
> default proposals for the IKEv2 protocol.
> Possible values for auth, enc, group, esn, and the *default proposals* are
> described below in CRYPTO TRANSFORMS. If omitted, iked(8) will use the
> default proposals for the ESP or AH protocol.
> 
> 
> But CRYPTO TRANSFORMS has no description for default proposals.
> 

Thanks for noticing. I just added the info to the man page.

Re: msyscall error during boot

[Jurjen Oskam]

On Thu, Jul 09, 2020 at 06:38:01AM +, mabi wrote:

> I just upgraded one of my vmd virtual machine from OpenBSD 6.6 to 6.7 using 
> sysupgrade and noticed a new msyscall error message I have never seen before 
> during reboot as you can see below:
> 
> ...
> preserving editor files.
> starting network daemons: sshd smtpd httpd.
> starting package daemons: dovecot postgresql php72_fpm netsnmpd.
> msyscall a35ee0ce000 a3000 error
> msyscall a35187dd000 a5000 error
> starting local daemons: cron.
> Thu Jul  9 08:07:15 CEST 2020
> 
> Any ideas where this could come from? and if it is bad?

Did you update your packages? I ran into the same issue when I forgot to update
the packages after upgrading the system.

Regards,

Jurjen

iXorg / xenodm logs fill with errors: "_XSERVTransSocketUNIXAccept: accept() failed"

[Why 42? The lists account.]

Hi All,

I'm running 6.7 snapshot (6.7 GENERIC.MP#302 amd64) as my main desktop
with Xfce.

Two or three times now I've noticed that these two files in /var/log have
become unexpectedly huge:
> mjoelnir:log # du -sh xenodm.log Xorg.0.log
> 378M  xenodm.log
> 487M  Xorg.0.log

Apart from the usual startup/initialisation messages (below) Xorg.0.log
contains many many instances of this message:
> mjoelnir:log # grep -c '_XSERVTransSocketUNIXAccept: accept() failed' 
> Xorg.0.log  8800235

The same message is logged to xenodm.log i.e.
> mjoelnir:log # grep -c '_XSERVTransSocketUNIXAccept: accept() failed' 
> xenodm.log 
> 8800235

I don't know why or when this occurs, but I have the impression it occurs
when coming out of lockscreen i.e. when I return to my computer and enter
my password. The whole desktop becomes unresponsive for tens of seconds
at this point, probably busy writing those log messages ...

I assume that there must be some an issue with xenodm or the X11
subsystem. A search on the Internet only resulted in a couple of hits,
from 2010 and 2012, at least one of which was related to the Cygwin
platform - so quite different. I ran OpenBSD 6.6 for several months on
this system (Intel NUC 8i5) and didn't notice this issue.

The only other video error I have noticed is this one in the console or
output of dmesg:
> drm:pid54673:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential atomic 
> update failure on pipe A

I don't know if that is related.

Any thoughts? Anyone else experienced anything similar?


FYI: Excerpt from Xorg.0.log
> [26.343] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
> (Operation not permitted)
> Check that you have set 'machdep.allowaperture=1'
> in /etc/sysctl.conf and reboot your machine
> refer to xf86(4) for details
> [26.343]linear framebuffer access unavailable
> [26.373] (--) Using wscons driver on /dev/ttyC4
> [26.386] 
> X.Org X Server 1.20.8
> X Protocol Version 11, Revision 0
> [26.386] Build Operating System: OpenBSD 6.7 amd64 
> [26.386] Current Operating System: OpenBSD mjoelnir.fritz.box 6.7 
> GENERIC.MP#273 amd64
> [26.386] Build Date: 15 June 2020  07:46:53PM
> [26.386]  
> [26.386] Current version of pixman: 0.38.4
> [26.386]Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> [26.386] Markers: (--) probed, (**) from config file, (==) default 
> setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [26.386] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 16 20:04:24 
> 2020
> [26.388] (==) Using system config directory 
> "/usr/X11R6/share/X11/xorg.conf.d"
> [26.389] (==) No Layout section.  Using the first Screen section.
> [26.389] (==) No screen section available. Using defaults.
> [26.389] (**) |-->Screen "Default Screen Section" (0)
> [26.389] (**) |   |-->Monitor ""
> [26.390] (==) No monitor specified for screen "Default Screen Section".
> Using a default monitor configuration.
> [26.390] (==) Automatically adding devices
> [26.390] (==) Automatically enabling devices
> [26.390] (==) Not automatically adding GPU devices
> [26.390] (==) Max clients allowed: 256, resource mask: 0x1f
> [26.394] (==) FontPath set to:
> /usr/X11R6/lib/X11/fonts/misc/,
> /usr/X11R6/lib/X11/fonts/TTF/,
> /usr/X11R6/lib/X11/fonts/OTF/,
> /usr/X11R6/lib/X11/fonts/Type1/,
> /usr/X11R6/lib/X11/fonts/100dpi/,
> /usr/X11R6/lib/X11/fonts/75dpi/
> [26.394] (==) ModulePath set to "/usr/X11R6/lib/modules"
> [26.394] (II) The server relies on wscons to provide the list of input 
> devices.
> If no devices become available, reconfigure wscons or disable 
> AutoAddDevices.
> [26.394] (II) Loader magic: 0xeed1a3f9000
> [26.394] (II) Module ABI versions:
> [26.394]X.Org ANSI C Emulation: 0.4
> [26.394]X.Org Video Driver: 24.1
> [26.394]X.Org XInput driver : 24.1
> [26.394]X.Org Server Extension : 10.0
> [26.395] (--) PCI:*(0@0:2:0) 8086:3ea5:8086:2074 rev 1, Mem @ 
> 0xc000/16777216, 0x8000/1073741824, I/O @ 0x4000/64
> [26.395] (II) LoadModule: "glx"
> [26.396] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
> [26.405] (II) Module glx: vendor="X.Org Foundation"
> [26.405]compiled for 1.20.8, module version = 1.0.0
> [26.405]ABI class: X.Org Server Extension, version 10.0
> [26.405] (==) Matched modesetting as autoconfigured driver 0
> [26.405] (==) Assigned the driver to the xf86ConfigLayout
> [26.405] (II) LoadModule: "modesetting"
> [26.405] (II) Loading /usr/X11R6/lib/modules/drivers/modesetting_drv.so
> [26.406] (II) Module modesetting: vendor="X.Org Foundation"
> [26.406]compiled for 

Enterprise Unified Communications

[B R I D G E Communications]

[https://www.bridgeoc.com/banners/email-pk3.png]



Attendant Console Solutions for Cisco, RingCentral, Avaya, AT, TELUS, BT and 
Microsoft



RingCentral



The Bridge Cloud Suite for RingCentral includes our flagship attendant console 
solution Bridge Operator Console. Bridge Operator Console is the premiere tool 
for enhancing the productivity of your receptionists and operators. Bridge 
Operator Console is also available for RC partners including Avaya, AT, 
TELUS, and BT.



[header 
image]

[header 
image]



Cisco



The Bridge Cloud Suite for Cisco includes our flagship attendant console 
solution Bridge Operator Console. Bridge Operator Console is the premiere tool 
for enhancing the productivity of your receptionists and operators.



[header 
image]

The Bridge Cloud Suite for Cisco includes our flagship attendant console 
solution Bridge Operator Console. Bridge Operator Console is the premiere tool 
for enhancing the productivity of your receptionists and operators. We also 
have a legacy desktop version for Windows desktop users.

[header image]



Microsoft



The Bridge Operator Console for Skype for Business is the premiere enterprise 
attendant console for Microsoft UC.



[header 
image]



[header image]

[header image]

[header image]

Manage Email 
Subscription

Bridge Communications
1830 52nd St S
Fargo, ND 58103
+17012124797

Re: Unbound Problems (Reverse Direction)

[Brian Brombacher]

Use these directives also in unbound (see the pattern and choose what you 
need, like 24.172.IN-ADDR.ARPA, to cover your 172.24.* reverse.

local-zone: "168.192.IN-ADDR.ARPA" nodefault
local-zone: "16.172.IN-ADDR.ARPA" nodefault
local-zone: "17.172.IN-ADDR.ARPA" nodefault
local-zone: "18.172.IN-ADDR.ARPA" nodefault
local-zone: "19.172.IN-ADDR.ARPA" nodefault
local-zone: "10.IN-ADDR.ARPA" nodefault
local-zone: "d.f.IP6.ARPA" nodefault


> On Jul 10, 2020, at 2:22 AM, Frank Habicht  wrote:
> 
> Hi,
> 
>>> On 09/07/2020 20:44, ken.hendrick...@l3harris.com wrote:
>> stub-zone:
>>   name:  30.24.172.in-addr.arpa.
>  good
>>   stub-addr: 127.0.0.1@53053
>> stub-zone:
>>   name:  2.168.192.in-arpa.arpa.
>  typo
>>   stub-addr: 127.0.0.1@53053
>> stub-zone:
>>   name:  224.in-addr.arpa.
>>   stub-addr: 127.0.0.1@53053
>> stub-zone:
>>   name:  255.in-addr.arpa.
>>   stub-addr: 127.0.0.1@53053
> 
> Frank

Missing description of the default proposals in iked.conf

[Антон Касимов]

The descriptions of the ikesa and childsa options contain the following
statements:

Possible values for auth, enc, prf, group, and the* default proposals* are
described below in CRYPTO TRANSFORMS. If omitted, iked(8) will use the
default proposals for the IKEv2 protocol.
Possible values for auth, enc, group, esn, and the *default proposals* are
described below in CRYPTO TRANSFORMS. If omitted, iked(8) will use the
default proposals for the ESP or AH protocol.


But CRYPTO TRANSFORMS has no description for default proposals.

-- 
Антон Касимов / Anton Kasimov

Re: Recommendation request for LTE modem on PC Engines APU2

[Kapfhammer, Stefan]

Hello Mikolaj,

Here are the recommendations from PCengines itself:

https://pcengines.ch/howto.htm#3G

or here:

https://www.sierrawireless.com/products-and-solutions/embedded-solutions/networking-modules/


Regards,
Stefan

> -Ursprüngliche Nachricht-
> Von: owner-m...@openbsd.org  Im Auftrag
> von Mikolaj Kucharski
> Gesendet: Freitag, 10. Juli 2020 10:57
> An: misc@openbsd.org
> Betreff: Recommendation request for LTE modem on PC Engines APU2
> 
> Hi,
> 
> I have couple of PC Engines boards and I was thinking to take one spare
> APU2E4 and plug into it an LTE modem. I see umb(4) manual page listing
> couple of models, but quick searching online shows different interface on
> those cards from available on APU. I see also umsm(4) and this one looks
> probably more appropriate for PC Engiens system, but not sure are they
> capable of LTE speeds.
> 
> Also, not sure what would be the practical differences between the cards, so
> question for some of you who may have hands on experience with any of
> them on OpenBSD.
> 
> - What do you use as LTE modem on OpenBSD with miniPCIe interface?
> 
> - Would you recommend it or would you go for different card?
> 
> - Do you have any type of mobile (3G, 4G or whatever) OpenBSD setup
>   on totally different hardware, if so, what is it?
> 
> I'm looking for LTE/4G card, something capable of (theoretical) 50Mbps or
> more, but if that's not possible, I may revisit my requirements.
> 
> Please CC me in any replies, I'm not subscribed to the list.
> 
> --
> Regards,
>  Mikolaj

Recommendation request for LTE modem on PC Engines APU2

[Mikolaj Kucharski]

Hi,

I have couple of PC Engines boards and I was thinking to take one spare
APU2E4 and plug into it an LTE modem. I see umb(4) manual page listing
couple of models, but quick searching online shows different interface
on those cards from available on APU. I see also umsm(4) and this one
looks probably more appropriate for PC Engiens system, but not sure are
they capable of LTE speeds.

Also, not sure what would be the practical differences between the
cards, so question for some of you who may have hands on experience
with any of them on OpenBSD.

- What do you use as LTE modem on OpenBSD with miniPCIe interface?

- Would you recommend it or would you go for different card?

- Do you have any type of mobile (3G, 4G or whatever) OpenBSD setup
  on totally different hardware, if so, what is it?

I'm looking for LTE/4G card, something capable of (theoretical) 50Mbps
or more, but if that's not possible, I may revisit my requirements.

Please CC me in any replies, I'm not subscribed to the list.

-- 
Regards,
 Mikolaj

Re: OpenMoko

[Benjamin Baier]

On Fri, 10 Jul 2020 04:12:03 + ()
m brandenberg  wrote:

> On Thu, 9 Jul 2020, Theo de Raadt wrote:
> 
> > static const struct urng_type urng_devs[] = {
> >{ { USB_VENDOR_OPENMOKO2, USB_PRODUCT_OPENMOKO2_CHAOSKEY },
> >  {64, 5, 0, 100, 5000} },
> 
> Interesting.  That's what became of OpenMoko...  a pool of DevIDs
> for small device builders?
Yes, for Open Source Hardware, see https://github.com/openmoko/openmoko-usb-oui

Re: Unbound Problems (Reverse Direction)

[Frank Habicht]

Hi,

On 09/07/2020 20:44, ken.hendrick...@l3harris.com wrote:
> stub-zone:
> name:  30.24.172.in-addr.arpa.
   good
> stub-addr: 127.0.0.1@53053
> stub-zone:
> name:  2.168.192.in-arpa.arpa.
   typo
> stub-addr: 127.0.0.1@53053
> stub-zone:
> name:  224.in-addr.arpa.
> stub-addr: 127.0.0.1@53053
> stub-zone:
> name:  255.in-addr.arpa.
> stub-addr: 127.0.0.1@53053

Frank