Bug with AC networks and network isolation
Posted: Fri Sep 14, 2018 11:04 am
I have attempted several times to set up network segmentation and isolation and been frustrated by an apparent bug with DHCP on the AC networks.
Here's a network map-
Default/Private interface group (192.168.1.x):
Client isolation. Internet access only. LAN side firewall.
Used by phones, tablets and anything they need to talk to directly (e.g. Chromecasts, satellite box, Roku etc.). LAN side firewall.
Strong password and used for owned devices that only need internet access. Client isolation. Internet access only. LAN side firewall.
Is this a known issue? Can I group N and AC networks in this way? Is there a bug with AC networks and network grouping?
DHCP vendor IDs are blank for all interface groups.
Here's a network map-
Default/Private interface group (192.168.1.x):
- P1
- P2
- P3
- P5/EWAN
- Private-WiFi-AC
- Private-WiFi
Client isolation. Internet access only. LAN side firewall.
- Guest-WiFi
- Guest-WiFi-AC
Used by phones, tablets and anything they need to talk to directly (e.g. Chromecasts, satellite box, Roku etc.). LAN side firewall.
- P4
- Wireless
- Wireless-AC
Strong password and used for owned devices that only need internet access. Client isolation. Internet access only. LAN side firewall.
- Isolated-WiFi
- Isolated-WiFi-AC
Is this a known issue? Can I group N and AC networks in this way? Is there a bug with AC networks and network grouping?
DHCP vendor IDs are blank for all interface groups.