VLANs do their job by keeping networks apart. But "completely apart" is rarely what a real business needs. Staff workstations have to reach the file server. The phones need to find the phone system. Everything needs a path to the internet. So the moment you segment a network, you create the next question: how do segments talk to each other when they're supposed to be separated?
The answer is inter-VLAN routing — and the whole skill is doing it selectively, so that the traffic that should cross between VLANs can, and everything else stays blocked. This is where segmentation either pays off or quietly falls apart. If you're new to the series, our VLAN basics and tagging articles set the stage; this is the next step.
Why VLANs can't talk by default — and why that's good
By design, a device in VLAN 10 cannot reach a device in VLAN 30 on its own. They're separate networks with separate address ranges, and a switch alone won't carry traffic between them. That isolation is the entire point of segmenting.
But isolation taken to the extreme makes the network unusable. The trick isn't to tear the walls down — it's to install controlled doors in them. Routing is what provides those doors. The question shifts from "can these VLANs talk?" to "which VLANs should talk, in which direction, and for what?"
The default gateway: every VLAN needs an exit
Start with a concept you've already met without naming it: the default gateway. When a device needs to reach anything outside its own VLAN — another segment, or the internet — it hands the traffic to its default gateway. The gateway is the device that knows how to route beyond the local network.
In a segmented network, each VLAN gets its own gateway address. VLAN 10 might use a gateway at one address, VLAN 30 another. Whatever device holds those gateway addresses is the thing doing the routing between VLANs. That device is the doorway between segments — which makes it the natural place to enforce the rules about who's allowed through. Two main designs put a device in that role.
Design 1: Router-on-a-stick
The classic, economical approach is charmingly named router-on-a-stick. You connect a single router to the switch over one trunk link — the "stick." On that one physical connection, you configure a virtual sub-interface for each VLAN, each holding that VLAN's gateway address.
Traffic from VLAN 10 destined for VLAN 30 travels up the trunk to the router, the router moves it from the VLAN 10 sub-interface to the VLAN 30 sub-interface, and it heads back down to the right segment. One router, one cable, all the routing between VLANs.
- Upside: simple and cheap — you reuse a router you likely already have.
- Downside: every bit of inter-VLAN traffic has to make a round trip up and down that single link. For a small office it's perfectly fine. For a busy network with heavy traffic between segments, that one link becomes a bottleneck.
Design 2: Layer 3 switch with SVIs
The faster, more common approach in modern business networks uses a Layer 3 switch — a switch that can also route. Instead of sending traffic out to a separate router, the switch routes between VLANs internally, at hardware speed.
It does this with SVIs — Switched Virtual Interfaces. An SVI is a virtual interface inside the switch that represents a whole VLAN and holds its gateway address. You create one SVI per VLAN, and the switch routes between them itself. No round trip to an external router, no single-link bottleneck.
Router-on-a-stick sends inter-VLAN traffic out to a router and back. A Layer 3 switch does the routing inside the box, at switch speed. Same job, very different performance.
For most growing businesses, a Layer 3 switch is the better foundation. But routing between VLANs is only half the design. The half that determines whether your segmentation is real is what you do with access control.
ACLs: the actual security lives here
Here's the part people miss. Turning on inter-VLAN routing, by itself, can quietly undo your segmentation. If every VLAN can now route freely to every other VLAN, you've rebuilt a flat network with extra steps — the walls are up, but every door is wide open.
The control that fixes this is the ACL — Access Control List. An ACL is a set of rules on the routing device that says which traffic may pass between VLANs and which may not. It's the lock on each door. Good ACLs are written from a "deny by default, permit only what's needed" stance:
- Staff to servers: permit — but only to the specific services they need, not everything.
- Guest to anything internal: deny. Guests get internet and nothing else.
- Cameras and IoT to the business network: deny. They have no business initiating connections inward.
- Workstations to the camera management interface: permit only from the specific machines that administer it.
Written well, ACLs turn "the VLANs can route to each other" into "exactly these conversations are allowed, and nothing else." That's the difference between a network that's segmented on paper and one that's segmented in practice. This careful rule-writing is a core part of how we approach network security for the businesses we support.
Don't forget the firewall
On many small-business networks, the firewall itself does the inter-VLAN routing and enforces the rules between segments. That's often the cleanest arrangement: the device already built to inspect and filter traffic is the one deciding what crosses between zones. Whether the routing lives in a Layer 3 switch, a router, or the firewall, the principle is identical — routing connects the segments, and access rules decide what's actually allowed to cross.
Putting it together
A well-built segmented network ends up looking like this:
- Each VLAN has its own gateway, so devices know how to reach beyond their segment.
- A Layer 3 switch or firewall routes between VLANs efficiently.
- ACLs permit only the specific cross-VLAN traffic the business actually needs.
- Everything else between segments is denied by default.
The outcome is a network that's both usable and contained: staff reach what they need, guests and untrusted devices stay boxed in, and a problem in one segment can't simply route its way into the others. Designing those rules correctly — tight enough to protect, open enough not to break daily work — is exactly the kind of thing we handle in our managed IT services for businesses across Tampa Bay.
The bottom line
Segmentation isn't about total isolation — it's about controlled connection. Inter-VLAN routing provides the doors between your segments; ACLs decide who walks through them. Skip the access rules and you've quietly flattened your network again. Get them right and you have the best of both worlds: segments that talk when they should and stay silent when they shouldn't. If you've segmented your network but were never sure the rules between VLANs were locked down, that's a question well worth answering.
