Wrong rule number in pflog with anchors

If you have an anchor in your pf ruleset, a packet that matches a rule with a log directive will reflect the rule number of the last anchor definition instead of the rule that caused the logging. My first rule in pf.conf is 'block log (all) all'. In 6.1, packets matching the block rule will show

Re: add keydisk to FDE FAQ

On Thu, Oct 12, 2017 at 11:39:22AM -0700, Scott Bonds wrote: > Here's a patch to add instructions for using a keydisk to the FAQ, as > promised: https://marc.info/?l=openbsd-bugs=150776298218879=2 > > I tried refactoring to reduce the redundancy between the passphrase and > keydisk methods in the

Re: [patch] hostname.if5 additional info on point to point addressing

Hi Ingo, First of all thanks for the feedback it is appreciated, especially when you think the thread is a waste of time. so rather than look for feedback on another patch for now If you could bear with me and let me outline why I think this thread is important important enough to be my first

add keydisk to FDE FAQ

Here's a patch to add instructions for using a keydisk to the FAQ, as promised: https://marc.info/?l=openbsd-bugs=150776298218879=2 I tried refactoring to reduce the redundancy between the passphrase and keydisk methods in the FAQ, but it came out more difficult to read, so I went with being

Re: RTM_DESYNC when starting network

On Thu, October 12, 2017 10:36 am, Martin Pieuchot wrote: > On 12/10/17(Thu) 10:33, trondd wrote: >> Just updated my -current VM hosted in VMware Fusion. Upon reboot, I got >> an em0: RTM_DESYNC and the boot process hung. After a couple forced >> reboots, I figured out that if I "Disconnect

Re: [PATCH] innovations.html - use singular nop instead of plural nops

Hi Raf, Raf Czlonka wrote on Wed, Oct 11, 2017 at 01:20:15AM +0100: > As per the subject - nops sequences -> nop sequences. Done, thanks. Ingo > Index: innovations.html > === > RCS file: /cvs/www/innovations.html,v > retrieving

Re: [patch] hostname.if5 additional info on point to point addressing

Hi Tom, it is still completely unclear what you are even trying to talk about. The patch is certainly not acceptable, it is vague, highly confusing, and fails to state what it is all about. If what you are trying to document is the so-called "IP unnumbered" hack: That is an abomination brewed

Re: [Patch] style(9) improvements for sample code in pf(4)

On Mon, Oct 09, 2017 at 11:56:03AM +1100, Ross L Richardson wrote: > Improved version, with thanks to anton@ > > [Should usage() be __dead?] > > Ross > fixed, thanks. jmc > Index: pf.4 > === > RCS file:

Re: RTM_DESYNC when starting network

On 12/10/17(Thu) 10:33, trondd wrote: > Just updated my -current VM hosted in VMware Fusion. Upon reboot, I got > an em0: RTM_DESYNC and the boot process hung. After a couple forced > reboots, I figured out that if I "Disconnect Network Adapter" then > reconnect it, booting will continue with

RTM_DESYNC when starting network

Just updated my -current VM hosted in VMware Fusion. Upon reboot, I got an em0: RTM_DESYNC and the boot process hung. After a couple forced reboots, I figured out that if I "Disconnect Network Adapter" then reconnect it, booting will continue with the DHCP exchange and all seems to work fine.

Re: mg: fgetln -> getline

commited, thanks! On Thu, Oct 12, 2017 at 04:17:10AM +, Scott Cheloha wrote: > > On Oct 11, 2017, at 2:36 AM, Florian Obser wrote: > > > > On Sun, Sep 17, 2017 at 02:56:32AM +, Scott Cheloha wrote: > >> > >> > >>if (buf[len - 1] == '\n') > >>

Re: mg: fgetln -> getline

OK florian@ or if someone gives me an OK I'll commit it. On Thu, Oct 12, 2017 at 04:17:10AM +, Scott Cheloha wrote: > > On Oct 11, 2017, at 2:36 AM, Florian Obser wrote: > > > > On Sun, Sep 17, 2017 at 02:56:32AM +, Scott Cheloha wrote: > >> > >> > >>if