From owner-freebsd-current@FreeBSD.ORG Thu Jan 13 22:47:15 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 C310716A4CE for ; Thu, 13 Jan 2005 22:47:15 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74D9743D2F for ; Thu, 13 Jan 2005 22:47:15 +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 j0DMlCWi036381 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Jan 2005 14:47:13 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41E6FA7F.2070406@errno.com> Date: Thu, 13 Jan 2005 14:47:27 -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> <20050113065003.GA2336@tongi.org> <38d37be7050113143868516018@mail.gmail.com> In-Reply-To: <38d37be7050113143868516018@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: Thu, 13 Jan 2005 22:47:16 -0000 Ben Becker wrote: > On Thu, 13 Jan 2005 14:50:03 +0800, Clive Lin wrote: > >>On Tue, Jan 11, 2005 at 09:23:08AM -0800, Ben Becker wrote: >> >>>[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. >> >>Hi, >> >> Have you tried ng_bridge(4)? My own experience is similar with >>yours, and the problem like yours is sovled via ng_bridge(4). Example >>scripts to setup ng_bridge(4) is at >>/usr/share/examples/netgraph/ether.bridge. >> > > > Thank you for the idea, but there are still problems that appear to be > related to net80211 or the ath driver. I did get a little further in > debugging this with ng_bridge, though. Packets from the remote > computer actually go through the bridge and get to the AP. I enabled > debug mode for ath0 on the AP(ifconfig ath0 debug), and here's what I > get when I try to send a packet from a remote computer that goes > through the bridge (hand transcribed): > > ath0: station 00:0c:6e:a7:47:3b deauthenticate (reason 6) > ath0: sending deauth to 00:0c:6e:a7:47:3b on channel 11 > ath0: station 00:0c:6e:a7:47:3b disassociate (reason 7) > ath0: sending disassoc to 00:0c:6e:a7:47:3b on channel 11 > ath0: received auth from 00:0b:6b:33:08:1a rssi 22 > ath0: sending auth to 00:0b:6b:33:08:1a on channel 11 > ath0: station already 00:0b:6b:33:08:1a authenticated > ath0: received assoc_req from 00:0b:6b:33:08:1a rssi 24 > ath0: sending assoc_resp to 00:0b:6b:33:08:1a on channel 11 > ath0: station already 00:0b:6b:33:08:1a associated > > 00:0c:6e:a7:47:3b is the MAC address of the remote computer's rl0 interface. > 00:0b:6b:33:08:1a is the MAC address of the bridge's ath0 interface. > > It appears as though ath0 on the AP sees the packet, but thinks the > remote computer is actually a station that isn't associated. Am I > correct here? I'm not very familiar with the net80211 code, but would > it be possible to simply allow the AP to receive and transmit packets > to/from layer 2 address that aren't necessarily associated? > > I know Sam recommended tunneling, but I'd like to essentially have a > system that works like those Ethernet-to-Wireless bridge devices (i.e. > D-Link DWL-810, newer Linksys WAP11). Am I dreaming -- is this even > possible? The more I look into it there doesn't seem to be any > standard way of creating an 'Ethernet-to-Wireless' bridge. I'd like > to hear from the net80211 pros what the best (if any) solution would > be for 'Ethernet-to-Wireless' bridging. Those devices tunnel using a 4-address 802.11 format specifically designed for this. Like I said, what you need is not currently supported. The encapsulation work is actually very simple; the hard bit is how everything ties into the system. I happen to be working on this but results will not be available for a while. Sam