Re: forcing 802.11a association
- From: dragoran <drago01 gmail com>
- To: Derek Atkins <warlord MIT EDU>
- Cc: James Ketrenos <jketreno linux intel com>, Zhu Yi <yi zhu intel com>, networkmanager-list gnome org, ipw3945-devel <ipw3945-devel lists sourceforge net>
- Subject: Re: forcing 802.11a association
- Date: Tue, 26 Jun 2007 12:32:15 +0200
Derek Atkins wrote:
Dan Williams <dcbw redhat com> writes:
Like I said, "the BSSID is the same on both (a) and (b/g)", so, yes,
my AP (a D-Link) has the same BSSID/MAC on both bands. I do not
believe there is any way for me to change this. In fact, it uses
the same BSSID/MAC on ALL three "interfaces" (802.3, 802.11a, and 802.11b/g)
Whee. So drivers internally now have to differentiate a specific access
point based on the (band, BSSID, SSID) tuple, which I'm pretty sure not
many do.
Um, all the drivers have ALWAYS done this. The iwl3945 is the first
driver NOT to differentiate them! The madwifi and the ipw3945 drivers
certain work "correctly" in my situation.
is this a known bug (feature?) in the iwlwifi drivers / ratescale alg ?
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]