From owner-freebsd-current@FreeBSD.ORG Wed Oct 19 09:01:40 2005 Return-Path: X-Original-To: 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 BE86616A41F for ; Wed, 19 Oct 2005 09:01:40 +0000 (GMT) (envelope-from konfer@mikulas.com) Received: from s1.vhost.cz (s1.vhost.cz [82.208.27.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A90B43D68 for ; Wed, 19 Oct 2005 09:01:37 +0000 (GMT) (envelope-from konfer@mikulas.com) Received: (qmail 5885 invoked by alias); 19 Oct 2005 11:01:30 +0200 Received: from unknown (HELO localhost) (127.10.10.10) by s1.vhost.cz with SMTP; 19 Oct 2005 11:01:30 +0200 Received: from unknown ([127.0.0.1]) by localhost (s1.vhost.cz [127.0.0.1]) (amavisd-new, port 10628) id 05559-06 for ; Wed, 19 Oct 2005 11:01:30 +0200 (CEST) Received: from unknown (HELO ?172.19.13.144?) (jiri@mikulas.com@195.122.204.153) by s1.vhost.cz with AES256-SHA encrypted SMTP; 19 Oct 2005 11:01:30 +0200 Message-ID: <43560B6A.4070505@mikulas.com> Date: Wed, 19 Oct 2005 11:01:30 +0200 From: Jiri Mikulas User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050429) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at vhost.cz Subject: ath client bridge X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Oct 2005 09:01:40 -0000 Hello I have problem to setup bridging box with ath in client mode and if_bridge When card is in AP mode, everything is ok, but if I want to run card in client mode, bridging is not working. Here are my testing steps: (it's quite long, so I prefer put URL there :) ) http://guli.praha12.net/bridge-test.log It seems to be ath related problem, or am I doing something wrong ? My second question is why chipset 5213 is detected as 5212 (ath0: )? Thaks for help and reply Jiri