Clean install or upgrade to 6.4 fw_update error

2018-10-18 Thread Mischa
Hi All, Just ran a couple of updates and clean installs and I am seeing the following error during boot. Clean install: running rc.firsttime Path to firmware: http://firmware.openbsd.org/firmware/6.4/ Installing: intel-firmware Checking for available binary patches...ftp:

Re: Clean install or upgrade to 6.4 fw_update error

2018-10-18 Thread Stuart Henderson
That error message is because there are no syspatch yet, it is not from the firmware update. On 18 October 2018 16:02:34 Mischa wrote: Hi All, Just ran a couple of updates and clean installs and I am seeing the following error during boot. Clean install: running rc.firsttime Path to

Re: join(1) on NULL values

2018-10-18 Thread Martijn van Duren
On 10/18/18 16:51, Martijn van Duren wrote: > When reviewing otto@'s diff I found the following, which was also part > of the r1.4 import. I managed to contact michaels and he told me that he > couldn't recollect anything other then what was in the commit message > and other local changes were

OpenBSD 6.4 released - Oct 18, 2018

2018-10-18 Thread Theo de Raadt
- OpenBSD 6.4 RELEASED - October 18, 2018. We are pleased to announce the official release of OpenBSD 6.4. This is our 45th release. We remain proud of OpenBSD's record of

join(1) on NULL values

2018-10-18 Thread Martijn van Duren
When reviewing otto@'s diff I found the following, which was also part of the r1.4 import. I managed to contact michaels and he told me that he couldn't recollect anything other then what was in the commit message and other local changes were most likely not intentional. I tested this behaviour

Re: Clean install or upgrade to 6.4 fw_update error

2018-10-18 Thread Mischa
That helps. Thanx! Mischa > On 18 Oct 2018, at 17:47, Stuart Henderson wrote: > > That error message is because there are no syspatch yet, it is not from the > firmware update. > > > On 18 October 2018 16:02:34 Mischa wrote: > >> Hi All, >> >> >> Just ran a couple of updates and clean

Re: igmp, router_info: use queue(3)

2018-10-18 Thread Alexander Bluhm
On Wed, Oct 17, 2018 at 07:12:32PM -0500, Scott Cheloha wrote: > The hand-rolled list queue(3) is replacing here is singly linked > but used an extra pointer in rti_delete() to get O(n) deletion. > I kept the O(n) deletion by using LIST. If the extra space needed > for LIST is unacceptable I can

diff: split ctloutput into getopt/setopt

2018-10-18 Thread David Hill
Hello - This diff splits the ctloutput functions into getopt/setopt, which could offer more fine-grained locking. It also removes some indentation and imo is easier to read. Thoughts? Index: net/rtsock.c === RCS file:

Re: signify: invalid comment in /tmp/syspatch.xxx/SHA256.sig

2018-10-18 Thread Stuart Henderson
On 2018/10/18 18:58, James Anderson wrote: > Freshly upgraded to 6.4, rebooted and went to update syspatches, firmware, > packages. Running syspatch I expected a 404 error > (https://marc.info/?l=openbsd-tech=153987805403874=2), but instead > was greeted with "signify: invalid comment". Thought

Re: VLAN priority field and PF queues

2018-10-18 Thread David Gwynne
> On 18 Oct 2018, at 15:55, Adrian Close wrote: > > Hi all, > > When using PF queues on a VLAN interface on 6.3/amd64, I'm seeing the VLAN > priority field always set to 7 for outbound traffic. For example: > > queue rootq_100 on vlan100 bandwidth 1G > queue ltd_100 parent rootq_100

multicast.4: drop unneeded (void *) casts

2018-10-18 Thread scottcheloha
Hi, getsockopt(2) and setsockopt(2) take a void pointer for the third parameter so there is no need for any of these casts. I can do other style(9)-type cleanup in a subsequent diff or I can cook this diff and do it all in one. Thoughts, preferences? Index: share/man/man4/multicast.4

Re: multicast.4: drop unneeded (void *) casts

2018-10-18 Thread Philip Guenther
On Thu, Oct 18, 2018 at 4:00 PM wrote: > getsockopt(2) and setsockopt(2) take a void pointer for the third > parameter so there is no need for any of these casts. > Yep. > I can do other style(9)-type cleanup in a subsequent diff or I can > cook this diff and do it all in one. > > Thoughts,

Re: www/64.html - OpenSSH version 7.8 or 7.9?

2018-10-18 Thread Darren Tucker
On 18 October 2018 at 07:20, Markus Lude wrote: > Hello, > > www/64.html mentions OpenSSH version 7.8. > > With snapshot from october 11th on amd64 the version of ssh is 7.9: > it's 7.9, which was officially released a couple of hours ago. The website will be updated shortly. $ ssh -V >

Re: bypass support for iommu on sparc64

2018-10-18 Thread David Gwynne
On Wed, May 10, 2017 at 10:09:59PM +1000, David Gwynne wrote: > On Mon, May 08, 2017 at 11:03:58AM +1000, David Gwynne wrote: > > on modern sparc64s (think fire or sparc enterprise Mx000 boxes), > > setting up and tearing down the translation table entries (TTEs) > > is very expensive. so

signify: invalid comment in /tmp/syspatch.xxx/SHA256.sig

2018-10-18 Thread James Anderson
Freshly upgraded to 6.4, rebooted and went to update syspatches, firmware, packages. Running syspatch I expected a 404 error (https://marc.info/?l=openbsd-tech=153987805403874=2), but instead was greeted with "signify: invalid comment". Thought this was a local issue but there are no

Re: www/64.html - OpenSSH version 7.8 or 7.9?

2018-10-18 Thread jungle boogie
Thus said Darren Tucker on Fri, 19 Oct 2018 14:23:48 +1100 On 18 October 2018 at 07:20, Markus Lude wrote: Hello, www/64.html mentions OpenSSH version 7.8. With snapshot from october 11th on amd64 the version of ssh is 7.9: it's 7.9, which was officially released a couple of hours ago.

VLAN priority field and PF queues

2018-10-18 Thread Adrian Close
Hi all, When using PF queues on a VLAN interface on 6.3/amd64, I'm seeing the VLAN priority field always set to 7 for outbound traffic. For example: queue rootq_100 on vlan100 bandwidth 1G queue ltd_100 parent rootq_100 bandwidth 20M max 50M queue std_100 parent rootq_100 bandwidth

bgpd refactor rib dumping

2018-10-18 Thread Claudio Jeker
Change the way ribs are porcessed. Currently all async dumpers have to call rib_dump_r() whenever progress should be made. Also creating the context for such a dump is all on the caller side. Change this to one central place. Now all that is needed is to call rib_dump_new() with the callbacks for

carp demote counter

2018-10-18 Thread Hrvoje Popovski
hi all, while playing around with carp, pfsync, pflow and doing ifconfig pfsync0 destroy && sh netstart in loop i noticed that carp demote counter becomes really high r710-2# ifconfig -g carp carp: carp demote count 4321 don't know is this normal or not but problem is that i can't lower that