Community discussions

MikroTik App
 
paraplu
just joined
Topic Author
Posts: 14
Joined: Fri Sep 18, 2015 9:35 pm

Make VLAN mgmt more easy, please

Sun Nov 07, 2021 1:44 am

Why is it so difficult to manage VLAN's with routeros ?
Taken an example from Zyxel attached, way easier.
Untitled.jpg
You do not have the required permissions to view the files attached to this post.
 
joegoldman
Forum Veteran
Forum Veteran
Posts: 767
Joined: Mon May 27, 2013 2:05 am

Re: Make VLAN mgmt more easy, please

Sun Nov 07, 2021 2:53 am

This looks more like a switch config - routers are very different.

SwitchOS has similar style of VLAN management.

RouterOS has very flexible options and management interfaces (winbox, webfig, cli etc), and GUI's like this are very restrictive to keeping that common style between the management interfaces.
The beautiful thing is - you could create a VLAN table like this and manage your switches by creating the GUI yourself, and translating to the right command in the background and hitting it via API!
 
mada3k
Long time Member
Long time Member
Posts: 697
Joined: Mon Jul 13, 2015 10:53 am
Location: Sweden

Re: Make VLAN mgmt more easy, please

Sun Nov 07, 2021 3:29 pm

Zyxel is typically used in homes or very small business. Then you want a very easy set of features so that users doesn't screw up.

Fortunally Mikrotik is more leaned to (semi-)professional use, having both CLI and API for manage thousands of devices.

What a bit of a failure is that the CRS1xx, CRS2xx and CRS3xx has very different VLAN setup and configuration style.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: Make VLAN mgmt more easy, please

Sun Nov 07, 2021 11:00 pm

Taken an example from Zyxel attached, way easier.
This isn't that much harder with RouterOS. Here is the equivalent:
/interface bridge port
add bridge=bridge interface=ether1 pvid=640
add bridge=bridge interface=ether2 pvid=2
add bridge=bridge interface=ether3 pvid=10
add bridge=bridge interface=ether4 pvid=10
add bridge=bridge interface=ether5 pvid=12
add bridge=bridge interface=ether6 pvid=12
add bridge=bridge interface=ether7 pvid=12
add bridge=bridge interface=ether8 pvid=12
add bridge=bridge interface=ether9 pvid=10
add bridge=bridge interface=ether10 pvid=10
add bridge=bridge interface=ether11 pvid=2
add bridge=bridge interface=ether12 pvid=2
/interface bridge vlan
add bridge=bridge tagged=ether2,ether12 vlan-ids=10
add bridge=bridge tagged=ether12 vlan-ids=12
add bridge=bridge tagged=ether11,ether12 vlan-ids=300
add bridge=bridge tagged=ether2 vlan-ids=640
Note that on whichever VLAN the switch itself is supposed to get an IP on (management vlan) you'll have to add "bridge" itself as another tagged port in order to still be able to reach the switch management interface after enabling bridge VLAN filtering.

Who is online

Users browsing this forum: No registered users and 10 guests