齋木 理(OSAMU SAIKI | 20 Jul 18:25 2014

??? AR9565 ath9k hostapd not run

HI.

 

please help me!!

 

 

hostapd -Bd /etc/hostapd/hostapd.conf                                                                                 

random: Trying to read entropy from /dev/random

Configuration file: /etc/hostapd/hostapd.conf

ctrl_interface_group=0

nl80211: Could not add multicast membership for vendor events: -2 (No such file or directory)

rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0

nl80211: TDLS supported

nl80211: TDLS external setup

nl80211: Supported cipher 00-0f-ac:1

nl80211: Supported cipher 00-0f-ac:5

nl80211: Supported cipher 00-0f-ac:2

nl80211: Supported cipher 00-0f-ac:4

nl80211: Supported cipher 00-0f-ac:6

nl80211: Using driver-based off-channel TX

nl80211: Use separate P2P group interface (driver advertised support)

nl80211: interface wlan0 in phy phy0

nl80211: Set mode ifindex 3 iftype 3 (AP)

nl80211: Setup AP(wlan0) - device_ap_sme=0 use_monitor=0

nl80211: Subscribe to mgmt frames with AP handle 0x9b9f590

nl80211: Register frame type=0xb0 nl_handle=0x9b9f590 match=

nl80211: Register frame type=0x0 nl_handle=0x9b9f590 match=

nl80211: Register frame type=0x20 nl_handle=0x9b9f590 match=

nl80211: Register frame type=0xa0 nl_handle=0x9b9f590 match=

nl80211: Register frame type=0xc0 nl_handle=0x9b9f590 match=

nl80211: Register frame type=0xd0 nl_handle=0x9b9f590 match=

nl80211: Register frame type=0x40 nl_handle=0x9b9f590 match=

nl80211: Add own interface ifindex 5

nl80211: Add own interface ifindex 3

nl80211: Adding interface wlan0 into bridge br0

phy: phy0

BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)

wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE

Previous country code 00, new country code JP

Continue interface setup after channel list update

ctrl_iface not configured!

 

 

 

cat /etc/hostapd/hostapd.conf

# ==== NETWORK INTERFACES ============================

interface=wlan0

bridge=br0

ctrl_interface=/var/run/wpa_supplicant

 

# ==== DRIVERS =======================================

# "Generic" driver

driver=nl80211

 

 

# ==== BASIC ACCESS POINT SETTINGS ===================

ssid=XXXX

channel=1

hw_mode=g

 

country_code=JP

ieee80211d=1

 

wme_enabled=1

ieee80211n=1

 

 

# ==== CONTROL PROGRAM ACCESS ========================

# Control program access

ctrl_interface=/var/run/hostapd

# Only allow access by root

ctrl_interface_group=0

 

 

# ==== DEVICE CONFIGURATIONS =========================

# Atheros Communications, Inc. AR9565 802.11n (TP-Link TL-WN722N)

ht_capab=[HT40+][SHORT-GI-20][SHORT-GI-40][RX-STBC1][DSSS_CCK-40]

 

 

# ==== AUTHENTICATION AND ENCRYPTION =================

macaddr_acl=0

auth_algs=1

ignore_broadcast_ssid=0

wpa=2

wpa_passphrase=XXXXXX

wpa_key_mgmt=WPA-PSK

wpa_pairwise=TKIP

rsn_pairwise=CCMP

 

uname -r                                                                                                                                   

3.13.0-30-generic

 

lspci | grep Wireless

0b:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)    

 

 

modinfo ath9k

filename:       /lib/modules/3.13.0-30-generic/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko

license:        Dual BSD/GPL

description:    Support for Atheros 802.11n wireless LAN cards.

author:         Atheros Communications

srcversion:     470F4A9FC9506B4AE23CF37

alias:          platform:qca955x_wmac

alias:          platform:ar934x_wmac

alias:          platform:ar933x_wmac

alias:          platform:ath9k

alias:          pci:v0000168Cd00000036sv*sd*bc*sc*i*

alias:          pci:v0000168Cd00000036sv0000185Fsd00003027bc*sc*i*

alias:          pci:v0000168Cd00000036sv00001B9Asd00002810bc*sc*i*

