Did I miss something? What was going wrong with cAP ac before this? Can you please give some details, please? Also, will it be backported to long term release?RouterOS version 6.45.2 has been released in public "stable" channel!
*) wireless - improved 802.11ac stability for all ARM devices with wireless;
I'm willing to bet that this is mostly related to wireless and 4011.Did I miss something? What was going wrong with cAP ac before this? Can you please give some details, please? Also, will it be backported to long term release?RouterOS version 6.45.2 has been released in public "stable" channel!
*) wireless - improved 802.11ac stability for all ARM devices with wireless;
Yes, broken SFP !!!!, rechecked all the modules that I have.Upgraded my RB4011 (non wireless) and my fibre SFP stopped working. It's not even recognised.
thanks a lot, we'll wait.Yes, something is not quite right with the SFP+ interface on RB4011, we will look forward to fixing it asap!
Sorry for flood... but GRE-problem is important too...thanks a lot, we'll wait.Yes, something is not quite right with the SFP+ interface on RB4011, we will look forward to fixing it asap!
How did this happen? There is nothing related to SFP in the changelog and this is supposed to be a "stable" release. If there was something, anything changed related to SFP, then it needs to go in the changelog so admins can decide with full information if they want to do the upgrade.Yes, something is not quite right with the SFP+ interface on RB4011, we will look forward to fixing it asap!
Omg. I've seen you fixed the beta, and it still doesn't work?SNMPv3 still broken in The DUDE....
seems not only RB4011 is affected,,Just bricked one of our CRS switches, connected via SFP to CCR. It was a testing one, but we still need to visit the site. How could SFP support get broken, if there are no SFP related changes? I expect fix to be released asap, not just in a mysterious stable release sometimes in the future?
Now that you know, it would be a good idea to put a line in the changelog:Often there are small changes/adjustments/refactoring in the code that does not (should not) change any functionality, but unfortunately some issues may be introduced in such way. We will resolve the RB4011 SFP+ interface issue in the next stable build. I apologize for any inconvenience.
9, nine errors introduced in a new version from previous version. Possible more.[
Changes in this release:
*) bonding - fixed bonding running status after reboot when using other bonds as slave interfaces (introduced in v6.45);
*) interface - fixed missing PWR-LINE section on PL7411-2nD and PL6411-2nD (introduced v6.44);
*) ipsec - allow peer argument only for "encrypt" policies (introduced in v6.45);
*) ipsec - fixed peer configuration migration from versions older than v6.43 (introduced in v6.45);
*) ipsec - improved stability for peer initialization (introduced in v6.45);
*) radius - fixed "User-Password" encoding (introduced in v6.45);
*) ssh - do not enable "none-crypto" if "strong-crypto" is enabled on upgrade (introduced in v6.45);
*) ssh - fixed executed command output printing (introduced in v6.45);
*) upgrade - fixed "auto-upgrade" to use new style authentication (introduced in v6.45);
*) vlan - fixed "slave" flag for non-running interfaces (introduced in v6.45);
Please, can you write something concrete about this? I look on the manual and there is nothing about it. I have problem with bad policies generated from mode config (something like in 6.45.1 thread - client policy is generated with bad src-address, from other mode-config), so I need to know if there are some configuration changes needed.*) ipsec - added "connection-mark" parameter for mode-config initiator;
*) ipsec - improved stability for peer initialization (introduced in v6.45);
Same for meI can not upgrade hAP lite - not enough space.
For "connection-mark" parameter for mode-config initiator see:Please, can you write something concrete about this? I look on the manual and there is nothing about it. I have problem with bad policies generated from mode config (something like in 6.45.1 thread - client policy is generated with bad src-address, from other mode-config), so I need to know if there are some configuration changes needed.*) ipsec - added "connection-mark" parameter for mode-config initiator;
*) ipsec - improved stability for peer initialization (introduced in v6.45);
Thank you.
I reported issues with IPSec and version 6.45.1. After all it looks like initiator device with old version caused this. Now that all devices have been updated I see no more issues.But there is not even an attempt to fix the VPN issues everyone is still having, there was never a clear way to fix that in the v6.45.1 thread, and MT needs to have those settings in the Quick Set "VPN Access" checkbox setup, because the default still has broken VPN.
May you could give a little more details here ?*) wireless - improved 802.11ac stability for all ARM devices with wireless;
I can not upgrade hAP lite - not enough space.
Perhaps before the wipe out you can try and uninstall unwanted packages to free more space.If that does not work either then you could also try a factory defaults and then upgrade as this will wipe out a few things.I've got a hAP-lite and hAP-mini in a test setup for OSPF routing, neither will upgrade. I deleted all files in the "Files" menu entry and it still won't upgrade. I rebooted them, still won't upgrade. The error is "not enough space". Maybe this is the end of the line for lower end devices?
I'd rather not wipe out the configs and do some kind of clean install if at all possible.
hAP's need quite some free RAM, they download upgrade packages to RAM disk. I fear that devices with tiny 32MB RAMs are on their edge if you run OSPF ... as it needs some RAM to contain routing tables. Same problem with long dynamic address lists (e.g. for blacklisting certain clients) etc.I've got a hAP-lite and hAP-mini in a test setup for OSPF routing, neither will upgrade.
Small changes/adjustments/refactoring should go in the beta release of the next version to be tested, while the early versions of the stable build are fixed to solve the issues not found in beta testing.Often there are small changes/adjustments/refactoring in the code that does not (should not) change any functionality, but unfortunately some issues may be introduced in such way. We will resolve the RB4011 SFP+ interface issue in the next stable build. I apologize for any inconvenience.
Running OSPF may be beyond what can be expected from them without encountering some issues...I've got a hAP-lite and hAP-mini in a test setup for OSPF routing, neither will upgrade. I deleted all files in the "Files" menu entry and it still won't upgrade. I rebooted them, still won't upgrade. The error is "not enough space". Maybe this is the end of the line for lower end devices?
Sysadmins that know Mikrotik well also know not to update anything for a few days after release or to do updates on non-critical test HW first.
It's always nice to see a new release, but then I always have to check the forum to see how broken it actually is... that's the reality.
But Mikrotik is also releasing SOHO targeted hardware and you have to think about people that update their routers using TikApp from their phones.
Cannot upgrade HAP lite series
thank's god, i have not upgrade my 1072 yet.Dear Mikrotik,
When are you going to start testing your releases? I'm guessing never, since that would be a huge workflow change internally.
When I see this in the patch notes "*) ospf - fixed possible busy loop condition when accessing OSPF LSAs;" and my routers are experiencing that problem, I wonder how fixing unrelated issues to this causes this to break. So I update to 6.45.2 because the "STABLE 6.45.1" wasn't really stable after all, so is that a term Mikrotik just throws around to sound cool around the water cooler?
Now after I update to 6.45.2 stable, (ha ha the jokes on me!) I've had a kernel panic reboot one of my CCR-1072's. The watchdog did one, with no supout file and then a second one appears to be a kernel panic with no logs. At what point do I start to say to myself and peers; Mikrotik is screwed, they can't test their patches, stable releases are a lie, whats the product I should be looking at to replace this fiasco? I also will need to ask when are the Tilera units (CCR series) going to be extinct, since it seems all of this is most likely related to the 10 year old linux kernel that keeps trying to get patched.
I see that others are questioning this as well with the SPF problem and undoubtedly more issues.
Now if the scripted response is to send a suport.rif to the support email that's just a joke right? Since most everyone knows that it's just a black-hole that never sees any light.
I just need to feel comfortable then if I use a "stable" release that it's actually that, stable. So far this has been bullshit ever since 6.44! And it wouldn't be so bad if the patch notes weren't just a passing statement, like we all should have know that the bug was there and Mikrotik is just reiterating it. I realize that my opinion here will never amount to anything that looks like real change in the Mikrotik camp, it''s more for posterity and other users who may just want to know how the company they used to trust is operated now.
I got around it by manually updating only selected packages, rather than the whole package. Basically I downloaded the SMIPS Extra Packages ZIP file on my PC, extracted it and then only uploaded the packages I actually needed to the device, which were System, Security, DHCP and Wireless, nothing else.I can not upgrade hAP lite - not enough space.
thank's for the tipsI got around it by manually updating only selected packages, rather than the whole package. Basically I downloaded the SMIPS Extra Packages ZIP file on my PC, extracted it and then only uploaded the packages I actually needed to the device, which were System, Security, DHCP and Wireless, nothing else.I can not upgrade hAP lite - not enough space.
https://blog.pessoft.com/2019/03/02/mik ... sk-device/
How do I convert it to "separate packages"? I'm not finding that information. I'm trying to remove packages now but the error is "can not uninstall bundled package". I assume this is what you mean by separate packages?Running OSPF may be beyond what can be expected from them without encountering some issues...I've got a hAP-lite and hAP-mini in a test setup for OSPF routing, neither will upgrade. I deleted all files in the "Files" menu entry and it still won't upgrade. I rebooted them, still won't upgrade. The error is "not enough space". Maybe this is the end of the line for lower end devices?
I assume you already use separate packages so you can remove what you do not need.
My hAP-lite still updates but I have converted it to separate packages some time ago and removed things I do not need, and I try the upgrade just after boot.
When desperate, you can /export or even backup the config and re-install it using netinstall (take the opportunity to use separate instead of combined package) and reload the configuration.
I explained how to do this in post #48How do I convert it to "separate packages"? I'm not finding that information. I'm trying to remove packages now but the error is "can not uninstall bundled package". I assume this is what you mean by separate packages?
[admin@CRS326] > /system resource print
uptime: 22m24s
version: 6.45.2 (stable)
build-time: Jul/17/2019 10:04:19
factory-software: 6.41
free-memory: 484.8MiB
total-memory: 512.0MiB
cpu: ARMv7
cpu-count: 1
cpu-frequency: 800MHz
cpu-load: 0%
free-hdd-space: 2120.0KiB
total-hdd-space: 16.0MiB
write-sect-since-reboot: 1119
write-sect-total: 83066
bad-blocks: 0%
architecture-name: arm
board-name: CRS326-24G-2S+
platform: MikroTik
[admin@CRS326] > /file print
# NAME TYPE SIZE CREATION-TIME
0 flash disk jan/01/1970 02:00:26
1 flash/skins directory jan/01/1970 02:00:23
2 flash/pub directory jun/12/2019 05:29:11
[admin@CRS326] >
HiDid you reboot device after uploading additional .npk's? What does log contain about it?
BTW, security requires DHCP package ....
HiHiDid you reboot device after uploading additional .npk's? What does log contain about it?
BTW, security requires DHCP package ....
yes after you write this i remember that DHCP and security are now dependant. So i might be that the way i described in the other post is not necessary. Let me try this with the second hap left on my to do list.
[admin@haplite1] > /log print without-paging
11:44:51 system,info installed system-6.45.2
11:44:51 system,info installed routing-6.45.2
11:44:51 system,info installed dhcp-6.45.2
11:44:51 system,info installed security-6.45.2
11:44:51 system,info installed wireless@-6.45.2
11:44:51 system,info installed advanced-tools-6.45.2
11:44:52 system,info,critical Firmware upgraded successfull
anges to take effect!
11:44:53 system,info router firmware has been automatically
11:44:53 system,info please reboot router to run new firmwa
11:44:53 system,info router rebooted
There's not enough information. I don't see where to download a zip file, only an npk file. I don't use Windows so I don't use winbox, which is how I assume you can upgrade individual packages? I don't see a way to do it on the command line.I explained how to do this in post #48How do I convert it to "separate packages"? I'm not finding that information. I'm trying to remove packages now but the error is "can not uninstall bundled package". I assume this is what you mean by separate packages?
At https://mikrotik.com/download, download "extra packages", which is the .zip with all, not just "extra", packages.I don't see where to download a zip file, only an npk file. I don't use Windows so I don't use winbox, which is how I assume you can upgrade individual packages? I don't see a way to do it on the command line.
Create a dedicated topic and post there configuration of the affected machine following the anonymisation hint in my automatic signature below.Our OpenVPN setup worked perfectly fine BEFORE upgrading to 6.45.1/6.45.2. Any ideas?
What was wrong with 802.11ac on ARM devices?RouterOS version 6.45.2 has been released in public "stable" channel!
*) wireless - improved 802.11ac stability for all ARM devices with wireless;
Ok, so it looks like upgrade from 6.43 to 6.44 migrated my IPsec configuration in a way that made it non-working.hEX PoE (VPN, IPsec with IKE2 RSA signature): upgrade to 6.45.2 from 6.43.x resulted in issue - somehow IPsec config was changed in a way that affected peers configuration. Clients couldn't connect due to "identity not found for peer: DER DN".
Attempts to fix it in peers config didn't help, though maybe I've missed some basic thing due to limited timeframe I had to roll back to 6.43.
However, roll-back to 6.43.16 and update of peer config with proper values fixed the issue.
FYI
I've upgraded again, but this time through interim long-term 6.44 and after that to 6.45. So far Chromecast works fine.hEX PoE + wAP ac (CAPsMAN): upgrade to 6.45.2 (also 6.46beta9) from 6.43.x resulted in issues - Chromecast couldn't connect to WiFi with "4-way handshake timeout" in logs.
Roll-back to 6.43.16 fixed the issue.
FYI
it's a known issue with winbox. Try upgrading it to 3.19Is there any chance to login with MAC Telnet ?
Thank you Sindy. Between this and post #48 I was able to get a working system. The key to my understanding was I didn't know that simply uploading a package to normal storage and rebooting would install that package.At https://mikrotik.com/download, download "extra packages", which is the .zip with all, not just "extra", packages.I don't see where to download a zip file, only an npk file. I don't use Windows so I don't use winbox, which is how I assume you can upgrade individual packages? I don't see a way to do it on the command line.
Then upload the individual .npk packages to the machine using scp (or ftp, or WebFig) and reboot.
public MK(string ip)
{
try
{
con = new TcpClient();
con.Connect(ip, 8728);
connection = (Stream)con.GetStream();
}
catch (Exception error)
{ MessageBox.Show("Error al conectar con Base.. Verifique su conexión" + Environment.NewLine + error.Message); }
}
public void Close()
{
connection.Close();
con.Close();
}
public bool Login(string username, string password)
{
Send("/login",false);
Send("=name=" + username,false);
Send("=password=" + password, true);
if (Read()[0] == "!done")
{
return true;
}
else
{
return false;
}
}
On 16M flash devices upgrade happens in RAM, so that should be fine. But you may occasionally need to reboot your device right before the upgrade to free some RAM. Also switching from bundle to individual packages should not be required, unless you want to add something that's not part of the bundle.Is it ok to have 7,4 MB available out of 16 total ?
I don't think there is a problem for 16M flash devices right now.I can't help but think this is the end of the line for 16 meg devices. I'm not sure average users are going to want to go through this, to the extent that there is an average Mikrotik user I guess. They had to know this was going to happen eventually. I see a boatload of 16 meg devices still being sold as new that won't be able to be "auto upgraded" to the latest version... And I have a bunch of them. Wow.
Welcome in the club.hAP lite has 32MB ram 16MB flash
No way to update after deleting all files and rebooted more than once (had to try netinstall yet).
The winbox method system->packages>CheckForUpdates, finds new version but "download and install button" refuses to appear (likely because of space issue).
hAP lite has 32MB ram 16MB flash
No way to update after deleting all files and rebooted more than once (had to try netinstall yet).
The winbox method system->packages>CheckForUpdates, finds new version but "download and install button" refuses to appear (likely because of space issue).
I'm usign the new login procedure.Maybe this:
Old API authentication method will also no longer work, see documentation for new login procedure:
https://wiki.mikrotik.com/wiki/Manual:API#Initial_login
public bool Login(string username, string password)
{
Send("/login",false);
Send("=name=" + username,false);
Send("=password=" + password, true);
if (Read()[0] == "!done")
{
return true;
}
else
{
return false;
}
Previously helped solve the problemhAP lite has 32MB ram 16MB flash
No way to update after deleting all files and rebooted more than once (had to try netinstall yet).
The winbox method system->packages>CheckForUpdates, finds new version but "download and install button" refuses to appear (likely because of space issue).
viewtopic.php?f=3&t=142298What was wrong with 802.11ac on ARM devices?RouterOS version 6.45.2 has been released in public "stable" channel!
*) wireless - improved 802.11ac stability for all ARM devices with wireless;
Mikrotik should focus & enhance there QA / QC Dept at higher level !9, nine errors introduced in a new version from previous version. Possible more.[
Changes in this release:
*) bonding - fixed bonding running status after reboot when using other bonds as slave interfaces (introduced in v6.45);
*) interface - fixed missing PWR-LINE section on PL7411-2nD and PL6411-2nD (introduced v6.44);
*) ipsec - allow peer argument only for "encrypt" policies (introduced in v6.45);
*) ipsec - fixed peer configuration migration from versions older than v6.43 (introduced in v6.45);
*) ipsec - improved stability for peer initialization (introduced in v6.45);
*) radius - fixed "User-Password" encoding (introduced in v6.45);
*) ssh - do not enable "none-crypto" if "strong-crypto" is enabled on upgrade (introduced in v6.45);
*) ssh - fixed executed command output printing (introduced in v6.45);
*) upgrade - fixed "auto-upgrade" to use new style authentication (introduced in v6.45);
*) vlan - fixed "slave" flag for non-running interfaces (introduced in v6.45);
Maybe there should be a better quality control?
I will wait for 6.45.8 before i dear to upgrade...
it might have been a channel issue, perhaps you have set auto channel EU, while the wifi client card is US, if router sets channel 12 for example you won't see it with that wifi client6.45.2 in my case appears to Cause in WAP AC ( RBwAPG-5ACT2HnD Models) some issues with older HP Laptops ( N max speed Intel Centrino Wireless Cards Circa 2015 Drivers ) (not AC)
The PC cannot see the Access Points for 2.4 and 5 GHz appear not Visible at all ( Either using the Built in Wifi Search or Acrylic Wifi ) .
Rolling the WAPS back to 6.44.5 have resolved the connectivity issue.
Samsung AC Phones etc ( S7 ) were still able to connect when the WAPS were at 6.45.2
Cheers Jason
Cheers Jason
Checked any hardware/power issues? A few CCRs are working perfectly OK hereMy CCR1009-7G-1C after upgraded to 6.45.x, it rebooted every night.
The logs says
"router was rebooted without proper shutdown, probaly kernel failure.
Kernel failure in previous boot."
Any solutions?
Should be, but it isn't.On 16M flash devices upgrade happens in RAM, so that should be fine.
Occasionally? It's every time and even then it doesn't work.But you may occasionally need to reboot your device right before the upgrade to free some RAM.
But it is. That's the only way to upgrade things.Also switching from bundle to individual packages should not be required
Welcome to the club! No fix afaik.My CCR1009-7G-1C after upgraded to 6.45.x, it rebooted every night.
The logs says
"router was rebooted without proper shutdown, probaly kernel failure.
Kernel failure in previous boot."
Any solutions?
Indeed! I think that whole combined package thing should be dropped, and at some time all installations are converted to separate packages during the upgrade to a new version.Why do you not just unbundle all those packages on these basic spec. devices? It's the only way they are going to work for the vast majority.
Sticking your collective heads in the sand isn't going to help. People repeatedly tell you on here that it's broken, but you don't seem to be listening.
+1Indeed! I think that whole combined package thing should be dropped, and at some time all installations are converted to separate packages during the upgrade to a new version.Why do you not just unbundle all those packages on these basic spec. devices? It's the only way they are going to work for the vast majority.
Sticking your collective heads in the sand isn't going to help. People repeatedly tell you on here that it's broken, but you don't seem to be listening.
And then the package manager should be extended with an option that allows installation of a package (from the upgrade server) with a simple mouseclick.
Some menu that shows you all the existing packages on the upgrade server, you can tick some of them, and then download them and reboot.
Just like it already happens during a regular upgrade once you have converted your device to separate packages. The mechanism is already in place, just make it accessible in the UI.
Use long-termHello, i just bought 2 hap ac^2 on one the wifi 5ghz was working on the other one, the network sometimes didnt show up . if it was visible to my laptop i couldnt connect.
I saw, that one was runing with 6.45.1 (this one was ok) and the other one with 6.45.2 had this problems.
will there be a fix?
kr
xlarge74
Youre lucky. I have CCR-1072, it not rebooting, just freezes and looking dead every 1-3 nights after upgrade to 6.45.x. Only hard reboot fix it. So, i wake up from bed and going to office to reboot. Every night.My CCR1009-7G-1C after upgraded to 6.45.x, it rebooted every night.
The logs says
"router was rebooted without proper shutdown, probaly kernel failure.
Kernel failure in previous boot."
Any solutions?
i will .. thanksUse long-termHello, i just bought 2 hap ac^2 on one the wifi 5ghz was working on the other one, the network sometimes didnt show up . if it was visible to my laptop i couldnt connect.
I saw, that one was runing with 6.45.1 (this one was ok) and the other one with 6.45.2 had this problems.
will there be a fix?
kr
xlarge74
viewtopic.php?f=21&t=150045
The point is that I haven't been able to restore the factory firmware (6.43) doing a factory reset (pressing button before turning on the power).
I wrote 19 Jul: Now that you know, it would be a good idea to put a line in the changelog:SFP+ on 4011 broken. Please pull the update. I have had two switches go offline due to this update.
You should hold off and wait for 6.46.not enough storage to update.
*) smips - reduced RouterOS main package size (disabled LTE modem, dot1x and SwOS support);
I run many services on this router, such as OSPF, OpenVPN and etc.Checked any hardware/power issues? A few CCRs are working perfectly OK hereMy CCR1009-7G-1C after upgraded to 6.45.x, it rebooted every night.
The logs says
"router was rebooted without proper shutdown, probaly kernel failure.
Kernel failure in previous boot."
Any solutions?
Probaly you need watchdog on 6.45.xYoure lucky. I have CCR-1072, it not rebooting, just freezes and looking dead every 1-3 nights after upgrade to 6.45.x. Only hard reboot fix it. So, i wake up from bed and going to office to reboot. Every night.My CCR1009-7G-1C after upgraded to 6.45.x, it rebooted every night.
The logs says
"router was rebooted without proper shutdown, probaly kernel failure.
Kernel failure in previous boot."
Any solutions?
Just downgrade to 6.44 (Long term) fix this problem to me.
Question to Mikroitk - what happening?! Why unstable firmware are going to stable release tree?!
Same problem here, there are already several crashes with routers only with OSPF, others with OSPF + BGP and all with 6.45.1. I have to force a restart to recover, it is accessible only by mac-telnet. OSPF and BGP are lost.Probaly you need watchdog on 6.45.xYoure lucky. I have CCR-1072, it not rebooting, just freezes and looking dead every 1-3 nights after upgrade to 6.45.x. Only hard reboot fix it. So, i wake up from bed and going to office to reboot. Every night.My CCR1009-7G-1C after upgraded to 6.45.x, it rebooted every night.
The logs says
"router was rebooted without proper shutdown, probaly kernel failure.
Kernel failure in previous boot."
Any solutions?
Just downgrade to 6.44 (Long term) fix this problem to me.
Question to Mikroitk - what happening?! Why unstable firmware are going to stable release tree?!
I just downgraded to 6.44.5 yesterday, it works fine!
Best solution so far for hAP lite: download and extract all_packages-smips-6.45.2.zip, upload only those packages that are enabled in your router, reboot -> router is upgraded and disabled packages are gone in one simple step.hap lite, update with netinstall and backup config. because no free space with default packages(
I run DHCP BGP Firewall NAT VLANs SFP+ L2TP (server and clients) UPnP SNMP Scripts Schedulers in most of them and so far not a single issue. Maybe the problem is service specific? Have you tried enabling logging to an external server to catch those logs before rebooting?I run many services on this router, such as OSPF, OpenVPN and etc.
Downgraded to 6.44.5 yesterday, the uptime is 10h until now without any issues.
Does it mean that my LTE modem will stop working when 6.46 is released and installed on my hAP lite? /edit: sorry, not lite but just hAP, my mistake/You should hold off and wait for 6.46.not enough storage to update.
MT is aware of the problem and seems to work on solution for the small space devices.
From 6.46Beta16*) smips - reduced RouterOS main package size (disabled LTE modem, dot1x and SwOS support);
How do you connect LTE modem to hAP lite?Does it mean that my LTE modem will stop working when 6.46 is released and installed on my hAP lite?You should hold off and wait for 6.46.not enough storage to update.
MT is aware of the problem and seems to work on solution for the small space devices.
From 6.46Beta16*) smips - reduced RouterOS main package size (disabled LTE modem, dot1x and SwOS support);
Through USB... oh sorry it's hAP - not liteHow do you connect LTE modem to hAP lite?Does it mean that my LTE modem will stop working when 6.46 is released and installed on my hAP lite?You should hold off and wait for 6.46.not enough storage to update.
MT is aware of the problem and seems to work on solution for the small space devices.
From 6.46Beta16*) smips - reduced RouterOS main package size (disabled LTE modem, dot1x and SwOS support);
Is this supported on all devices with enough flash?[*] it is possible to have two (or more) ROS versions installed in unit has flash storage with size of 64MB or more. In this case, one can partition flash to two halves and run different version of ROS in both partitions. If ROS crashes or fails to boot from one partition, it'll automatically try to boot from the other partition. If ROS is running normally, one can manually select partition for next boot.
I haven't tried it myself (the only ARM device I have has only 16MB flash), but some forum users reported that partitioning on RB4011 (IIRC) went fine.Is this supported on all devices with enough flash?[*] it is possible to have two (or more) ROS versions installed in unit has flash storage with size of 64MB or more. In this case, one can partition flash to two halves and run different version of ROS in both partitions. If ROS crashes or fails to boot from one partition, it'll automatically try to boot from the other partition. If ROS is running normally, one can manually select partition for next boot.
That is the disadvantage of putting things like that in a manual page that isn't automatically maintained. That page was likely made when those were the onlyhttps://wiki.mikrotik.com/wiki/Manual:Partitions says only MIPS, TILE and PowerPC, but my ARM-based RB1100AHx4s do have the /partition menu.
What happens when some of downloaded packages are broken during download? If you have bundle package - then you have error on bundle installation, and everything is rolled back. AFAIR, when system is already installed and some additional package is broken, it simply does not get installed, so... can't you bring your RouterOS into some "clipped" state without necessary functionality when installing separate packages?Indeed! I think that whole combined package thing should be dropped, and at some time all installations are converted to separate packages during the upgrade to a new version.
What actually that fix_space.npk does ???Previously helped solve the problemhAP lite has 32MB ram 16MB flash
No way to update after deleting all files and rebooted more than once (had to try netinstall yet).
The winbox method system->packages>CheckForUpdates, finds new version but "download and install button" refuses to appear (likely because of space issue).
Somewhere around ROS 6.41 the upgrade process could sometimes break and leave some files un-acounted for. Those could be removed only by net-installing the device. This npk tries to find such orphaned files and removes them. Newer versions are supposedly not breaking the same way and this npk won't fix anything.What actually that fix_space.npk does ???
Hello, I got a small 16gb flash drive for this. Format it as ext3 amd mount it. I keep packages, logs and backups on it. Be sure to copy them over to your PC from time to time as flash drives dont last very long.Hi,
after update all my export and backup files disapeared from files.
i'm using Hap AC2
is this beeing made by update so the devices with 16Mb memory could update normally?
Nope. Not the system part of it.Not any direct method to access to flash neither ?
No, it is made by reboot. The files directory on a device with 16M flash is a RAMDISK.Hi,
after update all my export and backup files disapeared from files.
i'm using Hap AC2
is this beeing made by update so the devices with 16Mb memory could update normally?
Hi,
Hello, I got a small 16gb flash drive for this. Format it as ext3 amd mount it. I keep packages, logs and backups on it. Be sure to copy them over to your PC from time to time as flash drives dont last very long.
On another note, can you check if your 5GHz AC wifi gets stuck at detecting radar if its set to 80MHz channel?
@normis and @mikrotik It is too hard answer this question? You rather let the user install a "defective" RouterOS for rb4011?Is it that hard to just add a warning to a changelog about not working SFP on 4011? If you don't want to pull the release, at least do the absolute minimum?
Similar issue here. Was able to solve it by switching from "Frequency: Auto" to "Frequency: 5180"hAP AC2 at AC 80MHZ XXXX stuck at detecting radar, 40 seems to work.
Issue not present on older 6.44.5 long term.
Issue from the previous stable build with high ping over 5g wifi is fixed.
Tell me if u need more info.
Can we just copy and paste whatever is in 6.44.5 for the wifi and dump it in 6.45.3?
Mine also stop working after Upgrade and CPU usage was high about (25-30%). But restoring old backup(configs) fix the problem.OpenVPN is not working anymore for us after upgrading to 6.45.1 and 6.45.2. OpenVPN clients are unable to get traffic from the OpenVPN-Net (10.10.10.x/24) to the Management Network (10.80.80.x/24). The IP Firewall in Winbox shows the following message on the rules which include the ovpn-instance:
in/out-interface matcher not possible when interface (ovpn-instance) is slave - use master instead (bridge-mgmt)
Our OpenVPN setup worked perfectly fine BEFORE upgrading to 6.45.1/6.45.2. Any ideas?
Mine also stop working after Upgrade and CPU usage was high about (25-30%). But restoring old backup(configs) fix the problem.OpenVPN is not working anymore for us after upgrading to 6.45.1 and 6.45.2. OpenVPN clients are unable to get traffic from the OpenVPN-Net (10.10.10.x/24) to the Management Network (10.80.80.x/24). The IP Firewall in Winbox shows the following message on the rules which include the ovpn-instance:
in/out-interface matcher not possible when interface (ovpn-instance) is slave - use master instead (bridge-mgmt)
Our OpenVPN setup worked perfectly fine BEFORE upgrading to 6.45.1/6.45.2. Any ideas?
And new features too!! The horror.Mine also stop working after Upgrade and CPU usage was high about (25-30%). But restoring old backup(configs) fix the problem.OpenVPN is not working anymore for us after upgrading to 6.45.1 and 6.45.2. OpenVPN clients are unable to get traffic from the OpenVPN-Net (10.10.10.x/24) to the Management Network (10.80.80.x/24). The IP Firewall in Winbox shows the following message on the rules which include the ovpn-instance:
in/out-interface matcher not possible when interface (ovpn-instance) is slave - use master instead (bridge-mgmt)
Our OpenVPN setup worked perfectly fine BEFORE upgrading to 6.45.1/6.45.2. Any ideas?
This is so fucked up. Every single ROS update introduces new bugs...
Not yet, I don't have externel log server for now.I run DHCP BGP Firewall NAT VLANs SFP+ L2TP (server and clients) UPnP SNMP Scripts Schedulers in most of them and so far not a single issue. Maybe the problem is service specific? Have you tried enabling logging to an external server to catch those logs before rebooting?I run many services on this router, such as OSPF, OpenVPN and etc.
Downgraded to 6.44.5 yesterday, the uptime is 10h until now without any issues.
SFP+ on 4011 broken. Please pull the update. I have had two switches go offline due to this update.
SFP+ on 4011 broken. Please pull the update. I have had two switches go offline due to this update.
Did you do the "Wireless Reset" as mentioned in previous version (6.45.1) change log?
*) rb4011 - fixed MAC address duplication between sfp-sfpplus1 and wlan1 interfaces (wlan1 configuration reset required);
Not really.What happens when some of downloaded packages are broken during download? If you have bundle package - then you have error on bundle installation, and everything is rolled back. AFAIR, when system is already installed and some additional package is broken, it simply does not get installed, so... can't you bring your RouterOS into some "clipped" state without necessary functionality when installing separate packages?Indeed! I think that whole combined package thing should be dropped, and at some time all installations are converted to separate packages during the upgrade to a new version.
Exactly the same here !at 6.45.1, gre tunnels stopped working. Redid all 15 routers on ip tunnels. 3 weeks after the release of 6.45.2, the ip tunnels stopped working ....
Did you check your firewalls allow inbound GRE? If you check the notes there was a fix for a bug that allowed it when it shouldn't've been allowed.Exactly the same here !at 6.45.1, gre tunnels stopped working. Redid all 15 routers on ip tunnels. 3 weeks after the release of 6.45.2, the ip tunnels stopped working ....
Upgraded from 6.42.7 to 6.45.2 on a CCR1036 and all the GRE tunnels stopped working.
Ok I know that the Mikrotik guys can't test everything ...but GRE ? seriously ?? c'mon guys....FIX IT !!!
...and while fixing that one, another one has been introduced which incorrectly labels the initial packet of a GRE connection with connection-state=invalid so you need to workaround this in your firewall if you drop "invalid" packets before all selective accept rules. This has also been discussed earlier in this topic.Did you check your firewalls allow inbound GRE? If you check the notes there was a fix for a bug that allowed it when it shouldn't've been allowed.
Hi...and while fixing that one, another one has been introduced which incorrectly labels the initial packet of a GRE connection with connection-state=invalid so you need to workaround this in your firewall if you drop "invalid" packets before all selective accept rules. This has also been discussed earlier in this topic.Did you check your firewalls allow inbound GRE? If you check the notes there was a fix for a bug that allowed it when it shouldn't've been allowed.
Can someone change remote-peers to active-peers in script listed on this wiki page: Securing L2TP Server for IPSec*) ipsec - renamed "remote-peers" to "active-peers";
Okay, let's then imagine "out of disk space" issue in the middle of installation of Nth package. Linux distros can work with "different" versions of packages, RouterOS can't.Not really.
Step1: Download ALL necessary packages. Use RAM if needed.
Step2: Verify ALL downloaded packages.
Step3: If everything is ok, install packages.
Done. This is how Linux Distros work: they download updates, verify integrity and then install.
This should only happen when something is corrupted. Normally, Linux distributions know beforehand how much extra diskspace is required when installing or updating a package.Okay, let's then imagine "out of disk space" issue in the middle of installation of Nth package. Linux distros can work with "different" versions of packages, RouterOS can't.
"Theoretically" is not always what will happen IRL. Like, gitlab-ce does PostgreSQL backup on package upgrade. Are you sure it calculates backup size before doing it? Are you sure it's even possible?This should only happen when something is corrupted. Normally, Linux distributions know beforehand how much extra diskspace is required when installing or updating a package.
So RouterOS can calculate if the new install will theoretically fit, and not start the upgrade when it does not fit.
I don't think there is such an issue with RouterOS updates. Maybe there is some need of temporary space (e.g. to generate a new config from the old one) but MikroTik engineers should be well aware of it."Theoretically" is not always what will happen IRL. Like, gitlab-ce does PostgreSQL backup on package upgrade. Are you sure it calculates backup size before doing it? Are you sure it's even possible?
Estou mesmo problema . nao achei soluçao aindaI have upgraded hAP lite RB941 and hotspot doesn't work correctly. No internet connections is shown when you select the wireless. With 6.44.3 is working but with 6.45.1 and 6.45.2 and 6.46beta give this issue.
It works only if you go to 192.168.88.1
No problem instead with RB951ui-2hnd
Any one else discovered this issue?
Okay, let's then imagine "out of disk space" issue in the middle of installation of Nth package. Linux distros can work with "different" versions of packages, RouterOS can't.Not really.
Step1: Download ALL necessary packages. Use RAM if needed.
Step2: Verify ALL downloaded packages.
Step3: If everything is ok, install packages.
Done. This is how Linux Distros work: they download updates, verify integrity and then install.
Indeed. Mikrotik you need to update this:IP Sec Scripting update
For those using scripting rules on IPSEC-L2TP the ip ipsec remote-peers has changed in ip ipsec active-peers
Any scripts using L2PT security on that might need to be updated.
You can download via the download page./system package update check-for-updates
channel: stable
installed-version: 6.45.2
latest-version: 6.45.2
status: System is already up to date
The 6.45.3 is not available yet!
I know it, but I would like download via the command line.You can download via the download page./system package update check-for-updates
channel: stable
installed-version: 6.45.2
latest-version: 6.45.2
status: System is already up to date
The 6.45.3 is not available yet!
https://mikrotik.com/download
No problem:I know it, but I would like download via the command line.
Thank You!!! You are GENIUS!!!!No problem:I know it, but I would like download via the command line.
/tool fetch url=("https://download.mikrotik.com/routeros/6.45.3/routeros-".[/system resource get architecture-name]."-6.45.3.npk")
Or you use my script, just copy and paste to your terminal:@CrimzinZA You have 3 things to check
ROS version, MT firmware and modem firmware.
Upgrading modem firmware solved my 4G issues.
Here is how to update modem firmware https://wiki.mikrotik.com/wiki/Manual:I ... re_upgrade
Thank you for the feedback.@CrimzinZA As noted above, make sure the firmware matches (in Winbox, System > Routerboard > Upgrade, then reboot the box). If that doesn't help, you might want to try downgrading to the "long term" release...under System > Packages, you can select the older package. Don't know if it will help, but something to try.
I had this randomly happen. After restarting a few times it sees it again. one issue is that I can see the LTE and the traffic but the unit itself cant connect to the internet although it states its registered and connected. When connected and there is internet it only last for a short while. ( from a few minutes to a day )When I upgraded an LtAP mini (luckily a test machine) to 6.45.1, I lost the LTE interface! When I upgraded to 6.45.2, the LTE interface is back again.
There is nothing in the release/change notes. Anybody else experiencing the same issue?
This will work if you have the main package installed but if you have packages (like devices with limited flash space for example) then this is a big problem and you have to get the full package and then extract and install the packages. This is OK and not such a big issue if you have one or maybe a few mikrotik devices to manage but it is a big problem if you mange a lot of them and each one may be different than the other in architecture as well as packages installed, so please Mikrotik, can you fix this problem?No problem:I know it, but I would like download via the command line.
/tool fetch url=("https://download.mikrotik.com/routeros/6.45.3/routeros-".[/system resource get architecture-name]."-6.45.3.npk")
@emils has explained that in the 6.45.3 topic you've spawned yourself - problems with the release system.One day since 6.45.3 released on download, nothing here on the forum.
Can't remember seeing this behavior before.
I agree it is bad, but on the other hand what is so complicated about adding protocol=!gre to the action=drop connection-state=invalid rule?6.45.3 has no GRE miss-marking fix. Very Bad...
Check Winbox version, it must be at least 3.19my RB750Gr3 with 6.41.5 version. After reboot it must be upgraded. But after that he did not start correctly, i can not seen him in winbox