*) cerm - guard template from parallel use
*) mipsle - fixed missing second level menu in CLI;
*) sstp - avoid routing loops on client when adding default route;
*) sstp - fixed problem where sometimes sstp ip addresses were invalid;
*) switch - fixed bogus log messages about excessive broadcasts/multicasts on master-port;
*) tftp - fix request file name reading from packet
*) pptp encryption - better handling for out-of-order packets;
*) ethernet - added support for new ASIX USB Ethernet dongles;
*) CAPsMAN - fix 100% CPU usage when trying to upgrade RouterOS on CAP;
*) upgrade - fixed default configuration export;
*) ppp - fixed ppp interface stuck in not running state;
*) ipsec - fixed kernel failure when packets were not ordered on first call;
*) upnp - randomize action urls to fix “filet-o-firewall” vulnerability;
*) RB532/RB564 - fixed no link after ethernet disable/enable;
*) romon - fixed default configuration export;
*) tile - fixed occasional deadlock on module unload;
*) mesh - fix router lock-up when interface is added/removed;
*) ipsec - fix sockaddr buf size on id generation for ipv6 address;
*) health - show correct voltage for CRS109,CRS112,CRS210 when powered through PSU and show voltage up to 27V when powered through PoE;
*) email - resolve server address;
*) snmp - show firmware upgrade info;
*) upgrade - report status in check-for-updates.
There are no new features, but it is not replacing the 6.30.4 as the “stable” one yet. When it will be polished enough, it might replace it, or maybe the next one
what is this exactly → email - resolve server address;
i was happy when i saw it because i believe that finally i could write at tools-email-server something like “mail.blablabla.com” and not only ip address. this is useful because ip address of mail outgoing server change. now i am using a script to resolve-update every hour the tools-email-server
I have still a problem on CRS212-1G-10S-1S+ - SFP modules (OEM) temperatures are not available, Wavelength is also not correct. It was working with 6.31.
The good thing is that this update has resolved full log of “excessive broadcast” (problem in 6.32.1, was fine in 6.31)
I was also inquisitive about this, turns out it will just resolve it once off to an IP when using a FQDN as the address in terminal, winbox (v2) doesnt allow the FQDN to be entered. (not sure about winbox v3).
MY tests were on on a RB951G-2HnD v6.32.2 (firmware v3.24).
So I dont think its 100% what you (we) were hoping for.
would be great if it allowed it to remain as an FQDN and only resolved to an IP when triggered.
Broke mesh, there goes the parasitic traffic that clogs the whole channel and the processor on all points, if one of the participants has been updated to 6.32.2.
What are the necessary data that would help fix?
Сломали mesh, в нём идёт паразитный трафик, который забивает весь канал и процессор на всех точках, если хотя бы один из участников обновился до 6.32.2.
Какие необходимы данные что бы помочь исправить?
good news everyone FQDN use for e-mail was brought back to developers and it will attempt to resolve an IP address on each send attempt, not just first one to save an IP address in the settings.
I would recommend the stable bugfix. But you should make your own tests before in both cases and don’t rely only on someone’s recommendation. The eventual failure will be only your fault. If there is no need for update,don’t do it.