hostapd events with multiple wlans

Michael Baird Michael.Baird at ecs.vuw.ac.nz
Mon Jan 29 14:35:50 PST 2018


Hi Ravi,

Yes the bridges were created externally. I have run it twice:

  1 - Using the same configuration as before so hostapd creates the 
bridges. Event messages only received for wlan1 & not wlan1_1.

  2 - Removed the 'bridge=br_200' & 'bridge=br_300' so no bridges are 
created. And again event messages are only received for wlan1 and not 
wlan1_1.

I also see when running with the bridges that on killing hostapd only 1 
of the bridges (br_200) is removed and not br_300.


Thanks.



On 30/01/18 10:17, ravi kant Aggarwal wrote:
> Hi Michael,
>
> While running hostapd, did you mentiones bridge interfaces in 
> hostapd.conf file or they are created by external commands. If they 
> are create externally, can you please remove them from bridge once and 
> test without putting in bridging.
>
>
> On Sun, Jan 28, 2018 at 12:32 PM, Michael Baird 
> <Michael.Baird at ecs.vuw.ac.nz <mailto:Michael.Baird at ecs.vuw.ac.nz>> wrote:
>
>     Hi Ravi,
>     Thanks.
>
>     I am using one USB WiFi card (wlan1) with multiple SSIDs these
>     both setup and run fine (except the event messages problem).
>
>
>     running hostapd_cli with the '-i wlan1' flag connects fine. but
>     '-i wlan1_1' does not.
>
>
>     'ip link' output: - wlan0 is not used.
>
>     1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
>     UNKNOWN mode DEFAULT group default qlen 1
>         link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
>     pfifo_fast state UP mode DEFAULT group default qlen 1000
>         link/ether b8:27:eb:c9:d1:43 brd ff:ff:ff:ff:ff:ff
>     3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
>     pfifo_fast state DOWN mode DEFAULT group default qlen 1000
>         link/ether b8:27:eb:9c:84:16 brd ff:ff:ff:ff:ff:ff
>     4: wlan1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq
>     master br_200 state UP mode DEFAULT group default qlen 1000
>         link/ether 02:f6:52:0f:e7:90 brd ff:ff:ff:ff:ff:ff
>     29: eth0.200 at eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500
>     qdisc noqueue master br_200 state UP mode DEFAULT group default
>     qlen 1000
>         link/ether b8:27:eb:c9:d1:43 brd ff:ff:ff:ff:ff:ff
>     30: eth0.300 at eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500
>     qdisc noqueue master br_300 state UP mode DEFAULT group default
>     qlen 1000
>         link/ether b8:27:eb:c9:d1:43 brd ff:ff:ff:ff:ff:ff
>     31: br_200: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
>     noqueue state UP mode DEFAULT group default qlen 1000
>         link/ether 02:f6:52:0f:e7:90 brd ff:ff:ff:ff:ff:ff
>     32: br_300: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
>     noqueue state UP mode DEFAULT group default qlen 1000
>         link/ether 02:f6:52:0f:e7:91 brd ff:ff:ff:ff:ff:ff
>     37: wlan1_1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq
>     master br_300 state UP mode DEFAULT group default qlen 1000
>         link/ether 02:f6:52:0f:e7:91 brd ff:ff:ff:ff:ff:ff
>
>
>     On 27/01/18 09:27, ravi kant Aggarwal wrote:
>>     Hi Michael,
>>
>>     Please use hostapd_cli with interface flag and interface name:
>>
>>     For eg: hostapd_cli -i wlan1 (It will give all the details
>>     associated with wlan1 interface)
>>     hostapd_cli -i wlan2 (It will give all the details associated
>>     with wlan2 interface)
>>
>>     You must have got two interfaces in this case. Please check with
>>     Ifconfig, if you have interfaces
>>
>>     -- 
>>     Thanks & Regards,
>>     Ravi Kant
>>     Cell: +919643408828 <tel:+91%2096434%2008828>
>
>
>
>
> -- 
> Thanks & Regards,
> Ravi Kant
> Cell: +919643408828




More information about the Hostap mailing list