Conventionally, I guess that sort of isolation doesn't typically happen as it's more work to set up and only really benefits users (privacy from each other), but maybe if more apps figure out how to take advantage of this things could change.
Conventionally, I guess that sort of isolation doesn't typically happen as it's more work to set up and only really benefits users (privacy from each other), but maybe if more apps figure out how to take advantage of this things could change.
For example, see Cisco’s Meraki documentation: https://documentation.meraki.com/MR/Firewall_and_Traffic_Sha...
> With Client Isolation enabled, clients will only be able to communicate with the default gateway and will not be able to communicate with any other devices on the same VLAN (or broadcast domain). In order for the wireless client to communicate with another device, the upstream gateway must be used to enable this communication (e.g. inter-VLAN routing and ACLs). Any traffic bound for an address on the same VLAN as a device in client isolation will be denied. Traffic bound for other VLANs will be forwarded and routed normally.
I'd bet that most of the configuration decisions are made based on how to minimize the likelihood of such problems ever occurring.