Below is the example configuration on Mikrotik and PMP-450 radios.
Topology :-
PC --> Mikrotik Router(ether2= VLAN-10, ether3= VLAN-20, ether5= Trunk VLAN 10,20) -->AP PMP 450 -->Wireless à SM PMP450 -->Mikrotik -->PC
Configurations on Mikrotik :-
- Configuring the trunk port:
/Interface vlan add name=vlan 10 vlan-id=10 interface =ether 5 disabled=no
/ Interface vlan add name=vlan 20 vlan-id=20 interface =ether 5 disabled=no
- In order to forward the packets add bridges:
/interface bridge add name=br-vlan10 disabled=no
/interface bridge add name=br-vlan20 disabled=no
- Add ports to the bridge
/interface bridge port add interface=”vlan-10” bridge=”br-vlan10” disabled=no
/interface bridge port add interface=”ether2” bridge=”br-vlan10” disabled=no
/interface bridge port add interface=”vlan-20” bridge=”br-vlan20” disabled=no
/interface bridge port add interface=”ether3” bridge=”br-vlan20” disabled=no
Configurations on PMP450 AP and SM:
On AP:
- Configuration>> Vlan >> Enable
- Management VID: 10
- Allow Frame Types: All Frames
- Dynamic Learning: Enabled
On SM:
- VLAN Port Type: Q
- Configuration>> Vlan >> Enable
- Management Vlan: 10
- Allow Frame Types: All Frames
- Dynamic Learning: Enabled
- Management VID: 10
- Default Port VID: 20
How to Verify the specific Vlan traffic hitting AP and SM from network devices:
- Go under Statistics >> VLAN >> Clear Statistics >> VLAN Statistics Configuration >> select the Vlan in this case its VID =10
- Click on Save Changes
- Monitor the Vlan 10 frames hitting the AP/SM under the "Most Recent Filtered Frames"
Interpret entries under Most Recent Filtered Frames as follows:
• Unknown— this must not occur. Contact Technical Support.
• Only Tagged— the packet was filtered because the configuration is set to accept only packets that have an 802.1Q header and this packet did not.
• Ingress— when the packet entered through the wired Ethernet interface, the packet was filtered because it indicated an incorrect VLAN membership.
• Local Ingress— when the packet was received from the local TCP/IP stack, the packet was filtered because it indicated an incorrect VLAN membership. This must not occur. Contact Technical Support.
• Egress— when the packet attempted to leave through the wired Ethernet interface, the packet was filtered because it indicated an incorrect VLAN membership.
• Local Egress— when the packet attempted to reach the local TCP/IP stack, the packet was filtered because it indicated an incorrect VLAN membership.
I have attached few screen shots for reference.
- VLAN statistics of AP for VLAN 10.jpg (42.1 KB)
- VLAN statistics of AP for VLAN 20.jpg (49.1 KB)
- VLAN statistics of SM for VLAN 10.jpg (55 KB)