Bdtyktl

I don't know if there is a limit to number of devices which can connect. It would make more sense that most routers are limited by their hardware, and will experience performance degradation as number of devices increase.

This, I suppose, largely depends on the speed of the routers CPU and available RAM, but it also would largely depend on the services running on the router, i.e. is NAT enabled, QoS, VPN, Access control, is wireless open or with password, etc. I think that the amount of traffic that devices make, is also an important factor to the limit.

I think that this also might be the reason why manufacturers do not specify number of devices which can connect, because it depends on many factors.

In theory you can have up to 255 devices connected to your router, but you will obviously see a performance hit. The performance will be determined by the internet connection you are receiving and specific hardware specification of your router.

You will need to balance load over devices in that you can have 20 devices doing very little work fine, or 2 devices with very high load bottling your connection completely. This all depends on what you want to do with your network.

Sound routers put a limit on the DHCP pool available, which you would have to look around your router settings to find (if it's there). If no such information exists then you can assume the above information. For example, on my router I have a listed range of about 100 for maximum performance, but I will never get close to this so it's largely irrelevant to me.

Looking at the [albeit] small snippet of information provided on that router from your source I can't imagine you would notice any issues with the numbers you are working with.DCHP

Source

From my professional experience: unless you are planning to connect hundreds of devices, you don't need to worry about it.

I agree with the responses of @Matthew and @D. Kasipovic, but sometimes the scientific method does not work for predictions.

I work as a computer scientist and I have deployed many (not very big: hotels and restaurants with less than 80 devices connected at the same time) WiFi networks during years (practically from the beginning of wireless 802.11 technology in networks), so I can tell you that my usual method has finally become: buy some router (or access point), install it and... good luck.

If it hangs (or there is any other strange behavior, like reboots or returning to firmware defaults automatically) often, remove it and buy a different model.

Sorry, I wanna be more theorical in my response, but I think you could lose a lot of time researching this. Simply buy any one (except those you know failed in the past).

Do you still want some good behavior model? The best I have found till now:

Buffalo WHR-HP-G54DD
Buffalo WHR-HP-GN

I hve found them to work fine 24 hours a day during months or years with 20-30 NAT clients connected to WPA WiFi transfering many network data, plus VPN server working, and they have support for DD-WRT firmware. They heat a bit, but it is not a problem if you don't put it in a small closet. Mostly the Buffalo models have proven to be stable. But remember: even them do some times hang (even with low usage and devices connected).

EDIT: Some router models have a very limited (10-20) number of available DHCP Reservation List. This could be important if you are planning to have a fixed correlation between device and IP address. This problem is, too, solved with DD-WRT firmware.

After the 2010 earthquake in Port-au-Prince I set up a network for a medical crisis center. All we have available in the beginning were the same Linksys AP units as shown in the original article. We had several acting as access points all feeding into one which was the connection to the Internet and the wired network. We had constant problems with them (especially the central router) and fried several. When one of them was giving signs of problems I touched it and found that it was hot enough that I could not pick it up. I do not know what the limits for this unit were but we were obviously exceeding it (we were running between 20 and 200 simultaneous connections).

While from a technical standpoint you would expect a limit of maybe 255 (as others have mentioned), this seems to be not always the case. Instead there might be much lower limits because of marketing / manufacturer politics.

Germany's most renowned IT magazine c't reported in December 2013 that the access point TP-Link TL-WA701ND only allows 15 WIFI clients (article in German). The article further states that the limit is arbitrarily set by the manufacturer in the firmware because the target market of the device is SOHO (Small Office/Home), and that the limit is not mentioned neither in the manual nor in the technical specification. It is claimed that with OpenWRT the limit should be eliminated, but using alternative firmware may not be acceptable or desired in all cases.

The article does not contain statements about other access points or manufacturers, but it does not present this limit as something unique, rare, or surprising. So I would assume that other devices targeted for SOHO usage may have similar limits. Note that it may not be apparent for which market segment a device is meant at first glance. The access point mentioned here even has features such as Multi-SSID WIFI, VLAN, and Power-over-Ethernet support, all of which I would primarily expect from an access point for professional usage in a larger network.

The article suggests to request a definitive answer on the maximum number of supported clients from the manufacturer prior to buying.

There are multiple limiting factors here:

1. Most WiFi module used in the small cheap WiFi routers have a hard limit of 32 devices per module. I believe that leaves 31 available for connections.




2. DHCP server on the WiFi router may only support 50 or so devices, that is combining all WiFi and Wired connections. This number can be changed but can be misleading. Each DHCP client leases the IP address for a length of time. Typically 24 hours. So when calculating total active devices, one must also calculate the number of client devices that was active within the last 24 hours, not just those which is currently powered up and active.




3. NAT pairs. NAT is what enables a connection between your computer and a web server on the internet. Most WiFi router does not publish the total number supported but in the early days of NAT routers, this equals to the number of DHCP clients supported.

Conclusion. If you are not sure or cannot find out those limits, and you find yourself rebooting the WiFi router to get performance. Time to setup a good router and multiple WiFi Access Points.

Using Cheap Access Points, best way is to name them differently per location so loading can be split by connection to different APs.

Just for fun, I checked my router's DHCP page.

As it turns out, I have 23 devices right now, with 3 satellite receivers (plus the WiFi bridge, which has its own IP), 6 mobile devices (smartphones, tablets, etc), 5 computers, 2 video game consoles, an Apple TV, a Slingbox, a Squeezebox, and several virtual machines.

Some of those devices are wired, and some are wireless.

I have no problems with my router.

As far as the maximum number of devices goes: some consumer routers limit you to a 24-bit subnet mask, which limits you to 254 IP addresses on your local network. However, my DLink actually lets me edit the mask, so I could (in theory) use up to a class A network with a 10.x.x.x address.

I would wager that any limits on your home network will be due to ISP bandwidth, and not limits on the actual router box.

I don't think 12 clients will be a problem.

Based on my experience with wireless routers, most of them out there cannot support more than 255 devices. When the network mask is changed to 22 or 255.255.252.0, all of them that I tried failed to function properly.

Depends on the Router.

The main factors are your subnet size, DHCP pool, and the limits of your hardware.

Most Belkins I have (begrudgingly) worked on limit the DHCP pool to the 1 octet or 252 addresses. Not 255 as some have said, 3 IPs have to be used for the router to function; one for network, one for broadcast, and one for the gateway.
As to the subnet, you could in theory set up your LAN on a Class A with /8 subnet (10.0.0.0 255.0.0.0), giving you 16,777,214 usable IP's to work with. But that would be a VERY bad idea. WiFi doesn't play well with that large of IP range.

Of course the limits of your network hardware, that is pretty well common sense.

As to knowing when you have maxed out your DHCP pool. You'll know when some devices can connect just fine but other can't, look at the IP address of the ones that can't and they will have a ip of 169.*.*.*. Power cycling the router will help for a bit, but not long.

Some of the posts are technically correct.. but rubbish on an actual site.

On consumer grade equipment.. limit it at 10 simultaneous. Yes, you may have a lot of devices at home, but you don't use them all at once.

If you are serious, use two WAP's. One at one end of the house and one at the other (physically). Set them on channels at lest 5 channels apart (3 and 10 or something). And have them shell out a different range of IP addresses if they are each acting as DHCP.

The next step up is to have each WAP on it's own IP subnet. With routes to the other subnet and the default gateway on each WAP to your router (via wired eth).

If you try and run everything at once you will just pull your hair out when it is busy and struggling.

I am not just saying this.. we have a site that has just gone from 9 to 13 laptops on a single WAP and it dies in the arse on any busy day. This is on a draytek and they're normally pretty good.

cheers

the only limitation would be in the amount of bandwidth your router can transmit. there would be no limit to the number of devices you could connect, however, you would see a performance degradation as you connected more devices.

I have been doing some searching. Found this on Netgear's site, saying they support 32 devices (64 on dual band).

How many clients can you connect wirelessly to a NETGEAR router?

NETGEAR home routers can accommodate up to 32 clients per wireless
band. If your router is dual band, the total wireless clients your
router can handle is 64 (32 for the 2.4GHz and 32 for the 5GHz).

However, since the router's wireless channel is shared between all the
wireless clients, adding clients will inevitably result in slower
network access for all clients. This will be particularly noticeable
if some of the clients are using a lot of wireless bandwidth, for
example by watching a video or doing a torrent download. Therefore,
the maximum number of wireless clients that will operate
satisfactorily while connected to the same router will vary depending
on what the devices are used for. It will also vary depending on how
much wireless congestion or interference are present in the location
where the router is installed.

How many clients can you connect wirelessly to a NETGEAR router?

Not all manufacturers are very good at documenting this information.

The limit is really on the wireless connections. Home routers typically (if not all) are limited to 32 connections. The default most take in the setup is 16 but you have the option to up this to 32. I personally run over 32 wireless devices at my home running everything from smart switches, HVAC units, sprinkler systems, security systems, Alexa devices, wireless remotes, etc. Nothing is hardwired. All connections are concurrent because they are either on cloud scheduling or logged in to security monitoring, etc. The only way I have around this is put part on the 5G and the rest on the 2G which each have the 32 connection limit.