π― What You'll Learn
In this comprehensive guide, you'll learn how to create a completely isolated network for your IoT devices using NETGEAR Plus switches. This setup will keep your smart home gadgets on a separate network while still allowing them internet accessβprotecting your computers, servers, and sensitive data from potential IoT security vulnerabilities.
π Table of Contents
π Why You Need a Separate IoT VLAN
IoT devices are notorious for having security vulnerabilities. From smart cameras to voice assistants, these devices often:
- Lack regular security updates from manufacturers
- Use weak default passwords that are rarely changed
- Collect and transmit data that you may not be aware of
- Provide entry points for malicious actors into your network
By creating a separate VLAN (Virtual Local Area Network) for IoT devices, you accomplish several important security goals:
- Prevents IoT devices from accessing your computers and servers
- Isolates compromised devices to prevent lateral network movement
- Allows IoT devices to communicate with each other when needed
- Maintains internet access for cloud-connected smart devices
- Simplifies network monitoring and traffic analysis
π οΈ What You'll Need
Before we begin, make sure you have the following equipment and access:
Hardware Requirements
- NETGEAR Plus Switch (Models: GS105Ev2, GS108Ev3, GS116Ev2, GS305E, GS308E, JGS516PE, JGS524Ev2, JGS524PE, or similar)
- Router with VLAN Support (Most modern routers support 802.1Q VLANs)
- Wireless Access Point (for WiFi-connected IoT devices)
- Ethernet Cables (Cat5e or higher recommended)
Network Access
- Administrative access to your switch (default password:
password) - Administrative access to your router
- Computer connected to the same network as the switch
πΊοΈ Network Overview
Here's what your network will look like after configuration:
Network Topology Diagram
Port Assignment Summary
| Port(s) | Purpose | VLAN Assignment | Tagging |
|---|---|---|---|
| Port 1 | Uplink to Router | VLAN 1 + VLAN 10 | Both Tagged (Trunk) |
| Ports 2-4 | Main Network Devices | VLAN 1 | Untagged, PVID 1 |
| Port 5 | Wireless Access Point | VLAN 10 | Untagged, PVID 10 |
| Ports 6-8 | Wired IoT Devices (optional) | VLAN 10 | Untagged, PVID 10 |
βοΈ Step-by-Step Switch Configuration
1 Access Your Switch
- Open a web browser on a computer connected to your network
- Enter your switch's IP address in the address bar (e.g.,
http://192.168.1.100) - Log in with your password (default is
password)
Check your router's DHCP client list, use the NETGEAR Switch Discovery Tool, or if the switch is off-network, it uses the default IP:
192.168.0.239
2 Enable Advanced 802.1Q VLAN
- Navigate to VLAN > 802.1Q > Advanced > VLAN Configuration
- Select the Enable radio button
- When warned that current VLAN settings will be lost, click OK
- Click Apply to save your settings
3 Create the IoT VLAN
- You should still be on the VLAN Configuration page
- In the VLAN ID field, enter
10(or any number 2-4093) - Click Add
- The new VLAN 10 appears in the VLAN Identifier Setting table
4 Configure the Uplink Port
The uplink port connects your switch to your router and must carry traffic for both VLANs.
- Navigate to VLAN > 802.1Q > Advanced > VLAN Membership
- In the VLAN ID menu, select VLAN 1
- Locate your uplink port (let's assume it's Port 1)
- Make sure Port 1 is checked and marked as Tagged (T)
- Click Apply
- Now select VLAN 10 from the VLAN ID menu
- Check Port 1 and mark it as Tagged (T)
- Click Apply
5 Configure the Wireless Access Point Port
- In the VLAN ID menu, select VLAN 10
- Select Port 5 (or whichever port you'll use for your WAP)
- Mark it as Untagged (U)
- Click Apply
6 Configure Additional IoT Ports (Optional)
If you have wired IoT devices (smart TVs, game consoles, etc.):
- Still in VLAN 10 membership
- Select Ports 6, 7, and 8 (or any additional ports)
- Mark them as Untagged (U)
- Click Apply
7 Set Port PVIDs
PVID (Port VLAN ID) tells the switch which VLAN to assign to untagged traffic on a port.
- Navigate to VLAN > 802.1Q > Advanced > Port PVID
- Select Port 5 (your WAP port)
- Enter
10in the PVID field - Click Apply
- Repeat for Ports 6-8 if you configured them for IoT
π Router Configuration
Your router configuration is crucial for this setup to work properly. The exact steps vary by router manufacturer, but here are the general principles:
Required Router Capabilities
- 802.1Q VLAN Support: Your router must support VLAN tagging
- Multiple VLAN Interfaces: Ability to create separate network interfaces for each VLAN
- Firewall Rules: Ability to create inter-VLAN firewall rules
General Router Setup Steps
Step 1: Create VLAN Interfaces
- Log into your router's admin interface
- Navigate to the VLAN configuration section (location varies)
- Identify the port connected to your switch
- Create two VLAN interfaces on that port:
- VLAN 1: 192.168.1.1/24 (your main network)
- VLAN 10: 192.168.10.1/24 (your IoT network)
Step 2: Enable DHCP for Both VLANs
- Configure DHCP server for VLAN 1:
- Range: 192.168.1.100 - 192.168.1.254
- Gateway: 192.168.1.1
- DNS: Your preferred DNS servers
- Configure DHCP server for VLAN 10:
- Range: 192.168.10.100 - 192.168.10.254
- Gateway: 192.168.10.1
- DNS: Your preferred DNS servers
Step 3: Configure Firewall Rules
This is the most critical step for security. You need to create firewall rules that:
Router Brand-Specific Tips
- pfSense/OPNsense: Create VLAN interfaces under Interfaces > Assignments, then configure firewall rules under Firewall > Rules
- UniFi (Ubiquiti): Create networks under Settings > Networks, then configure firewall rules under Settings > Security
- MikroTik: Use Bridge VLAN Filtering or create VLAN interfaces, then configure firewall rules in IP > Firewall
- TP-Link Omada: Configure under Settings > Wired Networks > LAN, then use ACL rules
π‘ Wireless Access Point Setup
Your wireless access point needs to be configured to broadcast an IoT-specific SSID:
WAP Configuration Steps
- Connect the WAP to Port 5 on your switch (or whichever port you configured for VLAN 10)
- Set WAP to Bridge/AP Mode: Not router mode! It should pass through DHCP requests to your router
- Create a new SSID:
- Name: Something like "IoT-Network" or "Smart-Home"
- Security: WPA2-PSK or WPA3-PSK (strong password required!)
- Network: Leave on default/untagged (it inherits VLAN 10 from the switch port)
- Disable client isolation if you want IoT devices to communicate with each other
- Save and reboot the access point
π§ͺ Testing Your Configuration
Before migrating all your IoT devices, it's crucial to test that the network segmentation is working correctly.
Test 1: IoT Device Internet Access
- Connect a test device (smartphone) to your IoT WiFi network
- Open a web browser and navigate to a website (e.g., google.com)
- Expected result: Website loads successfully β
Test 2: IoT to Main Network Isolation
- While connected to the IoT WiFi, try to ping a device on your main network:
ping 192.168.1.10
- Expected result: Request times out or "Destination unreachable" β
- Try to access your main network file shares or devices
- Expected result: Connection refused or times out β
Test 3: IoT Device Communication
- Connect two IoT devices to the IoT network
- Try to access one device from the other (e.g., view a camera from a smart display)
- Expected result: Devices can see and communicate with each other β
Test 4: Main Network to IoT (Optional Management Access)
- From a computer on your main network, try to access an IoT device's IP
- Expected result: Depends on your firewall rules (typically allowed for management) β
π§ Troubleshooting Tips
Problem: IoT Devices Can't Get Internet Access
- Check router DHCP: Make sure DHCP is enabled for VLAN 10
- Verify VLAN tagging: Ensure Port 1 is tagged for VLAN 10
- Check firewall rules: Make sure you have an ALLOW rule for VLAN 10 β Internet
- Test with static IP: Manually assign 192.168.10.50 to a device to rule out DHCP issues
Problem: IoT Devices CAN Access Main Network
- Check firewall rule order: DENY rules must come before ALLOW rules
- Verify rule syntax: Make sure the DENY rule specifies correct source/destination networks
- Clear router connection table: Some routers cache connections; reboot to clear
- Check for bypass rules: Some routers have default "allow established" rules that might bypass your DENY rule
Problem: Some IoT Devices Won't Connect
- Check WiFi security: Some older IoT devices only support WPA2, not WPA3
- Disable AP isolation: If enabled, devices can't discover each other
- Check 2.4GHz vs 5GHz: Many IoT devices only work on 2.4GHz
- Verify DHCP pool size: Make sure you have enough IP addresses for all devices
Problem: Lost Access to Switch Configuration
- If switch is on VLAN 1: Connect from a device on your main network
- If you can't access: Factory reset the switch (hold reset button for 2+ seconds)
- Prevention: Always save your configuration before major changes
π Configuration Summary Checklist
Switch Configuration β
- β Advanced 802.1Q VLAN enabled
- β VLAN 10 created
- β Port 1 tagged for VLAN 1 and VLAN 10
- β Port 5 untagged for VLAN 10, PVID 10
- β Ports 6-8 untagged for VLAN 10, PVID 10 (if used)
- β Configuration saved
Router Configuration β
- β VLAN 1 interface: 192.168.1.1/24
- β VLAN 10 interface: 192.168.10.1/24
- β DHCP enabled for both VLANs
- β Firewall rule: ALLOW VLAN 10 β Internet
- β Firewall rule: DENY VLAN 10 β VLAN 1
- β Rules tested and verified
WAP Configuration β
- β WAP in bridge/AP mode (not router mode)
- β IoT SSID created with strong password
- β Client isolation disabled
- β WAP connected to Port 5
π― Best Practices and Recommendations
Security Best Practices
- Use strong WiFi passwords: Minimum 16 characters with mixed case, numbers, and symbols
- Regularly update firmware: Keep your switch, router, and WAP firmware up to date
- Monitor network traffic: Use your router's logging to watch for suspicious activity
- Disable unused ports: On your switch, disable any ports you're not using
- Document your setup: Keep notes on your VLAN configuration for future reference
IoT Device Management
- Change default passwords: On every IoT device, change the default password immediately
- Disable unused features: Turn off UPnP, remote access, and other features you don't need
- Update regularly: Keep IoT device firmware current (if updates are available)
- Inventory your devices: Keep a list of all IoT devices and their IP addresses
Network Performance
- Monitor bandwidth: Some IoT devices (cameras) use significant bandwidth
- Consider QoS: If needed, configure Quality of Service to prioritize critical traffic
- Use Gigabit connections: Ensure all inter-switch connections are Gigabit or faster
- Separate WiFi channels: Use different channels for main and IoT WiFi networks
π Advanced Configurations
Multiple IoT VLANs
For even better security, you can create separate VLANs for different types of IoT devices:
- VLAN 10: Smart home devices (lights, thermostats)
- VLAN 20: Security cameras (often the most vulnerable)
- VLAN 30: Voice assistants (privacy concerns)
- VLAN 40: Guest network
VLAN-Aware Switch Stacking
If you need more ports, you can stack multiple NETGEAR Plus switches while maintaining VLAN configuration:
- Configure the first switch as described in this guide
- On the second switch, enable the same VLANs
- Connect the switches using a trunk port (tagged for all VLANs)
- Configure ports on the second switch as needed
πΎ Backup and Recovery
Save Your Configuration
Always maintain a backup of your switch configuration:
- Log into the switch
- Navigate to System > Maintenance > Save Configuration
- Click Save and download the .cfg file
- Store the file in a secure location with a descriptive name (e.g., "switch-config-2024-10-11.cfg")
Restore Configuration
If you need to restore a saved configuration:
- Navigate to System > Maintenance > Restore Configuration
- Click Browse and select your saved .cfg file
- Click Apply
- The switch will reboot with the restored configuration
π Additional Resources
- NETGEAR Support: netgear.com/support
- Switch Documentation: Download your model-specific manual from the NETGEAR support site
- Network Security Resources: Visit NIST Cybersecurity Framework for best practices
- Home Network Forum: Join the NETGEAR Community for help and advice
π Conclusion
Congratulations! You've successfully created a secure, isolated network for your IoT devices. This configuration provides several important benefits:
What You've Achieved:
- β Enhanced Security: Your main network is protected from IoT vulnerabilities
- β Network Segmentation: IoT devices are isolated but can still access the internet
- β Device Communication: IoT devices can discover and communicate with each other
- β Flexible Management: You can control access policies from your router
- β Scalability: Easy to add more devices or create additional VLANs
Remember to:
- Regularly test your firewall rules to ensure they're working as expected
- Keep all firmware updated on switches, routers, and IoT devices
- Document any changes you make to your network configuration
- Monitor your network for unusual traffic or security events
Network security is an ongoing process, not a one-time setup. Stay informed about IoT security best practices and adjust your configuration as needed.
Found This Guide Helpful?
Share it with others who might benefit from better IoT security!