MR200 - There is still a hidden Wifi when i turned of all Wifi networks
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi,
Same isssue as I read on archer x6-router.
Can't switch off WIFI, or unability to switch-off mesh could be what caused that..
Anybody familiar with disabling wifi-antennas fysically inside?
Mine has LTE-antennas external. I will try covering in metal except external LTE's.
I've sent this issue to tp-link-support. Because now it's unusable in environments with medical equipment.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi,
The hidden wireless network is used to build up the mesh wireless network system, and it cannot be detected by the common wireless devices.
You can refer to this article for more details:
https://community.tp-link.com/en/home/stories/detail/728
- Copy Link
- Report Inappropriate Content
Hi, glad to inform you that we've added MR200 V6 beta firmware with onemesh button in this thread: Disable OneMesh Hidden SSID on the 3G/4G modem
If necessary, please test if it works for you.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi,
The hidden wireless network is used to build up the mesh wireless network system, and it cannot be detected by the common wireless devices.
You can refer to this article for more details:
https://community.tp-link.com/en/home/stories/detail/728
- Copy Link
- Report Inappropriate Content
It is.
I detected it with "a very common wireless device". :-)
TPLink is working on it, problem is recognized and solved in the X6 with on/off-switch for Mesh. I hope it will besolved too on the MR200.
- Copy Link
- Report Inappropriate Content
This is noted, I will report to senior engineer to consider adding a OneMesh on/off switch
- Copy Link
- Report Inappropriate Content
Hi, glad to inform you that we've added MR200 V6 beta firmware with onemesh button in this thread: Disable OneMesh Hidden SSID on the 3G/4G modem
If necessary, please test if it works for you.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi,
MR200, the beta-firmware:
Access control:
Remote management can't be shut off. (I switched it off, saved again, no change) Everybody entering my public ip can get in my router. Not that bad, there is a password.
Public ip isn't the same as MR200 says it is. So can't use virtual server. I have apps that check regularly my public ip, ends up in a dead ip. Maybe that has something to do with tp-link's own dynamic dns-service? (I don't use that) The public ip as MR200 says is ok. And that ends up in the login-page from MR200-management.
Filtering: doesn't work. I have camera's who wants to access the internet, I can't block it.
But: one-mesh is off !
Peter
PS: Changed the port number for local management from 80 to another port, seems to work. Hitting my public IP now ends up in "not found".
- Copy Link
- Report Inappropriate Content
Hi, thank you very much for the feedback.
1. For remote management issue, did you try factory reset the MR200?
I will report it to our senior engineer and test if it can be reproduced on our end.
2. The router Internet IP address is assigned by the ISP, if it is different from real public IP address, it means you are behind your ISP CGNAT, it should be the same when you use previous firmware. And if necessary, you need to contact your ISP to see if they could assign you a public IP address.
3. If you mean the blacklist of Access Control function does not take effect, please make sure the MAC address of the camera is correct and also make sure the camera doesn't use random MAC address. You could compare the MAC address of the camera in the blacklist and also the client list.
- Copy Link
- Report Inappropriate Content
My apologies for presuming tp-link dyn dns caused public-ip issue.
I will follow your other suggestions.
For now, this CGNAT is bad news. Hope I find a solution to access home-network from outside. My dataplan is cheap: no public ip, no ipv6.
I can imagine authorities aren't happy with it too.
Factory-reset didn't change local/remote access to router-management..
But I did another test:
I noted the IP MR200 displays as public IP.
I took another tablet with 4G (another totally different WAN). Tried that IP, now I could NOT log in to router's management.
I guess:
If you browse to the IP that MR200 publishes as being public IP, then he redirects to local IP of MR200.
A bit strange, but it is safe. Nobody can access router's management from outside.
There is some logic in it: if MR200 knows I'm inside, then it considers it as local attempt.
I did this test too with router in access-point-mode and again another WAN-source. Same result.
Peter
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 895
Replies: 9
Voters 0
No one has voted for it yet.