alias:          pci:v0000168Cd00000036sv0000144Fsd00007202bc*sc*i*

alias:          pci:v0000168Cd00000036sv00001A3Bsd00002130bc*sc*i*

alias:          pci:v0000168Cd00000036sv000011ADsd00000612bc*sc*i*

alias:          pci:v0000168Cd00000036sv000011ADsd00000652bc*sc*i*

alias:          pci:v0000168Cd00000036sv000011ADsd00000642bc*sc*i*

alias:          pci:v0000168Cd00000036sv0000168Csd0000302Cbc*sc*i*

alias:          pci:v0000168Cd00000036sv0000168Csd00003027bc*sc*i*

alias:          pci:v0000168Cd00000036sv0000144Dsd0000411Ebc*sc*i*

alias:          pci:v0000168Cd00000036sv0000144Dsd0000411Dbc*sc*i*

alias:          pci:v0000168Cd00000036sv0000144Dsd0000411Cbc*sc*i*

alias:          pci:v0000168Cd00000036sv0000144Dsd0000411Bbc*sc*i*

alias:          pci:v0000168Cd00000036sv0000144Dsd0000411Abc*sc*i*

alias:          pci:v0000168Cd00000036sv00001028sd0000020Ebc*sc*i*

alias:          pci:v0000168Cd00000036sv0000103Csd0000217Fbc*sc*i*

alias:          pci:v0000168Cd00000036sv0000103Csd000018E3bc*sc*i*

alias:          pci:v0000168Cd00000036sv000017AAsd00003026bc*sc*i*

alias:          pci:v0000168Cd00000036sv00001A3Bsd0000213Abc*sc*i*

alias:          pci:v0000168Cd00000036sv000011ADsd00000662bc*sc*i*

alias:          pci:v0000168Cd00000036sv000011ADsd00000672bc*sc*i*

alias:          pci:v0000168Cd00000036sv000011ADsd00000622bc*sc*i*

alias:          pci:v0000168Cd00000036sv0000185Fsd00003028bc*sc*i*

alias:          pci:v0000168Cd00000036sv0000105Bsd0000E069bc*sc*i*

alias:          pci:v0000168Cd00000036sv0000168Csd0000302Bbc*sc*i*

alias:          pci:v0000168Cd00000036sv0000168Csd00003026bc*sc*i*

alias:          pci:v0000168Cd00000036sv0000168Csd00003025bc*sc*i*

alias:          pci:v0000168Cd00000036sv00001B9Asd00002812bc*sc*i*

alias:          pci:v0000168Cd00000036sv00001B9Asd00002811bc*sc*i*

alias:          pci:v0000168Cd00000036sv000011ADsd00006671bc*sc*i*

alias:          pci:v0000168Cd00000036sv000011ADsd00000632bc*sc*i*

alias:          pci:v0000168Cd00000036sv0000185Fsd0000A119bc*sc*i*

alias:          pci:v0000168Cd00000036sv0000105Bsd0000E068bc*sc*i*

alias:          pci:v0000168Cd00000036sv00001A3Bsd00002176bc*sc*i*

alias:          pci:v0000168Cd00000036sv0000168Csd00003028bc*sc*i*

alias:          pci:v0000168Cd00000037sv*sd*bc*sc*i*

alias:          pci:v0000168Cd00000034sv*sd*bc*sc*i*

alias:          pci:v0000168Cd00000034sv000010CFsd00001783bc*sc*i*

alias:          pci:v0000168Cd00000034sv000014CDsd00000064bc*sc*i*

alias:          pci:v0000168Cd00000034sv000014CDsd00000063bc*sc*i*

alias:          pci:v0000168Cd00000034sv0000103Csd00001864bc*sc*i*

alias:          pci:v0000168Cd00000034sv000011ADsd00006641bc*sc*i*

alias:          pci:v0000168Cd00000034sv000011ADsd00006631bc*sc*i*

alias:          pci:v0000168Cd00000034sv00001043sd0000850Ebc*sc*i*

alias:          pci:v0000168Cd00000034sv00001A3Bsd00002110bc*sc*i*

alias:          pci:v0000168Cd00000034sv00001969sd00000091bc*sc*i*

alias:          pci:v0000168Cd00000034sv000017AAsd00003214bc*sc*i*

