Home

Forums

Stories

Knowledge Base

Business Community > WiFi > Separate client isolation and guest network in stand alone EAP access points and omada controllers

< WiFi

Separate client isolation and guest network in stand alone EAP access points and omada controllers

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Separate client isolation and guest network in stand alone EAP access points and omada controllers

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

mymlact

2020-01-28 23:25:15 - last edited 2020-02-11 08:09:12

Posts: 11

Helpful: 9

Solutions: 0

Stories: 0

Registered: 2020-01-28

Separate client isolation and guest network in stand alone EAP access points and omada controllers

2020-01-28 23:25:15 - last edited 2020-02-11 08:09:12

Model: EAP245

Hardware Version: V3

Firmware Version: 2.3.1 Build 20191029 Rel. 61589(5553)

Hi TP-Link,

We have an EAP245 v3 witht the latest firmware. After updating to the latest firmware, I noticed that client isolation has been merged into "client networks", with also adds blocking to any non-routable/private subnet range.

This is a horrible idea for business that have multiple internal private networks!!!!!

We have a firewall that handles subnet access from clients on the wireless network and while we do want client isolation for wireless clients, this merged in guest network setting is preventing employees from access company assest on our internal subnets that all have subnets with private IPs.

PLEASE CHANGE THIS!

Thanks in advance.

Separate client isolation and guest network in stand alone EAP access points and omada controllers

Separate client isolation and guest network in stand alone EAP access points and omada controllers

Information

Voters 1

Tags