hostapd + 100 devices on Cubieboard
Bruno Antunes
baantunes at gmail.com
Thu May 4 07:11:35 PDT 2017
Hi,
On 4 May 2017 at 13:24, Marek Floriańczyk <marek.florianczyk at gmail.com> wrote:
> Dnia czwartek, 4 maja 2017 10:24:22 CEST Bruno Antunes pisze:
>> Hi,
>>
>> On 4 May 2017 at 07:28, Marek Floriańczyk <marek.florianczyk at gmail.com>
> wrote:
>> > Hi all,
>> >
>> > I need to run such a config:
>> > Cubieboard2 + wifi dongle + 100 devices - small ones, with low bandwidth,
>> > only to send text commands, from server to the devices.
>> > I have compiled hostapd-2.6 from sources.
>> >
>> > Can someone tell me is this configuration possible?
>> > What wifi dongle (preferably with antenna) would you recommend?
>> > Some options for hostapd? Like I said I don't need high speed from this
>> > configuration.
>> >
>> > Yesterday I was testing this setup with wifi dongle TP-Link TL-WN727N and
>> > it
>> Acording to wikidevi there are 3 versions of that adaptor:
>> https://wikidevi.com/wiki/TP-LINK_TL-WN727N_v3
>
> Hi
>
> Thanks for answer.
> My device looks like the one from wikidevi page
>
> Can You recommend a different wifi device ?
Honestly nothing USB based...
>
> From iw list, I can't tell how many devices will this support, below there is
> full output from iw list, can You make out something from this ?
>
Sorry my mistake, I was thinking on the number of interfaces a given
device can generate.
That would be what this command outputs.
>From the hostapd.conf
https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf
# Maximum number of stations allowed in station table. New stations will be
# rejected after the station table is full. IEEE 802.11 has a limit of 2007
# different association IDs, so this number should not be larger than that.
# (default: 2007)
max_num_sta=255
So if you didn't configured this value you should be able to connect 2007 Sta.
As far as my understanding if you can connect 60 devices its more than enough.
Comercial APs have limits around that.
Troubleshoot the dhcp server and increase the hostapd log (with -d option).
Its hard can give you an answer with so little info.
Regards,
Bruno
> Best Regards
> Marek
>
> Wiphy phy0
> max # scan SSIDs: 4
> max scan IEs length: 2257 bytes
> Retry short limit: 7
> Retry long limit: 4
> Coverage class: 0 (up to 0m)
> Device supports RSN-IBSS.
> Supported Ciphers:
> * WEP40 (00-0f-ac:1)
> * WEP104 (00-0f-ac:5)
> * TKIP (00-0f-ac:2)
> * CCMP (00-0f-ac:4)
> * 00-0f-ac:10
> * GCMP (00-0f-ac:8)
> * 00-0f-ac:9
> Available Antennas: TX 0 RX 0
> Supported interface modes:
> * IBSS
> * managed
> * AP
> * AP/VLAN
> * WDS
> * monitor
> * mesh point
> Band 1:
> Capabilities: 0x172
> HT20/HT40
> Static SM Power Save
> RX Greenfield
> RX HT20 SGI
> RX HT40 SGI
> RX STBC 1-stream
> Max AMSDU length: 3839 bytes
> No DSSS/CCK HT40
> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
> Minimum RX AMPDU time spacing: 2 usec (0x04)
> HT RX MCS rate indexes supported: 0-7, 32
> TX unequal modulation not supported
> HT TX Max spatial streams: 1
> HT TX MCS rate indexes supported may differ
> Bitrates (non-HT):
> * 1.0 Mbps
> * 2.0 Mbps (short preamble supported)
> * 5.5 Mbps (short preamble supported)
> * 11.0 Mbps (short preamble supported)
> * 6.0 Mbps
> * 9.0 Mbps
> * 12.0 Mbps
> * 18.0 Mbps
> * 24.0 Mbps
> * 36.0 Mbps
> * 48.0 Mbps
> * 54.0 Mbps
> Frequencies:
> * 2412 MHz [1] (20.0 dBm)
> * 2417 MHz [2] (20.0 dBm)
> * 2422 MHz [3] (20.0 dBm)
> * 2427 MHz [4] (20.0 dBm)
> * 2432 MHz [5] (20.0 dBm)
> * 2437 MHz [6] (20.0 dBm)
> * 2442 MHz [7] (20.0 dBm)
> * 2447 MHz [8] (20.0 dBm)
> * 2452 MHz [9] (20.0 dBm)
> * 2457 MHz [10] (20.0 dBm)
> * 2462 MHz [11] (20.0 dBm)
> * 2467 MHz [12] (20.0 dBm) (no IR)
> * 2472 MHz [13] (20.0 dBm) (no IR)
> * 2484 MHz [14] (20.0 dBm) (no IR)
> Supported commands:
> * new_interface
> * set_interface
> * new_key
> * start_ap
> * new_station
> * new_mpath
> * set_mesh_config
> * set_bss
> * authenticate
> * associate
> * deauthenticate
> * disassociate
> * join_ibss
> * join_mesh
> * set_tx_bitrate_mask
> * frame
> * frame_wait_cancel
> * set_wiphy_netns
> * set_channel
> * set_wds_peer
> * probe_client
> * set_noack_map
> * register_beacons
> * start_p2p_device
> * set_mcast_rate
> * Unknown command (104)
> * connect
> * disconnect
> Supported TX frame types:
> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0
> 0xb0 0xc0 0xd0 0xe0 0xf0
> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> Supported RX frame types:
> * IBSS: 0x40 0xb0 0xc0 0xd0
> * managed: 0x40 0xd0
> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
> * mesh point: 0xb0 0xc0 0xd0
> * P2P-client: 0x40 0xd0
> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
> * P2P-device: 0x40 0xd0
> software interface modes (can always be added):
> * AP/VLAN
> * monitor
> valid interface combinations:
> * #{ AP, mesh point } <= 8,
> total <= 8, #channels <= 1
> HT Capability overrides:
> * MCS: ff ff ff ff ff ff ff ff ff ff
> * maximum A-MSDU length
> * supported channel width
> * short GI for 40 MHz
> * max A-MPDU length exponent
> * min MPDU start spacing
> Device supports TX status socket option.
> Device supports HT-IBSS.
> Device supports SAE with AUTHENTICATE command
> Device supports low priority scan.
> Device supports scan flush.
> Device supports AP scan.
> Device supports per-vif TX power setting
> Driver supports full state transitions for AP/GO clients
> Driver supports a userspace MPM
>
>>
>> > looked like 60 devices has connected to hostapd, but there were some
>> > problems with dhcp server.
>>
>> There is no limitation on the number of devices connected in hostapd,
>> that is device dependent.
>> If the problem isn't on the dhcp server you can check the number of
>> max devices with:
>>
>> iw list | grep managed
>>
>>
>> Regards,
>> Bruno
>>
>> > Need some help, please.
>> >
>> > Best Regards
>> > Marek
>> >
>> > _______________________________________________
>> > Hostap mailing list
>> > Hostap at lists.infradead.org
>> > http://lists.infradead.org/mailman/listinfo/hostap
>
>
More information about the Hostap
mailing list