Why don't you combine your wired and wireless POS in one VLAN and bridge all of the used for VLAN ports and not the VLANs? In this you would utilize bridge VLAN and bind the POS and employee addresses to their respective VLANs:
Through this configuration you'll achieve the following:
1. Separate VLANs for employees, guests and POSes
2. Untagged VLAN traffic for employees and trunk port to switch with VLAN 20 and 30
3. No need for bridging VLANs
After you've setup this configuration you could divide the VLANs in the switch and further on the CAPs according to your needs (for instance one channel on a CAP for POS, one for clients, or one CAP for POSes, one for clients, etc.)
Code:
/interface bridgeadd name=bridge/interface bridge portadd bridge=bridge interface=eth2_kontor pvid=10add bridge=bridge interface=eth3_MikrotikAPsadd bridge=bridge interface=eth4_gastrofix_wired pvid=30/interface vlanadd vlan-id=10 interface=bridge name=EmployeeLAN_VLANadd vlan-id=20 interface=bridge name=GuestWIFI_VLANadd vlan-id=30 interface=bridge name=Gastrofix_VLAN/ip addressset [ find interface=eth2_kontor ] interface=EmployeeLAN_VLANset [ find interface=eth4_gastrofix ] interface=Gastrofix_VLANset [ find interface=AP_Bridge ] interface=GuestWIFI_VLAN/interface bridge vlanadd bridge=bridge tagged=bridge,eth3_MikrotikAPs vlan-ids=20add bridge=bridge tagged=bridge,eth3_MikrotikAPs vlan-ids=30/interface bridge set vlan-filtering=yes frame-types=admit-only-vlan-tagged1. Separate VLANs for employees, guests and POSes
2. Untagged VLAN traffic for employees and trunk port to switch with VLAN 20 and 30
3. No need for bridging VLANs
After you've setup this configuration you could divide the VLANs in the switch and further on the CAPs according to your needs (for instance one channel on a CAP for POS, one for clients, or one CAP for POSes, one for clients, etc.)
Statistics: Posted by TheCat12 — Fri Mar 08, 2024 8:18 pm