From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 19 18:41:34 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76B43106566C for ; Mon, 19 Dec 2011 18:41:34 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (secure.freebsdsolutions.net [69.55.234.48]) by mx1.freebsd.org (Postfix) with ESMTP id 4E9998FC13 for ; Mon, 19 Dec 2011 18:41:33 +0000 (UTC) Received: from jnielsen.socialserve.com ([12.249.176.26]) (authenticated bits=0) by ns1.jnielsen.net (8.14.4/8.14.4) with ESMTP id pBJIfTJ5099233 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 19 Dec 2011 13:41:29 -0500 (EST) (envelope-from lists@jnielsen.net) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: John Nielsen In-Reply-To: Date: Mon, 19 Dec 2011 13:41:24 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <40D93FD7-96BC-4A79-B92A-E19831BA9FB5@jnielsen.net> To: Adrian Chadd X-Mailer: Apple Mail (2.1084) X-DCC--Metrics: ns1.jnielsen.net 1282; Body=2 Fuz1=2 Fuz2=2 X-Virus-Scanned: clamav-milter 0.97.2 at ns1.jnielsen.net X-Virus-Status: Clean Cc: freebsd-wireless@freebsd.org Subject: Re: Is "bssid" parameter to ifconfig supported with ath? X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2011 18:41:34 -0000 On Dec 14, 2011, at 7:46 PM, Adrian Chadd wrote: > Please file another bug and I'll investigate what happened/changed. Submitted as bin/163455. > On 14 December 2011 16:21, John Nielsen wrote: >> I know at some point I was able to do e.g.: >>=20 >> ifconfig wlan0 create wlandev ath0 wlanmode hostap bssid >> ifconfig wlan1 create wlandev ath0 wlanmode hostap bssid >>=20 >> and end up with different MAC addresses on wlan0 and wlan1. Recently = (and possibly for some time) that has not been the case. All wlan = interfaces end up with the MAC address of the parent device, which = (obviously) causes problems if actually using more than one vap. Using = "wlanaddr" and a manual address instead works as expected. >>=20 >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to = "freebsd-wireless-unsubscribe@freebsd.org" >=20