Wi-Fi for Mosques and Places of Worship

Wi-Fi in a place of worship usually begins with a router someone donated, installed in the office, and left to work on its own. Most of the time that is enough: only a few staff use it.

The trouble arrives on particular days, a weekly class, Friday prayers, a major festival, when the number of people inside multiplies and the same network is asked to serve them all. At that point the building reveals the traits that stop it being treated as a large house.

Three things that set it apart

Worship spaces have a layout rarely found in other buildings, and all three traits bear directly on planning.

• The ceilings are high. An access point fixed to an eight-metre ceiling radiates from far above head height. The signal looks full on screen, but the link is weak because the real distance is much greater than the floor plan suggests.
• The space is open, without partitions. This actually helps, no walls cut the signal. The problem is not coverage but the number of devices at one point.
• Occupancy is wildly uneven. Five people on an ordinary day, three hundred at Friday noon. A network designed for the average fails precisely when it is most visible.

All three lead to the same conclusion: what matters is not how far the signal reaches, but how many devices can be served at once.

Estimating what you need

Start from the busiest day, not a typical one. A reasonable assumption: one person in three will connect a phone, and that share rises during longer gatherings.

The rough guide is one access point per 25–30 active devices. From there:

• A small prayer room, up to 50 people. One decent access point is enough. The provider's own router will often still cope.
• A medium mosque, 150–300 worshippers. Two or three access points in the main hall, plus one for the office and study room.
• A large mosque with several floors or a courtyard in use. Four units and up, and at this stage placement needs planning rather than guesswork.

Note that what is counted is devices, not area. Open space of any size does not help when three hundred phones gather in front of a single access point.

Mounting them at the right height

The most common mistake is mounting access points as high as possible because the room is tall. What the signal must reach is a phone in someone's hand, about a metre above the floor.

A few things hold generally in rooms like these:

• Mount at three to four metres, on a wall or column, not on the highest ceiling.
• Spread them out rather than stacking them. Two access points on opposite sides serve far better than two side by side in one corner.
• Avoid mounting behind metal ornament or inside a closed panel cabinet. Metal reflects the signal, and a sealed cabinet traps heat.
• If the courtyard is used on major days, one outdoor unit beats hoping the indoor signal will pass through walls.

Running cable to those points is extra work. But an access point on a cable, powered over that same cable with PoE, is far more reliable than a chain of repeaters extending one another, and needs no power socket at every column.

How to hand out access

Three approaches are common, and the choice depends on who will look after it day to day.

A posted password. Stuck on a wall or printed on a small sign. Simplest, and adequate for most places of worship. What matters: this password belongs to the guest network only, and is never the same as the staff network's.

A QR code. Removes typing errors and helps older visitors. It can be produced without any special app and printed card-sized for several locations.

A welcome page. Visitors tap a button before connecting, and the page can carry announcements or a donation link. Appealing, but it demands more expensive equipment and someone to maintain it. Without a regular technical volunteer, this approach becomes a burden more often than a benefit.

Whichever is chosen, a password is still needed. An open network with none is entirely unencrypted anyone nearby can read everyone else's traffic. A password on the wall still enables encryption, and that is a real difference even when everybody knows it.

Separating the staff network

In many places of worship the same network also carries things that must not mix with visitor traffic: an office computer holding member records, security cameras, network-connected public address equipment, and sometimes a printer.

Separating them needs no expensive hardware. Almost every router today offers a guest network as its own menu item. What to confirm:

• The guest network is enabled with a different name and password.
• The option usually called client isolation is on, so visitors' devices cannot see one another.
• Cameras and the office computer sit on the staff network, never the guest one.
• The router's admin page cannot be opened from the guest network.

This separation also protects against a quieter problem: if one visitor's device is infected, it has no route to the computer holding member records.

What it costs, and who carries it

The cost comes in two parts, and the second is often forgotten when equipment is donated.

The upfront outlay covers access points, cabling, and installation. The ongoing outlay covers the monthly subscription, replacing hardware every few years, and occasional repairs.

Donated equipment settles the first part only. Without an agreement on who pays the monthly bill, a network installed in good faith often goes dark a few months later. Settling it at the outset, a recurring line in the budget, or one regular donor who has said yes, determines its survival more than the brand of hardware chosen.

The responsibility that comes with it

Offering internet access to the public carries consequences worth knowing. If the network is used unlawfully, whoever provides the access can be asked to account for it, and the logged IP address points at the building's connection.

No need to over-react. A few simple measures put those responsible in a clear position:

• Leave the router's connection logging on, and do not clear it routinely.
• Post short terms of use beside the password, a few sentences is enough.
• Consider simple DNS-based content filtering, particularly where children use the network during classes.
• Record who holds the router's admin access, and make sure more than one person knows.

That last point causes the most difficulty later. A network understood by only one person stops being maintainable the moment that person moves away, and nobody knows the admin password.

Design for the busiest day, not the ordinary one. Count devices, not floor area. Mount access points three to four metres up and spread them out rather than stacking them in one corner. Separate the visitor network from the staff one, and keep a password even when it is announced.

The rest is upkeep: who pays the bill, and who knows the admin password when the people in charge change. Those two questions decide the network's lifespan far more than any hardware chosen today.

Frequently asked questions