mesh point and ap mode on same interface

[Peter Oh]

On 10/09/2017 12:07 PM, Peter Oh wrote:
>
>
>
> On 10/09/2017 08:08 AM, Thomas Pedersen wrote:
>> On Oct 9, 2017 1:46 AM, "Harms, Hannes" <hannes.harms at tu-bs.de 
>> <mailto:hannes.harms at tu-bs.de>> wrote:
>>
>>     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
>>
> Are you sure this configuration is what you're using?
> there is no way to use DFS channels on mesh via iw at this moment.
> and mesh id on brctl addif is different from interface add.
>
>>     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
>>
> hostapd also does not allow interface to use DFS channels without 
> country_code parameter.
>>
>>     I think mesh and AP channel frequency + width need to match. Try
>>     joining mesh after brining up AP and he should adopt AP's channel
>>     configuration. Or make AP VHT80 as well.
>>
>>
> This is good thing to try out.
> But as long as you're configuration is correct such as channel number 
> and interface name, your steps should work.
>>
>>     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
>>     <http://lists.infradead.org/pipermail/ath10k/2016-September/008374.html>
>>     mesh + ap seems possible, even with some stock firmware versions.
>>
>>
>>     _______________________________________________
>>     ath10k mailing list
>>     ath10k at lists.infradead.org <mailto:ath10k at lists.infradead.org>
>>     http://lists.infradead.org/mailman/listinfo/ath10k
>>     <http://lists.infradead.org/mailman/listinfo/ath10k>
>>
>>
>