Thank you for your reply here is ping
Here is ping result
From wireless client to access point
C:\>ping 192.9.90.139
Pinging 192.9.90.139 with 32 bytes of data:
Reply from 192.9.90.139: bytes=32 time=257ms TTL=64
Reply from 192.9.90.139: bytes=32 time=102ms TTL=64
Reply from 192.9.90.139: bytes=32 time=97ms TTL=64
Reply from 192.9.90.139: bytes=32 time=1780ms TTL=64
Ping statistics for 192.9.90.139:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 97ms, Maximum = 1780ms, Average = 559ms
C:\>ping 192.9.90.147
Pinging 192.9.90.147 with 32 bytes of data:
Reply from 192.9.90.147: bytes=32 time=1609ms TTL=64
Reply from 192.9.90.147: bytes=32 time=81ms TTL=64
Reply from 192.9.90.147: bytes=32 time=348ms TTL=64
Request timed out.
Ping statistics for 192.9.90.147:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 1609ms, Average = 679ms
From wireless client to controller
C:\>ping 192.9.60.181
Pinging 192.9.60.181 with 32 bytes of data:
Reply from 192.9.60.181: bytes=32 time=2464ms TTL=255
Reply from 192.9.60.181: bytes=32 time=1563ms TTL=255
Reply from 192.9.60.181: bytes=32 time=1771ms TTL=255
Request timed out.
Ping statistics for 192.9.60.181:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 1563ms, Maximum = 2464ms, Average = 1932ms
And sometime
C:\>ping 192.9.60.181
Pinging 192.9.60.181 with 32 bytes of data:
Reply from 192.9.60.181: bytes=32 time=29ms TTL=255
Reply from 192.9.60.181: bytes=32 time=96ms TTL=255
Reply from 192.9.60.181: bytes=32 time=34ms TTL=255
Reply from 192.9.60.181: bytes=32 time=724ms TTL=255
Ping statistics for 192.9.60.181:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 724ms, Average = 220ms
From wire client to access point
C:\>ping 192.9.90.147
Pinging 192.9.90.147 with 32 bytes of data:
Reply from 192.9.90.147: bytes=32 time=2114ms TTL=64
Reply from 192.9.90.147: bytes=32 time=2476ms TTL=64
Reply from 192.9.90.147: bytes=32 time=1524ms TTL=64
Request timed out.
Ping statistics for 192.9.90.147:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss)
Approximate round trip times in milli-seconds:
Minimum = 1524ms, Maximum = 2476ms, Average = 2038ms
C:\>ping 192.9.90.139
Pinging 192.9.90.139 with 32 bytes of data:
Reply from 192.9.90.139: bytes=32 time=2389ms TTL=64
Reply from 192.9.90.139: bytes=32 time=28ms TTL=64
Reply from 192.9.90.139: bytes=32 time=115ms TTL=64
Reply from 192.9.90.139: bytes=32 time=573ms TTL=64
Ping statistics for 192.9.90.139:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 2389ms, Average = 776ms
From wire client to controller
C:\>ping 192.9.60.181
Pinging 192.9.60.181 with 32 bytes of data:
Reply from 192.9.60.181: bytes=32 time=266ms TTL=255
Reply from 192.9.60.181: bytes=32 time=354ms TTL=255
Reply from 192.9.60.181: bytes=32 time=49ms TTL=255
Reply from 192.9.60.181: bytes=32 time=2140ms TTL=255
Ping statistics for 192.9.60.181:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 2140ms, Average = 702ms
our network subnet is class b