For plain 802.11 it works, we have been using it for ages.
At least in nv2 security and preshared key seems not to be supported by its way of operation.
How about no security and preshared key, will it work ?
Nstreme, we never tested it, but security profile can be picked up and is same way as in plain 802.11, will it work ?
We plan to put up one omni antenna as failback for sectors in one mast, just to be able letting customers work in degraded mode but working, or is only way to put up a fully fledged “crown” of antennas and basestation ?
Either use same security profile on each nv2 sector so omni can take over clients in case sector dies.
Or MT must develop an option in future OS that we can actually put multiple nv2 security profiles in router.
I do have at times when I pre configure CPE for installation but am not sure which AP is going to be used yet.
I can set ´connect-to´ rules for several AP’s and set the different freq’s to scan for. In normal 802.11 or nstreme protocol you could set different security profiles for each AP.
But NV2 can only have one security set, in the main wireless setting. So basically I have to explain installer how to set NV2 security on spot when he informed me about which AP is going to be used…
Maybe a request to MT: Can NV2 security be set like legacy 802.11 with different profiles for same radio interface? Future add-on for ROS?
