From: "Harms, Hannes" <hannes.harms@tu-bs.de>
To: Peter Oh <peter.oh@bowerswilkins.com>,
Ben Greear <greearb@candelatech.com>,
ath10k@lists.infradead.org
Subject: Re: mesh point and ap mode on same interface
Date: Mon, 9 Oct 2017 10:47:14 +0200 [thread overview]
Message-ID: <7dc592a5-9381-f715-6ea7-0a8b8deee311@tu-bs.de> (raw)
In-Reply-To: <43bf6a27-be58-35e4-26fa-5e6b380353ac@bowerswilkins.com>
On 10/06/2017 20:18, Peter, Oh wrote
> 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?
>
>
Yes, I changed the mac of the 2nd interface:
The mesh setup:
> brctl addbr mesh-bridge
> iw phy0 interface add wlan0 type mp mesh_id my_mesh
> iw wlan0 set freq 5500 80 5530
> ip link set dev wlan0 up
> iw wlan0 mesh join my_mesh
> brctl addif mesh-bridge mesh0
The ap interface:
> iw dev wlan0 interface add virtual_ap type __ap
> ip link set dev virtual_ap address 04:f0:21:1b:7b:48
> hostapd -B -dd hostapd.conf
the hostapd config:
interface=virtual_ap
#ctrl_interface=/var/run/hostapd
driver=nl80211
ssid=infra
hw_mode=a
channel=100
ht_capab=[HT40+]
ieee80211n=1
ieee80211ac=1
vht_oper_chwidth=1
vht_oper_centr_freq_seg0_idx=106
bridge=mesh-bridge
The 2nd interface is not running. (device or resource busy)
What I do not understand is, that according to
http://lists.infradead.org/pipermail/ath10k/2016-September/008374.html
mesh + ap seems possible, even with some stock firmware versions.
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-10-09 8:46 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
2017-10-09 8:47 ` Harms, Hannes [this message]
[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=7dc592a5-9381-f715-6ea7-0a8b8deee311@tu-bs.de \
--to=hannes.harms@tu-bs.de \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=peter.oh@bowerswilkins.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 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.