alias:          pci:v0000168Cd00000034sv0000168Csd00003117bc*sc*i*

alias:          pci:v0000168Cd00000034sv000011ADsd00006661bc*sc*i*

alias:          pci:v0000168Cd00000034sv00001A3Bsd00002116bc*sc*i*

alias:          pci:v0000168Cd00000033sv*sd*bc*sc*i*

alias:          pci:v0000168Cd00000032sv*sd*bc*sc*i*

alias:          pci:v0000168Cd00000032sv00001043sd0000850Dbc*sc*i*

alias:          pci:v0000168Cd00000032sv00001B9Asd00001C01bc*sc*i*

alias:          pci:v0000168Cd00000032sv00001B9Asd00001C00bc*sc*i*

alias:          pci:v0000168Cd00000032sv00001A3Bsd00001F95bc*sc*i*

alias:          pci:v0000168Cd00000032sv00001A3Bsd00001195bc*sc*i*

alias:          pci:v0000168Cd00000032sv00001A3Bsd00001F86bc*sc*i*

alias:          pci:v0000168Cd00000032sv00001A3Bsd00001186bc*sc*i*

alias:          pci:v0000168Cd00000032sv00001B9Asd00002001bc*sc*i*

alias:          pci:v0000168Cd00000032sv00001B9Asd00002000bc*sc*i*

alias:          pci:v0000168Cd00000032sv0000144Fsd00007197bc*sc*i*

alias:          pci:v0000168Cd00000032sv0000105Bsd0000E04Fbc*sc*i*

alias:          pci:v0000168Cd00000032sv0000105Bsd0000E04Ebc*sc*i*

alias:          pci:v0000168Cd00000032sv000011ADsd00006628bc*sc*i*

alias:          pci:v0000168Cd00000032sv000011ADsd00006627bc*sc*i*

alias:          pci:v0000168Cd00000032sv00001C56sd00004001bc*sc*i*

alias:          pci:v0000168Cd00000032sv00001A3Bsd00002100bc*sc*i*

alias:          pci:v0000168Cd00000032sv00001A3Bsd00002C97bc*sc*i*

alias:          pci:v0000168Cd00000032sv000017AAsd00003219bc*sc*i*

alias:          pci:v0000168Cd00000032sv000017AAsd00003218bc*sc*i*

alias:          pci:v0000168Cd00000032sv0000144Dsd0000C708bc*sc*i*

alias:          pci:v0000168Cd00000032sv0000144Dsd0000C680bc*sc*i*

alias:          pci:v0000168Cd00000032sv0000144Dsd0000C706bc*sc*i*

alias:          pci:v0000168Cd00000032sv0000144Dsd0000410Fbc*sc*i*

alias:          pci:v0000168Cd00000032sv0000144Dsd0000410Ebc*sc*i*

alias:          pci:v0000168Cd00000032sv0000144Dsd0000410Dbc*sc*i*

alias:          pci:v0000168Cd00000032sv0000144Dsd00004106bc*sc*i*

alias:          pci:v0000168Cd00000032sv0000144Dsd00004105bc*sc*i*

alias:          pci:v0000168Cd00000032sv0000185Fsd00003027bc*sc*i*

alias:          pci:v0000168Cd00000032sv0000185Fsd00003119bc*sc*i*

alias:          pci:v0000168Cd00000032sv0000168Csd00003122bc*sc*i*

alias:          pci:v0000168Cd00000032sv0000168Csd00003119bc*sc*i*

alias:          pci:v0000168Cd00000032sv0000105Bsd0000E075bc*sc*i*

alias:          pci:v0000168Cd00000032sv00001A3Bsd00002152bc*sc*i*

alias:          pci:v0000168Cd00000032sv00001A3Bsd0000126Abc*sc*i*

alias:          pci:v0000168Cd00000032sv00001A3Bsd00002126bc*sc*i*

alias:          pci:v0000168Cd00000032sv00001A3Bsd00001237bc*sc*i*

alias:          pci:v0000168Cd00000032sv00001A3Bsd00002086bc*sc*i*

alias:          pci:v0000168Cd00000030sv*sd*bc*sc*i*

alias:          pci:v0000168Cd0000002Esv*sd*bc*sc*i*

