Jensen IT Notes
Back to blog

Networking & Homelab

VLAN Basics for Homelab Beginners

June 24, 2026

A beginner-friendly explanation of VLANs and why they are useful in homelab and small network practice.

Network+VLANHomelabNetworkingSwitching

VLANs let you separate networks on the same physical switch. In a homelab, VLANs are useful for practicing how business networks separate users, servers, guests, cameras, labs, and management devices.

What a VLAN does

A VLAN is a logical network segment. Devices in one VLAN are separated from devices in another VLAN unless routing or firewall rules allow communication.

Beginner-friendly version: VLANs are like separate rooms inside the same building. Cantonese-friendly: “同一部 switch 入面,可以分幾個唔同 network 房間.”

Why VLANs are useful

VLANs help with:

  • Separating guest Wi-Fi from private devices.
  • Keeping lab servers away from daily devices.
  • Practicing small business network design.
  • Reducing broadcast traffic.
  • Applying firewall rules between groups.

Access ports and trunk ports

An access port usually carries one VLAN for an end device like a PC, printer, or camera.

A trunk port carries multiple VLANs, often between switches, routers, firewalls, or access points.

VLANs and Wi-Fi

Many access points can map different SSIDs to different VLANs. For example:

  • Staff Wi-Fi on one VLAN.
  • Guest Wi-Fi on another VLAN.
  • Lab Wi-Fi on a third VLAN.

If the switch port and AP VLAN settings do not match, users may connect to Wi-Fi but get no internet.

Beginner homelab example

A simple homelab might use:

  • VLAN 10 for daily devices.
  • VLAN 20 for lab servers.
  • VLAN 30 for guest Wi-Fi.
  • VLAN 99 for network management.

Start small. One or two VLANs are enough for learning.

Beginner Note

VLANs do not automatically provide internet or security by themselves. You also need routing, DHCP, firewall rules, and correct switch configuration.

Common Mistake

A common mistake is creating a VLAN on one device but forgetting to allow it on the trunk port or create DHCP for it.

Practical support example

After a new AP install, users connect to the staff SSID but get APIPA addresses. The SSID may be mapped to VLAN 20, but the switch trunk does not allow VLAN 20.

FAQ

Do I need VLANs at home?

No, but they are useful for learning and for separating guest or lab devices.

Is a VLAN the same as a subnet?

No. They often work together, but a VLAN is Layer 2 separation and a subnet is IP addressing.

Can VLANs improve security?

They can help, but only when paired with proper routing and firewall rules.

Quick Check

Original beginner-friendly review questions — not real exam questions.

1. Easy: A homelab uses one switch but wants guest and lab devices separated. What concept helps?
A. VLANs
B. Static DNS entries only
C. A larger DHCP lease time only
D. A different SSID name with no network changes

Answer: A. VLANs.

Why: VLANs provide logical separation on shared switching hardware.

2. Medium: An SSID is mapped to VLAN 30, but the switch trunk only allows VLAN 10 and 20. What symptom is likely?
A. Clients may connect but fail DHCP or network access
B. Clients will always get the management VLAN automatically
C. Only DNS will fail while DHCP always works
D. Only wired clients will be affected

Answer: A. Clients may connect but fail DHCP or network access.

Why: The wireless association can work while the VLAN path is blocked.

3. Hard: You created VLAN 20 but clients have no internet. What else may still be required?
A. Routing, DHCP, gateway, and firewall rules
B. Only changing the VLAN name
C. Only increasing Wi-Fi transmit power
D. Only clearing one client DNS cache

Answer: A. Routing, DHCP, gateway, and firewall rules.

Why: A VLAN alone is not complete connectivity. Supporting services and policies must also exist.

Keep exploring practical fixes

Browse more support notes and build a stronger troubleshooting routine.

View all posts