From: Peter Oh <peter.oh@bowerswilkins.com>
To: Ben Greear <greearb@candelatech.com>,
"Harms, Hannes" <hannes.harms@tu-bs.de>,
ath10k@lists.infradead.org
Subject: Re: mesh point and ap mode on same interface
Date: Fri, 6 Oct 2017 11:18:29 -0700 [thread overview]
Message-ID: <43bf6a27-be58-35e4-26fa-5e6b380353ac@bowerswilkins.com> (raw)
In-Reply-To: <cc8baced-bd74-5703-d885-6ec444eb62ce@candelatech.com>
I have tried t bring up the ap interface with iw / hostapd,
>> after joining the mesh.
>>
>> When I start the second interface, rtnetlink responds with
>> device or resource busy.
>
If you give more details of your steps, people may help you more.
Btw, did you create a 2nd interface on the same radio and change the mac
address?
> IBSS + AP works on the CT firmware/driver, at least,
> but our CT 10.1 (988x) firmware does not support MESH at this point.
>
> I think I had to modify the driver to relax the valid combinations check,
> and possibly the stock firmware cannot handle that.
>
> Maybe someday we'll support MESH on 988x, but to date, there has not been
> a lot of interest...
>
> http://www.candelatech.com/ath10k.php
>
> Thanks,
> Ben
>
>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-10-06 18:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 12:00 mesh point and ap mode on same interface Harms, Hannes
2017-10-06 16:52 ` Ben Greear
2017-10-06 18:18 ` Peter Oh [this message]
2017-10-09 8:47 ` Harms, Hannes
[not found] ` <CADjYELwdUxEap_z=_HD4DS4FEQ2_2HP3w9cvDU-BTFLoOTDipg@mail.gmail.com>
[not found] ` <5c04c7fe-8cf8-ddd8-d6a7-f42629586a63@bowerswilkins.com>
2017-10-09 19:14 ` Peter Oh
[not found] ` <067d234a-59f0-4175-55af-9354617057b9@tu-bs.de>
2017-10-11 18:10 ` Peter Oh
2017-11-08 12:49 ` Harms, Hannes
2017-11-08 18:13 ` Peter Oh
2017-11-15 10:01 ` Kalle Valo
2017-11-15 10:01 ` Kalle Valo
2017-11-15 10:13 ` Arend van Spriel
2017-11-15 10:13 ` Arend van Spriel
2017-11-15 10:27 ` Kalle Valo
2017-11-15 10:27 ` Kalle Valo
2017-11-15 10:36 ` Arend van Spriel
2017-11-15 10:36 ` Arend van Spriel
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=43bf6a27-be58-35e4-26fa-5e6b380353ac@bowerswilkins.com \
--to=peter.oh@bowerswilkins.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=hannes.harms@tu-bs.de \
/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 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.