Wireless¶
Wireless is where you record your Wi-Fi networks (SSIDs) and the groups that organize them - and you can link each SSID to the VLAN it bridges onto.
You build it in two layers: wireless LAN groups (how you organize SSIDs) and the wireless LANs (the SSIDs themselves).
Add a wireless LAN group¶
A group bundles related SSIDs together - for example Corporate, Guest, or IoT.
- Open Wireless → Wireless LAN groups in the sidebar and click Add group.
- Give it a name and a slug (a short URL-friendly identifier).
- Optionally add a description.
- Save.
Nothing is pre-filled
Danbyte ships no sample groups or SSIDs - you create exactly the ones your network uses.
Add a wireless LAN (SSID)¶
- Open Wireless → Wireless LANs and click Add wireless LAN.
- Enter the SSID - the broadcast network name.
- Optionally put it in a group.
- Set a status, the security details, and an optional VLAN bridge (see below).
- Save.
SSID details¶
| Field | What it records |
|---|---|
| Status | active, reserved, disabled, or deprecated. |
| VLAN | the VLAN this SSID bridges onto, so wireless and wired networks line up. |
| Security mode | WPA2-Personal, WPA3-Personal (SAE), WPA2/WPA3-Personal, the three Enterprise equivalents, Enhanced Open (OWE), Open, or the legacy WPA Personal, WPA Enterprise and WEP. |
| Cipher | Auto, AES-CCMP, GCMP-256, or TKIP (legacy). |
| PMF | Protected Management Frames: disabled, optional or required. |
| Pre-shared key | the passphrase of a Personal mode (or WEP key) - stored in the secret store, never in this record (see below). |
| Description / comments | free-text notes. |
Security settings that go together¶
The mode decides which cipher and PMF setting make sense, and Danbyte refuses the rest - the form only offers what fits, and the API returns a field error for anything else:
| Mode | Cipher | PMF |
|---|---|---|
| WPA2-Personal / -Enterprise | Auto, AES-CCMP, TKIP | any |
| WPA3-Personal (SAE) / -Enterprise | Auto, AES-CCMP, GCMP-256 | required |
| WPA2/WPA3 transition | Auto, AES-CCMP | optional or required |
| Enhanced Open (OWE) | Auto, AES-CCMP, GCMP-256 | required |
| Open, WEP | none | disabled |
Only Personal modes and WEP carry a passphrase. SAE (WPA3-Personal) still
starts from one, so it is stored the same way. Switching an SSID with a stored
passphrase to a mode without one - Enterprise, OWE or Open - removes the
passphrase on save; the form says so first, and the API refuses the switch
unless the same request clears it ("psk": null).
Leaving a field blank means not documented. The list has a PMF column and filter, so the SSIDs without PMF required are one click away.
The pre-shared key¶
A wireless key is a credential, so Danbyte treats it like one. The SSID record
holds only a reference; the passphrase itself is written to the
deployment's secret store - the same
local (encrypted) or vault backend device credentials use.
- Type the key into Pre-shared key on the SSID form. On an existing SSID the box is always empty: leaving it blank keeps the stored key, and typing a new one rotates it.
- The SSID page shows
••••••••when a key is set, with an eye button to reveal it. Revealing is a separate request, needs the reveal permission on wireless LANs, and is written to the change log - so who looked, and when, is on the record. - Deleting the SSID, or clearing the field, removes the key from the store too.
No secret store, no PSK
If no secret store is enabled, saving a PSK is refused with a message pointing at Settings → Security → Secret store. Danbyte does not fall back to keeping the key in the database in the clear - the same fail-closed rule every other key-bearing feature follows. Everything else about an SSID still saves normally; only the key needs a store.
SSID status¶
| Status | Meaning |
|---|---|
| Active | Broadcasting and in service. |
| Reserved | Planned or held, not yet live. |
| Disabled | Turned off. |
| Deprecated | Being retired. |
Groups in use can't be deleted
If a group still has SSIDs attached, Danbyte blocks the delete. Move or remove those SSIDs first.
Antennas¶
The radiating hardware documents on the DCIM side - see Antennas. In short: integrated elements are components on the AP (seeded from its device type), an external sector or dish is its own small device cabled to the AP's RF aux port, and gain/bands are structured fields, not free text.
Deleting several at once¶
Tick rows in the Wireless LANs or Wireless LAN groups list to delete several
at once. Before anything is removed Danbyte shows which rows go and which it
keeps because something still uses them. Only the free rows are deleted. More
than 1000 rows go 1000 at a time, under one confirmation (see
Large selections). The
bulk delete is POST /api/wireless-lans/bulk-delete/ (or
/api/wireless-lan-groups/bulk-delete/) with {"ids": [...]} (add
"dry_run": true for the preview) and needs the delete permission on the
type.
A group that still holds SSIDs is kept. A deleted SSID's pre-shared key is removed from the secret store, as with a single delete.
Wireless LAN group pages¶
Click a wireless LAN group name in its list to open its detail page - the pencil in the header edits it.
The Overview shows the group's name, slug and description; the Wireless LANs
tab lists every SSID in the group, using the same table the main Wireless LANs
page draws (minus the redundant Group column). It is powered by
GET /api/wireless-lans/?group=<id>, and it is the check to run before you
move or delete a group.
The page also carries Journal and Change log tabs. Groups have been audited all along, so the tab shows every recorded change to the row, including ones made before the page existed.
Wireless LAN pages¶
Clicking an SSID in Wireless → Wireless LANs opens that SSID's own page (it used to drop you straight into the edit form).
- Overview - the SSID, status, group, and description; then the Network card, which is what you actually come here to read: the VLAN it bridges onto, the security mode, cipher and PMF. Comments render below if there are any.
- Journal - your notes on this SSID.
- Change log - the automatic record of changes to the row.
Nothing in the data model points back at a wireless LAN, so the page has no related tabs - it links out to its group and VLAN, and stops there rather than padding itself with tabs that would always be empty.
Tags & custom fields¶
Need to track something extra - a controller name, a band, a PSK rotation date? Add a custom field for wireless LANs and it appears on every form. See Tags & custom fields.