// SETUP GUIDE · UK ISPs

How to set up mesh WiFi properly

Most mesh systems are installed in ten minutes and then quietly underperform for years. This is the order we actually work in, what to test after each step, and the specific settings for BT, EE, Sky, Virgin Media, Plusnet, TalkTalk and Vodafone hubs. Nothing here needs a tool more exotic than a network cable. Rated 4.9 on Google.

Get us to set it up Compare mesh systems first

● 9 ordered steps
● Every major UK ISP
● Test after each step

/00 — READ THIS FIRST

Two things to check before you touch anything

Ask about the landline first. On BT, EE and similar Digital Voice services the telephone registers to the ISP hub itself. Putting that hub into bridge mode, or bypassing it, stops the landline working — including 999 calls from that handset. This catches people out constantly, and it matters most in exactly the households least able to cope with it. Check before you change the topology, not after.

Photograph the label on the base of the router now. Admin password, default network name, WiFi key, serial number. Bridge and modem-mode changes can lock you out of the web interface, and that sticker is often the only way back in.

/01 — BASELINE

Step 1: measure before you change anything

Plug a laptop into a LAN port on the ISP router with a cable and run a speed test. This is your ceiling. Everything else is about how much of it you can deliver to a room.
Write down your provider and package, the exact hub model from the base label, and whether the line is full fibre (an Openreach ONT box on the wall), FTTC over the phone socket, or Virgin coax.
Walk the property with a signal meter and record the reading in each room. Our free 365 WiFi Optimizer does this live in the browser. As a scale: −30 to −55 dBm is excellent, −55 to −67 is fine for video calls and streaming, −67 to −75 is marginal, and worse than −75 is effectively unusable.
Mark the dead spots on a rough floor plan. You are going to want this later to prove you fixed them.
Note where the master socket, ONT or coax entry is. It is very often the worst possible place in the house — which is precisely why the router ended up there.

/02 — PLACEMENT

Step 2: move the router (this is often the whole fix)

Central, not cornered. A router in the front hall of a terrace throws half its signal into the street.
Off the floor — waist height or higher, on a shelf. Ofcom’s own advice is a table or shelf rather than the floor.
Out in the open. Never inside a media cabinet, a metal-doored meter cupboard, a fitted wardrobe or the understairs cupboard.
Away from microwave ovens, halogen lamps, dimmer switches, speakers, televisions and monitors — that list is Ofcom’s — and also mirrors, wall-mounted TVs, fridge-freezers and hot water tanks.
If it has external aerials, point them in different directions rather than all straight up. It helps between floors.
If the socket is in the wrong place, move the router rather than accepting it: on full fibre, run Ethernet from the ONT to the router (up to 100 m is fine); on FTTC, fit a data extension; on Virgin, a coax relocation is a chargeable engineer visit.

Re-survey now. If placement fixed it, stop — you may not need mesh at all. We would rather tell you that than sell you three boxes.

/03 — TOPOLOGY

Step 3: decide who is in charge of the network

There are four sensible shapes, in increasing order of hassle:

A. ISP hub alone, better placed. Try this first.
B. ISP hub plus your mesh in access-point mode. No double NAT, you lose a few vendor app features. This is the fallback that works on every UK ISP and it is what we use most often.
C. ISP hub in modem/bridge mode, your kit doing everything. Cleanest result, but it kills the hub’s WiFi and usually its landline features.
D. Your own router straight onto the ONT, hub removed entirely. Best on full fibre, needs the provider’s authentication details, and loses any hub-dependent landline.

Understand double NAT before you choose. Two routers in series interfere with port forwarding, VPNs, some streaming and some gaming (an Xbox will report Strict or Moderate NAT). It does not slow down normal browsing, so it is not the disaster forums make out. But if you run a VPN to the office, a NAS, CCTV with remote viewing or a VoIP phone system, don’t accept it.

/04 — ISP BY ISP

Step 4: modem and bridge mode, provider by provider

Verified July 2026 — check your exact model on the day. Availability changes with firmware and hardware revision, and providers do move things.

