My WAN port is configured to port 5
Is Quick Set still unsupported as widely suggested in this forum and does anyone know where the data is populated from?

1. You do not use VLAN1
2. You DO NOT use VLAN1
3. You remove default user admin and set a strong password before connecting to the internet.
4. You do not use Quickset.
5. You do not use detect internet.
6. You keep routerboard firmware upgraded to the same release as Ros software update
7. You manually set admin-mac=<MAC> and auto-mac=no on bridge(s)
8. ...

[*] You manually set admin-mac=<MAC> and auto-mac=no on bridge(s)

Would you mind explaining what this rule means?

Or point me to a thread that explains is.

Would you mind explaining what this rule means?

Or point me to a thread that explains is.

viewtopic.php?t=214219
viewtopic.php?t=209850
viewtopic.php?t=190747

The only possible issue of carving the MAC in stone is that if you restore a backup to another device on the same network (something you should not do anyway) you need to take care of the MAC duplication/conflict.

Is it really that bad to just allow the device to pick/assign it's own mac address? Yet another thing to setup and remember is another thing to go wrong.

Is it really that bad to just allow the device to pick/assign it's own mac address? Yet another thing to setup and remember is another thing to go wrong.

Of course it isn't, until it becomes so and bites you.

Resistentialism is a thing when dealing with Mikrotik:
https://en.wikipedia.org/wiki/Resistentialism

If you use default configuration (on devices that do have one) it should be already set.
viewtopic.php?t=190747
viewtopic.php?t=190747#p966670

Seriously, I don't know what the admin-mac is or what it is used for. I read some of the threads, faithfully staying in my 20-40% comprehension level, and I see that it is, by default, set to the same mac-address as the lowest numbered eth port, and that there might be a problem is/when restoring from an rsc. That's the extent of my understanding. I don't know what you mean by "if you use default [config] it should be already set." Set to what? Set to eth1? Set differently from eth1? Set to auto-admin-mac=no?

Seriously, I don't know what the admin-mac is or what it is used for. I read some of the threads, faithfully staying in my 20-40% comprehension level, and I see that it is, by default, set to the same mac-address as the lowest numbered eth port, and that there might be a problem is/when restoring from an rsc. That's the extent of my understanding. I don't know what you mean by "if you use default [config] it should be already set." Set to what? Set to eth1? Set differently from eth1? Set to auto-admin-mac=no?

It basically comes down to MT developers being lazy and not bothering to find a simple, good solution, so they just dump the responsibility on the user instead. Would be fun to know what that philosophy is called!

Seriously, I don't know what the admin-mac is or what it is used for.

I read some of the threads, faithfully staying in my 20-40% comprehension level, and I see that it is, by default, set to the same mac-address as the lowest numbered eth port, and that there might be a problem is/when restoring from an rsc. That's the extent of my understanding.

By default, bridge MAC address will be chosen automatically, depending on the bridge port configuration. To avoid unwanted MAC address changes, it is recommended to disable "auto-mac" and manually specifying the MAC address by using "admin-mac".

/interface bridge
                       add name=bridge disabled=no auto-mac=yes protocol-mode=rstp comment=defconf;
                     :local bMACIsSet 0;
                     :foreach k in=[/interface find where !(slave=yes   || name="ether1" || passthrough=yes   || name="ether1" || name~"bridge")] do={
                       :local tmpPortName [/interface get $k name];
                       :if ($bMACIsSet = 0) do={
                         :if ([/interface get $k type] = "ether") do={
                           /interface bridge set "bridge" auto-mac=no admin-mac=[/interface get $tmpPortName mac-address];
                           :set bMACIsSet 1;
                         }
                       }
                         :if (([/interface get $k type] != "ppp-out") && ([/interface get $k type] != "lte")) do={
                           /interface bridge port
                             add bridge=bridge interface=$tmpPortName comment=defconf;
                         }
                       }

This is the reason why we recommend setting bridge MAC manually, and all default configurations with bridge involved come out with the "admin-mac" set.

                     /interface bridge
                       add name=bridge disabled=no auto-mac=yes protocol-mode=rstp comment=defconf;
                     :local bMACIsSet 0;
                     :foreach k in=[/interface find where !(slave=yes   || name="ether1" || passthrough=yes   || name="ether1" || name~"bridge")] do={
                       :local tmpPortName [/interface get $k name];
                       :if ($bMACIsSet = 0) do={
                         :if ([/interface get $k type] = "ether") do={
                           /interface bridge set "bridge" auto-mac=no admin-mac=[/interface get $tmpPortName mac-address];
                           :set bMACIsSet 1;

Do I understand correctly that we are addressing the potential problems of having auto-mac=yes, which is the default setting for devices with no configuration?

And by 'no default configuration' we mean no config whatsoever (not even Quickset), right?

And the potential problem (or one of the problems) is that the admin-mac (of the bridge) might be copies from an eth port not a member of the bridge?

**... it also means if you add a new bridge at the CLI — either from blank or even a 2nd bridge — any new bridge added will have auto-mac=yes... which will use lowest MAC address as the bridge MAC automatically.

/interface bridge
add name=trunk vlan-filtering=yes
/interface vlan
add interface=trunk name=vlan-99 vlan-id=99
/interface bridge
add name=MGMT
/interface bridge port
add bridge=MGMT interface=vlan-99

I'm pretty sure that the example above doesn't cause any harm though.