From owner-freebsd-net@FreeBSD.ORG Sun Nov 9 23:23:07 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7F078726 for ; Sun, 9 Nov 2014 23:23:07 +0000 (UTC) Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 02B5C159 for ; Sun, 9 Nov 2014 23:23:07 +0000 (UTC) Received: by mail-wg0-f48.google.com with SMTP id m15so7470490wgh.35 for ; Sun, 09 Nov 2014 15:23:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=HvD9QeOebbOMmTysIaVbO5gCkEcLcWcBtd34WJXyHgU=; b=D0fB2CRZHfE60SGCKad6OuVwdw/x4czROymF7Ic1/TE9hun8rOAiDhJ79rOqVgcJ5+ x6loKrssNM6oHuLbTXgjKGez89M5yjjalfROlZD1btFHaRpceqlhi+Z1aNwMtvKf05ji BX8c/XS7qTnRGipZNwCoSl23/Jpw6t48OSaRQqwV9ovjPkPsq/exTqUvtMScDt/uizeW CA0O6grPz3g7nRmNUhtS+OoZaP+4kSVbasi8Zw8ff9VqKlhEllaM2D6D1+lo7qCGqQg7 XMM/Pt4fXTIA5TN01t7ML20WcBWehMdDxd5WAFoabxI/+ffWhZ/1u6ZORsJ9Dg5k7IIw h/TQ== MIME-Version: 1.0 X-Received: by 10.194.185.229 with SMTP id ff5mr37257698wjc.122.1415575385428; Sun, 09 Nov 2014 15:23:05 -0800 (PST) Sender: rizzo.unipi@gmail.com Received: by 10.194.19.9 with HTTP; Sun, 9 Nov 2014 15:23:05 -0800 (PST) In-Reply-To: References: <9C799778-79DC-4D5F-BA5C-EA94A573ED10@freebsdbrasil.com.br> Date: Sun, 9 Nov 2014 15:23:05 -0800 X-Google-Sender-Auth: 5jCvzhqUZAxS48E0J_OHRYBe6JU Message-ID: Subject: Re: netmap-ipfw on em0 em1 From: Luigi Rizzo To: Evandro Nunes Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Patrick Tracanelli , "freebsd-net@freebsd.org" , Mahnaz Talebi X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Nov 2014 23:23:07 -0000 On Sun, Nov 9, 2014 at 1:17 PM, Evandro Nunes wrote: > professor luigi > > where can I find the code for netmap-fwd you mentioned on usenix paper? > > =E2=80=8Bthat has been renamed to bridge.c cheers luigi =E2=80=8B > > ** https://www.usenix.org/system/files/conference/atc12/atc12-final186.pd= f > > On Sun, Nov 9, 2014 at 5:31 PM, Evandro Nunes > wrote: > >> hello again patrick >> >> On Sun, Nov 9, 2014 at 12:54 AM, Patrick Tracanelli < >> eksffa@freebsdbrasil.com.br> wrote: >> >>> > (Machine-A)<-->Machine-B<--->(MachineC) >>> > >>> > Machine-A: >>> > em0 172.16.251.3/24 >>> > >>> > Machine-B: >>> > em1: 172.16.251.1/24 >>> > em2: 172.16.252.1/24 >>> > 10.0-STABLE w/ latest netmap-ipfw and netmap code from google code >>> > repository >>> > >>> > Machine-C: >>> > em0 172.16.252.3/24 >>> >>> Now, your scenario is a typical routing topology. kipfw has no packet >>> forwarding capabilities whats why when you start it, you are out of >>> forwarding capabilities and therefore, out of communication between mac= hine >>> A and C because they just need it in your topology. >>> >>> So for your testing purposes read again what Mahaza said: >>> >>> >> ipfw works as a bridge and copy >>> >> incoming packets to em0 to em1 if they pass defined rules (and vice >>> versa, >>> >> from em1 to em0). >>> >>> Got it? kipfw will work as a BRIDGE and COPY between the NIC ports. >>> >>> Therefore on your topology do a simple change: >>> >>> Machine-C: >>> ifconfig em0 172.16.251.4/24 >>> >>> So machine C will be in the same network of machine A. >>> >>> WITHOUT kipfw you will be OUT of communication. If you want to have >>> communication without kipfw please configure if_bridge(4) properly. >>> >>> Now WHEN you ./kipfw netmap:em1 netmap:em2 you will BRIDGE em1 and em2 >>> ports and therefore you will HAVE communication between the NICS. >>> >>> And you are done, just as a miracle! Thanks to Luigi. >>> >> >> YES IT WORKED YES >> thank you VERY MUCH for the kind help and for making it clear all the >> stuff I missed reading, yes I assume I should have read more or at least >> understood >> now I can see how the things works and it does work >> >> THANK YOU again very much >> >> >> >>> Now its time to have some fun: >>> >>> ipfw/ipfw add pipe 1 all from 172.16.251.0/24 to 172.16.251.0/24 >>> ipfw/ipfw pipe 1 config bw 128Kbit/s >>> delay 300 >>> >>> and now ping machine-A and machine-C and see dummynet working as >>> expected... >>> >>> I believe you can keep on with your testings now!!! :-) >>> >> >> yes it worked as well >> >> now let me ask you all, other than click, does netmap offers something >> that can do packet forwarding? simple packet forwarding like the scenari= o I >> was trying before? I know this is not kipfw and not bridge but is there >> something? >> >> thank you >> >> >> >>> BTW Luigi, I see netmap was commited to GENERIC on -CURRENT. I believe >>> it may be a good idea to add netmap-ipfw to the base system now, to bot= h >>> promote more testing and also to be a good companion to netmap on GENER= IC. >>> I dont mean a new ipfw-netmap binary under /sbin/ but just the code on >>> /usr/src/tools/tools. >>> >> >> yes and some handbook or a better README that at least mentions the >> correct syntax for the tools >> I think adrian chadd mentioned something about that in an earlier messag= e >> >> >>> >>> I've been using netmap-ipfw for a while and sure it lacks more >>> flexbility like the ability to kipfw several ports, etc. But as it is r= ight >>> now, it's very stable and reliable for a preliminary code. Thats why I >>> believe it should be on the base system. Thank you very much for the >>> incredible technology. >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> > --=20 -----------------------------------------+------------------------------- Prof. Luigi RIZZO, rizzo@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL +39-050-2211611 . via Diotisalvi 2 Mobile +39-338-6809875 . 56122 PISA (Italy) -----------------------------------------+-------------------------------