UniFi Lab 01
Guest VLAN with no internet
Guest WiFi shows Connected but has no usable network.
Your job: get the guest phone online without opening the LAN.
This run: Break A. VLAN 40, subnet 192.168.40.0/24.
Lab complete. The guest phone is online and isolated from the LAN.
guest_online_isolatedConnected, isolated from LANTopology
Site: Guest WiFi lab- InternetISP handoff on the gateway WAN portWAN up
- Guest → WAN: AllowedGuest traffic reaches the internet.
- GatewayRoutes LAN and Guest. DHCP for 192.168.40.0/24, gateway 192.168.40.1
- Guest → Gateway (DHCP/DNS)Allow
- Guest → External / WANAllow
- Guest → LAN / InternalBlock
- Guest DNSAuto
- Port 1: Trunk, all VLANsGateway uplink. VLAN 1 untagged, VLAN 40 tagged.
- SwitchGuest traffic stops herePoE switch with port profiles12345678
Port 5 profile Access (LAN only)
- Port 5: VLAN 1 untagged, VLAN 40 droppedGuest tags dropped at the switch. Link LED is still up.
- Access pointSSID Guest-WiFi → VLAN 40Online
- Guest-WiFi, 5 GHz: ConnectedAssociated. RF looks fine.
- Guest phoneVisitor device on Guest-WiFino_ipNo IP
Client list
1 client| Connection | Connected |
|---|---|
| Network | Guest (VLAN 40) |
| AP | Access point, Guest-WiFi |
| IP | No IP |
| Gateway | No gateway |
| DNS | DNS unreachable |
| Internet | No |
| LAN (ping NAS) | Isolated from LAN |
Legend
- Link passes Guest traffic
- Guest traffic dropped or blocked
- WiFi association
- Up or allowed
- Failing symptom or block
- Warning, not a win
Controls
The six settings you can change in this lab. Everything else is fixed.
Switch, Port 5 (to the AP)
Guest network, VLAN 40
- VLAN ID
- 40
- DHCP mode
- DHCP Server
- Gateway IP
- 192.168.40.1
- Subnet
- 192.168.40.0/24
Zone-Based Firewall
WiFi, Guest-WiFi
Guests cannot reach each other. Keep it on.
Out of scope for this lab
Why this fails
copy key: no_ip_trunkThe AP uplink is an access port
Connected, No IP
Field note: the phone associates, so RF looks fine. Guest is a tagged VLAN. An access-only uplink drops those tags, so DHCP never arrives.
Fix: Trunk the AP uplink: Native = LAN/management, Tagged = Guest or Allow All.
Why Broken and Fixed
Console words
- No IPShowing
- No gatewayShowing
- DNS unreachableShowing
- Traffic blocked by firewallClear
- Connected, no internetShowing
- Isolated from LANYes, keep it
Associated is RF. Online is DHCP + gateway + DNS + WAN, with LAN still denied for guests.
Glossary
Core, Labs 01 to 03- Native
- Untagged VLAN on a switch port (PVID). Management traffic usually rides here on UniFi device uplinks.
- Tagged
- VLAN IDs carried with an 802.1Q tag on a trunk. Guest and IoT SSIDs need their VLANs tagged on the AP uplink.
- Access port
- One VLAN only, untagged. Fine for a printer. Wrong for an AP that serves multiple SSIDs.
- Trunk
- Native + tagged VLANs. Correct pattern for UniFi switch to AP / switch to gateway when multiple networks exist.
- ZBF
- Zone-Based Firewall. Policies between zones (Gateway, External, Internal, Guest, etc.), not just classic LAN IN rules.
- Gateway zone
- Where the router answers DHCP and DNS for a network. Block Guest to Gateway and clients get No IP or DNS unreachable.
- Client isolation
- WiFi setting that stops guest clients from talking to each other. Keep on for Guest.
- PoE class
- AF (~15 W), AT (~30 W), BT / PoE++ (higher). UniFi budgets on documented max draw, not quiet daytime watts.
- PoE budget
- Sum of max PD draws vs what the switch or injector can supply. Exceed it and devices disconnect.
- Injector
- Power source for a Flex or similar. Wrong class (AF on a loaded Flex) is a classic field fail.
- Max draw
- Datasheet maximum watts for a PD (IR on, boot). UniFi PoE budget math uses this, not the quiet live reading.
- Flex budget
- USW-Flex downstream totals by input: AF 8W, AT 20W, BT or 60W injector 46W (set Power Source to PoE Injector).
- Remote Unlock via Endpoint
- Access setting. When off, Endpoint receivers can talk on a call but cannot unlock.
- Door Attendant / receiver
- User assigned to get the door call. Not on the list means no Unlock for that door.
- Inform
- Device check-in URL to the Network application, usually controller host on port 8080, path /inform.
- STUN
- UDP 3478 helper for L3 / remote adoption. GUI on 443 is not the same path.
Fiber terms, glossary ready for later
MM and SM grades, cage form factors, DAC, AOC, and complementary BiDi ends. Full rows land with the fiber-sfp-dac lab.
Symptom words (overlay language)
Before and after
Diff rows marked| Setting or symptom | Broken start | Now |
|---|
Gear in this lab
- 1 Gateway
- 1 Switch
- 1 Access point
- 1 Guest phone
Config only. The fix needs no new hardware. Counts only, no prices.
Takeaway
Connected is not the same as online
When guest WiFi says Connected but nothing loads, the cause is usually a trunk or a firewall zone, not the internet provider. Fix it in this order and the LAN stays closed.
- Trunk the AP uplink. Native LAN, Guest tagged.
- Allow Guest → Gateway for DHCP and DNS.
- Allow Guest → External / WAN.
- Keep Guest → LAN blocked and client isolation on.
Want guest WiFi set up like this at your place? We design guest networks and VLANs as part of a UniFi install.
Also in Labs
All labs /labs
A teaching lab, not a quote and not a design for your site. Settings are simplified from the UniFi Network app. No account, and nothing from this lab is saved.