Virgin Media (Hub 3, 4, 5 and Super Hub 1/2/2AC): connect by cable, browse to 192.168.0.1, log in with the settings password from the base of the hub (not the WiFi key), then Modem Mode → Enable → Apply Changes, and wait several minutes. Afterwards the hub’s WiFi is off and its interface moves to 192.168.100.1. Connect your router to Ethernet port 1 only — ports 2 to 4 stop working. Power-cycle the hub after connecting so it picks up the new WAN address.
Virgin Hub 5x: Virgin state modem mode is not currently available. Use access-point mode, or ask them to swap you to a Hub 5.
BT residential Smart Hub 2: no bridge or modem-only mode. The Business Smart Hub 2 does have one (Hub Manager → Advanced Settings → Broadband → Routing → Enable Bridging). On residential BT, use access-point mode or go direct to the ONT.
BT and EE on full fibre: the ONT is only a media converter — there is nothing to bridge. Run ONT to your router’s WAN port and configure PPPoE. Ask your provider for the correct credentials — never guess them on someone else’s account. Leave VLAN tagging off on genuine Openreach lines.
EE Smart Hub / Smart Hub Plus: no bridge mode. Turn the hub’s WiFi off and run your kit as access points, or (if there is no Digital Voice) go direct to the ONT.
Sky Broadband Hub: cannot be bridged. Sky uses DHCP rather than PPPoE, and some lines need DHCP Option 61 with a client ID. Option 61 support is patchy — present on many ASUS and Netgear routers, absent across much of TP-Link’s consumer range. Check before you buy a router for a Sky line.
Plusnet Hub Two (FTTC): 192.168.1.254 → Advanced Setting → Broadband → Internet → Bridging → Enabled. Then cable from one of the first three LAN ports to your router’s WAN port and set up PPPoE with your Plusnet credentials. On Plusnet Full Fibre, go straight to the ONT instead.
TalkTalk (Sagemcom hub): no true bridge mode. If TalkTalk supplied an eero on Full Fibre, the eero itself can be bridged. Otherwise, access-point mode with the Sagemcom’s WiFi disabled.
Vodafone: treat as an access-point-mode provider unless you can confirm otherwise with Vodafone for that specific hub and package.

Access-point mode — the universal fallback. Leave the ISP hub handling DHCP and NAT. Set the mesh to Access Point, Bridge or “use existing router”. Cable the mesh’s WAN port into a hub LAN port. Disable the hub’s 2.4 and 5 GHz radios completely — not just hide them. Give the mesh a different network name from the hub’s old one so you can always prove which network a device is really on.

/05 — BACKHAUL

Step 5: how the units talk to each other

Order of preference: Ethernet → existing coax → powerline → wireless. TP-Link’s own wording is that “a wired connection is more stable and faster than a wireless backhaul”, and they sell the wireless ones.

Cat5e is fine — 100 m maximum run, and it carries 2.5 Gbps the whole way. Use Cat6 on new installs if it costs little more. Do not pay for Cat7 or Cat8 in a house; it is money for nothing.
Practical routes: skirting trunking, UV-stable cable up an outside wall, through the loft into upstairs bedrooms, or alongside an existing aerial run. Solid-core in the walls, stranded patch leads for the last metre. Keep data cable about 50 mm away from parallel mains and cross it at 90°.
Check the property first. Many houses built from the 2000s onwards already have network sockets terminating in a hall or loft cupboard. Two minutes with a cable tester can save you a node.
Powerline only where Ethernet is impossible, and always directly into a wall socket — never an extension lead, surge strip or UPS. Expect a big drop across separate circuits and close to nothing across a separate consumer unit.
Coax networking is rarely right in the UK — most homes have no in-house coax backbone, and standard TV splitters block it.

The single most common DIY mistake: running wireless backhaul through the one wall you already know is the problem. You get full bars and terrible speed, and it is baffling until you realise the node is only as good as its link home.

/06 — NETWORK NAMES & SMART DEVICES

Step 6: one network name, and the smart-home trap

Default to one network name across all bands with band steering, so devices roam properly instead of clinging to the wrong one.

Then there is the exception that generates more support calls than anything else on this page. A great deal of smart-home kit — plugs, bulbs, video doorbells, robot vacuums, older printers, thermostats, garage door openers, cheap cameras — is 2.4 GHz only. During setup they scan 2.4 GHz only, and if the phone running the app is sitting on 5 GHz, pairing fails with a misleading “wrong password” error. Nothing is wrong with your password.

A UK-specific gotcha almost nobody mentions: the UK permits 2.4 GHz channels 1–13, but many US-designed smart devices only support 1–11 and literally cannot see a network on channel 12 or 13. If a device insists it “cannot find” a network that is plainly working, check the channel before you check anything else.

Clean fix: a dedicated 2.4 GHz network for smart devices, where your system supports one.
Quick fix: temporarily disable 5 GHz or create a temporary 2.4 GHz guest network, join the phone to it, pair the device, then re-enable. Most devices remember the name and password, not the band.
Naming: one clear main name plus -IoT and -Guest. Avoid your house number, your business name and address, or the router model. Never leave the manufacturer default.
Keep the name and password identical on every node and on any access point you have kept.

