First of all, this is my test setup;
The issue is now that the DHCP client doesn't get an address... but now it becomes even more strange. Port 2 is in fact connected to my core switch but on an access port (which internally is linked to VLAN 255 - but this is offcourse stripped when leaving the access port- which is my provider). If I change the VLAN id in the configuration of the CRS above to also use 255... the DHCP client DOES get an address ???/interface ethernet
set [ find default-name=sfp1 ] name=sfp1 master-port=none
set [ find default-name=ether2 ] name=ether2 master-port=sfp1
# Interfaces VLAN
add name=VLAN50 vlan-id=50 interface=sfp1
# Switch VLAN
/interface ethernet switch vlan
add ports=sfp1,switch1-cpu,ether2 vlan-id 50 learn=yes
# Switch VLAN tagging
/interface ethernet switch egress-vlan-tag
add vlan-id 50 tagged-ports=switch1-cpu
# Switch In VLAN
/interface ethernet switch ingress-vlan-translation
add customer-vlan-format=any customer-vid=0 new-customer-vid=50 ports=ether2 sa-learning=yes
add name=VLAN50-pool ranges=192.168.50.1-192.168.50.100
/ip dhcp-server network
add address=192.168.50.0/24 gateway=192.168.50.254 dns-server=220.127.116.11
add name=VLAN50-DHCP interface=VLAN50 lease-time=01:00:00 address-pool=VLAN50-pool
How can this be... the CRS shouldn't know at all about the VLAN on my core switch ! I used wireshark to see if somehow VLAN tagged traffic is coming out if it but it doesn't ???
Due to all this I played a bit more and replaced the DHCP client by an IP-address linked to VLAN50. The strange thing is that when I now connect a laptop (which has a static IP in the same subnet) to port 2, I can ping it fine... however if I connect another laptop to port 2 the same ping doesn't work anymore (while on my core switch both laptops work fine) ???
Am I missing something... or is this some magic going on ? Any additional information about what each Switch VLAN menu does would be a great help.