From owner-freebsd-current@FreeBSD.ORG Wed Jan 12 02:51:51 2005 Return-Path: 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 BF8E316A4CE for ; Wed, 12 Jan 2005 02:51:51 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62D8D43D58 for ; Wed, 12 Jan 2005 02:51:51 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.92] ([66.127.85.92]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j0C2poWi024526 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Jan 2005 18:51:50 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41E490D4.70504@errno.com> Date: Tue, 11 Jan 2005 18:52:04 -0800 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ben Becker References: <38d37be7050111092379f2a898@mail.gmail.com> In-Reply-To: <38d37be7050111092379f2a898@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Atheros and SIS bridging problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2005 02:51:51 -0000 Ben Becker wrote: > Hello, > > I'm working on a FreeBSD-based bridge with one Atheros 5004X (5212) > wireless interface and one SIS Ethernet interface. The Atheros > interface is associated to an access point running hostap (another > FreeBSD box) while the Ethernet port is connected to my laptop. > Here's a quick outline: > > [Laptop]--------(sis0)-[FreeBSD Bridge]-(ath0)--------[FreeBSD AP] > > There seems to be a problem with bridging ath0 and sis0. I have 1 IP > assigned to ath0 which is 192.168.1.3, and I've sysctl'd > 'net.link.ether.bridge.enable=1' and > 'net.link.ether.bridge.config=ath0,sis0'. From the bridge, I can ping > the AP (192.168.1.1) and the laptop (192.168.1.5). However I can't > ping from the laptop to the AP or from the AP to the laptop. > > When I sysctl net.link.ether.bridge.debug on, I notice something > strange. Packets to and from the AP have a destination of BDG_UNKNOWN > until the bridge shows 'bridge_in: new addr xx.xx.xx.xx.xx.xx at 3121 > for ath0'. At that point, I'm able to send and receive a few packets > through the link, but it's very inconsistent. However, the bridge > debug info now shows the proper interfaces as the destination. This > only lasts about 20 seconds until I get a 'bdg_timeout: flushing stale > entry 3121' at which point everything gets forwarded to BDG_UNKNOWN > again and no traffic gets passed. Wtihin a few minutes I get the > 'bridge_in: new addr' message again and the cycle repeats. The amount > of time seems to vary, though. > > I've tried this on current, 5.3 and 5.2.1. The wireless interface is > configured without WEP and I've tried 11b and 11g mode. The AP is a > 5.2.1 system with the same type of Atheros card in non-bridged 11b > hostap mode. I can't think of any additional debug info other than > the bridge debug output, so please let me know if there is anything > else I can supply to help troubleshoot this issue. Also, has anybody > successfully set up a bridge like this in the past? This doesn't work because the wireless interface will not receive frames from the ap destined for the laptop. You basically need/want to tunnel the laptop frames which requires support that's not currently in the system. Sam