Master port after update to 6.41.2 (2011UiAS-2HnD)

RouterOS General
1

Hey guys, :slight_smile:

Really weird scenario. I have Mikrotik RB2011UiAS-2HnD (Atheros8327 (ether1-ether5+sfp1); Atheros8227 (ether6-ether10)), RouterOS 6.40.8 - all of the interfaces are in one bridge, named: “bridge”.
I have upgraded the Mikrotik to: 6.41.2, and the master ports, were still there: ether2-master and ether6-master.

I decided to change the configuration and to remove all of the interfaces from the bridge, except: ether3, ether4 and ether10 (I need the PoE). Strangely when ether2-master and ether6-master were removed from the “bridge”, there were created automatically two more bridges: “for-master1”; “for-master2”, which I removed.

Currently in the “bridge”, there are two ports from the first switch ship are in the bridge and one from the second, there is hardware offload.

For example:

etheр10 is being looped with ether7, there is H
etheр4 is being looped with ether2, there is H
etheр4 is being looped with ether9, there is H

Despite the fact that there is flag for Hardware offload, there is nothing in the logs as:
15:15:01 bridge,info hardware offloading activated on bridge “bridge” ports: ether2-master
for this connections.

More confusing to me is why after the update, there are still master ports.

2

Does that mean that the names of these ports still contain the string “master” or that some other ports refer to these as their master ports? Because the latter should be impossible, the “master port” item is not available any more in port configuration.

Normally, when you have a master port with some slaves in 6.40.x, and the master port is a member of a bridge, after upgrade to 6.41.x, the previously master port remains a member of the bridge and the previously slave ports of that master become members of the same bridge. I suppose (haven’t tested that) that if, in 6.40.x, some configuration like IP address, DHCP server etc. is attached directly to a master port which has some slaves and is not a member of any bridge, the upgrade creates a bridge to which all the settings from the master port are moved, and makes both the previously master port and all its slaves members of that newly created bridge. But in neither case the name of the port changes.