Client Bridge Issue (I Think)

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Advanced Networking
Author Message
brock.travis
DD-WRT User


Joined: 22 May 2011
Posts: 51

PostPosted: Tue Jun 19, 2012 20:52    Post subject: Client Bridge Issue (I Think) Reply with quote
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

_________________
2x e3000 on 15962
Sponsor
brock.travis
DD-WRT User


Joined: 22 May 2011
Posts: 51

PostPosted: Wed Jun 20, 2012 16:20    Post subject: Reply with quote
Update to this. I went ahead an just did the ping test to the LAN side of my router on the otherside of the wireless bridge.

Pretty much the same result which leads me to believe it must be issues/problems in the wireless communication.

I will be bridging the routers with a cable for testing here in the next few days and run the same ping tests to see if I get the same results.

I'll also be trying different firmware again should I be unable to correct the problem on my current firmware.

CMD wrote:

Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=48ms TTL=64
Reply from 192.168.2.254: bytes=32 time=42ms TTL=64
Reply from 192.168.2.254: bytes=32 time=59ms TTL=64
Reply from 192.168.2.254: bytes=32 time=78ms TTL=64
Reply from 192.168.2.254: bytes=32 time=69ms TTL=64
Reply from 192.168.2.254: bytes=32 time=19ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=3ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=9ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64

CMD wrote:

Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=34ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=33ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=2ms TTL=64
Reply from 192.168.2.254: bytes=32 time=43ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=499ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=3ms TTL=64
Reply from 192.168.2.254: bytes=32 time=468ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64
Reply from 192.168.2.254: bytes=32 time=1ms TTL=64

_________________
2x e3000 on 15962
brock.travis
DD-WRT User


Joined: 22 May 2011
Posts: 51

PostPosted: Thu Jun 21, 2012 2:27    Post subject: Reply with quote
Removed the wireless bridge and connected the routers via a temporary patch cable and the issue vanished.

Now I guess I play with the newer builds again until I can find one with a stable Client Bridge connection...

CMD wrote:

Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64
Reply from 192.168.2.254: bytes=32 time<1ms TTL=64

_________________
2x e3000 on 15962
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Advanced Networking All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum