2 x TL-WA7510, A.P to A.P client router bad communication.

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

2 x TL-WA7510, A.P to A.P client router bad communication.

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
2 x TL-WA7510, A.P to A.P client router bad communication.
2 x TL-WA7510, A.P to A.P client router bad communication.
2016-11-19 02:47:26
Model : TL-WA7510N

Firmware Version:







[/TD]
[TD="colspan: 2"]3.12.6 Build 130427 Rel.69746n

Hardware Version: WA7510N v1 00000000








[TD="class: Item"][TD="colspan: 2"][/TD]
[/TD]





ISP :

Hello.

I have two antennas (TL-WA7510) where one of them acts like an AP and the other receives internet as A.P client router .

The primary problem is that I am unable to hit any page ,at A.P client router lan . There is communication between the two antennas and the PING is very good. Though, when I try to load any page the ping values goes too high.

This is the ping values. The Request timed out result occurs when I try to load a page.

[CODE]
Ping statistics for 192.168.1 Pinging 192.168.1.131 with 264 bytes of data:

Reply from 192.168.1.131: bytes=264 time=13 TTL=64 seq=1
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=2
Reply from 192.168.1.131: bytes=264 time=22 TTL=64 seq=3
Reply from 192.168.1.131: bytes=264 time=17 TTL=64 seq=4
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=5
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=6
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=7
Reply from 192.168.1.131: bytes=264 time=2 TTL=64 seq=8
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=9
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=10
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=11
Reply from 192.168.1.131: bytes=264 time=7 TTL=64 seq=12
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.131: bytes=264 time=727 TTL=64 seq=25
Reply from 192.168.1.131: bytes=264 time=555 TTL=64 seq=26
Reply from 192.168.1.131: bytes=264 time=10 TTL=64 seq=27
Request timed out.
Request timed out.
Reply from 192.168.1.131: bytes=264 time=36 TTL=64 seq=30
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=31
Reply from 192.168.1.131: bytes=264 time=10 TTL=64 seq=32
Reply from 192.168.1.131: bytes=264 time=4 TTL=64 seq=33
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=34
Reply from 192.168.1.131: bytes=264 time=18 TTL=64 seq=35
Reply from 192.168.1.131: bytes=264 time=8 TTL=64 seq=36
Reply from 192.168.1.131: bytes=264 time=4 TTL=64 seq=37
Reply from 192.168.1.131: bytes=264 time=5 TTL=64 seq=38
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=39
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=40
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=41
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=42
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=43
Reply from 192.168.1.131: bytes=264 time=3 TTL=64 seq=44
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=45
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=46
Reply from 192.168.1.131: bytes=264 time=2 TTL=64 seq=47
Reply from 192.168.1.131: bytes=264 time=3 TTL=64 seq=48
Reply from 192.168.1.131: bytes=264 time=7 TTL=64 seq=49
Reply from 192.168.1.131: bytes=264 time=1 TTL=64 seq=50

Ping statistics for 192.168.1.131
Packets: Sent = 50, Received = 36, Lost = 14 (28% loss),
Approximate round trip times in milliseconds:
Minimum = 1, Maximum = 727, Average = 40.131
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milliseconds:
Minimum = 1, Maximum = 20, Average = 7


[/CODE]

Is anything I should try to isolate the problem?

Thanks.
  0      
  0      
#1
Options