From owner-freebsd-current@FreeBSD.ORG  Tue Sep 16 11:16:58 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9EDFB16A4B3
	for <freebsd-current@freebsd.org>;
	Tue, 16 Sep 2003 11:16:58 -0700 (PDT)
Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CAE6543FA3
	for <freebsd-current@freebsd.org>;
	Tue, 16 Sep 2003 11:16:56 -0700 (PDT)
	(envelope-from julian@elischer.org)
Received: from interjet.elischer.org ([12.233.125.100])
          by attbi.com (rwcrmhc13) with ESMTP
          id <2003091618165501500bv1ime>; Tue, 16 Sep 2003 18:16:56 +0000
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA53842;
	Tue, 16 Sep 2003 11:16:55 -0700 (PDT)
Date: Tue, 16 Sep 2003 11:16:54 -0700 (PDT)
From: Julian Elischer <julian@elischer.org>
To: Sam Leffler <sam@errno.com>
In-Reply-To: <329513875.1063710581@melange.errno.com>
Message-ID: <Pine.BSF.4.21.0309161114590.52605-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: jesse@wingnet.net
cc: freebsd-current@freebsd.org
Subject: Re: atheros (ath) driver bridging
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2003 18:16:58 -0000

I'm not sure what I typed there but what I meant to say was....
"At one stage the wi driver could not be put in promiscuous mode and 
the bridging code required that. Most people still think this is true."

On Tue, 16 Sep 2003, Sam Leffler wrote:

> > I think what he meant was that at on state was known (I don't know the
> > current state) that as the wi could not be but in promiscuous mode it
> > could not be used for bridging..  Bridging requires promiscuous mode
> > (or some very tricky proxy-arp stuff).
> 
> You can put wi (and ath) in promiscuous mode.  The bridge manual page is
> wrong and I will fix it.
> 
> 	Sam
> 
>