On this page
Editorial correction, 1 November 2026: Earlier hardware and performance claims were not supported by traceable test records. They have been withdrawn. Documentary verification is not physical testing; no replacement measurements are claimed.
Why Segment a Home Network
Segmentation can restrict reachability between trusted devices, guests and IoT, but does not make a network inherently secure. This is a planning guide for OpenWrt with device-specific interface/bridge topology. No line-rate guarantee or universal switch script is established.
VLAN Planning: IDs, Subnets, DHCP Pools
Write down the exact router ports, switch uplinks, access ports, subnets, DHCP scopes, DNS needs and permitted traffic. Keep a separate management/recovery route. VLAN IDs do not themselves create firewall policy; an external access point or managed switch is a separate compatibility and cost item.
| Role | Plan explicitly |
|---|---|
| Trusted | Management access and least-privilege paths to services |
| IoT | Required DNS/DHCP and intentional outbound destinations |
| Guest | Internet access; no implied access to trusted networks |
| VPN | Tunnel addressing, routes, zone and return path |
Find a router with the ports your VLAN plan needs
OpenWrt VLAN Configuration
Network changes can remove local and remote management. Back up the known-working configuration, identify this release’s actual DSA/bridge/port layout and keep console/failsafe instructions for the exact device. Stage one change at a time with a proven revert path. The earlier generic UCI script did not establish correct bridge membership for every device and is withdrawn. Use current device and OpenWrt network documentation before implementing the plan.
Firewall Zone Rules for Inter-VLAN Traffic
Distinguish traffic to the router (input), router-originated traffic (output) and routed traffic (forward). Explicitly plan DNS and DHCP as required, including the relevant transports and IP versions. A guest policy must not accidentally expose administration. The earlier UDP-only DNS and generic zone rewrite are withdrawn. Keep a configuration backup and local recovery: reverting uncommitted UCI changes is not a rollback for already committed changes.
Integrating a WireGuard VPN Zone
Decide which peers may reach which subnets and preserve return routes. A WireGuard interface does not automatically belong to the intended firewall zone. OpenWrt netifd/firewall configuration differs from full-Linux wg-quick/UFW. Avoid blanket bidirectional trusted-zone forwarding unless the policy requires it.
DNS Privacy: DNS-over-TLS
Choose resolver behavior and provider deliberately, then verify both successful resolution and the intended upstream transport. Encrypted DNS is not equivalent to privacy from every participant and does not enforce VLAN isolation. Current package/configuration details require the selected OpenWrt release’s documentation.
Testing Isolation
Test from a device in each zone against both permitted and prohibited destinations: administration, DNS/DHCP, application ports and return traffic. Include IPv4 and IPv6 where enabled. A failed ping does not prove application traffic is blocked, and a successful ping does not prove DNS is correct. Recheck after reboot and upgrade; preserve the expected policy and observed results.
Common Mistakes
- Assuming another router’s physical port names apply.
- Changing tagged/untagged membership without preserving management.
- Confusing VLAN membership with routed firewall policy.
- Allowing DNS on only one required transport.
- Calling an untested revert command a committed-configuration rollback.
- Ignoring IPv6 or application-level reachability.
Related Reading
Consult the exact BPI-R4 or OpenWrt One setup guide and current primary device documentation. FleetCare does not reconfigure routers or verify network isolation.