[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FD5AX0MTDNSRF0S70YA1P6":3,"skill-same:01M7FD5AX0MTDNSRF0S70YA1P6":49},{"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":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7FD5AX0MTDNSRF0S70YA1P6","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.","siddu1004\u002FSFP","siddu1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260113491?v=4","01M7F8W1SAJAR49097VRTE1TW5","Siddhardh Vanguri","01M7F8W1SYGY7JE15AHAECCT9R",5,"MIT","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fnetworking\u002Fskills\u002Fhomelab-vlan-segmentation\u002FSKILL.md",[],[],"2026-11-16 10:05:34",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","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fnetworking\u002Fskills\u002Fhomelab-vlan-segmentation",0,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsfp-hive","https:\u002F\u002Fgithub.com\u002Fsiddu1004","I am a student at Amrita Vishwa Vidyapeetham pursuing my BTECH degree in Electronics and Electrical Engineering (2024-2028).","2026-11-09 16:04:40",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add siddu1004\u002FSFP --skill homelab-vlan-segmentation",{"tool":41,"command":42},"bunx","bunx skills add siddu1004\u002FSFP --skill homelab-vlan-segmentation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill homelab-vlan-segmentation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fnetworking\u002Fskills\u002Fhomelab-vlan-segmentation\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7FEEDADZBNBVY19H3XZKCBQ","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7FEE0JS04FE58MST48D0MMC","polyhaven-texture-apply","Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal\u002Fwood\u002Fmarble, or change object surface.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-texture-apply\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7FEDJRWV194TY411WVRS84W","polyhaven-studio-setup","Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-studio-setup\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7FED5H2FGS50XGETMGSM0RV","polyhaven-scene-builder","Build complete product scenes using PolyHaven assets — HDRI environment, textured ground\u002Fpedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-scene-builder\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7FECSNZ2CJA7Z8TPE5R844R","polyhaven-material-swap","Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color\u002Ffinish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-material-swap\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7FECBPQ6YWH48PYAMS0C5CE","polyhaven-hdri-showcase","Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-hdri-showcase\u002FSKILL.md",[],[]]