Connecting to n-devs-smb.tplinkcloud.com AND n-deventry-smb.tplinkcloud.com - UNACCEPTABLE
My OPNSense FW is blocking connection back to
n-devs-smb.tplinkcloud.com
n-deventry-smb.tplinkcloud.com
This is unacceptable to have this calling home and it looks like using smb across the internet, clearly unsafe and since I don not use cloud based is a breach in GDPR since I have not authorised said software from connecting to these domains. Also looks like developer entry points!!
Please advise that this will be taken out on the next firmware upgrade or of required, then only those whom choose to use cloud based solution\updates and so forth.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Fae Hi, any update at all please?
- Copy Link
- Report Inappropriate Content
Dear @Pugs,
Pugs wrote
@Fae Hi, any update at all please?
Omada Software Controller v5.2.4 is for trial now, which has added the button to disable cloud-connection behavior of Omada Devices. But it requires to upgrading the Omada devices to the adapted firmware, as far as I know, the EAP firmware adapted to controller v5.2 hasn't been ready for release yet. We may need to wait for the EAP firmware update.
- Copy Link
- Report Inappropriate Content
is it already know if the full omada devices will get a FW update to be able to disable this phone home ?
or will there be a time table, now these , now these etc.....
Its just to be able to keep track of all my devices which I need to update for this
- Copy Link
- Report Inappropriate Content
Thx for that thread. Just searched my Pi Hole and also found several domains!
n-smb-api.tplinkcloud.com
n-euw1-device-api.tplinkcloud.com
n-use1-device-api.tplinkcloud.com
This didn't happen a while ago.
Seems that TP Link did change something within controller settings?
As you said - this is a 'No Go'!
@Fae :
Any update/statement on this?
I'm using an locally hosted controller (linux machine) with EAP610 Outdoor, EAP225v3 Outdoor, EAP660HD
EDIT: For clarification > I do not use any beta/trial version - only final firmware/final controller software!
- Copy Link
- Report Inappropriate Content
EDIT
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@btx Yeah, said further up thread that it was the wrong terminology to use i.e. GDPR. Just ignore that part. The issues is the phoning home when people want to isolate their devices from the internet and have a secure environment, after all, these aren't or shouldn't be insecure IoT devices, they are business products.
I'm a great advocate of privacy on the web, compartmentalize my personal life from business and don't use social media, except a tube account and even then its not linked to my personal life, so the unscrupulous big players don't get owt from me for free. Even the phone uses CalyxOS. If they want my data, they can frickin pay me for the use of it..lol. Worse still some of theses companies have say 200 affiliated third party companies they sell your data to,. Now exponentially multiple that what those third parties do with your data. Yeah, probably ends up on the dark web being sold. So by its very nature they are fueling the fire.
Best thing is the right browser (defo not Chrome\Edge), the right extensions, never use your name, FOSS emails used along with something like simplelogin. No social media, FOSS OS and a good VPN. However, back to the point, these shouldn't be phoning home if you haven't opted in
- Copy Link
- Report Inappropriate Content
EDIT
- Copy Link
- Report Inappropriate Content
v5.0.5 is out for the EAP265 which doesn't fix the problem. I've downgraded to 5.0.3 to stop this incessant phone-home behaviour.
The other thing I've noticed that drives me nuts is the APs always trying to get to external NTP servers when it's configured for perfectly functioning internal servers.
Annoying, unwarranted and frankly a bit amateur hour.
- Copy Link
- Report Inappropriate Content
@Brad_C Agreed
- Copy Link
- Report Inappropriate Content
Information
Helpful: 4
Views: 8504
Replies: 50