Is there a way to prevent neighbor access points running in static WDS mode from connecting to an access point that doesn't have a WDS entry for it? I have several access points WDS'd together in a chain, and even the distant one tries to connect to the nearest one, and is always listed in the registration list with a signal of -100 @ 1Mbps. They all share the same ssid, all in ap-bridged mode, static wds, running MT 2.8.27. This network works great, but has a few side effects. It spams the logs with connect/disconnect messages that may be making them crash. Two, I'd like to gather some information about client connections, but the numbers aren't accurate as the list in the registration table is showing other APs that shouldn't be connected and registered.

I've tried entering the unwanted APs in the access list and disabling forwarding and authentication, but they still try to connect, and still show up in the registration table. Is there any way to prevent unwanted WDS neighbors from connecting and showing up in the registration table? Thanks in advance.

I cant think of any way to block them as they bypass access lists (i am unable to grasp why this potential design issue isnt done differently). Instead, how about using static WDS or station-wds mode?

In v2.8, you should use static WDS if you want to only allow certain connections.

In the logs it may say that WDS is connected, but when in static WDS, there will be no data to or from this WDS link.

John

Actually, they are all in static WDS mode. They are hopping APs, which need to allow client connections, so I don't think I can use station-wds (?)

John, If anything it would just be nice to block them altogether so they don't show as registered clients and don't spam the log with connect/disconnect. Strictly out of curiousity, is this just a limitation of how WDS works, or is there a possibility of implementing this in the future?

We can remove the 'log spamming', but thats about it.

John