6 ms·
It’s not really more work; it’s just a matter of enabling the ‘client isolation’ setting on the wireless AP. For example, see Cisco’s Meraki documentation: htt
by Tijdreiziger 4y ago
It’s not really more work; it’s just a matter of enabling the ‘client isolation’ setting on the wireless AP.
For example, see Cisco’s Meraki documentation: https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/Wireless_Client_Isolation 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.
- inadequatespace 4y agoEven that extremely minor step counts as “more work” for the clientele we’re talking about here.
- Tijdreiziger 4y agoI would certainly expect a cruise-ship-wide paid network to be managed professionally.
- mikepurvis 4y agoRealistically though, it's probably a multi-ship contract involving some small IT firm who installs everything, and then gives the onboard electrician/maintenance-guy a quick primer on how to do basic diagnosis of problems. I'd bet that most of the configuration decisions are made based on how to minimize the likelihood of such problems ever occurring.
- ComodoHacker 4y agoBut you can't use Briar and the like with this Client Isolation, can you?
- Philip-J-Fry 4y agoIsn't that their point? The only reason it worked on a cruise ship connected to the WiFi was because local devices could talk to eachother and were not isolated.