I`m not able to get eth1 back to the bridge because master port can`t do it.
Master port was just a different way of configuration of hardware forwarding among ports of a switch chip.
So there is no reason why you could not make ether1 an ordinary member of a bridge. The fact that it still bears a name ether1-master after the upgrade has no effect on its functionality (and it never had, what was actually meaningful was a configuration of the other ports). And there is a known issue with the configuration migration, which keeps the IP configuration attached to the ex-master port instead of moving it to the bridge.
So in pre-6.41, it was like this:
- ether1 was a master port, and the DHCP client or static IP configuration was attached to ether1 as an IP interface
- ether2 and ether3 were part of the same switch port group, linked together by setting master-port=ether1 in their configuration; L2 traffic between devices connected to any of those three ports was forwarded directly by the switch chip, bypassing the CPU.
In 6.41+, the same topology is now represented by three objects commonly named a
bridge. To provide the same functionality, the three Ethernet ports are all made member ports of that bridge, and the
/interface bridge port rows bear a
hw=yes parameter to enable the switch chip forwarding between them. And the IP configuration must be attached to the router interface part of the bridge, not to one of the member Ethernet ports.
So it is possible that something else than an IP configuration is attached to your ether1, which prevents it from being added as a member port of the bridge, so the configuration migration process was unable to do that.
Post the export of your current configuration if the information above is not sufficient. Read my automatic signature below before posting it.