1

I have a pair of Ubiquiti AirFiber APs to connect our main building to another a couple miles down the road. No issues for a very long time, but recently I’ve been having to build up the network and add some VLANs, and they don’t appear to be passing to the main building.

I have a Meraki MX firewall that’s handing all the VLAN work; the AirFiber on the main building is on a separate VLAN, but whoever set up the remote building had everything (including the AP) on the default network. If I try to set up a new VLAN and have it communicate back to the Main Building, there’s no communication, even though the switches are set to allow and pass all tagged VLANs.

This is the only building I have with these APs, so I’m wondering if I’m missing something, or if it was set up incorrectly. Unfortunately, the company that set them up has been unresponsive.

1 Spice up
2

Ubiquiti AirFiber devices are transparent bridges - this means they just pass all ethernet frames to the other side.
To support mutliple vlans you just need to TAG the vlans to the Airfiber.
Basically pretend the Air Fiber PTP link does not exist and that the two switches are directly linked by a cable. Configure the ports for required vlans.
Ideally use the same native vlan at each site, but you don’t need to.
Example: Site 1 uses native/untagged vlan 1 and tags vlan 2,3,4 on AF port. Site 2 uses native vlan 5 and tags vlan 2,3,4 on AirFiber port. Vlans 2,3,4 work as expected but anything from vlan 1 at site 1 will enter vlan 5 at site 2.
If they both use the same native vlan then it gets less confusing.

3

That it was just a bridge is my understandings, too. Sounds like the company that set it up, leaving the 2nd end on the default VLAN, might be the culprit.