It seems like a sound decision to consolidate any shortcomings to make the Netinstall installation and usage as streamlined as possible. When things gets fricked-up badly you more then ever need a tool that is reliable and doesn’t cause additional hassle during the restoration process.
Yeah, when it comes to legacy code nothing is simple. Regarding compatibility it depends on how far back in time you want to stretch things. If you are dependent on an old third-party win32 network stack, you might have some extra work to do, but if you settle for Winsock 2.0, it will work on all versions from Win95 (1995) onwards.
What do they look like now? Again these “lookup in table abc” replaced by “lookup in table *0x4000” or similar?
That has happened to me before on upgrades, twice in fact. It seems they cannot get that under control.
local VPN can’t see my local networks. my local VPN address is 192.168.22.0/32 and local network is 10.5.51.0/24. before upgrade to 7.2.3 everything working without any issue.
can you explain about this (“lookup in table *0x4000”), i have same problem, for me i have mangle rule, usually i override with route rule for some ip, for some reason it go to mangle rule route first and ignore the route rule, i decided to downgrade to 7.2.1 and all rule work again
The problem that the lookup table is replace with * and some hex number is caused by the problem that routing tables are lost during upgrade.
So after upgrade, when you have problems you should go along all places where you defined and used routing tables, and fix the settings.
(first add the table again, then go to the routing rules or mangle rules and replace the *number with the actual routing table again)
The bare minimum of a stable release should be that it boots without bricking the device, i don’t mind if there’s some other bug that means I roll back, no stable release should ever crash a device to the point where manual intervention to physically recover the device is required. that is what the ‘testing’ or ‘development’ tree is for.
There should be a semblance of stability in the ‘stable’ branch.
Reading the forum to see if a stable update kills your device isn’t good enough, If Microsoft bricked 25% of machines with every patch Tuesday people would be screaming, they wouldn’t be saying “But did you read the forums?”
For the most part we aren’t installing RouterOS on home built hardware (x86 aside) we’re installing it on devices Mikrotik have designed, built and pertain to support, if the software doesn’t run reliably on their own hardware in the stable branch then whats the point of upgrading at all? How do we know what will or wont kill our devices?
[quote=dbnetwork post_id=931431 time=1651793702 user_id=194520]
does anyone know what is the “passthrough” action to use in routing filters in v7?
[/quote]
There is no need for that in v7, ROS automatically continues in the chain when you do not reject or accept.
