Posted: Tue Jun 19, 2012 20:52 Post subject: Client Bridge Issue (I Think)
I periodically have a communication "glitch" in what I think is my Client Bridge.
If I "ping pingtest.com -t" and wait, I see evidence of the issue.
As you can see, my response time jumps up for about 5 seconds.
My signal stats.
Signal: -50
Noise: -79
SNR: 29
I've already lowered my Beacon Interval to 75 from 100 to attempt to help keep the routers in sync.
I have no RX errors on either side of the Client Bridge.
I have very few TX errors (less than 20 in 24hours).
Not sure what to do now...
This is a small snippet from about a 5 minute ping.
CMD wrote:
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=60ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=60ms TTL=48
Reply from 216.240.172.176: bytes=32 time=60ms TTL=48
Reply from 216.240.172.176: bytes=32 time=60ms TTL=48
Reply from 216.240.172.176: bytes=32 time=62ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=73ms TTL=48
Reply from 216.240.172.176: bytes=32 time=60ms TTL=48
Reply from 216.240.172.176: bytes=32 time=64ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=802ms TTL=48
Reply from 216.240.172.176: bytes=32 time=806ms TTL=48
Reply from 216.240.172.176: bytes=32 time=810ms TTL=48
Reply from 216.240.172.176: bytes=32 time=812ms TTL=48
Reply from 216.240.172.176: bytes=32 time=817ms TTL=48
Reply from 216.240.172.176: bytes=32 time=820ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=60ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=60ms TTL=48
Reply from 216.240.172.176: bytes=32 time=60ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=60ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=65ms TTL=48
Reply from 216.240.172.176: bytes=32 time=60ms TTL=48
Reply from 216.240.172.176: bytes=32 time=60ms TTL=48
Reply from 216.240.172.176: bytes=32 time=60ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48
Reply from 216.240.172.176: bytes=32 time=60ms TTL=48
Reply from 216.240.172.176: bytes=32 time=61ms TTL=48