On Tue, May 02, 2017 at 05:03:20PM +0000, Stuart Henderson wrote: > Probably the best thing to do at this point is to write a mail to bugs@: > > 1. describe what the machine is doing in detail. carp? ipsec? pfsync? > what sort of relays? include config (sanitized if necessary, but do that > consistently). > > 2. copy in the panic message and stack trace as text (re-type it, > don't attach a picture or send a link to a picture). > > 3. make it a self-contained report with description etc all in the one > message, don't rely on people having message history. > > 4. include dmesg.
Hi Stuart, Thx for your answer ! I didn't have the time to work on this since early may. But from time to time, I check the commit on pf.c and I saw this one which seemed to perfectly match my bug : http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/net/pf.c?rev=1.1035&content-type=text/x-cvsweb-markup I tried the diff, and it seems to be OK ! I can't trigger the bug right now (it was 100% before). So, thx you again, and special thx to bluhm@ who made the patch ! -- Mathieu