alias:          pci:v0000168Cd0000002Dsv*sd*bc*sc*i*

alias:          pci:v0000168Cd0000002Csv*sd*bc*sc*i*

alias:          pci:v0000168Cd0000002Bsv*sd*bc*sc*i*

alias:          pci:v0000168Cd0000002Bsv00001A3Bsd00002C37bc*sc*i*

alias:          pci:v0000168Cd0000002Asv000010CFsd00001536bc*sc*i*

alias:          pci:v0000168Cd0000002Asv000010CFsd0000147Dbc*sc*i*

alias:          pci:v0000168Cd0000002Asv000010CFsd0000147Cbc*sc*i*

alias:          pci:v0000168Cd0000002Asv0000185Fsd0000309Dbc*sc*i*

alias:          pci:v0000168Cd0000002Asv00001A32sd00000306bc*sc*i*

alias:          pci:v0000168Cd0000002Asv000011ADsd00006642bc*sc*i*

alias:          pci:v0000168Cd0000002Asv000011ADsd00006632bc*sc*i*

alias:          pci:v0000168Cd0000002Asv0000105Bsd0000E01Fbc*sc*i*

alias:          pci:v0000168Cd0000002Asv00001A3Bsd00001C71bc*sc*i*

alias:          pci:v0000168Cd0000002Asv*sd*bc*sc*i*

alias:          pci:v0000168Cd00000029sv*sd*bc*sc*i*

alias:          pci:v0000168Cd00000027sv*sd*bc*sc*i*

alias:          pci:v0000168Cd00000024sv*sd*bc*sc*i*

alias:          pci:v0000168Cd00000023sv*sd*bc*sc*i*

depends:        ath9k_hw,mac80211,ath9k_common,cfg80211,ath

intree:         Y

vermagic:       3.13.0-30-generic SMP mod_unload modversions 686

signer:         Magrathea: Glacier signing key

sig_key:        6C:4C:CC:D2:3E:C5:78:FE:E9:B9:E0:C7:E2:67:0C:91:F2:E0:A0:AC

sig_hashalgo:   sha512

parm:           debug:Debugging mask (uint)

parm:           nohwcrypt:Disable hardware encryption (int)

parm:           blink:Enable LED blink on activity (int)

parm:           btcoex_enable:Enable wifi-BT coexistence (int)

parm:           bt_ant_diversity:Enable WLAN/BT RX antenna diversity (int)

parm:           ps_enable:Enable WLAN PowerSave (int)

 

 

hostapd -v

hostapd v2.1

User space daemon for IEEE 802.11 AP management,

IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator

Copyright (c) 2002-2014, Jouni Malinen <j <at> w1.fi> and contributors

 

                                                       Haru  Thank you

_______________________________________________
ath9k-devel mailing list
ath9k-devel <at> lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Kamran Nishat | 19 Jul 23:14 2014
Picon

idle time or (Tx + Rx)Time

Hi,
Is there a way or any debugs entry to find for how much time HW has been in idle state. Or can I estimate Tx and Rx time for HW?


Regards,

Kamran
_______________________________________________
ath9k-devel mailing list
ath9k-devel <at> lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Benoit Taine | 18 Jul 17:26 2014
Picon

[PATCH 0/25] Replace DEFINE_PCI_DEVICE_TABLE macro use

We should prefer `const struct pci_device_id` over
`DEFINE_PCI_DEVICE_TABLE` to meet kernel coding style guidelines.
This issue was reported by checkpatch.

