From owner-freebsd-net@FreeBSD.ORG  Mon Sep 19 06:33:29 2005
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
X-Original-To: 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 1BA0416A421
	for <freebsd-net@freebsd.org>; Mon, 19 Sep 2005 06:33:29 +0000 (GMT)
	(envelope-from peter@dataloss.nl)
Received: from useful.dataloss.nl (useful.dataloss.nl [80.84.249.161])
	by mx1.FreeBSD.org (Postfix) with SMTP id 8E7F943D45
	for <freebsd-net@freebsd.org>; Mon, 19 Sep 2005 06:33:26 +0000 (GMT)
	(envelope-from peter@dataloss.nl)
Received: (qmail 36131 invoked by uid 1001); 19 Sep 2005 06:33:22 -0000
Date: Mon, 19 Sep 2005 08:33:22 +0200
From: Peter van Dijk <peter@dataloss.nl>
To: freebsd-net@freebsd.org
Message-ID: <20050919063322.GA17888@dataloss.nl>
References: <20050919.004531.92589257.mshindo@mshindo.net>
	<432D9249.9090202@mac.com> <432DA0AC.8010802@thedarkside.nl>
	<432DA922.5030303@errno.com>
	<200509190606.j8J66JbO095192@banyan.cs.ait.ac.th>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200509190606.j8J66JbO095192@banyan.cs.ait.ac.th>
User-Agent: Mutt/1.4i
Subject: Re: ARP behavior in FreeBSD vs Linux
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
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, 19 Sep 2005 06:33:29 -0000

On Mon, Sep 19, 2005 at 01:06:19PM +0700, Olivier Nicole wrote:
> To me, it seems that FreeBSD does just that too once bridge is enabled.

'Enabling' bridging is a no-op.. However, when you -configure- a
couple of interfaces together in a bridge, they share this behaviour;
but this is correct as bridging is supposed to effectively merge the
chosen interfaces into one. This does not affect any other interfaces,
which makes it substantially different from the Linux behaviour.

Cheers, Peter
-- 
peter@dataloss.nl        | ~ tonight tonight, what is this potion
http://blog.dataloss.nl/ | ~ that makes a fool of me
UnderNet/#clue           |     Wayfinder, fr-025 soundtrack