From: Bob Copeland <me@bobcopeland.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: Ben Greear <greearb@candelatech.com>,
Yeoh Chun-Yeow <yeohchunyeow@gmail.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: attempting mesh on ath10k
Date: Tue, 28 Apr 2015 08:25:55 -0400 [thread overview]
Message-ID: <20150428122554.GA4527@localhost> (raw)
In-Reply-To: <CA+BoTQmrboeJOw0J67PWkbjteh38xrWntivvBKSWY1MBQ=B6Dg@mail.gmail.com>
On Tue, Apr 28, 2015 at 07:47:40AM +0200, Michal Kazior wrote:
> > Perhaps there is a BSSID filter enabled or something like that (in mesh
> > there's no BSSID, just individual addresses on group addressed frames).
>
> In that case try creating a monitor interface and bring it up. This
> should prompt ath10k to create monitor vdev and subsequently disable
> most Rx filters in firmware.
Indeed, that did the trick, thanks! So mesh is functional now with raw mode
patch and a few hacks:
root@archer:~# iw dev
phy#0
Interface mon0
ifindex 8
wdev 0x2
addr e8:de:27:d6:9c:d0
type monitor
Interface wlan0
ifindex 4
wdev 0x1
addr e8:de:27:d6:9c:d0
type mesh point
channel 149 (5745 MHz), width: 20 MHz (no HT), center1: 5745 MHz
root@archer:~# ping 10.10.10.13
PING 10.10.10.13 (10.10.10.13): 56 data bytes
64 bytes from 10.10.10.13: seq=0 ttl=64 time=10.031 ms
64 bytes from 10.10.10.13: seq=1 ttl=64 time=1.074 ms
64 bytes from 10.10.10.13: seq=2 ttl=64 time=1.074 ms
64 bytes from 10.10.10.13: seq=3 ttl=64 time=1.082 ms
64 bytes from 10.10.10.13: seq=4 ttl=64 time=1.032 ms
64 bytes from 10.10.10.13: seq=5 ttl=64 time=2.905 ms
64 bytes from 10.10.10.13: seq=6 ttl=64 time=1.093 ms
64 bytes from 10.10.10.13: seq=7 ttl=64 time=1.205 ms
64 bytes from 10.10.10.13: seq=8 ttl=64 time=1.057 ms
64 bytes from 10.10.10.13: seq=9 ttl=64 time=1.039 ms
64 bytes from 10.10.10.13: seq=10 ttl=64 time=1.107 ms
64 bytes from 10.10.10.13: seq=11 ttl=64 time=1.040 ms
^C
--- 10.10.10.13 ping statistics ---
12 packets transmitted, 12 packets received, 0% packet loss
round-trip min/avg/max = 1.032/1.978/10.031 ms
root@archer:~# iw dev wlan0 mpath dump
DEST ADDR NEXT HOP IFACE SN METRIC QLEN
EXPTIME DTIM DRET FLAGS
00:03:7f:10:4e:2d 00:03:7f:10:4e:2d wlan0 2427 1366 0
0 100 0 0x4
--
Bob Copeland %% http://bobcopeland.com/
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-04-28 12:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 12:50 attempting mesh on ath10k Bob Copeland
2015-04-24 17:55 ` Yeoh Chun-Yeow
2015-04-25 1:38 ` Ben Greear
2015-04-26 14:15 ` Bob Copeland
2015-04-26 15:42 ` Ben Greear
2015-04-27 13:00 ` Bob Copeland
2015-04-28 5:47 ` Michal Kazior
2015-04-28 12:25 ` Bob Copeland [this message]
2015-05-27 6:51 ` Bartosz Markowski
2015-05-27 11:12 ` Bob Copeland
2015-05-27 11:15 ` Bartosz Markowski
2015-04-28 12:41 ` Bob Copeland
2015-04-28 12:50 ` Yeoh Chun-Yeow
2015-04-28 12:57 ` Bob Copeland
2015-04-28 14:47 ` Ben Greear
-- strict thread matches above, loose matches on Subject: below --
2015-07-06 21:25 Freddy Lee
2015-07-06 21:49 ` Bob Copeland
2015-07-06 21:54 ` Bob Copeland
2015-07-12 14:25 ` Bob Copeland
2015-07-13 1:43 ` Bob Copeland
2015-07-13 8:13 ` Michal Kazior
2015-07-13 10:57 ` Bob Copeland
2015-07-20 13:57 ` Bob Copeland
2015-08-13 3:14 ` Bob Copeland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150428122554.GA4527@localhost \
--to=me@bobcopeland.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=michal.kazior@tieto.com \
--cc=yeohchunyeow@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox