Community discussions

MikroTik App
 
pacman88
newbie
Topic Author
Posts: 31
Joined: Mon Aug 22, 2016 7:08 pm

vlan bridge config is PITA - improvement suggestions

Sat Feb 16, 2019 2:31 pm

Hi

no matter how much I love Mikrotik and appreciate that there are now really usable new switch models like the 328-24P - configuring vlan bridges is a PITA.

my usual scenario is to have
.) one or more uplink/trunk ports with a range of vlans (tagged)
.) one or more groups of hybrid/access ports with usually one untagged vlan (eg. clients) and one or more tagged vlan(eg. voice)

this means I have to
1.) create interface lists for each group (eg trunk, clients_a, clients_b,...)
2.) add each interface list as port member to the bringe and set the PVID of the access vlan
3.) create each VLAN that is used as untagged vlan as seperate vlan (no ranges)
4.) create all remaining VLANs that are only used as tagged vlans (ranges can be used here)
5.) add each single port to each vlan it should be a tagged member of (for some reason i can't use if lists here)

especially 5.) is a real PITA. imagine you are having 24 ports which you already added to an iflist and now you want these to carry 1 or more tagged vlans in adition to the untaged access vlan then you will have to edit each and every tagged vlan and add 24 ports to it. if you need to change it later you have to touch all these vlans again...

suggestion:
a) allow the use of interface lists in "/interface bridge vlan add tagged=<interface>"
b) or even better: drop the vlan tab and allow specifying tagged port/vlan memberships when adding the port to the bridge like "/interface bridge port add pvid=<untagged_vlan> tagged=<vlan_ids/range>"
c) to make things perfect: allow easily adding port ranges to interface lists like "add ports=ether1..12"

is there any chance this might get implemented or do i need to start building scripts to synthesise this?

BR
Alex
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 12980
Joined: Thu Mar 03, 2016 10:23 pm

Re: vlan bridge config is PITA - improvement suggestions

Sat Feb 16, 2019 6:46 pm

I guess your proposal b) is a realistic one and would be nice to have.

Proposal a) would be nice as well, but probably harder to implement (any change in interface list membership would have to trigger complete VLAN setting reconfig).

Proposal c) can't be done as port names are changable and list as written in example is meaningless.
 
User avatar
pcunite
Forum Guru
Forum Guru
Posts: 1347
Joined: Sat May 25, 2013 5:13 am
Location: USA

Re: vlan bridge config is PITA - improvement suggestions

Sat Feb 16, 2019 7:56 pm

If you're doing this very frequently, there would be gains to scripting it all, for sure. Someone could even make a web-based GUI to export it all for us.

Who is online

Users browsing this forum: eider, erlinden and 31 guests