#623: Scanning incorrect channels in Adhoc mode with r1552
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: other | Version: trunk
Resolution: | Keywords:
Patch_attached: 0 |
-------------------------------------+--------------------------------------
Comment (by [EMAIL PROTECTED]):
I've had a look at the driver source, and unless I'm mistaken the chances
of it scanning any channel other than 10 and 11 has been practically nill
since the introduction of source:/trunk/net80211/ieee80211_scan_sta.c back
in r1775. Does anyone know why the compatibility mode for Ad-Hoc only
uses channels 10 and 11 for b? The creation of the list of channels to
scan for Ad-Hoc mode is done in adhoc_start and above that we have the
following code (and comment) starting on line 1132 of r1520 (the last
modification):
{{{
/*
* Adhoc mode-specific support.
*/
static const u_int16_t adhocWorld[] = /* 36, 40, 44, 48 */
{ 5180, 5200, 5220, 5240 };
static const u_int16_t adhocFcc3[] = /* 36, 40, 44, 48 145,
149, 153, 157, 161, 165 */
{ 5180, 5200, 5220, 5240, 5725, 5745, 5765, 5785, 5805, 5825 };
static const u_int16_t adhocMkk[] = /* 34, 38, 42, 46 */
{ 5170, 5190, 5210, 5230 };
static const u_int16_t adhoc11b[] = /* 10, 11 */
{ 2457, 2462 };
}}}
Any comments?
--
Ticket URL: <http://madwifi.org/ticket/623>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
