Cyberlium

Network › Module 3 › Lesson 2

BeginnerModule 3Lesson 2/5

VLANs and Trust Zones as Ideas

Zones are named trust, not magic tags — then map ideas onto THIS host and /:8792.

15 min+40 XP3 quiz
Module progress2 of 5

Visual · vlan_trust_zones

A VLAN tag is not automatically trust. Loopback zones on 8782/8792. Original Cyberlium.

Opening

A VLAN is a label. A trust zone is a promise about who may speak. The label can lie.

Lesson 1 named blast radius. This lesson names the usual cure as an idea, not as a switch cookbook. A VLAN (virtual LAN) splits broadcast domains when someone actually configures the switch and the ports. A trust zone is a sentence: “these identities may use these ports toward these dests.” You can have VLANs with no real trust (every VLAN routed any-any) and trust without 802.1Q (host firewalls, security groups, identity-aware proxies). Original Cyberlium. DEMO http://192.168.0.1/ YOUR lab app.

1. 802.1Q is plumbing; trust is policy

Tags keep some broadcasts off some ports. They do not decide whether VLAN 20’s app server may query VLAN 30’s database. That decision is routing policy, firewall policy, or a service mesh — words for “named yeses.” If the core router says any-any between VLANs, you bought colored cables.

Cyberlium will not walk you through Cisco IOS on a switch you do not own. If 192.168.0.1 is the home router, STOP: consumer “VLAN” pages are easy to brick and still not your classroom. Your artifact is a zone list on disk plus THIS host’s addresses.

Command guide

802.1Q is plumbing; trust is policy

═══ INSTALL ═══

Linux (Debian/Ubuntu):

Command — copy this

sudo apt install dnsutils

macOS: Built-in

Windows: Use nslookup (built-in)

═══ COMMANDS ═══

Command — copy this

ip -4 -o addr show || powershell.exe -NoProfile -Command "Get-NetIPAddress -AddressFamily IPv4 | Select-Object IPAddress,InterfaceAlias | Format-Table -AutoSize"

2. Two loopback dests keep the idea honest

Calling 8782 “guest” and 8792 “app” does not isolate them in the kernel the way a NIC-per-zone would. It still trains the sentence: traffic is allowed because you named a dest, not because they share 127.0.0.1. Same IP, different ports, different promises — like two processes that should not share credentials.

Do not bind either to 0.0.0.0 to “make VLANs more real.” Publishing on Wi-Fi is the opposite of a zone. Wait for the lab to start listeners on loopback only.

Command guide

Two loopback dests keep the idea honest

═══ INSTALL ═══

Linux (Debian/Ubuntu):

Command — copy this

sudo apt install curl
sudo apt install python3

macOS:

Command — copy this

brew install python3

Windows: Built-in (PowerShell: Invoke-WebRequest) Download https://python.org/downloads/

═══ COMMANDS ═══

Command — copy this

python3 - << 'PY'
import socket
for name, port in (("public_cartoon", 8782), ("app_cartoon", 8792)):
  s = socket.socket(); s.settimeout(0.4)
  r = s.connect_ex(("127.0.0.1", port))
  s.close()
  print(name, "127.0.0.1:%s" % port, "up" if r == 0 else "down(%s)" % r)
PY

Command — copy this

curl -sS -m 2 -I "http://127.0.0.1:8782/" | head -n 8

3. Identity-aware zones beat tag-only folklore

Zero-trust marketing aside, the useful beginner idea is: do not trust a packet because it arrived from “inside.” Inside is a VLAN id someone could mis-patch. Trust a user/service identity plus an allowlist dest. Topic 11 will return to that in Wi-Fi/zero-trust; here you only refuse the folklore that VLAN = safe.

Record: plumbing vs promise. Never: nmap for VLAN hops, hydra on the router’s VLAN page, ettercap between tags you do not own.

Command guide

Identity-aware zones beat tag-only folklore

═══ COMMANDS ═══

Command — copy this

grep -c "^zone=" "$HOME/cyberlium-lab/t11-m03-zones.txt"

4. What you ship: named promises, not a switch config you do not own

t11-m03-zones.txt lists two loopback dests with promises. THIS host addresses listed. DEMO GATE honored. No consumer VLAN wizard. No 0.0.0.0. No /24 scan.

5. What you record before the next lesson

Date. VLAN = plumbing; zone = promise. 8782 vs 8792 names. ip/Get-NetIPAddress done. chmod 600. NEVER nmap/hydra/router VLAN clicks.

6. Wrong vs right: stranger networks vs literacy on systems you own

Worked failure — same network word, opposite target. Right never needs a café or campus LAN.

  • Wrong

    Create VLANs on a hotel controller. nmap to discover VLAN IDs. Any-any route between tags and call it segmentation.

  • Right

    Write two promises on loopback dests. Leave other people’s switches. Next: East-West vs North-South.

Mission: write two zone promises on dests YOU own

1) / STOP if router. 2) List THIS host IPv4. 3) Write public_cartoon 8782 and app_cartoon 8792 with a one-line promise each. Do not configure a live switch.

Stuck? Ask Cyberlium AI Mentor

Ask Mentor why any-any between VLANs is still flat — not how to trunk a café AP.

Knowledge Check

1

APPLY: Two VLANs exist but the router ACL is any-any. What do you have?

Multiple choice

Knowledge Check

2

APPLY: True or False: Opening the Netgear VLAN page at 192.168.0.1 is the Cyberlium VLAN lab.

True or False

Knowledge Check

3

APPLY: Best beginner stand-in for two zones on a PC you own?

Multiple choice

← Previous

Answer all 3 knowledge checks to continue. (0/3 answered)