From owner-freebsd-arch Fri Oct 25 2:46: 0 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85D7437B401; Fri, 25 Oct 2002 02:45:59 -0700 (PDT) Received: from premijer.tel.fer.hr (premijer.tel.fer.hr [161.53.19.221]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AD7143E6A; Fri, 25 Oct 2002 02:45:59 -0700 (PDT) (envelope-from zec@tel.fer.hr) Received: from tel.fer.hr (unknown [161.53.19.178]) by premijer.tel.fer.hr (Postfix) with ESMTP id 2B2AA1380; Fri, 25 Oct 2002 11:45:38 +0200 (MET DST) Message-ID: <3DB912CF.DF6F7B74@tel.fer.hr> Date: Fri, 25 Oct 2002 11:45:51 +0200 From: Marko Zec X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: "J. 'LoneWolf' Mattsson" , freebsd-net@freebsd.org, freebsd-arch@freebsd.org Subject: Re: RFC: BSD network stack virtualization References: Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Julian Elischer wrote: > On Thu, 24 Oct 2002, Marko Zec wrote: > > > Julian Elischer wrote: > > > > > > > 11/ why was ng_bridge unsuitable for your use? > > > > Both the native and netgraph bridging code, I believe, were designed with > > the presumption that only one "upper" hook is really needed to establish the > > communication to kernel's single network stack. However, this concept > > doesn't hold on a kernel with multiple network stacks. I just picked the > > native bridging code first and extended it to support hooking to multiple > > "upper" hooks. The similar extensions have yet to be applied to ng_bridge, I > > just didn't have time to implement the same functionality in two different > > frameworks. > > ng_bridge doesn't really distinguish between hooks to upper and lower > detinations. it only knows wha tMAC addresses are seen to come from each > hook and ensures that packets destined to those addresses are sent to > those hooks.. you can have as many > 'upper' hooks as you wish (and there are some uses for that). I just checked (only the functionality, not the ng_bridge code), and it doesn't work properly out of the box for bridging between the virtual network stacks. The inbound broadcast/multicast traffic seems to be delivered properly, but the outbound traffic doesn't pass the bridge when initiated outside the "master" virtual image. I'm just to lazy to dig into the code right now, maybe I'll check it more thoroughly later... Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message