second wds client screws things up

We have a small test network with 6 customers. A 532RB with an Ethernet daughter card acts as the router. Wan1 is dhcp to our provider, it has 2 local subnets 192.168.17.x and 172.16.250.x. Nat is enabled, and we access it via a windows machine and a PPTP vpn connection.

from my pc I can ping the ap (bridged wds) at 192.x.x.10. We started replacing some of the clients with rb112 boards. The first one worked fine when the second one was added problems started. To make a long story short. When a second wds (rb112) clinet is enabled with in a few minutes you can no longer ping any of the clients. Disable the second client and with in a few minutes things will return to normal. It does not matter which client is enabled (one is an Sr2 the other is a CM9).

Did i miss something in the routing or in the WDS? I can post the conifigs if anyone is interested.

Thanks

Erik

update.

Pinging from the ap to the single wds clients is fine. Pings from the router to the ap are fine. Pings from the router to the client yields a small loss.

Could be nice to see some configs.. For me it sounds like some looping (dynamic WDS?) or maybe conflicting IP’s.. Whatever, need to see some data..

/Henrik

Thanks Diganet, The issues appears to have been some sort of WDS loop, I disabled all but one client at at time and was then able to get into the board and check the configs. There were several errors in the programing of 2 of the 3 rb112. I corrected the problems and everyone is happy. Now all that is left is to clean up the other junk on the system and move some antennas to clean up the rf side.

Thanks for the hint.


Erik