This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
2.4 GHz has few non-overlapping channels. 5 GHz and 6 GHz have more, and they have rules about width. A wider channel is more throughput and more chance of overlap. The visualiser shows overlap from channels you type. It does not scan the building.
A survey you were asked to do is a walk with a purpose. This page does not tell you to capture other people's networks beyond the channel numbers you need to avoid them.
Write the band, the width, and the channel for one access point. The AP-count page owns how many radios. This page owns the channel choice.
6 GHz is not automatic. The clients have to support it. Say whether they do.
The change you can finish
Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.
Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.
- Name the AP.
- Choose a band the clients support.
- Choose a width.
- Pick a channel and check overlap with the ones you already run.
- Write it down.
- Do not turn on every width to see.
Mistakes that outlive the command
Wi-Fi Channels Explained (2.4, 5 and 6 GHz) goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Every AP on the same 2.4 GHz channel.
- A wide channel chosen without looking at overlap.
- A scan saved as a map of neighbours' traffic.
- 6 GHz enabled for clients that cannot use it, as the only SSID.
Decisions to write down
One decision for Wi-Fi Channels Explained (2.4, 5 and 6 GHz): The band is written. The width is written. The channel was checked against your other APs. Client support is a yes or no. And no capture of neighbour payloads.
Checks before you call it done
Confirm this before you call the change done: AP, band, width, and channel are in the ticket. Overlap with your APs was considered. No payload capture was taken. The SSID change waits. And one AP is this window. If one of those fails, stop.
One AP. One channel.
Do not capture neighbour payloads.Before you leave the device
Wi-Fi Channels Explained (2.4, 5 and 6 GHz) ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.
0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.
One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.
A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.