From owner-freebsd-current@FreeBSD.ORG  Tue Sep 16 10:46:02 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 79CED16A4E1
	for <freebsd-current@freebsd.org>;
	Tue, 16 Sep 2003 10:46:02 -0700 (PDT)
Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7538F43FAF
	for <freebsd-current@freebsd.org>;
	Tue, 16 Sep 2003 10:46:01 -0700 (PDT)
	(envelope-from julian@elischer.org)
Received: from interjet.elischer.org ([12.233.125.100])
          by attbi.com (rwcrmhc11) with ESMTP
          id <200309161746000130036gkne>; Tue, 16 Sep 2003 17:46:01 +0000
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA53556;
	Tue, 16 Sep 2003 10:46:00 -0700 (PDT)
Date: Tue, 16 Sep 2003 10:45:58 -0700 (PDT)
From: Julian Elischer <julian@elischer.org>
To: Sam Leffler <sam@errno.com>
In-Reply-To: <324565320.1063705632@melange.errno.com>
Message-ID: <Pine.BSF.4.21.0309161043150.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 17:46:02 -0000

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).

On Tue, 16 Sep 2003, Sam Leffler wrote:

> > Is the ath(4) driver, like the wi(4) driver, incapable of performing
> > bridging?
> 
> Yes.  Bridging happens outside the operation of the driver.
> 
> 	Sam
> 
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>