Added
- VLANs can now be set up from the panel, not just adjusted. Edit mode on the Interfaces card opens a VLAN editor: add the VLANs you need, then give each port a role — Access in one VLAN, or Trunk carrying several. The PVID box from the previous release is gone; it required knowing what a PVID is, and the editor does not.
- The panel works out how your hardware wants to be configured. Some MikroTik switches keep their hardware offload when VLANs live on the bridge; others lose it and have to be configured on the switch chip instead. You are not asked which kind of device you have. The editor looks the same either way and writes whichever configuration is right for that model, so the traffic stays offloaded.
- A switch with nothing configured on it is a normal starting point. If the device has no bridge yet, saving creates it, moves the ports into it, writes the VLAN table and switches VLAN filtering on — in the one order that does not interrupt traffic halfway through. You describe the ports; the rest is what that means.
- A management checkbox on each VLAN. Tick it and the device gets its own interface in that VLAN, on the bridge, so it can be reached there. It does not move any address — that stays your decision.
- The port the panel manages the device through is identified and kept out of the change. It is worked out from the device's own IP configuration, including when the address sits on a VLAN interface riding a physical port. Where the management path runs through the bridge itself, it cannot be kept out of the change — so instead the editor refuses to delete that VLAN, to take the bridge out of it, or to leave it reaching no port, and says plainly that everything else in this configuration still affects how you reach the device.
- Nothing is written until you have seen it. Review changes shows the exact RouterOS commands, in the order they will run, with a plain-language summary of what each port ends up as and what any of it costs.
- An automatic rollback runs on the device itself. Before the first change the device is given a rollback that fires in three minutes unless you confirm. The panel shows the countdown with Keep it and Roll back now. Closing the browser does not stop it — if you lose the device, it puts itself back.
- A backup is taken before anything is changed, and a failed backup cancels the change.
- VLAN names are stored on the device, as the VLAN's comment, so a name given here is visible in Winbox and the other way round.
- Ports the device added by itself are shown, not hidden. On an access point the Wi-Fi interfaces are attached to the bridge by RouterOS rather than by you. They are listed with the VLANs they are in and marked
Dynamic, and they have no controls — RouterOS does not allow them to be changed, and they are configured where they are created. Without them the list showed two ports on a bridge that has eight.
Two roles only, on purpose: Access and Trunk, and a trunk carries its VLANs tagged. A port that was set up elsewhere with untagged traffic alongside its tagged VLANs is still editable — the plan tells you which traffic stops being carried rather than refusing the change. Ports nobody has configured are left exactly as they are: opening the editor and saving does not quietly tighten them.