From owner-freebsd-current Tue Jul 11 6:35: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from almso1.proxy.att.com (almso1.att.com [192.128.167.69]) by hub.freebsd.org (Postfix) with ESMTP id 3919B37BAFE for ; Tue, 11 Jul 2000 06:35:04 -0700 (PDT) (envelope-from myevmenkin@att.com) Received: from njb140r1.ems.att.com ([135.65.202.58]) by almso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id JAA21446; Tue, 11 Jul 2000 09:35:01 -0400 (EDT) Received: from njb140bh1.ems.att.com by njb140r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id JAA14385; Tue, 11 Jul 2000 09:33:52 -0400 (EDT) Received: by njb140bh1.ems.att.com with Internet Mail Service (5.5.2650.21) id <3352HDTH>; Tue, 11 Jul 2000 09:35:00 -0400 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'Jordan K. Hubbard'" Cc: "'freebsd-current@freebsd.org'" Subject: RE: New version of TAP driver for FreeBSD -current Date: Tue, 11 Jul 2000 09:34:49 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan, > I've looked at this driver and think it looks useful, though I'm a > little concerned about the handling of bridge support. We don't > really encourage users to edit module Makefiles just to enable a given > feature in the compiled module [...] i think that whole ``#ifdef BRIDGE'' section can be removed from the code. ``ether_input'' seems to be take care of it. it also feeds frame to ``bpf'', so it also can be removed. thanks to Nick Sayer for the hint :) i just got e-mail that makes a good point about Ethernet bridging it seems freebsd 4.x bridgin code is somewhat broken.. (it initializes the tables of devices it can bridge at boot time).. thus tap0 isnt available yet.. so basically bridging doesnt work ;( ooops :) will check on it :) seems to me we need some interface to add/remove interfaces to/from bridge. Thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message