FYI this is necessary for Google Nest Doorbell (Battery) to work, as ROS 7.3.x changed the DHCP options order and the Google doorbell refuses DHCP offers if option 53 isn’t first.
Alternatively if you have this issue you can drop back to ROS 7.2.3.
So a more complete changelog for 7.4beta5 would be this: http://forum.mikrotik.com/t/v7-4beta-testing-is-released/158543/1 + this:
*) container - (!)ALL CONTAINERS FROM THE PREVIOUS BETA WILL HAVE TO BE RECREATED, due to the changes below, sorry about that;
*) container - fixed pulling remote images to internal storage, now they get pulled in the destination set as “tmpdir” in /container/config;
*) container - implemented workaround for sudo issues;
*) container - environment variables changed syntax, “list” is now “name”, “name” is now “key”:
so this from 7.4beta4: /container/envs/add list=pihole_envs name=WEBPASSWORD value=“mysecurepassword”
became this in 7.4beta5: /container/envs/add key=WEBPASSWORD name=pihole_envs value=“mysecurepassword”
(!)settings don’t get migrated to the new syntax, so please export the settings before updating to beta5;
*) container - memory limit can only be set via WinBox (container->config), it is not visible in an export, sorry about that, we’ll try to fix it in future releases;
*) container - fixed adding comments;
*) netwatch - fixed on-down script execution;
*) netwatch - fixed visibility in CLI and config export;
*) winbox - added container support;
What did I miss?
For me these changelogs are just too non-informative.
already in beta4 changelog
*) container - added support for running Docker ™ containers on ARM, ARM64 and x86;
Then again in beta5
*) container - added support for running Docker ™ containers on ARM, ARM64 and x86;
They apparently added docker support twice. Niceeee. Twice is better than once. Always good to have a spare docker. Quite an efffort to add the support two times, even if supporting docker once would be sufficient.
And if this is true, that the simple line
*) container - added support for running Docker ™ containers on ARM, ARM64 and x86;
actually means this:
Then I feel confirmed. I already criticized “Improve stability”, “add support”, “fix the thing”, “fix all” changelog entries. They do not add any value. Such changelog entries can be in fact omitted.
But many people seem to be fine with these often misleading changelog entries. When you don’t know what a “improve stability of X”-change actually improves, then every update is actually like: “maybe it may fix my issue with X. but most likely I am going to experience new issues while the existing issue with X isn’t covered”. So the serious workflow for an admin, who reads changelogs and decides whether to apply an update or not, is just impossible. So one just updates (a lab device) and then come here to the forum complaining, because the existing issue they had still applies - and another functionality that broke instead (please lay down your arms, “always check in lab first”-folks. Checking in lab to see if some existing issue is fixed, because changelogs a more or less blackboxes, is cumbersome too).
Dictionary for MikroTik changelog entries:
“improved stability” = under certain circumstances the router crashed. we have made changes to hopefully prevent that. we will not tell you exactly how it crashed.
“add support” = a first attempt at supporting a new feature has been added. it likely requires several more iterations. probably it works only in commandline mode.
“fixed” = one more iteration towards a working situation has been made. please test and report. we will probably not read your report here, so make a support ticket (we like to be overwhelmed by similar tickets!)
I think they should start by fixing wwave2 on supported products before porting it elsewhere.
Nothing is added twice. BETA releases always include ALL changes since last non-BETA. This is how it’s always been. The reason is that when 7.4 will be released, it will have all changes from last stable
Thanks, that is actually quite close explanation.
- Yes and that is intended, we do not want to tell people exact scenarios how to crash a device for your own good.
- Yes, and all iterations are listed under the same changelog entry during the beta stage as often there are major overhaul or huge amount of work on the new feature.
- Also yes, and multiple tickets actually may help increase the priority of the issue on our side.
Thanks you all for the feedback regarding the changelog, now back to the topic please.
I wouldn’t put money on this statement.
Other than that, great work! netwatch and containers are in a usable state.
Is the manual gonna be updated with the new changes to Container? or will the environment variables settings be changed back to how they used to be in beta4?
Thanks! most of them, if not all, are findings by @daaf (thanks, again!), I can’t take all the credits ^^. I’ve only put them in a list.
Not true at all. How do you then explain that change log for beta2 is much larger than beta4 and beta4 change log is larger than beta5 change log.
From what you do say beta5 should have all in beta2 and beta4.
These are only in beta5
*) dhcpv4-server - disallowed overriding message type option;
*) dhcpv4-server - log message when user option updates existing option;
*) dhcpv4-server - placed option 53 as the first one in the packet;
*) health - fixed requesting data from sensor when issuing "get" command;
*) health - fixed voltage reporting on some RBmAP-2nD devices;
*) lte - validate LTE attached IP type in MBIM mode;
*) poe - hide "poe-voltage" parameter on devices that do not support it;
*) route - expose all valid routes to route select filter from OSPF and RIP;
*) route-filter - fixed route select filter rules;
*) upgrade - ignore same version packages during upgrade procedure;
*) winbox - added "name" parameter under "Routing/BGP/Session" menu;
*) winbox - added "to-address" and "to-ports" parameters under "IPv6/Firewall/NAT" menu;
*) winbox - added support for "Routing/GMP" menu;
*) winbox - added support for "veth" interface types;
*) winbox - fixed "inactive" flag naming under "MPLS/Local Mapping" menu;
*) winbox - fixed minor typo under "Interface" stats;
*) winbox - fixed units for "reachable-time" parameter under "IPv6/ND" menu;
*) winbox - removed "TLS Host" parameter from "IP/Firewall/NAT" menu;
*) winbox - removed duplicate signal strength column under "Wireless/Registration Table" menu;
These are both in beta4 and beta5
*) container - added support for running Docker (TM) containers on ARM, ARM64 and x86;
*) netwatch - added support for more advanced probing;
*) wifiwave2 - added initial support for roaming (802.11r) between local AP interfaces;
These are only beta4 changes: According to statement above all these are removed from beta5???
*) defconf - fixed default configuration loading on devices with WifiWave2 package;
*) dhcp-relay - fixed DHCPv6 relay forward and reply creation (introduced in v7.1.3);
*) dhcp-server - change "vendor-class-id" matcher to generic option matcher;
*) dot1x - fixed "undo" command for server instances;
*) l2tp - improved stability when establishing l2tp-ether connection (introduced in v7.3);
*) leds - fixed GPS LED configuration on LtAP LTE kit;
*) leds - fixed LTE signal strength LED configuration on LHGG LTE kit;
*) leds - fixed LTE signal strength LED configuration on LtAP LTE kit;
*) lte - added AT chat support for Dell dw5821e modem;
*) lte - fixed LTE interface running state after modem reconnection;
*) mqtt - fixed socket error handling;
*) ovpn - fixed "called-station-id" RADIUS attribute value for OVPN server;
*) ppp - do not fail connection when trying to add existing IP address to address list;
*) ppp - log warning message when remote IP address can not be added;
*) route - changed "mode" setting to "exclude" for group management protocol (CLI only);
*) route - made export run faster on tables with a large number of dynamic routes;
*) routing-filter - added origin matcher to match for example routes of a specific OSPF instance;
*) routing-filter - made "do-jump" work in select rules;
*) ssh - fixed host key generation (introduced in v7.3);
*) switch - fixed multicast flooding when HW offloaded bridge port gets disabled;
*) system - fixed configuration reset with "run-after-reset" with file stored on ramdisk;
*) upgrade - improved RouterOS upgrade stability with attached USB modem on MIPSBE, SMIPS and MMIPS devices;
*) w60g - improved interface initialization after being inactive for a while;
*) winbox - fixed filename dropdown value filtering;
*) x86 - fixed Broadcom NIC support;
Please stay on topic. Deleting offtopic now
OK, but what is the answer to my question. You do say that every new change log do show all added stuff since main release. My post clearly that what is sad, does not add up.
RB760 iGS
switch → L3 HW Offload
it is some mistake?
or 750gr3/760igs will be “special” in small device category ?
Chateau 5G comfortably running 7.4beta5
https://help.mikrotik.com/docs/display/ROS/Switch+Chip+Features
Bridge HW vlan-filtering was added in the RouterOS 7.1rc1 (for RTL8367) and 7.1rc5 (for MT7621) versions. The switch does not support other ether-type 0x88a8 or 0x9100 (only 0x8100 is supported) and no tag-stacking. Using these features will disable HW offload.
vlan filtering is L2 feature, and yes, i was glad when MT enabled this option on mt7621
but question was about L3 HW offload ?
That looks like a visual issue in WinBox. RB760 iGS does not support L3 HW Offloading.
Because you are missing the point. Only new features repeat. Fixes do not.
all my hopes are gone now 
i was excited that after L2 HW, small 750/760 will be gifted with L3 HW like big brothers
tnx for reply
Change notes should be put on a dynamic website where you can query “what has changed between version X and version Y”, with a link to that website in the forum release topics and the same query being made from the “check for upgrades” function of the router (where it will show changes between the version you are currently running and the offered version).
That will end all confusion and will make maintenance much easier. Nice project for a trainee or intern: make a database where all published change notes are stored and a query that returns a list similar to what we have now. Requires no RouterOS knowledge so any developer can quickly get started on this.