Once you understand that a VLAN turns one switch into several separate networks, a fair question follows: how do those separate networks survive the trip between switches? You've got a Tampa office with switches on two floors, ten VLANs spanning both, and one cable connecting them. If everything's supposed to stay separated, how does that single uplink carry ten networks at once without scrambling them together?
The answer is a standard called 802.1Q, and the two ideas at its heart — tagging and trunking. This is where VLANs go from "neat concept" to "how the network actually works," and it's worth understanding even if you'll never touch a switch yourself. If you haven't read our VLAN basics yet, start there; this builds on it.
The problem trunking solves
Picture two switches. Switch A is on the first floor, Switch B on the second. You've set up VLAN 10 (staff) and VLAN 30 (cameras) on both, and there are devices in each VLAN on each floor. A staff PC upstairs needs to reach a staff resource downstairs. A camera upstairs needs to reach the camera network downstairs. Both kinds of traffic have to cross the one cable between the switches.
If that cable just carried "traffic," the switch on the other end would have no way to know which frame belonged to VLAN 10 and which to VLAN 30. The whole point of separation would collapse the moment traffic left the switch. You need a way to label each frame with its VLAN as it crosses the link.
The VLAN tag: a sticky note on each frame
That label is the VLAN tag. As a frame leaves the switch on a trunk link, the switch inserts a small piece of information into it — essentially a sticky note that reads "I belong to VLAN 10." The switch on the receiving end reads that tag, says "ah, VLAN 10," strips the note off, and delivers the frame into VLAN 10 on its side. VLAN 30 traffic gets a "VLAN 30" tag and the same treatment.
A VLAN tag is just a label stamped on each frame as it crosses a shared link, so the switch on the far end knows which network it belongs to and keeps it sorted.
This is the entire trick. One cable, many VLANs, kept perfectly separate because every frame carries its VLAN identity with it. The 802.1Q standard defines exactly how that tag is written so that equipment from different manufacturers agrees on it — which is why a switch and a firewall from two different vendors can trunk to each other.
Access ports vs. trunk ports
This gives us the two kinds of switch ports you'll hear about, and the distinction is the key to the whole topic.
Access ports — for end devices
An access port belongs to exactly one VLAN, and the device plugged into it has no idea VLANs exist. A PC, a printer, a regular phone — they send ordinary, untagged traffic. The switch quietly puts that traffic into the port's assigned VLAN, and strips the tag off anything coming back before handing it to the device. Most ports in a building are access ports: one device, one VLAN, no tagging visible to the device.
Trunk ports — for the links between switches
A trunk port is built to carry many VLANs at once, and it expects traffic to be tagged so it can keep the VLANs sorted. Trunks connect switch to switch, switch to firewall, or switch to a wireless access point that broadcasts several networks. That access point in your lobby that puts out both "Staff Wi-Fi" and "Guest Wi-Fi"? It almost certainly connects over a trunk port, with each Wi-Fi network riding its own VLAN tag down the same cable.
So the short version: access ports face the devices; trunk ports face other network gear. Access ports speak plain, untagged traffic for one VLAN. Trunk ports speak tagged traffic for many.
The native VLAN — the one exception
There's one wrinkle worth knowing, because it trips people up and has real security implications: the native VLAN.
On a trunk port, one VLAN is designated as "native," and traffic in that VLAN crosses the trunk untagged — no sticky note. This exists for historical compatibility: it lets a trunk interoperate with older or simpler gear that doesn't understand tags, and any untagged traffic arriving on the trunk gets dropped into the native VLAN.
That convenience is also a soft spot. If the native VLAN is left at the default and carries real traffic, it can open the door to "VLAN hopping" tricks where crafted frames slip from one VLAN into another. The standard hardening practice is straightforward: set the native VLAN to an unused, dead-end VLAN that has no real devices in it, and don't let anything important ride untagged. It's a small configuration detail with an outsized impact on whether your segmentation actually holds.
Putting it together: one uplink, ten networks
Now the original puzzle resolves cleanly. Back to the two-floor office:
- Each PC, phone, and camera plugs into an access port set to its VLAN. The devices send plain, untagged traffic and never know VLANs exist.
- The cable between the two switches is a trunk, carrying every VLAN at once.
- As traffic crosses that trunk, each frame wears a tag identifying its VLAN, so nothing gets mixed up.
- The native VLAN on the trunk is set to a safe, unused VLAN, not the default, so untagged traffic can't sneak between networks.
That's how a single uplink quietly carries ten separated networks. Scale it up — more switches, more floors, more sites — and the same principle holds. Trunks tie the segmented network together; tags keep it sorted; access ports keep it simple for the devices.
Why this matters even if you'll never configure it
You don't need to set up a trunk port to benefit from understanding this. The reason it's worth knowing is that the difference between a network that's genuinely segmented and one that just looks segmented often comes down to these details — trunks carrying the right VLANs and no more, native VLANs hardened, access ports locked to the correct VLAN. Get those wrong and the walls you thought you built have gaps in them.
This is the kind of unglamorous, behind-the-panel work that determines whether segmentation holds up under pressure, and it's part of how we build and maintain networks under our managed IT services. If your network was set up in a hurry years ago and nobody's been sure whether the VLANs are really separated, that's a very answerable question — and a worthwhile one for any business in Pinellas or Pasco County to settle.
The bottom line
802.1Q sounds like deep networking arcana, but the idea is plain: a tag is a label, a trunk is a shared road that carries many tagged networks, an access port is the simple end where devices plug in, and the native VLAN is the one quirk you harden so the whole thing stays honest. Understand those four pieces and you understand how a segmented network actually moves traffic — and how to tell whether yours is doing it right.
