Put the guest network on the fridge

Because the code is not a key to the wall; it is the password itself, written in a shape a camera can read. Four separate conversations say a Wi-Fi code is unencrypted — whoever scans it has the password in plain text — and two contraindications say the same thing from the other side: do not print the main network’s code if you have devices you do not patch, or visitors you do not fully trust. Three separate conversations say the answer is a guest network, which routers offer as a second network with its own name and password, kept apart from the one your own devices are on. The accounts give two reasons and argue about which matters. One exchange of one account to one puts privacy first — a guest on your main network can see the devices on it — a caution with two accounts names the smart television and the streaming box; the other side, in two separate conversations, says the bigger reason is a visitor’s phone or cheap gadget that already carries something, which scans whatever network it lands on. Two prerequisites the accounts state add the setting that makes the guest network worth having: the option, on some routers, that stops guest devices from seeing each other or anything local — the accounts call it client isolation or no local access. One account says a guest network with a bandwidth cap keeps a visitor from taking the whole connection. The conversation this page began from is its own correction: the original advice was to print the main network’s code, and the poster changed it to the guest network after being told so. Switching on a guest network for any particular router is a gap in these conversations; the router’s own manual or its settings page is the place.

On the phone that is already connected. Three separate conversations say the phone makes the code itself: on the two common phone systems the network’s own settings page, or the phone’s saved-passwords screen, has a share or show-as-code option, and this page checked that one of the two system makers documents it — the device gives you a code, and a friend scans it with another device to join. The other system gained the same screen in 2024, so one correction in these conversations, which said it had no such feature, was true when it was written and is not now. One contraindication and one caution, from separate places in these conversations, say the reason to use the phone: a website that offers to turn your network name and password into a code has just been given your network name and password, and the accounts say there is no way to know what it keeps. One account who wanted no website and no phone screen says the code is only a line of text in a fixed shape — the network type, the name, the password, each after its own label — and any tool that makes a code from text will make this one; this page carries that as one account’s. What the code makes possible is the other four-conversation theme: a password so long and random that nobody would type it, which the accounts say is the point — the code carries the typing. On what the password should be, the accounts argue with each other. Two conversations say some hosts prefer a guessable one — a name, a phone number — because it is easier to remember and, they argue, less risky if exposed; one contraindication says not a phone number and not a simple pattern, and one correction says the attacks that work are not brute force but dictionaries of words and known leaks with variations, so a simple pattern is exactly what gets tried. Two single accounts say the middle path: a long phrase of ordinary words is both easy to remember and hard to crack, because length is what costs an attacker time. This page carries the contraindication’s direction.

This is the loudest doubt in these conversations, and most of it is dated. Four separate conversations say not every phone reads a Wi-Fi code and that a visitor without a connection cannot download the reader they would need — and three conversations say the whole idea is not practical for everyone, because of the phone or because the person has never scanned anything. Those conversations run from 2012, and the cameras on phones sold since about 2017 read a code without any added app; one account, later in these conversations, says people were far less baffled by codes after the pandemic. So the chicken-and-egg problem — no connection to fetch the app that reads the code — mostly belongs to the phones of that decade, and one account in an exchange of one to three says even now a code in poor light, at a bad angle, can take longer than typing a short password. The repair the accounts give for the visitor it does not work for is on the paper itself: one account, and one more in a second place, writes the network name and password in plain letters under the code, for laptops and for the person who prefers to type. One exchange of two accounts to one argues whether that defeats the purpose — the two say it is acceptable for the convenience, the one says text under the code is the password on the wall for anyone who can read; this page carries both and notes that the code alone was already the password for anyone who can scan. Two conversations turn the code into something to look at — a cross-stitch, a tile mosaic, a sticker — and one caution says a code on anything that is not flat, a cushion for instance, may not scan. Single accounts add a tap-to-join tag behind the paper for phones that read those, and this page carries it as theirs. What to offer a visitor whose device reads nothing at all is a gap in these conversations; the accounts’ own answer is the words under the code, said aloud.

Anyone who can see the fridge, and that is the whole question of where it hangs. One exchange across accounts runs two to three: the two say a code in your kitchen is for people you have already let through the door, and the three say the door is not the boundary — a window onto the street, a neighbour’s visit; single accounts add a tradesperson in the house alone and a photograph of your kitchen posted online. One caution says a code visible from outside can be scanned from outside; one account hangs theirs on the ceiling so it appears in no photographs, and this page carries that as one account’s. Two accounts in one caution, and one more in another, say a paper code can be swapped for one that points a scanning phone at something else — which is a reason to notice if your code has been reprinted by someone who is not you. Two contraindications name the homes this is not for: a house that strangers pass through often, and a small town where the accounts say the network name alone tells everyone whose it is. Taking it back is the easy part, and two separate conversations say so: change the guest network’s password and the code on the fridge stops working that moment, for everyone who ever scanned it, because the code is only the password. One caution adds the cost: you print a new code. How to remove one particular guest while keeping the others is a gap in these conversations, and the accounts’ own method is to change the password and reprint. The argument under all of this is whether the code is worth having at all, and the accounts run it two ways. Within one conversation, three accounts to three, it is convenience against a security risk or an annoyance; across conversations, three to three, it is the fork above — whether being asked for the password is a nuisance to remove or part of having people in your home. One exchange of one to one says it is overkill for a quiet household and made for a flat with a new face every weekend, and two objections with five accounts behind them ask why anyone has enough visitors to need it; the accounts who do have them answer that they were tired of spelling.