WR710N & WR702N in AP Mode - connected wireless clients problems

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

WR710N & WR702N in AP Mode - connected wireless clients problems

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
WR710N & WR702N in AP Mode - connected wireless clients problems
WR710N & WR702N in AP Mode - connected wireless clients problems
2016-10-25 17:15:08
Model :

Hardware Version :

Firmware Version :

ISP :

Hello TP-Link community,

i have a serious problems with the WR710N (V1 and latest Firmware) and WR702N (V1 and latest Firmware).

I have spent 2 weeks, about 150 hours to find the problem in my network. It turns out that the TP-Links are the bad guys.

Whats the problem?

I run these 2 TP-Links both as APs in my network.
If a mobile device like an iPhone is connect to AP1 and then to AP2 i can't ping / access / see mobile devices behind AP1.
Same happens on the other way.
AP1 is on the ground floor, AP2 is on the first floor. If im on the first floor with my smartphone i can access to wifi devices which are connected to AP2.
Then i go to the ground floor - my iphone changes his connection to AP1, i cannot access to wifi devices which are connected to AP2.

Like i said i've spend 150 hours to find it out.

The problem is when im auto changing to the better AP, the previous AP does not get that im (iPhone) not longer connected to him.
Then when im sending a ping over AP1 from my iphone to a device behind AP2 the echo does not come back, because AP2 has my iphone as well as "ghost device" in his wireless statistics.

When i login to AP2 and kick my iphone out manually. I can ping devices behind AP2.

Same with both TP-Link pocket routers. I have reset them many times, i have down- and upgrade their firmware, nothing helps.


Does anybody every heard about this problem?


Cheers,

Pagemaster
  0      
  0      
#1
Options
4 Reply
Re:WR710N & WR702N in AP Mode - connected wireless clients problems
2016-10-26 22:42:16
@ Mods please delete these two spamming posts, thank you.
  0  
  0  
#2
Options
Re:WR710N & WR702N in AP Mode - connected wireless clients problems
2016-11-03 03:39:08
Nobody has this problem before me?
I bought 2 additional tp-link routers - WR841N and WR810N, the problem occurs at these units as well.

Just test it, you'll see you can produce this errror with every tp link product.

It's a very serious problem when you want to access to other wireless device in your private network when the other wireless devices are connected to a different access point.

Example: You are connected with your iPad to AP1 (WR841N), your IP camera is connected to AP2 (WR810N). And you can't access to your IP camera.
  0  
  0  
#3
Options
Re:WR710N & WR702N in AP Mode - connected wireless clients problems
2017-01-05 02:51:14
You have probably solved your problem by now. I setup a WR710N today and had similar problems. My network uses 192.169.1.x but the WR710N uses 192.169.0.x which will cause the problems you are having. I reset the IP address, but then used to wizard to set the device to AP mode. I hadn't realised the IP address would be reset to the default, so when I couldn't access anything properly I reconnected the WR710N to my computer and set a manual IP address to suit my network. This solved the problem and now everything is working correctly. Might be useful for someone else with similar issues.
  0  
  0  
#4
Options
Re:WR710N & WR702N in AP Mode - connected wireless clients problems
2017-01-05 20:59:30
Hello scgf,

thank you for your post.

Sadly my problem isn't solved yet and my problem has nothing to do with yours, cause all my devices and all my APs are in the same address range 192.168.1.xxx

I can reproduce the problem with many TP-Link products.


Just to let you know an additional info:
You need to open the "connected devices" list in your TP-Link webinterface.
If for example a smartphone is conntect with this AP for a while it is logical listed in this list.

If the smartphone is out of the range of this AP and it is conntect to another AP it should disapear in this list from AP1, but that does not happen.
And in this situation the routing is broken or something like that. Devices behind AP1 are not visible for devices behind AP2 when they are still listed as "ghost devices" in AP1 under conntected devices.


Sadly the TP-Link support does not reply to any email requests about this case.
  0  
  0  
#5
Options