Guest WiFi: share the password, not the LAN

Pasting the main network password on a wall hands every stranger who walks in the same subnet as your till, cameras, NAS and printer. What belongs on the wall is a guest network.

1. What sharing one network actually exposes

AssetShared networkSeparate guest network
Till / office laptopVisible and probeable by visitor devicesDifferent subnet; not discoverable
Cameras / NASWeak-credential devices get scanned automaticallyUnreachable once isolated
Printer / shared driveCan be joined or printed to by accidentInvisible to guests
BandwidthLarge downloads slow the business downCan be capped independently

The point is not defending against a determined attacker — it is keeping mass accidental mistakes and low-grade automated scanning out. Most small venues are not breached; they are inconvenienced by a visitor's adware rattling around the subnet.

2. Three things make it real

Non-negotiables

  1. A separate SSID. Enable "Guest Network" in the router and name it plainly, e.g. shopname-Guest.
  2. Client isolation (AP isolation). Devices on that network become invisible to each other.
  3. A password different from the main one. Staff and your own devices keep the main network; the guest password can rotate without disruption.

Two optional settings that are usually worth it: a bandwidth cap (give guests about a third of the link) and a schedule (switch the guest network off after closing).

3. Where to find it — menus differ, logic doesn't

If the firmware has no guest network at all, two alternatives: replace the router with one that does (simplest), or put a dedicated access point on a separate VLAN for guest traffic — physically more thorough.

4. Prove the isolation works

  1. Join the guest network and try to reach a main-network device — a NAS admin page or a camera IP. It should fail.
  2. Use two devices on the guest network and try to ping or transfer files between them. It should fail.
  3. Run a speed test: confirm the cap applies and main traffic is unaffected.

If anything "just works", isolation is not in place. The usual cause is a guest network bridged onto the main subnet, or a "guest" label that is only cosmetic.

5. Turn it into a scannable sign

Once the guest SSID and password exist, put them in a QR code: guests join without staff repeating the password, and a rotation means reprinting one small insert instead of the whole board.

Build it in the WiFi QR studio; wording and placement are covered in the guest sign guide; the rental case is in the rental card guide.

6. Password policy

SettingRotateNote
Café or restaurant, dozens per dayMonthlyAlign with the business cycle and reprint the insert
Rental / AirbnbEvery turnoverSo the previous guest cannot keep using it
Office guest networkQuarterly, or on departureEspecially when interns share it with visitors
HomeAlmost neverUnless an unknown device shows up

Make the password easy to read and type: lowercase letters and digits, avoid 0/O and 1/l, 10–12 characters. Guest access is about usability, not symbol soup.

7. Two things people forget

Put the guest network on a sign

Enter the guest SSID and password, pick a layout, export a PDF, print it for the counter or the door.

Open the WiFi QR studio

Related guides

Frequently asked questions

Does a guest network need to be separate from the main one?
Yes, and the value is isolation, not the extra name. Guest devices must not share a subnet with the till, office laptops, cameras or NAS, so a malicious or adware-infected visitor device cannot discover them.
What is client isolation?
AP isolation (or guest isolation) makes devices on the same network invisible to each other. It is usually a checkbox next to the guest network switch; with it on, guests cannot reach each other either, which suits shops and rentals.
How often should the guest password change?
By traffic: a shop serving dozens of people a day about once a month, a rental at the end of every stay, an office quarterly or when someone leaves, a home almost never. Keep the printed card as a replaceable insert so a rotation costs one reprint.
Can I limit guest bandwidth?
Most routers with a guest network expose a bandwidth cap or priority setting. Giving guests roughly a third of the link and prioritising the main network keeps downloads from starving the till or office traffic.
Am I responsible for what guests do on my network?
Rules differ by jurisdiction. The safe framing is to treat guest access as a utility: post usage terms, avoid logging or inspecting traffic, and follow local registration requirements where they exist.

Templates that fit this setup

Three layouts picked for this scenario — swap the venue name and password, then export.