Ticket #52 (closed task: duplicate)

Opened 6 years ago

Last modified 4 years ago

Fix DFS/TPC support in madwifi

Reported by: pjf Assigned to: xmxwx
Priority: high Milestone: 3.0
Component: Madwifi Version:
Severity: blocker Keywords:
Cc:

Description (Last modified by xmxwx)

IEEE 802.11h defines:

  • "dynamic frequency selection (DFS): Facilities mandated to satisfy requirements in some regulatory domains for radar detection and uniform channel spreading in the 5 GHz band. These facilities may also be used for other purposes, such as automatic frequency planning."
  • "transmit power control (TPC): Facilities mandated to satisfy requirements in some regulatory domains for maximum transmit power and transmit power mitigation in the 5 GHz band. These facilities may also be used for other purposes, e.g., reduction of interference, range control reduction of power consumption."

DFS and TPC functionality has been designed to "satisfy regulatory requirements for operation in the 5 GHz band in Europe." (see ETSI EN 301 893); Actually, only a subset of IEEE802.11h needs to be implemented in order to satisfy these requirements.

However, (as mentioned above) majority of DFS and TPC functions are useful for purposes other than complying to the standards. These functions can potentially increase overall network performance and simplify its maintenance.

Some parts of IEEE802.11h require a subset of IEEE802.11d functionality, so the latter should also be considered.

Change History

07/25/06 11:37:16 changed by pjf

  • priority changed from lowest to normal.

08/10/06 11:34:00 changed by pjf

  • milestone changed from Lintrack 0.2rc1 to Lintrack 0.2.

08/12/06 00:13:55 changed by dpc

  • owner changed from xmxwx to dpc.
  • status changed from new to assigned.

08/12/06 00:14:26 changed by dpc

  • owner changed from dpc to xmxwx.
  • status changed from assigned to new.

08/12/06 19:54:03 changed by dpc

  • type changed from defect to task.

08/18/06 15:32:36 changed by pjf

  • priority changed from normal to high.

08/29/06 14:44:31 changed by xmxwx

  • status changed from new to assigned.
  • description changed.

IEEE 802.11h Protocol Implementation Conformance Statement (as of madwifi-ng-!r1705)

SM1Country, Power Constraint, and TPC Report elements included in Beacon and Probe Response framesno/partialmandatory
SM2Spectrum Management Capability bitincorrectmandatory
SM3Power Capability and Supported Channels elements in Association and Reassociation framesno/partialmandatory
SM4Action frame protocol for spectrum management actionsnomandatory
SM5Measurement Requestsnomandatory
SM6Measurement Reportsnomandatory
SM7Quiet intervalnomandatory
SM8Association control based on spectrum management capabilitynomandatory for AP
SM9Association control based on transmit power capabilitynomandatory for AP
SM10Maximum transmit power Levelspartial: only APmandatory
SM11Selection of transmit powerpartial: only APmandatory
SM12Adaptation of transmit powernooptional*
SM13Testing channels for radarsunknown**mandatory
SM14Detecting and discontinuing operations after detection of a radarpartial: only AP / unknown**mandatory
SM15Requesting and reporting of measurementsnomandatory
SM16Autonomous reporting of radarsnomandatory
SM17Independent basic service set (IBSS) dynamic frequency selection (DFS), Element including channel mapnomandatory for IBSS
SM18DFS owner functionnomandatory for IBSS
SM19DFS owner recovery procedurenomandatory for IBSS
SM20Channel switch procedureyes (BSS only)mandatory

* TPC Report is mandatory, but it is already in SM1
** not tested

IEEE 802.11d Protocol Implementation Conformance Statement (as of madwifi-ng-!r1705)

MD1Country Information Elementyes*mandatory
MD2Inclusion of Request Information in the Probe Request framenooptional
MD3Hopping pattern parametersnomandatory for 802.11b
MD4Hopping Pattern Informationnomandatory for 802.11b
MD5Request Information Elementnomandatory
MD5**Entering a Regulatory Domainnomandatory
MD6Determination of the Hopping Patternsnomandatory for 802.11b
MD7Roaming requires Beacon frame with country information elementnomandatory
MD8Actions to be taken upon the receipt of the beaconnomandatory
MD9Ignore improperly formed Request Information Elementnooptional
MD10Hopping Pattern set attributenomandatory for 802.11b

* suboptimal in 5GHz band
** improper numbering in IEEE802.11d PICS Proforma

10/14/06 18:02:28 changed by xmxwx

  • milestone changed from 2.0 to 3.0.

(follow-up: ↓ 11 ) 01/20/07 15:20:29 changed by pjf

Would it be possible to include this in 2.1 release?

02/08/07 13:14:25 changed by xmxwx

  • status changed from assigned to new.

(in reply to: ↑ 9 ) 03/04/07 02:18:50 changed by xmxwx

  • status changed from new to assigned.
  • milestone changed from 3.0 to 2.1.

Replying to pjf:

Would it be possible to include this in 2.1 release?

Probably. #105 will push TPC-related work much further.

I need some idea for testing radar detection (for DFS). Does anyone have a radar signal generator? Any idea where to get one? Maybe I should plan a trip to a nearby airport?

03/04/07 02:47:20 changed by pjf

A radar? Let me think... I guess we could get one on, well... say "russian market" ;-D

Probably, http://www.google.com/search?q=radar+signal+generator is a good starting point.

Oh and a trip to Pyrzowice would be cool as well ;-).

04/30/07 17:43:18 changed by pjf

  • milestone changed from 2.1 to 3.0.

Moving to 3.0 release ;-)

03/09/08 00:05:08 changed by pjf

  • status changed from assigned to closed.
  • resolution set to duplicate.

Folks at MadWiFi project continue the work of Michał on DFS/TPC. Hopefully they release the final version soon so we can integrate it in Lintrack.