/07 — CHANNELS

Step 7: channels and widths (set them manually)

2.4 GHz: channel 1, 6 or 11 only, at 20 MHz. Using 40 MHz on 2.4 GHz in a terrace or a block of flats is antisocial and self-defeating — you will interfere with your neighbours and they with you.
Pick the 2.4 GHz channel by scanning from the middle of the property and weighting by signal strength, not the number of networks. One very strong neighbour on channel 6 is worse than four weak ones on channel 1.
5 GHz: 80 MHz is the sensible default. Drop to 40 MHz if lots of strong neighbours overlap. 160 MHz is worth trying only in a detached property, because in the UK a 160 MHz block almost always includes radar-sharing channels.
Radar channels, explained properly. UK 5 GHz splits into channels 36–48 (no radar detection required, 200 mW), 52–64 (indoor only, radar detection and power control required), 100–140 (indoor and outdoor, up to 1 W, radar detection required) and 149–165 (no radar detection, 200 mW). Before using a radar-sharing channel the equipment must listen for at least 60 seconds, must stop transmitting within 10 seconds of detecting radar, and must then avoid that channel for at least 30 minutes.
The Dorset rule: near an airport, a Met Office radar, a port or an exposed coastal site — which covers a great deal of this county — pin 5 GHz to a non-radar channel and accept slightly more neighbour congestion. It is the difference between a network that occasionally vanishes for a minute and one that doesn’t.
6 GHz is licence-exempt in the UK from 5925–6425 MHz and essentially empty of neighbours — excellent for backhaul and same-room speed, poor through walls. Treat it as a same-room band.
Set channels manually. Auto-channel re-scans and hops, and each hop is a short outage. Re-check every 6–12 months.

/08 — PLACING NODES

Step 8: place the nodes, one at a time

Halfway, not in the dead spot. This is the most common mistake by a distance. A node placed where there is no signal has nothing to relay.
Distance ceiling on wireless backhaul: TP-Link suggest no more than about 15 m between Deco units; Netgear suggest planning to about two-thirds of a node’s maximum range so coverage overlaps. If the nodes are wired, distance stops mattering entirely.
Count walls, not metres. One stud wall is cheap. One solid brick wall is expensive. Two solid walls plus a chimney breast is fatal to 5 GHz. Prefer hallways and landings with line of sight through doorways.
Same height as the main unit, in the open, away from metal cabinets, microwaves and USB 3.0 devices. A shelf beats a socket behind a bed.
Add nodes one at a time: set up the main unit and confirm internet → power the first satellite in the same room, let it join and update its firmware → move it to position → check the link quality in the app → only then open the next box.
What good looks like: TP-Link recommend at least two bars between units. As an engineering guide, aim for −60 dBm or better node-to-node, and treat worse than about −70 dBm as needing to move the node closer to the router — not further towards the dead spot, which is the instinct and is wrong.
Name every node something meaningful: “Landing”, “Kitchen”, “Loft office”. Future you will be grateful.
After each node, walk the survey again and speed-test both next to the node and in the room it was meant to fix. Fast at the node but poor in the room means the position is wrong. Poor even at the node means the backhaul is the problem.

/09 — SECURITY & HANDOVER

Step 9: lock it down before you call it finished

Change the router’s admin password. Three random words plus a number or symbol, stored in a password manager rather than on a sticky note under the hub.
Set WPA3, or WPA2/WPA3 transitional if older devices need it. WPA3 has been mandatory for newly certified devices since July 2020. Never leave WEP or WPA/TKIP enabled.
Change the WiFi password from the one on the label if it has ever been photographed, given to a tradesperson, or if the router is second-hand. Length beats complexity.
Disable WPS. It is not part of WPA3 certification and it is a known weak point.
Turn off remote management and UPnP unless something genuinely needs them.
Enable automatic firmware updates on the router and every node — and check they are actually applying. Look up the manufacturer’s end-of-support date too: an unsupported router is a permanent open door, and no amount of good configuration closes it.
Set up a guest network with client isolation. Give it its own password and change it now and then. The trades and the cleaner should not have your main password.
Segregate true set-and-forget devices — cameras, plugs, sensors, doorbells. One caveat: on some consumer kit the “IoT network” is a convenience band-split rather than genuine isolation, so check whether your vendor documents actual separation. And leave Chromecast, AirPlay, Sonos, smart TVs and printers on the main network unless your router supports cross-network discovery, or they will simply vanish from everyone’s phones.
Business note: under Cyber Essentials, an ISP-provided home router is out of scope for a homeworker — but a router the business supplies is in scope and must meet the firewall requirements. Worth knowing before you buy kit for staff.

