* No Beacon Received in IBSS mode or adhoc mode
@ 2014-02-11 6:09 Yeoh Chun-Yeow
2014-02-11 6:34 ` Michal Kazior
0 siblings, 1 reply; 4+ messages in thread
From: Yeoh Chun-Yeow @ 2014-02-11 6:09 UTC (permalink / raw)
To: Kalle Valo, ath10k
Hi, Kalle
I have took another look on the IBSS or adhoc mode in ath10k.
In IBSS or adhoc mode, the beacon generated by others is filtered by
the FW (999.999.0.636) and thus not pushed up to mac80211. However, in
AP mode, the beacon is not filtered and can reach mac80211.
Is that possible to allow beacon to be able to push up to mac80211
without FW filtering in IBSS mode?
Please advice. Thanks
Regards,
Chun-Yeow
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: No Beacon Received in IBSS mode or adhoc mode
2014-02-11 6:09 No Beacon Received in IBSS mode or adhoc mode Yeoh Chun-Yeow
@ 2014-02-11 6:34 ` Michal Kazior
2014-02-11 8:30 ` Yeoh Chun-Yeow
0 siblings, 1 reply; 4+ messages in thread
From: Michal Kazior @ 2014-02-11 6:34 UTC (permalink / raw)
To: Yeoh Chun-Yeow; +Cc: Kalle Valo, ath10k
On 11 February 2014 07:09, Yeoh Chun-Yeow <yeohchunyeow@gmail.com> wrote:
> Hi, Kalle
>
> I have took another look on the IBSS or adhoc mode in ath10k.
>
> In IBSS or adhoc mode, the beacon generated by others is filtered by
> the FW (999.999.0.636) and thus not pushed up to mac80211. However, in
> AP mode, the beacon is not filtered and can reach mac80211.
>
> Is that possible to allow beacon to be able to push up to mac80211
> without FW filtering in IBSS mode?
If you need a quick hack I suspect starting a monitor vdev would do
the trick. I'm not really sure how stable that is going to be though..
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: No Beacon Received in IBSS mode or adhoc mode
2014-02-11 6:34 ` Michal Kazior
@ 2014-02-11 8:30 ` Yeoh Chun-Yeow
2014-02-11 8:42 ` Michal Kazior
0 siblings, 1 reply; 4+ messages in thread
From: Yeoh Chun-Yeow @ 2014-02-11 8:30 UTC (permalink / raw)
To: Michal Kazior; +Cc: Kalle Valo, ath10k
>
> If you need a quick hack I suspect starting a monitor vdev would do
> the trick. I'm not really sure how stable that is going to be though..
>
I did a quick hack bringing up the monitor interface using
ath10k_monitor_create and ath10k_monitor_scan but no luck the FW
crashed.
[ 276.060000] ath10k: firmware crashed!
[ 276.060000] ath10k: hardware name qca988x hw2.0 version 0x4100016c
[ 276.070000] ath10k: firmware version: 999.999.0.636
[ 276.080000] ath10k: target register Dump Location: 0x0040AC14
[ 276.080000] ath10k: target Register Dump
[ 276.090000] ath10k: [00]: 0x4100016C 0x00000000 0x009C4521 0x00000000
[ 276.090000] ath10k: [04]: 0x009C4521 0x00060530 0x00000019 0x00955A00
[ 276.100000] ath10k: [08]: 0x00002898 0x00000000 0x0040CC94 0x00000020
[ 276.110000] ath10k: [12]: 0x00000000 0x00000000 0x00958360 0x0095836B
[ 276.110000] ath10k: [16]: 0x80991091 0x0040AD94 0x00430854 0x00000000
[ 276.120000] ath10k: [20]: 0x0000FFFF 0x00000000 0x00000045 0x00000000
[ 276.130000] ath10k: [24]: 0x809A0978 0x0040AD94 0x00439304 0x00A26009
[ 276.130000] ath10k: [28]: 0x809AD1A2 0x0040ADE4 0x00439304 0x0043F8BC
[ 276.140000] ath10k: [32]: 0x00000001 0x00000005 0x00000000 0x004325CC
[ 276.150000] ath10k: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
[ 276.150000] ath10k: [40]: 0x00000000 0x00000000 0x0000000E 0x00000000
[ 276.160000] ath10k: [44]: 0x00439C00 0x00000000 0x00000000 0x00400000
[ 276.160000] ath10k: [48]: 0x809AE0B4 0x0040AE04 0x00400000 0x0043F8BC
[ 276.170000] ath10k: [52]: 0x00000001 0x00000000 0x004231F0 0x00400000
[ 276.180000] ath10k: [56]: 0x809AE17E 0x0040AE44 0x0040FE6C 0x0040D310
[ 276.270000] ieee80211 phy0: Hardware restart was requested
Also, monitor mode is not a good idea, cause what we need is beacon
frame generated by others.
The only way that I can get the IBSS beacon generated by another node
is by triggering the "iw wlan0 scan". But then, it makes no sense
since we need to that whenever a station join the IBSS.
So, is there any way to turn of the beacon filtering in IBSS mode for the FW?
----
Chun-Yeow
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: No Beacon Received in IBSS mode or adhoc mode
2014-02-11 8:30 ` Yeoh Chun-Yeow
@ 2014-02-11 8:42 ` Michal Kazior
0 siblings, 0 replies; 4+ messages in thread
From: Michal Kazior @ 2014-02-11 8:42 UTC (permalink / raw)
To: Yeoh Chun-Yeow; +Cc: Kalle Valo, ath10k
On 11 February 2014 09:30, Yeoh Chun-Yeow <yeohchunyeow@gmail.com> wrote:
>>
>> If you need a quick hack I suspect starting a monitor vdev would do
>> the trick. I'm not really sure how stable that is going to be though..
>>
>
> I did a quick hack bringing up the monitor interface using
> ath10k_monitor_create and ath10k_monitor_scan but no luck the FW
> crashed.
>
> [ 276.060000] ath10k: firmware crashed!
> [ 276.060000] ath10k: hardware name qca988x hw2.0 version 0x4100016c
> [ 276.070000] ath10k: firmware version: 999.999.0.636
> [ 276.080000] ath10k: target register Dump Location: 0x0040AC14
> [ 276.080000] ath10k: target Register Dump
> [ 276.090000] ath10k: [00]: 0x4100016C 0x00000000 0x009C4521 0x00000000
> [ 276.090000] ath10k: [04]: 0x009C4521 0x00060530 0x00000019 0x00955A00
> [ 276.100000] ath10k: [08]: 0x00002898 0x00000000 0x0040CC94 0x00000020
> [ 276.110000] ath10k: [12]: 0x00000000 0x00000000 0x00958360 0x0095836B
> [ 276.110000] ath10k: [16]: 0x80991091 0x0040AD94 0x00430854 0x00000000
> [ 276.120000] ath10k: [20]: 0x0000FFFF 0x00000000 0x00000045 0x00000000
> [ 276.130000] ath10k: [24]: 0x809A0978 0x0040AD94 0x00439304 0x00A26009
> [ 276.130000] ath10k: [28]: 0x809AD1A2 0x0040ADE4 0x00439304 0x0043F8BC
> [ 276.140000] ath10k: [32]: 0x00000001 0x00000005 0x00000000 0x004325CC
> [ 276.150000] ath10k: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
> [ 276.150000] ath10k: [40]: 0x00000000 0x00000000 0x0000000E 0x00000000
> [ 276.160000] ath10k: [44]: 0x00439C00 0x00000000 0x00000000 0x00400000
> [ 276.160000] ath10k: [48]: 0x809AE0B4 0x0040AE04 0x00400000 0x0043F8BC
> [ 276.170000] ath10k: [52]: 0x00000001 0x00000000 0x004231F0 0x00400000
> [ 276.180000] ath10k: [56]: 0x809AE17E 0x0040AE44 0x0040FE6C 0x0040D310
> [ 276.270000] ieee80211 phy0: Hardware restart was requested
Be aware that monitor vdev is unstable in 636 and it cannot run
standalone. Monitor vdev must be run alongside other vdev.
> Also, monitor mode is not a good idea, cause what we need is beacon
> frame generated by others.
Well, theoretically it should work as monitor vdev disables rx filters.
> The only way that I can get the IBSS beacon generated by another node
> is by triggering the "iw wlan0 scan". But then, it makes no sense
> since we need to that whenever a station join the IBSS.
Hmm, then you could probably try to hack around and create a sort of a
background scan that lasts forever. Firmware is supposedly able to
handle concurrent scans. You'll probably need to tweak
ath10k_wmi_event_scan() for that. ath10k uses scan for roc so it might
actually work.
> So, is there any way to turn of the beacon filtering in IBSS mode for the FW?
Unfortunately I don't know any except the hacks I've mentioned already.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-02-11 8:42 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-02-11 6:09 No Beacon Received in IBSS mode or adhoc mode Yeoh Chun-Yeow
2014-02-11 6:34 ` Michal Kazior
2014-02-11 8:30 ` Yeoh Chun-Yeow
2014-02-11 8:42 ` Michal Kazior
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.