I have a little problem, that probably is a little bigger for me - because that I am more used to the way Cisco handles/names VLAN.
This is the first Mikrotik I have used for about 6 years, and a lot have changed since then
History:
Hardware: Cisco Catalyst 3560 switch and Apple Airport
When an Apple Airport Extreme is connected as a router to a generic switch port (equal port not configured for special purpose) - all other Apple Airport devices is able to replicate the Guest Wireless network from the Apple router.
Apple creates a VLAN 1003 for all guest networks, and it originates on the Airport running router.
The Apple Airport router acts as DHCP server for both wired, office wireless and guest network.
Office/wireless shares same DHCP server and the Guest network (VLAN 1003) has another DHCP range on the DHCP server.
The Cisco Catalyst has not been changed in configuration since this has been working, and no ports needed any special configuration. All airports is connected directly to individual ports on the Catalyst.
The new setup:
Hardware: Mikrotik CRS109-8G-1S-2HnD now running as router instead of Apple Airport, AP is an Apple Airport (bridge)
Mikrotik CSR has been updated from 6.19 to 6.22.
Port 1 is the internet connection (WAN), Port 2 goes to the Catalyst switch on same port that previously was used to connect to the Apple Airport.
There is a normal DHCP server configured on the Mikrotik, for normal cabled and wireless network on the Master port (port 2)
A VLAN 1003 is created on the Mikrotik, with a DHCP server on the VLAN.
The VLAN 1003 is not configured for a specific port, but is connected to the local Bridge - the office network on the Master port.
When an Apple Airport is connected directly to the Mikrotik CSR (port 5), the Airport is able to create at Guest network and is delivering the DHCP IP from the VLAN-1003 DHCP server in the Mikrotik.
The Problem:
Hardware: Mikrotik CSR, Cisco Catalyst, Apple Airport
When an Apple Airport is connected to the Cisco Catalyst, the Airport no longer delivers an IP from the VLAN 1003 DHCP server - meaning that the there is no VLAN 1003 traffic on the port where the Airport is connected.
This worked in the previous setup, so I assume I do something wrong on the CSR. I just can't figure out where or what. It could be VLAN tagging or perhaps on the CSR switch setup.
Supplemental: It is not possible to create a VLAN 1003 configuration on the Catalyst, as Cisco uses VLAN 1003-1005 for internal special purposes. Hence I am not able to pass the specific VLAN to a switch port on the Catalyst.
So somehow, I have to get the Mikrotik CSR to replicate the VLAN 1003 like the Apple Airport did before. And this is what I need help with.
I hope someone is able to help me with this - I tried with Hairpin NAT without success. Perhaps because of the way Cisco handles VLAN's and the CSR built in switch.
But I am sure that there probably is someone else who have had the same problem.
Below is a copy of the configuration (extract of the relevant - only wireless networks that the CSR is AP for is omitted):
[admin@MikroTik] /interface> print
Flags: D - dynamic, X - disabled, R - running, S - slave
NAME TYPE ACTUAL-MTU L2MTU MAX-L2MTU MAC-ADDRESS
0 R ;;; WAN
ether1-gateway ether 1500 1588 4064 4C:5E:0C:9F:68:47
1 RS ;;; Local
ether2-master-local ether 1500 1588 4064 4C:5E:0C:9F:68:48
10 RS wlan1 wlan 1500 2290 4C:5E:0C:9F:68:50
12 R ;;; Local
bridge-local bridge 1500 1588 4C:5E:0C:9F:68:48
13 R ;;; VLAN1003
eth-vlan1003 vlan 1500 1584 4C:5E:0C:9F:68:48
[admin@MikroTik] /interface vlan> print
Flags: X - disabled, R - running, S - slave
NAME MTU ARP VLAN-ID INTERFACE
0 R ;;; VLAN1003
eth-vlan1003 1500 enabled 1003 bridge-local
[admin@MikroTik] /interface bridge> print
Flags: X - disabled, R - running
1 R ;;; Local
name="bridge-local" mtu=auto actual-mtu=1500 l2mtu=1588 arp=enabled mac-address=4C:5E:0C:9F:68:48
protocol-mode=rstp priority=0x8000 auto-mac=no admin-mac=4C:5E:0C:9F:68:48 max-message-age=20s
forward-delay=15s transmit-hold-count=6 ageing-time=5m
[admin@MikroTik] /ip address> print
Flags: X - disabled, I - invalid, D - dynamic
ADDRESS NETWORK INTERFACE
0 ;;; Local
192.168.1.1/24 192.168.1.0 ether2-master-local
1 ;;; TeamGuest
172.16.1.1/24 172.16.1.0 ap-TeamGuest
2 ;;; VLAN1003
172.16.10.1/24 172.16.10.0 eth-vlan1003
3 D 91.144.236.24/22 91.144.236.0 ether1-gateway
(eth-vlan1003 is the VLAN DHCP server setup)