A simplified version of the semantic patch that makes this change is as
follows (http://coccinelle.lip6.fr/):

// <smpl>

 <at>  <at> 
identifier i;
declarer name DEFINE_PCI_DEVICE_TABLE;
initializer z;
 <at>  <at> 

- DEFINE_PCI_DEVICE_TABLE(i)
+ const struct pci_device_id i[]
= z;

// </smpl>

I have 103 patches ready, and will only send a few for you to judge if
it is useful enough, and to prevent from spamming too much.

Thanks.
Le Tran Dat | 17 Jul 11:18 2014
Picon

ath9k with openwrt - can not enable wifi

Hi list,

I use openwrt trunk at r41670 to compile ath9k (default make menuconfig) with LuCi enable.

svn info
Path: .
Repository Root: svn://svn.openwrt.org/openwrt
Repository UUID: 3c298f89-4303-0410-b956-a3cf2f4a3e73
Revision: 41670

I can see OpenWrt default ssid from LuCI webpage but I can not enable it from LuCI.

$ iw phy

Wiphy phy0
        max # scan SSIDs: 4
        max scan IEs length: 2257 bytes
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports AP-side u-APSD.
        Device supports T-DLS.
        Available Antennas: TX 0x3 RX 0x3
        Configured Antennas: TX 0x3 RX 0x3
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * WDS
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO
        Band 1:
                Capabilities: 0x11ef
                        RX LDPC
                        HT20/HT40
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-15
                Frequencies:
                        * 2412 MHz [1] (30.0 dBm)
                        * 2417 MHz [2] (30.0 dBm)
                        * 2422 MHz [3] (30.0 dBm)
                        * 2427 MHz [4] (30.0 dBm)
                        * 2432 MHz [5] (30.0 dBm)
                        * 2437 MHz [6] (30.0 dBm)
                        * 2442 MHz [7] (30.0 dBm)
                        * 2447 MHz [8] (30.0 dBm)
                        * 2452 MHz [9] (30.0 dBm)
                        * 2457 MHz [10] (30.0 dBm)
                        * 2462 MHz [11] (30.0 dBm)
                        * 2467 MHz [12] (disabled)
                        * 2472 MHz [13] (disabled)
                        * 2484 MHz [14] (disabled)
        valid interface combinations:
                 * #{ managed, WDS } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client, P2P-GO } <= 1, #{ IBSS } <= 1,
                   total <= 2048, #channels <= 1, STA/AP BI must match
        HT Capability overrides:
                 * MCS: ff ff ff ff ff ff ff ff ff ff
                 * maximum A-MSDU length
                 * supported channel width
                 * short GI for 40 MHz
                 * max A-MPDU length exponent
                 * min MPDU start spacing

root <at> OpenWrt:/lib/wifi# cat /etc/config/wireless

config wifi-device 'radio0'
        option type 'mac80211'
        option channel '11'
        option hwmode '11g'
        option path 'platform/qca953x_wmac'
        option htmode 'HT20'
        option txpower '30'
        option country 'US'

config wifi-iface
        option device 'radio0'
        option network 'lan'
        option ssid 'OpenWrt'
        option mode 'ap'
        option encryption 'none'

Thanks,
Dat
_______________________________________________
ath9k-devel mailing list
ath9k-devel <at> lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Andres | 16 Jul 20:22 2014
Picon

Monitor Mode issue

Hi,

I'm getting lots of invalid frames when using a TL-WN722N(AR9271) in monitor mode. I couldn't find a bug report about this, is there a fix or someone knows if this is a known issue?

Regards

Andrés
_______________________________________________
ath9k-devel mailing list
ath9k-devel <at> lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
mahaveer gupta | 14 Jul 14:15 2014
Picon

Matching spectral scan results with data packets

Hi All,

I am trying to map the rssi of received packets to the associated spectral scan results. - http://wireless.kernel.org/en/users/Drivers/ath9k/spectral_scan/

Rssi is reported on a per packet basis, but spectral scan results are not. One simple way to match packet-rssi with corresponding spectral components is to match the time-stamp of the received packets and spectral scan results.

Please let me know if the matching will be accurate without much errors, or suggestions if you have a better idea.

--
Thanks,
M
_______________________________________________
ath9k-devel mailing list
ath9k-devel <at> lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Hosam Hittini | 8 Jul 08:20 2014
Picon

AR9280 AP mode - 5GHz band

Hello there,

I have this dual band wireless adapter https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-dual-band-usb-adapter-gnu-linux-tpe-nusbdb and it uses AR9280 chipset for the 5GHz communication
It’s using ath9k driver; I have Ubuntu 13.10 running 3.11 kernel and the adapter worked out of the box
I’m using hostapd to configure the adapter as a software AP
When I tried to configure the adapter as an AP on the 2.4GHz channels it worked fine
When tried the 5GHz channels it gives me the following error
channel [1] (40) is disabled for use in AP mode, flags: 0x77
wlan1: IEEE 802.11 Configured channel (40) not found from the channel list of current mode (2) IEEE 802.11a
wlan1: IEEE 802.11 Hardware does not support configured channel
In addition, iw list command shows that the 5GHz channels have the “passive scanning” and “no IBSS” flags
I can associate with an AP on the 5GHz though
How to solve that
Thank you

Regards,
Eng. Hosam Hittini

_______________________________________________
ath9k-devel mailing list
ath9k-devel <at> lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Matteo Danieletto | 7 Jul 11:41 2014
Picon

[INFO] Understand queues file for ath9k and atk9k_htc


Dear all,

I am trying to understand the output furnished by

cat ath9k/queues :

(VO): qnum: 0 qdepth:  0 ampdu-depth:  0 pending:   0 stopped: 0

(VI): qnum: 1 qdepth:  0 ampdu-depth:  0 pending:   0 stopped: 0

(BE): qnum: 2 qdepth: 59 ampdu-depth:  0 pending:  59 stopped: 0

(BK): qnum: 3 qdepth:  0 ampdu-depth:  0 pending:   0 stopped: 0

------------------------------------------------------------------------------------

For VO VI and so on I know the meaning (802.11e).

However, I wish to understand the difference between qdepth and pending. 

Moreover, I have an USB adapter with ath9k_htc modules.

In this case I have the following output:

Mgmt endpoint :          0

Cab endpoint :          0

Data BE endpoint :          0

Data BK endpoint :          0

Data VI endpoint :          0

Data VO endpoint :          0

Failed queue :          0

Queued count :          0


Is Data BE endpoint  equal to BE qdepth and/or pending?

Thank you a lot

Regards

Matteo



--
Matteo Danieletto
_______________________________________________
ath9k-devel mailing list
ath9k-devel <at> lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
mahaveer gupta | 7 Jul 02:21 2014
Picon

ad-hoc mode

Hello,

I am trying to do some experiments with a few devices in the ad-hoc mode.

However, I observe that after a while, the connectivity drops abruptly and the only way to restore it seems to be reloading the driver.

The node on which the connectivity has dropped sends out ARP requests when I try to ping another node. The other node promptly responds with ARP reply. However, the first node doesn't seem to be getting it.

A look into the dmesg logs shows that the first node has destroyed all the stations with 


wlan2: Destroyed STA xx:xx:xx:xx:xx:xx
and 
wlan2: Removed STA xX:xx:xx:xx:xx:xx 

messages in the log.

However, the disconnected node has appropriate cell-d and ip addresses, not quite sure what is going wrong

Could someone please point out what could be potentially happening. 

--
Thanks,
M
_______________________________________________
ath9k-devel mailing list
ath9k-devel <at> lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Zhuo Chen | 3 Jul 20:02 2014
Picon

About Modifying 802.11 MAC Frame

Is that possible to modify 802.11 MAC Frame using ath9k driver? For example, I want to add more fields in existing beacon frame, association frame, or even create a new type of frame. Can I implement this using ath9k with Atheros chips? Thanks.

Best regards,
Zhuo
_______________________________________________
ath9k-devel mailing list
ath9k-devel <at> lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Yi-Hung Wei | 3 Jul 19:02 2014
Picon

About duration field in RTS/CTS frame

Dear all, 

I am doing some experiments about virtual carrier sense that I manipulate the duration field in RTS/CTS frames. I manually inject CTS frames, set the duration field to a specific number (i.e. 2000), and use a sniffer to monitor those frames. However, the duration filed is not the desired number as I filled in. The duration filed is always 0. 

I also observed that to enable CTS for regular data frame (by setting ATH9K_TXDESC_CTSENA  in xmit.c). Hardware generate a CTS frame for the data frame, and the hardware sets the duration field of the corresponding CTS frame automatically. I am wondering if there is some way to force the hardware to send out CTS frames with manually configured duration field. 

I am running this experiment in a Ubuntu 12.04 machine with Linux kernel 3.11 and backports driver 3.13. My Wi-Fi card is AR9280.

I appreciate any comments and suggestions. 

Best,

-Yi-Hung Wei
_______________________________________________
ath9k-devel mailing list
ath9k-devel <at> lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

Gmane