IoT network issue on Deco X55
I have a fairly new 3-pack Deco X55 system, v1.6, which I really like. TP-Link just released a new firmware version (1.2.0 Build 20230113 Rel. 54525) with a separate IoT network feature, which is what I (and many others apparently) have been waiting for. It's great that TP-Link is listening!
However, I installed the new firmware, but unfortunately I think that they messed up and didn't really understand what was needed. In particular, I did some simple testing, and when logged on the IoT WiFi SSID, I can see all the devices on my main network: computers, NAS, printers, etc. IMO, the main point of an IoT network is to isolate the IoT devices from the rest of the network, so this new feature is basically useless to me as-is! Does anyone know of a workaround? If not, I'm hoping the the TP-Link engineering team is listening and can fix this soon. Right now I maintain two physically separate router networks, one dedicated for IoT, but it would be great to use the Deco X55 for both functions.
Also, I really want the option of having the IoT network devices see each other, but not devices on the main network. That way, if multiple IoT devices need to talk to each other, they could do so (if I so allow), but the main network is protected. As another example, sometimes during the setup for a new IoT device, the configuring system (phone app or website) needs to be able to talk directly to the IoT device, which isn't usually possible on a guest network. If TP-Link is listening here, this should be a user-selectable option on the IoT network (as well as on the guest network, imo). I have seen older D-Link routers that had that kind of user-selectable option on their guest network, and it was very useful at times (e.g., when configuring a new IoT device).
Any input or feedback is appreciated. Thanks!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Just jumping into this thread with interest. Thanks to everyone for sharing...
Coming at this with 25 years of networking background, so, yeah, was 100% floored to understand that the IoT "network" does little (if anything) to isolate / block / firewall devices for each other. Kinda the entire point. I had 100% assumed it would, just like the GUEST network... so, the Product Owner really needs that feedback..
the "Isolate Devices" is a reasonable workaround (although, I can't find a way to remove a device from this list, am I missing this basic function?)
I would 2nd (or 3rd or 5th) calling this an "IoT SSID" (not a network) and being clear that it only provides a new SSID / Password, nothing else (unless you manually implement device isolation).
Could you also check on why there is no way to remove a MAC address for the device isolation list for M5's? That seems really basic, right?
- Copy Link
- Report Inappropriate Content
Never mind my "how to remove devices for. Isolation list" question. You just swipe left! I'm getting old. Doh!
- Copy Link
- Report Inappropriate Content
Hey TP-Link...
This issue has been on the table for more than a year now and nothing seems to have been done about it.
I would 100% agree with all the other people posting that this is a MUST HAVE feature. The fact that the IOT "network" does nothing to isolate the devices on it from the main or guest network is absolutely bonkers and makes the IOT network feature completely useless.
Speaking personally, I have been incredibly impressed with my Deco X55's so far. They are super fast, quite reliable, and I love the regular feature updates.
But seriously -- if you need to prioritise, then fixing the IOT network thing should be much higher on the list (especially given that it's been more than a year since people pointed out it's shortcomings)
Anyway, I do hope that we will see this resolved in the next update!
Many thanks.
- Copy Link
- Report Inappropriate Content
Agreed that it should be high priority, but apparently it's not. I finally figured out at least one good thing that their current IoT network incarnation does: it allows you to have a 2.4GHz-only network for IoT devices, which is helpful because a lot of them apparently cannot function if there is a single SSID with both 2.5 and 5GHz. Until that dawned on me,I couldn't figure out any reason at all for the function! TP-Link's explanations seemed confusing and ambiguous.
Having said that, the IoT network separation is much more useful, since I have always been able to temporarily disable 5Ghz long enough to enroll a new IoT device with that limitation. There is a critical security issue with IoT devices, and network separation would give the Deco devices a feature that is unique among consumer WiFi routers.
Please, TP-Link, add this function which would make your Deco routers even better!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 4
Views: 13979
Replies: 34