Search Linux Wireless

Re: [PATCH 04/12] iwlwifi: document scan command

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> +/**
> + * struct iwl3945_scan_channel - entry in REPLY_SCAN_CMD channel table
> + *
> + * One for each channel in the scan list.
> + * Each channel can independently select:
> + * 1)  SSID for directed active scans
> + * 2)  Txpower setting (for rate specified within Tx command)
> + * 3)  How long to stay on-channel (behavior may be modified by quiet_time,
> + *     quiet_plcp_th, good_CRC_th)

This reminds me. How did you arrive at the dwell time? With hostapd
running on b43 I've frequently seen the dwell time being too low:

iwl4965 will transmit a probe request and go to the next channel before
hostapd sends the probe response, iwl4965 still sees the response, but
the b43 card never sees the ACK because it's receiver isn't quite as
good as the iwl4965 receiver.

Are there any restrictions in IEEE 802.11 on how fast probe responses
must be transmitted?

johannes

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux