From owner-freebsd-current@FreeBSD.ORG Fri May 10 20:04:17 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 45D55676; Fri, 10 May 2013 20:04:17 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) by mx1.freebsd.org (Postfix) with ESMTP id C6B5F5E8; Fri, 10 May 2013 20:04:16 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.6/8.14.6) with ESMTP id r4AK49Xj002077; Sat, 11 May 2013 00:04:09 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.6/8.14.6/Submit) id r4AK49OU002076; Sat, 11 May 2013 00:04:09 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Sat, 11 May 2013 00:04:09 +0400 From: Gleb Smirnoff To: Spil Oss Subject: Re: Problems with ipfw/natd and axe(4) Message-ID: <20130510200409.GT15182@FreeBSD.org> References: <20130415015850.Y56386@sola.nimnet.asn.au> <20130415160625.K56386@sola.nimnet.asn.au> <20130417133637.W56386@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-ipfw@freebsd.org, current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 May 2013 20:04:17 -0000 Spil, On Fri, May 10, 2013 at 09:06:35AM +0200, Spil Oss wrote: S> There seems to be quite a bit of overhaul on the firewall code, pf and S> ipfw have been moved to sys/netpfil? Can there be some regressions in S> there that I hit? Yes, a regression is possible there. However, the issue seems to be axe(4) specific, since there are no reports on more common NICs. S> Just upgraded to r250404 but that does not help. Should I file a PR? Having a PR, with all information gathered in one report, is definitely better than not having one. -- Totus tuus, Glebius.