RB 750GL (Level 4)-VLANs on Dell switch-DHCP server per VLAN

Hello!

Here is my scenario. I have a VLAN capable Dell switch (PowerConnect 2824).

I have one internet ADSL gateway.

I need to create 3 VLANs with different DHCP subnets, and every machine in each VLAN to be able to have internet access.

I will create the VLANs on Dell sw, can I use RB 750 GL to accomplish that?

Regards

Kostas

Yes. Search wiki for “Router on a stick”

This is the link: http://wiki.mikrotik.com/wiki/SwOS/Router-On-A-Stick

Thank you!

In this case, I need a VLAN capable router, don’t I?

Regards

Kostas

Yeah. Like an RB750GL, for example.

Thank you.

In this scenario, how to set the trunk ports on the RB? I will have 3 VLANs on Dell and one trunk. The goal is all the 3 VLANs to have Internet access, but different ip range.

Best regards

Kostas

http://wiki.mikrotik.com/wiki/Manual:Interface/VLAN

Add VLAN interfaces to the same physical interface on the router. Configure IP addresses on VLAN interfaces. Connect switch to router. That’s pretty much it.

/interface vlan 
add interface=ether1 vlan-id=10 disabled=no name=vlan10
add interface=ether1 vlan-id=20 disabled=no name=vlan20
/ip address
add interface=vlan10 address=10.10.0.1/24
add interface=vlan20 address=10.20.0.1/24

Thanks.

Do I have to use the same interface for all traffic? Can I use separate interface for each VLAN?

Best regards

Kostas

I ordered my RB750, hopefully I will have it tomorrow.

My first need is to create 2 separate VLANs to be used with 2 different SSIDs of one Unifi AP.

With the code provided, is there anything else to do for the VLANs to have internet access? Do I have to set the ports of the VLANs to have as master port the main network port? Do I have to setup NAT?

I did not quite understand how the VLANs will get internet access. I will read the doc.

Best regards

Kostas

VLAN’s in Mikrotik are simply another interface, and as such they are treated just like any “normal” interface as far as routing traffic is concerned.

A lot of people get caught up with the idea of “trunk ports” and other Cisco or HP terminology. For clarity, I typically name my VLAN subinterfaces with both the VLAN and physical interface they are on. To use the above example:

/interface vlan 
add interface=ether1 vlan-id=10 disabled=no name=V10-E1
add interface=ether1 vlan-id=20 disabled=no name=V20-E1
add interface=ether3 vlan-id=20 disabled=no name=V20-E3
/ip address
add interface=V10-E1 address=10.10.0.1/24
add interface=V20-E2 address=10.20.0.1/24

The reason I do this is because VLAN’s don’t magically move through the router, they are treated just like any normal interface. If I want VLAN 20 to “pass through” from port 1 to port 3, I need to make a bridge with both V20-E1 and V20-E3, just like I would with normal Ethernet ports.

/interface bridge
add bridge=Br-VL20 disabled=no interface=V20-E1
add bridge=Br-VL20 disabled=no interface=V20-E3

So in the example provided:
untagged traffic coming in Ether1 would show up on “Ether1”
VLAN10 tagged traffic coming in Ether1 would show up on “V10-E1”
VLAN20 tagged traffic coming in Ether1 would show up on “Br-VL20” and pass through to VLAN20 on Ether3.

Thank you very much!

I will try and post back.

Best regards

Kostas