From owner-freebsd-ipfw@FreeBSD.ORG Wed Jun 30 10:10:11 2010 Return-Path: Delivered-To: freebsd-ipfw@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FEA3106566B for ; Wed, 30 Jun 2010 10:10:11 +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 7599F8FC15 for ; Wed, 30 Jun 2010 10:10:11 +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 o5UAABL9025483 for ; Wed, 30 Jun 2010 10:10:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o5UAABQv025482; Wed, 30 Jun 2010 10:10:11 GMT (envelope-from gnats) Date: Wed, 30 Jun 2010 10:10:11 GMT Message-Id: <201006301010.o5UAABQv025482@freefall.freebsd.org> To: freebsd-ipfw@FreeBSD.org From: "Terrence Koeman" Cc: Subject: Re: kern/145305: [ipfw] ipfw problems, panics, data corruption, ipv6 socket weirdness X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Terrence Koeman List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 10:10:11 -0000 The following reply was made to PR kern/145305; it has been noted by GNATS. From: "Terrence Koeman" To: "bug-followup@FreeBSD.org" Cc: Subject: Re: kern/145305: [ipfw] ipfw problems, panics, data corruption, ipv6 socket weirdness Date: Wed, 30 Jun 2010 12:08:36 +0200 I spoke too soon. The panics and corruption are gone, but there's still the= problem of local ipv6 addresses being used 'as' ipv4 addresses which resul= ts in bad source addresses: Jun 30 10:50:42 adinava kernel: ipfw: 65529 Accept TCP 1.23.2.0:28593 :25 out via bce0 I'm having tons of those, where 1.23.2.0 is obviously not a locally bound I= P but the result of the local system trying to send a SYN from a local ipv6= address to a remote ipv4 address. PS: Excuse me for signing my previous followup. -- Regards, T. Koeman, MTh/BSc/BPsy; Technical Monk MediaMonks B.V. (www.mediamonks.com) Please quote all replies in correspondence.