How Many device can connected in Radio 2,4 Ghz and how many device in Radio 5Ghz ?

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

How Many device can connected in Radio 2,4 Ghz and how many device in Radio 5Ghz ?

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
How Many device can connected in Radio 2,4 Ghz and how many device in Radio 5Ghz ?
How Many device can connected in Radio 2,4 Ghz and how many device in Radio 5Ghz ?
2020-07-16 03:31:09
Model: EAP245  
Hardware Version: V3
Firmware Version: 2.4.0 Build 20200117 Rel. 39932

dear all community

 

Can i know eap 245 support how many device in radio 2,4Ghz  and Ghz ?

i have trouble when 25 device connected in 2,4Ghz the latency to ping AP will be 100 ms ? and in radio 5Ghz when the device connected to 25 also raise to 100ms

i'm already change channel also but not tooo long can be stable in 2 ms

  0      
  0      
#1
Options
1 Reply
Re:How Many device can connected in Radio 2,4 Ghz and how many device in Radio 5Ghz ?
2020-07-16 09:10:53 - last edited 2020-07-16 09:17:57

 

RTO888 wrote

Can i know eap 245 support how many device in radio 2,4Ghz  and Ghz ?

 

According to TP-Link specs an EAP245 can theoretically support 80-100 clients in total.

 

However, the maximum number of clients depends on many environmental influences. Of course, a »full house« will increase the latency as it is usual for any shared medium such as a wireless network. Naturally, total bandwidth is shared by all those clients, so the price to supply many clients is lower throughput, which also depends on the typical use pattern of your clients.

 

Some parameters which affect the maximum number of users are:

  • Multi-SSIDs: the more SSIDs you have the more AirTime is needed for the beacon alone.
  • WiFi rates: clients negotiating lower WiFi rates (e.g. due to obstacles, interferences, distance etc.) will acquire more AirTime to transmit data, too.
    Old clients which only support old rates will do so, too. It can help to limit available WiFi rates if all your client support newer standards such as 802.11n/ac.

 

2ms stable latency over a half-duplex shared medium for clients at a certain distance, in an urban area and with obstacles in LoS tot he AP?
Never ever:

 

$ ping 192.168.178.1
PING 192.168.178.1 (192.168.178.1): 56 data bytes
64 bytes from 192.168.178.1: icmp_seq=0 ttl=64 time=1.531 ms
64 bytes from 192.168.178.1: icmp_seq=1 ttl=64 time=2.967 ms
64 bytes from 192.168.178.1: icmp_seq=2 ttl=64 time=1.552 ms
64 bytes from 192.168.178.1: icmp_seq=3 ttl=64 time=2.075 ms
64 bytes from 192.168.178.1: icmp_seq=4 ttl=64 time=4.639 ms
64 bytes from 192.168.178.1: icmp_seq=5 ttl=64 time=3.014 ms
64 bytes from 192.168.178.1: icmp_seq=6 ttl=64 time=1.811 ms
64 bytes from 192.168.178.1: icmp_seq=7 ttl=64 time=1.411 ms
64 bytes from 192.168.178.1: icmp_seq=8 ttl=64 time=1.480 ms
64 bytes from 192.168.178.1: icmp_seq=9 ttl=64 time=3.167 ms
64 bytes from 192.168.178.1: icmp_seq=10 ttl=64 time=16.756 ms
[...]

64 bytes from 192.168.178.1: icmp_seq=24 ttl=64 time=6.455 ms
64 bytes from 192.168.178.1: icmp_seq=25 ttl=64 time=20.229 ms
64 bytes from 192.168.178.1: icmp_seq=26 ttl=64 time=1.544 ms
^C

--- 192.168.178.1 ping statistics ---
28 packets transmitted, 27 packets received, 3.6% packet loss
round-trip min/avg/max/stddev = 1.381/3.946/20.229/4.823 ms
$

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#2
Options