WS-24 1.3.3 VLAN Trunking Issue (not passing VLAN)

[Hexis]

I have a WISP SW 24 on 1.3.3 I have the switch port set as "trunk" with the following config:



On port 10 I have an airfiber 5x , which needs to pass all VLANS. I have a cisco catalyst off of the airfiber with devices that are tagged VLAN 300, but nothing from port 10 is passing VLAN 300, despite the fact that the mac table of the cisco shows these items on VLAN 300. I have another UBNT radio (rocket ac), which contains the same VLAN on vlan 300 which has mac addresses from the customer side. The customer side MAC addresses show up on the netonix, but not the MACs on VLAN 300 from the AirFiber link. VLAN 1 however, it transversing port 10 without issue.

[sirhc]

Please post up a picture with the VLAN IDs please.

Why on earth would you configure a switch this way, what is the point?

[adairw]

It does seem like an odd configuration to set every port to trunk.
I don't personally use the trunk check box so I can't speak to it working but I don't see why it wouldn't.
HOWEVER, to test your setup. remove your trunk check boxes from all ports, add vlan 300 and tag it on the ports you need and see if it passes traffic to it.
alternatively, only trunk the ports you need to pass all vlans.

[Hexis]

This switch is doing only trunking, it contains only access points and backhauls, across which all VLANs are allowed, including management and customer VLANs, why is this a strange setup? All tagging is done by routers.

Apart from this, what is it interesting is that I followed adairw's suggestions and tagged it on the port that I was trying to use it on, which made me unable to access things on the management interface (as expected), but after removing the tag and setting it back to trunk, suddenly I was able to see VLANs all the way from one end to the other, where I previously was unable to see them transversing the AirFiber link on port 10.