Also - related to my original post here
The single GUI page should also have the ability to manage both HW-bridges and non-HW-bridges.
The new GUI could possibly auto-detect if a port is already configured and mark it in the single GUI as non-configurable because the port is already
configured in other sections of port/switch configurations - aka only able to configure in the GUI if the port & bridge & vlans that are not already configured else where. This might make it easy to create a single page GUI if the GUI page does not have to translate and/or modify other sections of ports & bridges. Thus if a port or vlan or bridge is already configured , then the admin would simpley delete/remove the old configurations for that port then let the new single-page GUI do it all.
Note - I just did a forum search for vlan
I got the following response: Search found 62303 matches
** That's a huge amount of vlan ( port /switch ) questions - and none of them simple/easy for any non-guru Mikrotik admin.
The single GUI page should also have the ability to manage both HW-bridges and non-HW-bridges.
The new GUI could possibly auto-detect if a port is already configured and mark it in the single GUI as non-configurable because the port is already
configured in other sections of port/switch configurations - aka only able to configure in the GUI if the port & bridge & vlans that are not already configured else where. This might make it easy to create a single page GUI if the GUI page does not have to translate and/or modify other sections of ports & bridges. Thus if a port or vlan or bridge is already configured , then the admin would simpley delete/remove the old configurations for that port then let the new single-page GUI do it all.
Note - I just did a forum search for vlan
I got the following response: Search found 62303 matches
** That's a huge amount of vlan ( port /switch ) questions - and none of them simple/easy for any non-guru Mikrotik admin.
Statistics: Posted by TomjNorthIdaho — Thu Mar 27, 2025 2:47 am