We are running into an issue where we are trying to deploy A5’s but the current firmware limits a SSID to either have per CPE vlans or trunk all vlans. We need some CPE’s to be trunk mode, some to be a single native vlan, (and ideally a third option, a native vlan + trunk)
This is pretty common on cambium and ubiquity equipment.
Our scenario/use is for BRAS/radius deployments where the native vlan from the customer needs to be a specific tower vlan but we also need to be able to trunk in and handle both tagged and untagged traffic to CPE’s on site.
Is this reasonable to expect from a future firmware? We would greatly perfer the vlan setting to be per CPE, and mimic most switch chips in that the port can be the following;
Untagged traffic only in from the LAN of the CPE, apply “x” vlan tag to it in the radio and send it up to the AP. (traditional vlan tagged access port) block any tagged traffic from passing up to the AP.
Untagged traffic + tagged traffic. Tag untagged traffic in from the LAN of the CPE along with tagged traffic, apply a tag of “x” to any untagged and send up, allow other tagged traffic also up to the AP. (traditional native vlan + tagged)
Tagged only: Discard any untagged traffic, allow only tagged traffic to pass up to the AP. (tagged only port)
Ideally with an option to set in the A5 which tagged vlans to allow/listen to so someones random internal tagged VLAN isn’t leaking in.