From owner-freebsd-pf@FreeBSD.ORG Sun Mar 14 00:50:03 2010 Return-Path: Delivered-To: freebsd-pf@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB9D4106564A for ; Sun, 14 Mar 2010 00:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9B7AA8FC15 for ; Sun, 14 Mar 2010 00:50:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o2E0o3CH088362 for ; Sun, 14 Mar 2010 00:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o2E0o3kF088361; Sun, 14 Mar 2010 00:50:03 GMT (envelope-from gnats) Date: Sun, 14 Mar 2010 00:50:03 GMT Message-Id: <201003140050.o2E0o3kF088361@freefall.freebsd.org> To: freebsd-pf@FreeBSD.org From: Nick Leuta Cc: Subject: Re: kern/143543: [pf] [panic] PF route-to causes kernel panic X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Nick Leuta 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, 14 Mar 2010 00:50:03 -0000 The following reply was made to PR kern/143543; it has been noted by GNATS. From: Nick Leuta To: bug-followup@FreeBSD.org, slava@aprec.ru Cc: Subject: Re: kern/143543: [pf] [panic] PF route-to causes kernel panic Date: Sun, 14 Mar 2010 03:34:50 +0300 I have the similar problem but in a bit different situation... the rule is: pass out quick route-to (vlan2 192.168.0.1) from 192.168.0.2 to any where 192.168.0.2 is binded to the vlan2 interface. The default gateway is 192.168.1.1 and is accessible through another interface. The "ping -S 192.168.0.2 192.168.0.1" command is used for test purposes, and (sic!) the 192.168.0.1 is unreachable (really down...). Without that rule we have: PING 192.168.0.1 (192.168.0.1) from 192.168.0.2: 56 data bytes ping: sendto: Host is down With the rule we obtain the kernel panic (in "ping" process) instead of the "ping: sendto: Host is down" message after the same timeout as in the case without rule.