From owner-freebsd-pf@freebsd.org Sun Nov 20 21:00:31 2016 Return-Path: Delivered-To: freebsd-pf@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39BBDC4C9A1 for ; Sun, 20 Nov 2016 21:00:31 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0A3E81F4A for ; Sun, 20 Nov 2016 21:00:31 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uAKL01os016611 for ; Sun, 20 Nov 2016 21:00:30 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201611202100.uAKL01os016611@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-pf@FreeBSD.org Subject: Problem reports for freebsd-pf@FreeBSD.org that need special attention Date: Sun, 20 Nov 2016 21:00:30 +0000 X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2016 21:00:31 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 203735 | Transparent interception of ipv6 with squid and p 1 problems total for which you should take action. From owner-freebsd-pf@freebsd.org Thu Nov 24 19:36:59 2016 Return-Path: Delivered-To: freebsd-pf@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D4E7C53EA0 for ; Thu, 24 Nov 2016 19:36:59 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 781F41DA for ; Thu, 24 Nov 2016 19:36:58 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from baby-jane.lamaiziere.net (4.169.100.84.rev.sfr.net [84.100.169.4]) by mx.zohomail.com with SMTPS id 1480016207090658.360907885652; Thu, 24 Nov 2016 11:36:47 -0800 (PST) Date: Thu, 24 Nov 2016 20:36:39 +0100 From: patrick lamaiziere To: "freebsd-pf@freebsd.org" Subject: pfsync(4) maxupd ? Message-ID: <20161124203639.14abb3e0@baby-jane.lamaiziere.net> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; i386-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2016 19:36:59 -0000 Hello, I'm asking about the goal of the parameter maxupd of pfsync, ie when we should change it ? At work we have a lot of states (~1 200 000) with many changes and it looks like we lose some states deletion across pfysnc. Does an augmentation of maxupd could help ? the manual : The pfsync interface will attempt to collapse multiple state updates into a single packet where possible. The maximum number of times a single state can be updated before a pfsync packet will be sent out is con- trolled by the maxupd parameter to ifconfig (see ifconfig(8) and the example below for more details). The sending out of a pfsync packet will be delayed by a maximum of one second. Thanks, regards. From owner-freebsd-pf@freebsd.org Fri Nov 25 16:28:01 2016 Return-Path: Delivered-To: freebsd-pf@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 76008C5529E for ; Fri, 25 Nov 2016 16:28:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4D9A8CEE for ; Fri, 25 Nov 2016 16:28:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uAPGS150015041 for ; Fri, 25 Nov 2016 16:28:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-pf@FreeBSD.org Subject: [Bug 212115] kldunload pf causes panic Date: Fri, 25 Nov 2016 16:28:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: shriyogeshchandra@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-pf@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2016 16:28:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212115 shriyogeshchandra@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |shriyogeshchandra@gmail.com --- Comment #1 from shriyogeshchandra@gmail.com --- Just signed up here, so apologies for any transgressions. I too experience = this bug.=20 In case it helps someone better equipped, here is the dump (copied from the terminal running the virtual machine):=20 Fatal trap 12: page fault while in kernel mode cpuid =3D 0; apic id =3D 00 fault virtual address =3D 0x3b0 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff80ad43cb stack pointer =3D 0x28:0xfffffe000023a3a0 frame pointer =3D 0x28:0xfffffe000023a430 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 2166 (kldunload) trap number =3D 12 panic: page fault cpuid =3D 0 KDB: stack backtrace: #0 0xffffffff80b24077 at kdb_backtrace+0x67 #1 0xffffffff80ad93e2 at vpanic+0x182 #2 0xffffffff80ad9253 at panic+0x43 #3 0xffffffff80fa0d51 at trap_fatal+0x351 #4 0xffffffff80fa0f43 at trap_pfault+0x1e3 #5 0xffffffff80fa04ec at trap+0x26c #6 0xffffffff80f84141 at calltrap+0x8 #7 0xffffffff82234eb1 at vnet_pf_uninit+0xa1 #8 0xffffffff80aa5de0 at linker_file_unload+0x720 #9 0xffffffff80aa71bc at kern_kldunload+0xfc #10 0xffffffff80fa16ae at amd64_syscall+0x4ce #11 0xffffffff80f8442b at Xfast_syscall+0xfb Uptime: 9h2m39s Dumping 220 out of 991 MB:..8%..15%..22%..37%..44%..51%..66%..73%..87%..95% Dump complete --=20 You are receiving this mail because: You are the assignee for the bug.=