The same here, have to stay on 7.2.1 (7.2.3 or 7.3 - the same issue). Not only this, currently when upgraded from 7.2.1 to 7.3 I lost again some parts of configuration (at least all simple queues now), but even though I fix that by restoring saved configuration from 7.2.1, the routing issue still persist. Downgrade to 7.2.1 solve everything again. I have a support ticket SUP-81294 on this since 4.5.2022 but still no relevant solution/help from Mikrotik support
[quote=TimmZahn post_id=937874 time=1654612859 user_id=200086]
RB5009UG is still reporting the error “cpu not running at default frequency” after upgrading to v7.3.
[/quote]
Upgraded CCR1009-8G-1S-1S+PC without problems. Running nat, few vlans, ipsec, ipip/gre tunnels, ospf, wireguard. So far everything works fine. Also successfully upgraded RB2011-UiAS-2HnD.
On such a device (with enough flash), always partition the router with 2 partitions and copy the active to inactive partition before upgrading.
Then, when it bootloops at least you have easy (automatic) recovery.
Can you give more information how VLAN tagging works on 7.3 (versus 7.2/7.1/7.0)? I migrated from ROS6 to 7.0 and since ever all my VLAN worked…
Also did not see any doc saying VLAN config method changed suddenly.
Upgraded multiple devices inc CCR1009 / CRS317 / RB4011 / RB3011 / wAP AC all OK.
However, I encountered an issue when upgrading my RB5009 from 7.2.3 to 7.3: it has a bonded WAN interface (Ether 2 and 3) connected to a Virgin Media HUB 4 (in modem mode). The bonded WAN interface is configured as a DHCP client and normally gets a 192.168.100.x IP address from the hub with a number of short DHCP lease times, which eventually gets replaced with the public IPv4 address once the cable modem is fully initialised.
However, after upgrading to ROS 7.3 (& firmware 7.3), it gets the initial 192.168.100.x IP addresses via short DHCP leases from the HUB4, but never obtains the final public IPv4 address, even when clicking on the RENEW button in the DHCP client config window.