eap245 v3 no isolate ssid
Hi,
I found in this thread, https://community.tp-link.com/en/business/forum/topic/159499 , that states tp-link completely replaced the isolate ssid with guest mode which does the same thing with the addition of disallowing connection to any private network. This seems like a horrible idea to me. We have multiple internal subnets here and although i do NOT want the wifi clients to be able to connect to each other, i DO want them to be able to connect to certain internal hosts, this is crucial.
This function seems like it should be the job of the firewall, not an access point! It seems to me that both functions should be available for a little finer grained control, ESPECIALLY in a buiness class access point.
I'm not interested in running a vlan as it just adds overhead to the work that the access point has to do and complexity.
Is there a way to possibly do this from the command line interface?
Thanks in advance.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
mymlact wrote
tp-link completely replaced the isolate ssid with guest mode which does the same thing with the addition of disallowing connection to any private network. This seems like a horrible idea to me.
I completely agree with you and did request from TP-Link several times to bring back the »Client Isolation« setting again. Since feature requests will have a better chance if more customers request it, please add your demand to re-introduce »Client Isolation« to my thread here (it's request #7 in my post): Feature requests for Omada Controller
In my opinion, this important function has been combined into a new »Guest Network« setting b/c of many demands from SOHO users for an easy guest network setting.
While a »Guest Network« setting is fine for home users, the »Client Isolation« setting could have been left intact for power users, too. Both settings could co-exist. Since it even is not a new function, it isn't a feature request strictly speaking.
@forrest, please add this gentleman's vote to the record as one more customer requesting to bring back the former »Client Isolation« setting again in Omada Controller/firmware. Thanks!
- Copy Link
- Report Inappropriate Content
Hi R1D2,
I clicked the below link, but got a 404 not found error.
@forrest
I don't run the controller, but would like to see this added back in the standalone firmware as well.
Adding this guest option is a fine idea for companies without a dedicated firewall, but for those of us that do, it introduces headaches when our enployees can't access internal nodes.
Thanks
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@mymlact , I agree 100%, you need to separate the guest ssid and isolated. I recently ran into this problem. it will be great if these are two separate settings
- Copy Link
- Report Inappropriate Content
@mymlact, it's this post (scroll down to request #7): https://community.tp-link.com/en/business/forum/topic/186224
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I agree 1000% - Please add "isolate ssid" back to the EAP245 firmware.
I have a captive portal with vouchers and I need access to the local network to display the captive portal page. It would be nice to just enable "isolate ssid"
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 2876
Replies: 9