Date: Sat, 22 Oct 2005 14:38:31 +0400 From: Gleb Smirnoff <glebius@FreeBSD.org> To: Chris Dionissopoulos <dionch@freemail.gr> Cc: net@FreeBSD.org Subject: Re: What's wrong with netgraph NG_FWD_NEW_DATA? Message-ID: <20051022103831.GI59364@cell.sick.ru> In-Reply-To: <4353765C.4030802@freemail.gr> References: <4353765C.4030802@freemail.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 17, 2005 at 01:01:00PM +0300, Chris Dionissopoulos wrote: C> Trying to split inbound traffic based on layer2 characteristics, C> i have create a new netgraph module(ng_l2split) using C> ng_vlan(4) as reference. The design and implementation is C> pretty simple as ng_vlan : C> C> xl0:upper C> | C> +---------+ C> | ng_l2split|-----ng0 (ng_eiface on ngeth0) C> +---------+ ( --- ng1,2,....) C> | C> xl0:lower C> C> ng_l2plit has 2 basic hooks as descriped in ng_vlan(4) man page: C> - downstream hook (attached to physical's "lower" ) C> - nomatch hook (attached to physical's "upper" ) C> C> and for every ng_eiface node you attach you must provide a C> mac address for filtering (later this will be automated). Uhmm, wouldn't it be simplier to use ng_bridge? ,-- ngeth0 (with MAC address X) / xl0:lower -- bridge \ `-- ngeth1 (with MAC address Y) -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051022103831.GI59364>