John, 1) yes, you can reserve the IPs for the 4410N's by MAC of each device. That works fine but why not just explicitly set the IP of each device to be static? Take a troubleshooting step out of the loop. 2) Even after doing that the status tab shows both wired and wireless mac addresses to be associated with the same dynamic ip address... My AP541N's do the same thing. Same MAC and IP for both its own LAN and WLAN interfaces. I assume that's because each device always either forwards from WLAN-LAN or stays in the airspace and skips the LAN altogether. BTW, I'm also seriously disappointed in the lack of knowledgeable documentation and best practices for SBPro devices. I have different devices than you, but same category. Little to no advice on security settings, wireless radio settings, optimizing for speed or coverage, etc. Little to no explanation of clustering/ WDS bridging and benefits/drawbacks. Absolutely subpar speed and connection persistence.
... View more
I wish I had answers to all of your questions, but I'm afraid that I can mostly offer moral support. I too have a pair of AP541N's doing WDS bridging. In my case they are bridging two LAN's in separate buildings. The AP's have line-of-sight to each other about 90-100 feet away from each other (same signal strength /speed as when they were in the same room for testing). Firmware is 1.9.2 on both (came with 1.8.0). I have tried WPA, WEP, and no encryption on the bridge. 5 GHz radio with 40 MHz channel bandwidth. No other 5 GHz wireless devices in area. Channels set to match. Pretty much everything you have done. My AP management cluster view shows 26 Mb/s wireless link. Transfer speeds across bridge match this topping out at <3 MB/s. It seems that consumer-level wireless G hardware can do better than this. My AP541Ns' sole purpose is for bridging wirelessly. I currently have no need for wireless client access and plan to purchase separate AP's when and if that need arises. One further issue is that my AP's reset their hostname to default when they are powered off and back on, not normally a problem, except after power outages. This happens even when the config has been saved -- in fact, it's the only setting that changes after a power cycle. So if I can be of any help: 1) DHCP works across my WDS bridge. Win2003 Server is the DHCP server. DNS and LDAP work fine also, as they should i suppose, since no ports or protocols are being blocked. I believe I've heard of a registry mod for certain Windows situations to make DHCP jump further or not as far. 2) WDS bridge speed....I wish we could both make our AP's go faster, but I'm searching for answers on this like you. Again, I've tried just about all encryption options from none to RADIUS, and it's always really slow. 3) CCA is not nearly as useful as the web config. One advantage is that certain basic parameters (hostname, IP) can be easily set for your various access points from one interface. However, there are no radio controls, bridging, or useful security options in CCA. It redirects you to the AP web-config for important settings. 5) I do believe that setting the radio channel explicitly (which I had to do to complete my bridge) is a 'hard setting' for the device as a whole. So yes, all VAP's are limited to that setting. I initially set mine up for auto channel on 5 GHz band but when the two devices auto-selected different channels, I picked the higher of the two and set them to be the same. I don't believe that this will result in a bottleneck, as the device is only using a certain channel width (20 or 40 MHz) in its spectrum (5 GHz in this case), whether it is auto-selected or not.
... View more