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