From owner-freebsd-current@FreeBSD.ORG  Tue Sep 16 09:48:53 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 1982B16A4B3
	for <freebsd-current@freebsd.org>;
	Tue, 16 Sep 2003 09:48:53 -0700 (PDT)
Received: from ebb.errno.com (ebb.errno.com [66.127.85.87])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5089243FD7
	for <freebsd-current@freebsd.org>;
	Tue, 16 Sep 2003 09:48:52 -0700 (PDT)	(envelope-from sam@errno.com)
Received: from melange.errno.com (melange.errno.com [66.127.85.82])
	(authenticated bits=0)
	by ebb.errno.com (8.12.9/8.12.9) with ESMTP id h8GGmo17019240
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 16 Sep 2003 09:48:51 -0700 (PDT)
	(envelope-from sam@errno.com)
Date: Tue, 16 Sep 2003 09:48:50 -0700
From: Sam Leffler <sam@errno.com>
To: jesse@wingnet.net, freebsd-current@freebsd.org
Message-ID: <324662870.1063705730@melange.errno.com>
In-Reply-To: <bk7c8o$rdo$1@sea.gmane.org>
References: <bk7c8o$rdo$1@sea.gmane.org>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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 16:48:53 -0000

> Is the ath(4) driver, like the wi(4) driver, incapable of performing
> bridging?

Sorry, answered too quickly.  ath and wi have the same restrictions.  You
can use bridging to hookup a wired and wireless network but not two
wireless networks.  I can't tell from your posting what you are trying to
do.

	Sam