From owner-freebsd-net@FreeBSD.ORG Mon May 12 07:49:50 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C5880D55 for ; Mon, 12 May 2014 07:49:50 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A55062512 for ; Mon, 12 May 2014 07:49:50 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1WjkzX-0004Mu-AL for freebsd-net@freebsd.org; Mon, 12 May 2014 00:49:43 -0700 Date: Mon, 12 May 2014 00:49:43 -0700 (PDT) From: kariz To: freebsd-net@freebsd.org Message-ID: <1399880983187-5911668.post@n5.nabble.com> In-Reply-To: References: Subject: Re: running netmap-ipfw with real NICs MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2014 07:49:50 -0000 Hi, I tested my scenario. it is true. I could not receive packets in receiver and thought that my scenario is wrong!! My problem in this test solved by using latest version of netmap and netmap-based ipfw. Thanks from Luigi for his great work. -- View this message in context: http://freebsd.1045724.n5.nabble.com/running-netmap-ipfw-with-real-NICs-tp5906992p5911668.html Sent from the freebsd-net mailing list archive at Nabble.com.