/10 — THE ORDER

The order, and what to test after each step

Baseline → placement → topology (check for double NAT: is the second router’s WAN address a private one?) → backhaul (confirm the links come up at 1 Gb/s, not 100 Mb/s — a 100 Mb/s link on gigabit kit almost always means a damaged pair) → nodes, one at a time → network names (walk the property and confirm the phone holds one name) → channels (leave it 24 hours, then check the logs for radar events and auto-channel changes) → security (try to reach a main-network device from the guest network — it should fail) → onboard the awkward devices last and test end-to-end (does the doorbell notification actually arrive on a phone that is on mobile data?) → document and hand over.

Realistic targets to aim for: −55 dBm or better in the main living and working rooms; at least 50–60% of your wired baseline over WiFi in the same room as a node; and no dead zones where a video call drops. Never promise the headline package speed over WiFi anywhere — if an installer does, be suspicious.

Change one thing at a time, with a test in between. Change five things at once and you cannot reproduce the fix, or diagnose the regression next week.

FAMILY-RUN SINCE 1995 · ★ 4.9 ON GOOGLE · 200+ COMPUTERS UNDER OUR CARE · NO FIX, NO FEE · SAME-DAY REMOTE SUPPORT

// GOOD QUESTIONS

Frequently asked

Can I put my Sky router into modem mode for mesh WiFi?

No — Sky’s hubs have no bridge or modem-only mode. The reliable route on Sky is access-point mode: leave the Sky hub in charge of the connection, cable your mesh’s main unit into it, switch the mesh to AP/bridge mode and turn the hub’s own WiFi radios off. If you’d rather replace the hub entirely, Sky uses DHCP rather than a username/password, and some lines need DHCP option 61 support — patchy on consumer routers, so check before buying one for a Sky line.

Should I put my ISP router in bridge mode or use access point mode?

Access-point mode is the safer default and works on every UK provider: the ISP hub keeps handling the connection, your mesh handles the WiFi, and you disable the hub’s radios completely. Bridge or modem mode gives a slightly cleaner result but is unavailable on several UK hubs — including the residential BT Smart Hub 2, the Sky hub and the Virgin Hub 5x — and it will stop a Digital Voice landline working, including 999 calls from that handset.

How do I put a Virgin Media hub into modem mode?

Connect by cable, browse to 192.168.0.1 and sign in with the settings password printed on the base of the hub (not the WiFi key), then choose Modem Mode, enable it and apply. Wait several minutes. Afterwards the hub’s WiFi is off and its interface moves to 192.168.100.1, and you must use Ethernet port 1 — ports 2 to 4 stop working. Note that Virgin state modem mode is not currently available on the Hub 5x.

Why won’t my smart plug or video doorbell connect to my WiFi?

Almost always because the device is 2.4 GHz-only and the phone running the setup app is on 5 GHz — which usually shows up as a misleading “wrong password” error. Join the phone to a 2.4 GHz network temporarily and pair again. If it still cannot see the network, check the 2.4 GHz channel: the UK allows channels 1–13 but many US-designed devices only support 1–11 and are blind to 12 and 13.

Where should I put my mesh WiFi nodes?

Roughly halfway between the router and the problem area — not in the dead spot itself, which is the most common mistake. Keep them at the same sort of height as the main unit, out in the open, and count walls rather than metres: one stud wall is cheap, one solid brick wall is expensive. Add them one at a time, pairing each in the same room as the main unit before moving it into place.

Do I need to run Ethernet between mesh nodes?

You do not have to, but it is the single biggest improvement available. Wireless backhaul shares airtime with your devices and loses close to half its throughput per hop. If you can get one cable between two points — through a loft, along a skirting or up an outside wall — it will outperform spending several hundred pounds more on radios.

What WiFi channel should I use in the UK?

On 2.4 GHz use channel 1, 6 or 11 at 20 MHz width, chosen by signal strength rather than the number of neighbouring networks. On 5 GHz, 80 MHz is the sensible default. Near airports, ports or the coast — much of Dorset — pin 5 GHz to a non-radar channel, because radar detection will otherwise knock you off the channel for at least half an hour at a time.

Would you rather we just did it?

We set up mesh networks properly — placed, wired where it matters, channels planned, IoT devices onboarded and the whole thing documented and handed over. Remote where possible, in person across Bournemouth, Poole and Dorset where it isn’t.

Get us to set it up Compare mesh systems first

01202 775566 · help@365techies.co.uk · MON–FRI 9AM–5PM