attempting mesh on ath10k

Bob Copeland me at
Tue Apr 28 05:25:55 PDT 2015

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 at archer:~# iw dev
        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 at archer:~# ping
PING ( 56 data bytes
64 bytes from seq=0 ttl=64 time=10.031 ms
64 bytes from seq=1 ttl=64 time=1.074 ms
64 bytes from seq=2 ttl=64 time=1.074 ms
64 bytes from seq=3 ttl=64 time=1.082 ms
64 bytes from seq=4 ttl=64 time=1.032 ms
64 bytes from seq=5 ttl=64 time=2.905 ms
64 bytes from seq=6 ttl=64 time=1.093 ms
64 bytes from seq=7 ttl=64 time=1.205 ms
64 bytes from seq=8 ttl=64 time=1.057 ms
64 bytes from seq=9 ttl=64 time=1.039 ms
64 bytes from seq=10 ttl=64 time=1.107 ms
64 bytes from seq=11 ttl=64 time=1.040 ms
--- ping statistics ---
12 packets transmitted, 12 packets received, 0% packet loss
round-trip min/avg/max = 1.032/1.978/10.031 ms

root at archer:~# iw dev wlan0 mpath dump
DEST ADDR         NEXT HOP          IFACE       SN      METRIC  QLEN
00:03:7f:10:4e:2d 00:03:7f:10:4e:2d wlan0       2427    1366    0
0       100     0       0x4

Bob Copeland %%

More information about the ath10k mailing list