No. The untagged membership will be dynamically generated from the pvid= settings under /interface bridge port
-Why do the interface numbers change? My goodness this is the most annoying thing!
For physical interfaces they shouldn’t change as they already exist and cannot be removed. For interfaces which can be added (e.g. tunnels, VLANs) an internal index number is created and used behind the scenes where the name is used in configuration statements, so when an interface is renamed you do not have to change the name used in all of the statements.
-After deleting all the interfaces inside the default bridge group, I run this command to add most ports to the new bridge; it doesn’t work for multiple interfaces. Do I really need to do this individually 40 times? “add bridge=BridgeStaff interface=ether1,2,3,…,40 pvid=10”
Why remove the ports from the bridge in the default configuration and add them to another one? Just change the desired settings.
-Do I need to specify the “hw=yes” flag (I assume this is for hardware offloading)?
IIRC it is the default so can be left out.
-If I rename an interface with a human understandable name, what is the best way to keep the interfaces in order? (eg. 1-RM207-Mary, 2-RM307-Bob) [I’m useed to CISCO gi1/1 or te1/1 being consistent and adding description to interface]
I either append something descriptive to the original name, e.g. ether1-RM207-Mary, or leave the name unchanged and add a comment to the interface.
-Under bridge port print, what does *3E mean?
That is the internal index number for an interface which has been deleted.
-Is “/export” same as ‘show run’?
Pretty much. Unlike Cisco, where you make changes to the running configuration and then save them, configuration changes are immediate. You can use Safe Mode which will roll back changes on loss of connectivity to Winbox/CLI.
-When I run “/interface bridge vlan add bridge=BridgeStaff tagged=ether48 untagged=ether1 vlan-ids=10” it says failure vlan already added
Once you have created something with add you should use set to modify it.
-How do I tell what an interface is setup as (turnk, access, vlan, etc) “/interface ethernet print” is super vague [/interface bridge port> print] might work
/interface bridge port print and /interface bridge vlan print are the correct place to look for the PVID and VLAN memberships. /interface ethernet print is just for the underlying physical interfaces.
Seems Mikrotik’s implementation of vlans and trunks is absurdly complicated and not necessary. I cannot wait for SwOS to come out, until then; buying more of this switch is out of the question. The smaller CRS328-24P-4S+RM is great though with SwOS.
It is just different, I don’t particularly like the Cisco CLI compared to HP.
For trunk and hybrid ports http://forum.mikrotik.com/t/vlan-issues/143197/1 may be useful.