[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2HDKGTJPGAJS4G5RG7PYZ":3,"skill-same:01M7B2HDKGTJPGAJS4G5RG7PYZ":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7B2HDKGTJPGAJS4G5RG7PYZ","homelab-vlan-segmentation",null,"Segmenting home networks into VLANs for IoT, guest, trusted, and server traffic using UniFi, pfSense\u002FOPNsense, and MikroTik — including switch trunk config, firewall rules, and wireless SSID mapping. Use when splitting a home network into IoT, guest, trusted, and server VLANs on UniFi, pfSense\u002FOPNsense, or MikroTik.","lytong760-cell\u002Fcompiler_ko","lytong760-cell","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F289977458?v=4","01M7B1YD239K88PFQRD4PVC9DW","Nguyên Games","01M7B1YD2RM70TZ71QNQ0XTN4R",2,"MIT","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fhomelab-vlan-segmentation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: homelab-vlan-segmentation\ndescription: Segmenting home networks into VLANs for IoT, guest, trusted, and server traffic using UniFi, pfSense\u002FOPNsense, and MikroTik — including switch trunk config, firewall rules, and wireless SSID mapping. Use when splitting a home network into IoT, guest, trusted, and server VLANs on UniFi, pfSense\u002FOPNsense, or MikroTik.\nmetadata:\n  origin: community\n---\n\n# Homelab VLAN Segmentation\n\nHow to split a home network into isolated VLANs so IoT devices, guests, and your main\nPCs cannot talk to each other. The most impactful security upgrade for a home network.\n\nAll firewall rules shown here add isolation between segments — they do not remove\nexisting protections. Apply changes in a maintenance window and verify connectivity\nbetween segments after each step before moving on.\n\n## When to Use\n\n- Setting up VLANs on a home network for the first time\n- Isolating IoT devices (smart bulbs, cameras, TVs) from trusted devices\n- Creating a guest Wi-Fi network that cannot reach home devices\n- Explaining how VLANs work to someone unfamiliar with the concept\n- Configuring trunk ports, access ports, and SSID-to-VLAN mapping\n- Troubleshooting inter-VLAN routing or firewall rule issues on pfSense\u002FOPNsense\u002FUniFi\n\n## How It Works\n\n```\nWithout VLANs — flat network:\n  All devices on 192.168.1.0\u002F24\n  Smart TV (potential malware) → can reach your NAS, PCs, everything\n\nWith VLANs:\n  VLAN 10 — Trusted    192.168.10.0\u002F24  (PCs, phones, laptops)\n  VLAN 20 — IoT        192.168.20.0\u002F24  (smart TV, bulbs, cameras)\n  VLAN 30 — Servers    192.168.30.0\u002F24  (NAS, Pi, VMs)\n  VLAN 40 — Guest      192.168.40.0\u002F24  (visitor Wi-Fi)\n  VLAN 99 — Management 192.168.99.0\u002F24  (switch\u002FAP web UIs)\n\n  Smart TV → blocked from reaching 192.168.10.0\u002F24 and 192.168.30.0\u002F24\n  Guests → internet only, cannot see any home devices\n```\n\n## VLAN Design Template\n\n```\nVLAN  Name        Subnet              Gateway         Purpose\n10    trusted     192.168.10.0\u002F24     192.168.10.1    PCs, phones, laptops\n20    iot         192.168.20.0\u002F24     192.168.20.1    Smart home devices\n30    servers     192.168.30.0\u002F24     192.168.30.1    NAS, Pi, self-hosted\n40    guest       192.168.40.0\u002F24     192.168.40.1    Visitor Wi-Fi\n99    management  192.168.99.0\u002F24     192.168.99.1    Network gear web UIs\n```\n\n## Examples\n\n**Typical homelab with UniFi AP and managed switch:**\n\n```\nScenario: 3-bedroom house, UniFi Dream Machine + UniFi 8-port switch + 2 APs\n\nVLAN 10 — Trusted    192.168.10.0\u002F24   MacBook, iPhones, iPad\nVLAN 20 — IoT        192.168.20.0\u002F24   Nest thermostat, Philips Hue, Ring doorbell, smart TVs\nVLAN 30 — Servers    192.168.30.0\u002F24   Synology NAS (192.168.30.10), Pi-hole (192.168.30.2)\nVLAN 40 — Guest      192.168.40.0\u002F24   Visitor Wi-Fi — internet only\n\nSSID → VLAN mapping:\n  \"Home\"      → VLAN 10 (WPA2, strong password, trusted devices only)\n  \"IoT\"       → VLAN 20 (WPA2, separate password, printed on router for setup)\n  \"Guest\"     → VLAN 40 (WPA2, simple password you can share freely)\n\nSwitch port behavior:\n  Port 1  → trunk to router (tagged VLANs 10,20,30,40,99)\n  Port 2  → trunk to APs (tagged VLANs 10,20,40; AP handles per-SSID tagging)\n  Port 3  → access VLAN 30 (NAS — untagged, no VLAN awareness needed)\n  Port 4  → access VLAN 30 (Pi-hole — untagged)\n  Port 5–8 → access VLAN 10 (wired workstations)\n\nFirewall rules applied (all rules add isolation, none remove existing protections):\n  IoT → Trusted: BLOCK\n  IoT → Servers: BLOCK except 192.168.30.2:53 (Pi-hole DNS allowed)\n  IoT → Internet: ALLOW\n  Guest → Local networks: BLOCK\n  Guest → Internet: ALLOW\n  Trusted → everywhere: ALLOW\n```\n\n## UniFi Configuration\n\n### Create Networks in UniFi Controller\n\n```\nSettings → Networks → Create New Network\n\nFor each VLAN:\n  Name: IoT\n  Purpose: Corporate  (gives DHCP + routing)\n  VLAN ID: 20\n  Network: 192.168.20.0\u002F24\n  Gateway IP: 192.168.20.1\n  DHCP: Enable\n  DHCP Range: 192.168.20.100 – 192.168.20.254\n```\n\n### Map SSIDs to VLANs (UniFi)\n\n```\nSettings → WiFi → Create New WiFi\n\n  Name: IoT-Network\n  Password: \u003Cseparate password>\n  Network: IoT  ← select your VLAN here\n  # All devices connecting to this SSID land in VLAN 20\n\n  Name: Guest\n  Password: \u003Cguest password>\n  Network: Guest\n  Guest Policy: Enable  ← isolates guests from each other too\n```\n\n### UniFi Firewall Rules (Traffic Rules)\n\n```\nSettings → Traffic & Security → Traffic Rules\n\n# Block IoT from reaching Trusted VLAN\n  Action: Block\n  Category: Local Network\n  Source: IoT (192.168.20.0\u002F24)\n  Destination: Trusted (192.168.10.0\u002F24)\n\n# Allow IoT to reach internet only\n  Action: Allow\n  Source: IoT\n  Destination: Internet\n\n# Block Guest from all local networks\n  Action: Block\n  Source: Guest\n  Destination: Local Networks\n```\n\n## pfSense \u002F OPNsense Configuration\n\n### Create VLANs\n\n```\nInterfaces → Assignments → VLANs → Add\n\n  Parent Interface: em1  (your LAN NIC)\n  VLAN Tag: 20\n  Description: IoT\n\n# Repeat for each VLAN, then assign each VLAN to an interface:\nInterfaces → Assignments → Add\n  Select the VLAN you created → click Add\n  Enable the interface, set IP to gateway address (192.168.20.1\u002F24)\n```\n\n### DHCP for Each VLAN\n\n```\nServices → DHCP Server → Select your VLAN interface\n\n  Enable DHCP\n  Range: 192.168.20.100 to 192.168.20.254\n  DNS Servers: 192.168.30.2  ← Pi-hole IP if you have one\n```\n\n### Firewall Rules (pfSense\u002FOPNsense)\n\n```\n# Rules are processed top-to-bottom, first match wins.\n\n# On the IoT interface (VLAN 20):\n  Rule 1: Allow IoT → Pi-hole DNS  ← MUST come before the RFC1918 block rule\n    Protocol: UDP\u002FTCP\n    Source: IoT net\n    Destination: 192.168.30.2 port 53\n    Action: Allow\n\n  Rule 2: Block IoT → RFC1918 (all private IP ranges)\n    Protocol: any\n    Source: IoT net\n    Destination: RFC1918  (192.168.0.0\u002F16, 10.0.0.0\u002F8, 172.16.0.0\u002F12)\n    Action: Block\n\n  Rule 3: Allow IoT → internet\n    Protocol: any\n    Source: IoT net\n    Destination: any\n    Action: Allow\n\n# On the Trusted interface (VLAN 10):\n  Allow all (trusted devices can reach everything)\n    Source: Trusted net\n    Destination: any\n    Action: Allow\n\n# Additional exceptions for IoT devices that need specific local services:\n  Insert before Rule 2 (the RFC1918 block):\n    Protocol: TCP\n    Source: IoT net\n    Destination: 192.168.30.x port 8123  ← Home Assistant\n    Action: Allow\n```\n\n## MikroTik Configuration\n\n```\n# Step 1: Create a bridge with VLAN filtering enabled\n\u002Finterface bridge\nadd name=bridge vlan-filtering=yes\n\n# Step 2: Add physical ports to the bridge\n# Trunk port to router\u002Fuplink (tagged for all VLANs)\n\u002Finterface bridge port\nadd bridge=bridge interface=ether1 frame-types=admit-only-vlan-tagged\n\n# Access port for trusted devices (untagged VLAN 10)\n\u002Finterface bridge port\nadd bridge=bridge interface=ether2 pvid=10 frame-types=admit-only-untagged-and-priority-tagged\n\n# Access port for IoT devices (untagged VLAN 20)\n\u002Finterface bridge port\nadd bridge=bridge interface=ether3 pvid=20 frame-types=admit-only-untagged-and-priority-tagged\n\n# Step 3: Define which VLANs are allowed on which ports\n\u002Finterface bridge vlan\nadd bridge=bridge tagged=ether1 untagged=ether2 vlan-ids=10\nadd bridge=bridge tagged=ether1 untagged=ether3 vlan-ids=20\n\n# Step 4: Create VLAN interfaces on the bridge (gateway IPs)\n\u002Finterface vlan\nadd interface=bridge name=vlan10 vlan-id=10\nadd interface=bridge name=vlan20 vlan-id=20\n\n# Step 5: Assign gateway IPs\n\u002Fip address\nadd interface=vlan10 address=192.168.10.1\u002F24\nadd interface=vlan20 address=192.168.20.1\u002F24\n\n# Step 6: DHCP pools and servers\n\u002Fip pool\nadd name=pool-trusted ranges=192.168.10.100-192.168.10.254\nadd name=pool-iot ranges=192.168.20.100-192.168.20.254\n\n\u002Fip dhcp-server\nadd interface=vlan10 address-pool=pool-trusted name=dhcp-trusted\nadd interface=vlan20 address-pool=pool-iot name=dhcp-iot\n\n\u002Fip dhcp-server network\nadd address=192.168.10.0\u002F24 gateway=192.168.10.1\nadd address=192.168.20.0\u002F24 gateway=192.168.20.1\n\n# Step 7: Firewall — block IoT from reaching trusted VLAN\n\u002Fip firewall filter\nadd chain=forward src-address=192.168.20.0\u002F24 dst-address=192.168.10.0\u002F24 \\\n    action=drop comment=\"Block IoT to Trusted\"\n```\n\n## Switch Trunk vs Access Ports\n\n```\n# Trunk port: carries multiple VLANs (tagged) — connects switch-to-switch, switch-to-router, switch-to-AP\n# Access port: carries one VLAN (untagged) — connects to end devices (PC, camera, NAS)\n\n# A managed switch port connected to your router should be a trunk:\n  Allowed VLANs: 10, 20, 30, 40, 99\n\n# A port connecting to a PC should be an access port:\n  VLAN: 10 (trusted)\n  No tagging — the PC does not know or care about VLANs\n\n# A port connecting to an AP must be a trunk:\n  The AP tags traffic from each SSID with the right VLAN ID\n  Allowed VLANs: 10, 20, 40  (whichever SSIDs the AP serves)\n```\n\n## Anti-Patterns\n\n```\n# BAD: Creating VLANs without adding firewall rules\n# VLANs without firewall rules do not provide security — inter-VLAN routing is open by default\n# GOOD: Add explicit block rules immediately after creating VLANs\n\n# BAD: Putting the Pi-hole in the IoT VLAN\n# IoT devices can reach it but trusted devices cannot (without extra rules)\n# GOOD: Pi-hole in the Servers VLAN with a rule allowing all VLANs to reach port 53\n\n# BAD: Native VLAN equals management VLAN\n# Untagged traffic landing in your management VLAN enables VLAN hopping attacks\n# GOOD: Use a dedicated unused VLAN as native (e.g. VLAN 999), keep management traffic tagged\n\n# BAD: Same Wi-Fi password for IoT SSID and trusted SSID\n# Anyone who learns the password can connect IoT devices to the wrong segment\n```\n\n## Best Practices\n\n- Start with 4 VLANs: Trusted, IoT, Servers, Guest — add more as needed\n- Put Pi-hole in the Servers VLAN (192.168.30.x)\n- Add a firewall rule allowing DNS (port 53) from all VLANs to the Pi-hole IP — before any RFC1918 block rule\n- Test isolation after every rule change: from the IoT VLAN, try to ping a trusted device — it should fail\n- Use a management VLAN for switch and AP web UIs and restrict access to the Trusted VLAN only\n- Document your VLAN design in a table (VLAN ID, name, subnet, purpose)\n\n## Related Skills\n\n- homelab-network-setup\n- homelab-pihole-dns\n- homelab-wireguard-vpn\n","# Homelab VLAN Segmentation\n\nHow to split a home network into isolated VLANs so IoT devices, guests, and your main\nPCs cannot talk to each other. The most impactful security upgrade for a home network.\n\nAll firewall rules shown here add isolation between segments — they do not remove\nexisting protections. Apply changes in a maintenance window and verify connectivity\nbetween segments after each step before moving on.\n\n## When to Use\n\n- Setting up VLANs on a home network for the first time\n- Isolating IoT devices (smart bulbs, cameras, TVs) from trusted devices\n- Creating a guest Wi-Fi network that cannot reach home devices\n- Explaining how VLANs work to someone unfamiliar with the concept\n- Configuring trunk ports, access ports, and SSID-to-VLAN mapping\n- Troubleshooting inter-VLAN routing or firewall rule issues on pfSense\u002FOPNsense\u002FUniFi\n\n## How It Works\n\n```\nWithout VLANs — flat network:\n  All devices on 192.168.1.0\u002F24\n  Smart TV (potential malware) → can reach your NAS, PCs, everything\n\nWith VLANs:\n  VLAN 10 — Trusted    192.168.10.0\u002F24  (PCs, phones, laptops)\n  VLAN 20 — IoT        192.168.20.0\u002F24  (smart TV, bulbs, cameras)\n  VLAN 30 — Servers    192.168.30.0\u002F24  (NAS, Pi, VMs)\n  VLAN 40 — Guest      192.168.40.0\u002F24  (visitor Wi-Fi)\n  VLAN 99 — Management 192.168.99.0\u002F24  (switch\u002FAP web UIs)\n\n  Smart TV → blocked from reaching 192.168.10.0\u002F24 and 192.168.30.0\u002F24\n  Guests → internet only, cannot see any home devices\n```\n\n## VLAN Design Template\n\n```\nVLAN  Name        Subnet              Gateway         Purpose\n10    trusted     192.168.10.0\u002F24     192.168.10.1    PCs, phones, laptops\n20    iot         192.168.20.0\u002F24     192.168.20.1    Smart home devices\n30    servers     192.168.30.0\u002F24     192.168.30.1    NAS, Pi, self-hosted\n40    guest       192.168.40.0\u002F24     192.168.40.1    Visitor Wi-Fi\n99    management  192.168.99.0\u002F24     192.168.99.1    Network gear web UIs\n```\n\n## Examples\n\n**Typical homelab with UniFi AP and managed switch:**\n\n```\nScenario: 3-bedroom house, UniFi Dream Machine + UniFi 8-port switch + 2 APs\n\nVLAN 10 — Trusted    192.168.10.0\u002F24   MacBook, iPhones, iPad\nVLAN 20 — IoT        192.168.20.0\u002F24   Nest thermostat, Philips Hue, Ring doorbell, smart TVs\nVLAN 30 — Servers    192.168.30.0\u002F24   Synology NAS (192.168.30.10), Pi-hole (192.168.30.2)\nVLAN 40 — Guest      192.168.40.0\u002F24   Visitor Wi-Fi — internet only\n\nSSID → VLAN mapping:\n  \"Home\"      → VLAN 10 (WPA2, strong password, trusted devices only)\n  \"IoT\"       → VLAN 20 (WPA2, separate password, printed on router for setup)\n  \"Guest\"     → VLAN 40 (WPA2, simple password you can share freely)\n\nSwitch port behavior:\n  Port 1  → trunk to router (tagged VLANs 10,20,30,40,99)\n  Port 2  → trunk to APs (tagged VLANs 10,20,40; AP handles per-SSID tagging)\n  Port 3  → access VLAN 30 (NAS — untagged, no VLAN awareness needed)\n  Port 4  → access VLAN 30 (Pi-hole — untagged)\n  Port 5–8 → access VLAN 10 (wired workstations)\n\nFirewall rules applied (all rules add isolation, none remove existing protections):\n  IoT → Trusted: BLOCK\n  IoT → Servers: BLOCK except 192.168.30.2:53 (Pi-hole DNS allowed)\n  IoT → Internet: ALLOW\n  Guest → Local networks: BLOCK\n  Guest → Internet: ALLOW\n  Trusted → everywhere: ALLOW\n```\n\n## UniFi Configuration\n\n### Create Networks in UniFi Controller\n\n```\nSettings → Networks → Create New Network\n\nFor each VLAN:\n  Name: IoT\n  Purpose: Corporate  (gives DHCP + routing)\n  VLAN ID: 20\n  Network: 192.168.20.0\u002F24\n  Gateway IP: 192.168.20.1\n  DHCP: Enable\n  DHCP Range: 192.168.20.100 – 192.168.20.254\n```\n\n### Map SSIDs to VLANs (UniFi)\n\n```\nSettings → WiFi → Create New WiFi\n\n  Name: IoT-Network\n  Password: \u003Cseparate password>\n  Network: IoT  ← select your VLAN here\n  # All devices connecting to this SSID land in VLAN 20\n\n  Name: Guest\n  Password: \u003Cguest password>\n  Network: Guest\n  Guest Policy: Enable  ← isolates guests from each other too\n```\n\n### UniFi Firewall Rules (Traffic Rules)\n\n```\nSettings → Traffic & Security → Traffic Rules\n\n# Block IoT from reaching Trusted VLAN\n  Action: Block\n  Category: Local Network\n  Source: IoT (192.168.20.0\u002F24)\n  Destination: Trusted (192.168.10.0\u002F24)\n\n# Allow IoT to reach internet only\n  Action: Allow\n  Source: IoT\n  Destination: Internet\n\n# Block Guest from all local networks\n  Action: Block\n  Source: Guest\n  Destination: Local Networks\n```\n\n## pfSense \u002F OPNsense Configuration\n\n### Create VLANs\n\n```\nInterfaces → Assignments → VLANs → Add\n\n  Parent Interface: em1  (your LAN NIC)\n  VLAN Tag: 20\n  Description: IoT\n\n# Repeat for each VLAN, then assign each VLAN to an interface:\nInterfaces → Assignments → Add\n  Select the VLAN you created → click Add\n  Enable the interface, set IP to gateway address (192.168.20.1\u002F24)\n```\n\n### DHCP for Each VLAN\n\n```\nServices → DHCP Server → Select your VLAN interface\n\n  Enable DHCP\n  Range: 192.168.20.100 to 192.168.20.254\n  DNS Servers: 192.168.30.2  ← Pi-hole IP if you have one\n```\n\n### Firewall Rules (pfSense\u002FOPNsense)\n\n```\n# Rules are processed top-to-bottom, first match wins.\n\n# On the IoT interface (VLAN 20):\n  Rule 1: Allow IoT → Pi-hole DNS  ← MUST come before the RFC1918 block rule\n    Protocol: UDP\u002FTCP\n    Source: IoT net\n    Destination: 192.168.30.2 port 53\n    Action: Allow\n\n  Rule 2: Block IoT → RFC1918 (all private IP ranges)\n    Protocol: any\n    Source: IoT net\n    Destination: RFC1918  (192.168.0.0\u002F16, 10.0.0.0\u002F8, 172.16.0.0\u002F12)\n    Action: Block\n\n  Rule 3: Allow IoT → internet\n    Protocol: any\n    Source: IoT net\n    Destination: any\n    Action: Allow\n\n# On the Trusted interface (VLAN 10):\n  Allow all (trusted devices can reach everything)\n    Source: Trusted net\n    Destination: any\n    Action: Allow\n\n# Additional exceptions for IoT devices that need specific local services:\n  Insert before Rule 2 (the RFC1918 block):\n    Protocol: TCP\n    Source: IoT net\n    Destination: 192.168.30.x port 8123  ← Home Assistant\n    Action: Allow\n```\n\n## MikroTik Configuration\n\n```\n# Step 1: Create a bridge with VLAN filtering enabled\n\u002Finterface bridge\nadd name=bridge vlan-filtering=yes\n\n# Step 2: Add physical ports to the bridge\n# Trunk port to router\u002Fuplink (tagged for all VLANs)\n\u002Finterface bridge port\nadd bridge=bridge interface=ether1 frame-types=admit-only-vlan-tagged\n\n# Access port for trusted devices (untagged VLAN 10)\n\u002Finterface bridge port\nadd bridge=bridge interface=ether2 pvid=10 frame-types=admit-only-untagged-and-priority-tagged\n\n# Access port for IoT devices (untagged VLAN 20)\n\u002Finterface bridge port\nadd bridge=bridge interface=ether3 pvid=20 frame-types=admit-only-untagged-and-priority-tagged\n\n# Step 3: Define which VLANs are allowed on which ports\n\u002Finterface bridge vlan\nadd bridge=bridge tagged=ether1 untagged=ether2 vlan-ids=10\nadd bridge=bridge tagged=ether1 untagged=ether3 vlan-ids=20\n\n# Step 4: Create VLAN interfaces on the bridge (gateway IPs)\n\u002Finterface vlan\nadd interface=bridge name=vlan10 vlan-id=10\nadd interface=bridge name=vlan20 vlan-id=20\n\n# Step 5: Assign gateway IPs\n\u002Fip address\nadd interface=vlan10 address=192.168.10.1\u002F24\nadd interface=vlan20 address=192.168.20.1\u002F24\n\n# Step 6: DHCP pools and servers\n\u002Fip pool\nadd name=pool-trusted ranges=192.168.10.100-192.168.10.254\nadd name=pool-iot ranges=192.168.20.100-192.168.20.254\n\n\u002Fip dhcp-server\nadd interface=vlan10 address-pool=pool-trusted name=dhcp-trusted\nadd interface=vlan20 address-pool=pool-iot name=dhcp-iot\n\n\u002Fip dhcp-server network\nadd address=192.168.10.0\u002F24 gateway=192.168.10.1\nadd address=192.168.20.0\u002F24 gateway=192.168.20.1\n\n# Step 7: Firewall — block IoT from reaching trusted VLAN\n\u002Fip firewall filter\nadd chain=forward src-address=192.168.20.0\u002F24 dst-address=192.168.10.0\u002F24 \\\n    action=drop comment=\"Block IoT to Trusted\"\n```\n\n## Switch Trunk vs Access Ports\n\n```\n# Trunk port: carries multiple VLANs (tagged) — connects switch-to-switch, switch-to-router, switch-to-AP\n# Access port: carries one VLAN (untagged) — connects to end devices (PC, camera, NAS)\n\n# A managed switch port connected to your router should be a trunk:\n  Allowed VLANs: 10, 20, 30, 40, 99\n\n# A port connecting to a PC should be an access port:\n  VLAN: 10 (trusted)\n  No tagging — the PC does not know or care about VLANs\n\n# A port connecting to an AP must be a trunk:\n  The AP tags traffic from each SSID with the right VLAN ID\n  Allowed VLANs: 10, 20, 40  (whichever SSIDs the AP serves)\n```\n\n## Anti-Patterns\n\n```\n# BAD: Creating VLANs without adding firewall rules\n# VLANs without firewall rules do not provide security — inter-VLAN routing is open by default\n# GOOD: Add explicit block rules immediately after creating VLANs\n\n# BAD: Putting the Pi-hole in the IoT VLAN\n# IoT devices can reach it but trusted devices cannot (without extra rules)\n# GOOD: Pi-hole in the Servers VLAN with a rule allowing all VLANs to reach port 53\n\n# BAD: Native VLAN equals management VLAN\n# Untagged traffic landing in your management VLAN enables VLAN hopping attacks\n# GOOD: Use a dedicated unused VLAN as native (e.g. VLAN 999), keep management traffic tagged\n\n# BAD: Same Wi-Fi password for IoT SSID and trusted SSID\n# Anyone who learns the password can connect IoT devices to the wrong segment\n```\n\n## Best Practices\n\n- Start with 4 VLANs: Trusted, IoT, Servers, Guest — add more as needed\n- Put Pi-hole in the Servers VLAN (192.168.30.x)\n- Add a firewall rule allowing DNS (port 53) from all VLANs to the Pi-hole IP — before any RFC1918 block rule\n- Test isolation after every rule change: from the IoT VLAN, try to ping a trusted device — it should fail\n- Use a management VLAN for switch and AP web UIs and restrict access to the Trusted VLAN only\n- Document your VLAN design in a table (VLAN ID, name, subnet, purpose)\n\n## Related Skills\n\n- homelab-network-setup\n- homelab-pihole-dns\n- homelab-wireguard-vpn\n",{"name":5,"metadata":24,"description":7},{"origin":25},"community","main","c32dc0b68600587f78aff3310f3bbd4212173ab3",".kilo\u002Fskills\u002Fhomelab-vlan-segmentation",1,"https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko","https:\u002F\u002Fko-lang.ai.studio","https:\u002F\u002Fgithub.com\u002Flytong760-cell","hanaminikata.com","hello ","2026-11-05 18:26:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add lytong760-cell\u002Fcompiler_ko --skill homelab-vlan-segmentation",{"tool":42,"command":43},"bunx","bunx skills add lytong760-cell\u002Fcompiler_ko --skill homelab-vlan-segmentation",{"tool":45,"command":46},"pnpm","pnpm dlx skills add lytong760-cell\u002Fcompiler_ko --skill homelab-vlan-segmentation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fhomelab-vlan-segmentation\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7B36K22Z7155PTGEGTSDNJ4","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fx-api\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7B36HCAE9ESGBVS6J0FR52F","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7B36DYH4ZFJ3GZHPAEMVQAY","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fworkspace-surface-audit\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7B36A1QXMEZT8VZMFVQNR5E","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7B364EK3N88VQQJ6HFATJQE","windows-desktop-e2e","E2E testing for Windows native desktop apps (WPF, WinForms, Win32\u002FMFC, Qt) using pywinauto and Windows UI Automation. Use when writing E2E tests for a Windows native desktop app with pywinauto or UI Automation.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwindows-desktop-e2e\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7B360YF7GGNAF21KT4QB5PG","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]