From owner-freebsd-current@FreeBSD.ORG  Mon May 13 04:36:47 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 241926F2;
 Mon, 13 May 2013 04:36:47 +0000 (UTC)
 (envelope-from pyunyh@gmail.com)
Received: from mail-da0-x230.google.com (mail-da0-x230.google.com
 [IPv6:2607:f8b0:400e:c00::230])
 by mx1.freebsd.org (Postfix) with ESMTP id E5B69366;
 Mon, 13 May 2013 04:36:46 +0000 (UTC)
Received: by mail-da0-f48.google.com with SMTP id h32so2082027dak.21
 for <multiple recipients>; Sun, 12 May 2013 21:36:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=x-received:from:date:to:cc:subject:message-id:reply-to:references
 :mime-version:content-type:content-disposition:in-reply-to
 :user-agent; bh=uRqiMIRB/lntrwVS8116ZDQHR+DUul0Z4SDg+lDAeiQ=;
 b=fFcPQr61o5OcAva3nLPXMjy7pA/gDRdWtZTGdWrKNZBWXI5760l7NSa0PfZFuPsrSM
 ji+oGZyoRG/FYatzLMyEcQfSX5FbIPhas8PLSvsOCFAZb8zsaBhw+RoCcirmpZcVVsDX
 A2x9cKotSXHyx+ysPXJ9S7ZIB3jAHWN8SxIIGzlAKkz6msLrJeZNiz9GUHOduUD8t4tV
 jpc76bFiQ6qdLE0WIjJMbFBWcixTbFFU3Xj8aBokXaXpjGfVxUi9nrZjjrymC7BQKFKH
 cF917QeVTXnC7Z0HBHSZAOA2H7keR85sYLLxc7UK0zy3uhb7TWxpnNvG8GLae3erXJOV
 Pzcw==
X-Received: by 10.66.161.227 with SMTP id xv3mr27631377pab.82.1368419806728;
 Sun, 12 May 2013 21:36:46 -0700 (PDT)
Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249])
 by mx.google.com with ESMTPSA id fr1sm1865753pbb.26.2013.05.12.21.36.42
 for <multiple recipients>
 (version=TLSv1 cipher=RC4-SHA bits=128/128);
 Sun, 12 May 2013 21:36:45 -0700 (PDT)
Received: by pyunyh@gmail.com (sSMTP sendmail emulation);
 Mon, 13 May 2013 13:36:39 +0900
From: YongHyeon PYUN <pyunyh@gmail.com>
Date: Mon, 13 May 2013 13:36:39 +0900
To: Gleb Smirnoff <glebius@freebsd.org>
Subject: Re: Problems with ipfw/natd and axe(4)
Message-ID: <20130513043639.GA1480@michelle.cdnetworks.com>
References: <CAEJyAvOZ6fW0i3yT_D4fH1huje-qsJwA7GGeXqAO1PKzge-YNw@mail.gmail.com>
 <20130415015850.Y56386@sola.nimnet.asn.au>
 <CAHu1Y73Xu64NY1B=idaKmHKDGOB3AHbcXKi4A48-SNkhJrMy6Q@mail.gmail.com>
 <20130415160625.K56386@sola.nimnet.asn.au>
 <CAEJyAvP-4FZ7eZ0o4c3qMzC0nY_gT4GfS3KjBVQiuzNY3aXz4Q@mail.gmail.com>
 <CAEJyAvMGKr9gZEEhg2KCD2FkZ=F4Xbx20v8iWyu8hhA_Pq8phw@mail.gmail.com>
 <20130417133637.W56386@sola.nimnet.asn.au>
 <CAEJyAvO_KA8dYSLkFXCoBqcogTkurBX_X=KZn25R4MKoeUGaVQ@mail.gmail.com>
 <CAEJyAvNL4NWmm8BMGkT6usZgGt2VWJNqQXeXBgYY9+MiNoUBVw@mail.gmail.com>
 <20130510200409.GT15182@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130510200409.GT15182@FreeBSD.org>
User-Agent: Mutt/1.4.2.3i
Cc: Spil Oss <spil.oss@gmail.com>, freebsd-ipfw@freebsd.org,
 current <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: pyunyh@gmail.com
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 13 May 2013 04:36:47 -0000

On Sat, May 11, 2013 at 12:04:09AM +0400, Gleb Smirnoff wrote:
>   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.

There was no change to axe(4) except added a new device id so it
seems the issue is not in driver. In addition, AX88772B engineering
sample I have works without problems on CURRENT.
I didn't use ipfw(4) or natd though.