Fri Oct 12, 2012 4:53 pm
802.1Q VLAN's will work between any vender that support them. Basically all that the VLAN is doing is adding or reading 1's and 0's in the packet header.
If you add a vlan for example VLAN 10 to ether5 then put an IP address on that VLAN then a device plugged into ether5 that is on that same subnet with that same VLAN will be accessible.
We have a Unifi here at the office... and my boss likes them and sells them however, I would much rather use MikroTik Access Points. The MikroTik will do the job and will not need some software installed on a computer to manage it. The problem in my opinion with the Unifi is that the advantages of easy deployment require the management and maintenance of a system that has noting to do with the wireless network. If you forget about the controller software down the road when you upgrade the PC originally used to setup the network then you just lost the advantage of the Unifi platform. If you use MikroTik and set them up as a mesh or WDS then you can just open the box, drop a config on them and go.
I don't want my wireless AP's controlled by an external software package any more then I want my up-line ISP controlling my IP provisioning. However, if UBNT had all of the controlling and management run on the AP I would sing a different tune. Except for the fact that we do have to reboot the UBNT gear from time to time and I cannot remember the last time I had to reboot a MikroTik to get it to behave. If I did have a MikroTik require a reboot then I would remove it form service and put it through the ringer to find out what's wrong.