From owner-freebsd-net@FreeBSD.ORG  Mon Mar 21 04:08:03 2005
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5E7BD16A4CE
	for <freebsd-net@freebsd.org>; Mon, 21 Mar 2005 04:08:03 +0000 (GMT)
Received: from roadrunner.metaflex.com (roadrunner.metaflex.com
	[209.246.232.249])
	by mx1.FreeBSD.org (Postfix) with SMTP id A6C3843D49
	for <freebsd-net@freebsd.org>; Mon, 21 Mar 2005 04:08:02 +0000 (GMT)
	(envelope-from nlandys@atrask.lt)
Received: (qmail 4547 invoked by uid 511); 21 Mar 2005 04:07:45 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 21 Mar 2005 04:07:45 -0000
Date: Sun, 20 Mar 2005 20:07:45 -0800 (PST)
From: Nerius Landys <nlandys@atrask.lt>
X-X-Sender: nlandys@roadrunner.metaflex.com
To: Julian Elischer <julian@elischer.org>
In-Reply-To: <423A86D1.5090604@elischer.org>
Message-ID: <Pine.LNX.4.62.0503202005220.4544@roadrunner.metaflex.com>
References: <Pine.SGI.4.58.0503161125380.15799222@be-research.ucsd.edu>
 <423A86D1.5090604@elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
cc: Nerius Landys <nlandys@bioeng.ucsd.edu>
cc: freebsd-net@freebsd.org
Subject: Re: transparent bridge and ARP proxy confusion
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2005 04:08:03 -0000

> what happens with netgraph bridging?
> (/usr/share/examples/netgraph/....)

With netgraph bridging (using the ether.bridge example) everything works 
as expected - the "local" interface promiscuously uses the same MAC 
address out every physical interface.