Remember to make backup/export files before an upgrade and save them on another storage device;
Make sure the device will not lose power during upgrade process;
Device has enough free storage space for all RouterOS packages to be downloaded.
What's new in 6.46rc1 (2019-Nov-26 13:19):
**MAJOR CHANGES IN v6.46:
!) lora - added support for LoRaWAN low-power wide-area network technology for MIPSBE, MMIPS and ARM;
!) package - accept only packages with original filenames (CVE-2019-3976);
!) package - improved package signature verification (CVE-2019-3977);
!) security - fixed improper handling of DNS responses (CVE-2019-3978, CVE-2019-3979);
----------------------**
Changes since last beta release:
!) ptp - disabled support for IEEE 1588 Precision Clock Synchronization Protocol until further notice;
*) bridge - do not add dynamically VLAN entry when changing "pvid" property for non-vlan aware bridge;
*) capsman - fixed MAC address detection for "common-name" parameter in certificate requests;
*) certificate - added progress bar when creating certificate request;
*) certificate - allow specifying "name" parameter for import (CLI only);
*) crs3xx - improved system stability when initializing SFP modules;
*) export - always export "ssid" value for w60g interfaces;
*) fetch - do not allocate extra 500KiB on SMIPS;
*) ipsec - fixed IPsec policy checking on RB4011 (introduced in v6.46beta68);
*) switch - added "comment" property for switch vlan menu (CLI only);
*) w60g - do not reset link when changing comment on station;
*) w60g - fixed "monitor" command on disabled interfaces;
*) w60g - move stations to new bridge when "put-in-bridge" parameter is changed;
*) winbox - added enable/disable and comment buttons for "IP->SNMP->Communities" menu;
*) winbox - fixed field validation with negative integers (introduced in v6.46beta);
*) wireless - added "ETSI" regulatory domain information;
Is ROMON working on last 2 versions?It seams broken to me, simple wireless bridge between 2 routers, no firewall rules, i can see router listed(MAC,ROUTER OS version, Router model) but it cant connect it just timeouts with disconnected from ROMON after 10 sec.
OK, tested it as I hoped that UPS would now be supported correctly.
UPS connected via USB to tthe USB-Hostport of a CRS109-8G-1S-2HnD (mipsbe).
WIthin System → UPS, the UPS is been identified connected to Port usbhid1 with a name of ups1 (with a preceeding red exclamation mark!) and as model ‘Smart-UPS 1500 FW:COM 02.1 / UPS.05.I’
‘Offline After’ and ‘Load (%)’ both do not show any value, whereas ‘On Line’ is flagged as ‘yes’.
For the details pages:
General:
Name: ups1
Port: usbhid1
Off Line time: 00:05:00
Min Run time: 00:05:00
Alarm Setting: immediate
Status:
all empty except for the following fields:
Run Time Left: 00:30:00 (been updated!)
Battery Charge: 100%
On Line: checked
If system is running on battery nothing get´s updated. Hitting the ‘Beep Button’ does not result in any action. Hitting the beep button on the top level UPS-page give an error ‘Beep Error - Cannot beep USB ups (6)’
To make this long story short: NOT WORKING as expected!
I do have several models at hand. Did my test with the main one, a APC SMart-UPS 1500, SMT1500I
Also tested with a SMART-UPS 750 FW: UPS 09.4 / ID=18, APC Smart UPS, SMT750I
and I tested with a SMART-UPS 1000 FW: UPS 09.4 / ID=18, APC Smart UPS, SMT1000I
For the SMT750I and SMT1000I I noticed that at least the flag on the Status page for ‘on Line’ gets dropped upon power loss and the value for ‘offline After’ get´s then filled in. But that´s it. As I am willing to get that running I will now test each and every new beta-version.
All of the APC UPS do have the newest firmware! (in case that might help)
I am using DNS names, then if your are using the DNS server from the IKEv2 providers you have a chicken and egg problem. To get the IP address you need DNS server and to have DNS you need a IKEv2 connection and to have a connection you need a IP address…start over again.
My DNS server is public and this worked with 6.45.7 without issues. This is specific to 6.46rc1 (and possibly beta releases, did not try these).
So no chicken and egg problem.
When will this error be fixed where DHCPv6 Client stays forever on “rebinding” without getting actual dhcp information?
You always have to manually hit release / renew to restart the dhcp client process, then it immediately gets the dhcp information and switches status to bound.
Really annoying bug that exists for ages now.
For me this happens with PPPoE Interfaces, often after a reboot, or when the parent interface goes down and up again.
No, sorry emils. I didn’t realize the changelog in the first post isn’t the full changelog.
Couldn’t find anything DHCPv6 related, my bad.
When 6.46 has been officially released, I’ll try it again and report back. Thanks!