Please include the relevant CVE number for fixes like this, so we can independently evaluate the urgency of an upgrade.*) smb - fixed file path validation (introduced in v6.46);
*) www - improved WWW service stability when receiving bogus packets;
At the moment, the download has dropped. But I would like to know what it was, if there is any information.Are you guys serious? The second update, in the last couple of months, with problems you don't expect at all. One core is constantly 100% loaded with something incomprehensible.
Can someone enlighten me about this one? I have 3 of these and one of them run channel ch54-5270 and this works and this is within U-NII-2 or I'm I just plain stupid after the vacation as my brain has yet to start working, which is most likely the case :)*) wireless - added support for U-NII-2 for cAP ac;
What issues?I don't see any fixes for the w60g reliability issues introduced with v6.47 Any word on that?
Constant disconnects. See for example:What issues?I don't see any fixes for the w60g reliability issues introduced with v6.47 Any word on that?
Are you guys serious? The second update, in the last couple of months, with problems you don't expect at all. One core is constantly 100% loaded with something incomprehensible.
well, likely some script/task which has to run after startup. E.g. scheduled script downloading firewall rules? BGP with large table? etc...At the moment, the download has dropped. But I would like to know what it was, if there is any information.Are you guys serious? The second update, in the last couple of months, with problems you don't expect at all. One core is constantly 100% loaded with something incomprehensible.
/tool fetch upload=yes url="sftp://server/path/file" user=example password=example src-path=file src-address=ip
failure: only http[s]/sftp supports src-address
open image link ohne "t" (thumbnail)i can't properly see your picture, can you make bigger for usAre you guys serious? The second update, in the last couple of months, with problems you don't expect at all. One core is constantly 100% loaded with something incomprehensible.
https://c.radikal.ru/c39/2008/2c/6e9b16a53516t.jpg
Full image: https://c.radikal.ru/c39/2008/2c/6e9b16a53516.jpg
Thats a ~18 Euro hardware, dont expect much from such a device...hAP Lite - not enough space for upgrade
That may apply for other manufacturers but not for Mikrotik. It is expected that software release will work on every supported device, no matter the price.Thats a ~18 Euro hardware, dont expect much from such a device...hAP Lite - not enough space for upgrade
need more info about this..can anyone add somethingHi,
I am sorry but I am still having the same problem on this point :
*) l2tp - fixed multiple tunnel establishment from the same remote IP address (introduced in v6.47); any advice ?
need more info about this..can anyone add somethingHi,
I am sorry but I am still having the same problem on this point :
*) l2tp - fixed multiple tunnel establishment from the same remote IP address (introduced in v6.47); any advice ?
Downgrade to an older smaller version like 6.44, then upgrade to latest. PS this may give problem with your current configuration.hAP Lite - not enough space for upgrade
I think your test is not OK because this issue is very common and reported everywhere.ErfanDL, vecernik87 - hAP lite and other SMIPS architecture devices are tested on every release and can be upgraded while running default configuration.
@strodsmozerd - What is the error that you receive? Can you access the router over the MAC connection?
Agreed, maybe MT can make v7 lite and v7 full builldsMaybe some users use them to build a toy lab, but usually they will be running only system and wireless, maybe advanced-tools.
But MPLS, BGP, OSPF, IPsec, Hotspot... REALLY?
The same could be done with 6.47. Make the "combined" package (a thing that IMHO never should have been made in the first place...) include onlyAgreed, maybe MT can make v7 lite and v7 full builldsMaybe some users use them to build a toy lab, but usually they will be running only system and wireless, maybe advanced-tools.
But MPLS, BGP, OSPF, IPsec, Hotspot... REALLY?
I fully agree with that! The router also should have a selection menu where you can select additional packages to be downloaded from the upgrade server, instead of first having to download an all-packages .zip (carefully watching the architecture and version), extracting the wanted package from there, and upload it to the router. The router already knows how to download those packages, the only thing that it could require is an URL at the download server that serves a list of available packages. Cannot be too hard.I have been uselessly asking mikrotik to stop using the combined package and put only the essential packages directly into the routers during the manufacturing process for many years. They had never heard me.
$DownloadPackage wireless
I think the system->packages menu should list all available packages, also those not installed, and then allow to download+install them with an install button similar to the "enable/disable/uninstall" buttons.No, it is not too hard. My scripts collection (see signature) has a function for that. Just run...
Code: Select all$DownloadPackage wireless
Many people in poor countries use hAP lite.I think your test is not OK because this issue is very common and reported everywhere.ErfanDL, vecernik87 - hAP lite and other SMIPS architecture devices are tested on every release and can be upgraded while running default configuration.
It probably is not caused by files stored on the flash, but by use of the RAM memory which is required for storage of the update files. Not enough RAM can be made available for that and the upgrade fails in the downloading phase.
Maybe you would need to throw the towel and make the SMIPS devices a separate class that does not support all the features.
Maybe some users use them to build a toy lab, but usually they will be running only system and wireless, maybe advanced-tools.
But MPLS, BGP, OSPF, IPsec, Hotspot... REALLY?
[admin@MT] > int ipipv6 print detail
Flags: X - disabled, R - running
0 R name="v6tun" mtu=auto actual-mtu=1440 local-address=::
remote-address=xxxxxxxxxxx.sn.mynetname.net
current-remote-address=240e:3a1:1234:5678::1
dscp=inherit clamp-tcp-mss=yes
It is easy to create a PPP profile for your PPPoE client and add some scripts to it, to handle this (and other) small problems resulting from down/up state changes!An ipipv6 tunnel problem in 6.47.2. When pppoe client disconnect and then reconnect, ipv6 address of device is changed , but local address of ipipv6 tunnel is not changed (ipv6 firewall connection print), and the tunnel is down actually.
I didn't configure "local-address" value. I think it should be changed automatically. Please fix it.
:if ($bound=1) do={
:local pdns [/ip dhcp-client get value-name=primary-dns [find interface=$"interface"]]
:local sdns [/ip dhcp-client get value-name=secondary-dns [find interface=$"interface"]]
/ip route add gateway=$"gateway-address" dst-addres=$"pdns" comment="Route to DNS"
/ip route add gateway=$"gateway-address" dst-addres=$"sdns" comment="Route to DNS"
} else {
/ip route remove [find comment="Route to DNS"]
}
Code: Select all:if ($bound=1) do={ :local pdns [/ip dhcp-client get value-name=primary-dns [find interface=ether2]] :local sdns [/ip dhcp-client get value-name=secondary-dns [find interface=ether2]] /ip route add gateway=$"gateway-address" dst-addres=$"pdns" comment="Route to DNS" /ip route add gateway=$"gateway-address" dst-addres=$"sdns" comment="Route to DNS" } else { /ip route remove [find comment="Route to DNS"] }
Maybe you should wait a bit longer after reboot for system to finish upgrade ...I have a hap ac which was running on 6.47.1. I upgraded to 6.47.2 and it went well, then on reboot I upgraded the firmware too. But on reboot I couldn't login using winbox. The system was not responding to reset for 4 attempts. On the fifth time it got reset and I could login using winbox. What did I do wrong? Do I need to reset the device before updating? What is the best practice for upgrading routeros?
That sounds like too much hustle for most users ... seems to me that for most people making main package for SMIPS smaller without unnecessary features would solve upgrade issues, and for those who need something more extra packages are always available to play with ...Many people in poor countries use hAP lite.
They usually do not have the ability to buy better equipment.
Features like IPsec and hotspot are essential for them.
All you have to do is back up your settings before upgrading and reset the router to default configuration, then upgrade router and then restore your backup.
I've tried that PPP profile scripts , disable and enable tunnel do not handle the problem of "local-address" which remained old value before down/up state changed !It is easy to create a PPP profile for your PPPoE client and add some scripts to it, to handle this (and other) small problems resulting from down/up state changes!An ipipv6 tunnel problem in 6.47.2. When pppoe client disconnect and then reconnect, ipv6 address of device is changed , but local address of ipipv6 tunnel is not changed (ipv6 firewall connection print), and the tunnel is down actually.
I didn't configure "local-address" value. I think it should be changed automatically. Please fix it.
Just disable your ipipv6 tunnel in the down script and enable it again in the up script.
There is no problem restoring the backup to the new version.Even poor admins should not restore backup on other device or version that differs from where it was made.
This seems to me that you are all arguing due to simple jargon confusion.There is no problem restoring the backup to the new version.Even poor admins should not restore backup on other device or version that differs from where it was made.All you have to do is back up your settings before upgrading and reset the router to default configuration, then upgrade router and then restore your backup.
/system backup
/export
Yeah, you need to use some temporary variable with different name: https://wiki.mikrotik.com/wiki/Manual:S ... able_nameshi,
i have following dhcp client script, that's not working until i replace $interface variable with real interface name. according to wiki interface variable should be known for dhcp client script - https://wiki.mikrotik.com/wiki/Manual:I ... Properties
please check.
The "stable" stack has a very misleading name. It is an advanced version that is only used when you really need the new features. Otherwise stick with the "long term" stack, that is the most stable set. Or rely on your own validation. E.g. 6.45.6 is a very stable version in the stable stack for me.Very bad! I have hAP ac, after updating to version 6.47.2 I can no longer connect to the 5GHz network, only the 2.4GHz network is available, although the 5GHz module in the router settings has the status "running". I would never recommend MikroTik products because the software is very unstable!
I checked the problem, and found that the 5GHz network appears only 10 minutes after restarting the router, if the 5GHz network is unavailable, it has the status "radar detected". But the fact is that before updating to version 6.47.2, this problem never it was, the 5GHz network always appeared immediately after restarting the router.The "stable" stack has a very misleading name. It is an advanced version that is only used when you really need the new features. Otherwise stick with the "long term" stack, that is the most stable set. Or rely on your own validation. E.g. 6.45.6 is a very stable version in the stable stack for me.Very bad! I have hAP ac, after updating to version 6.47.2 I can no longer connect to the 5GHz network, only the 2.4GHz network is available, although the 5GHz module in the router settings has the status "running". I would never recommend MikroTik products because the software is very unstable!
You are also in the 5 GHz world. There are some pitfalls, like the mandatory 1 minute or even 10 minutes radar test period for DFS frequencies. 5 GHz will be totally dead for that time, with interface enabled.. This is not Mikrotik specific, but a mandatory requirement for all wifi equipment sold.
I downgraded the firmware to version 6.45.9 and the problem is solved! Now the 5GHz network is available immediately after starting the router. The problem was 100% in the new version 6.47.2. I will never update to a new version again!Very bad! I have hAP ac, after updating to version 6.47.2 I can no longer connect to the 5GHz network, only the 2.4GHz network is available, although the 5GHz module in the router settings has the status "running". I would never recommend MikroTik products because the software is very unstable!
Did you try to setup the config from scratch, or did you just upgrade and it stopped working.I will never update to a new version again!
Yes. Without config we can only guess. But it's most probably a config that just allows random behavior.you need to manually configure it to get it working.
Not sure of you tried changing your wireless settings so it does not scan the radar band or not. There is a setting that will hold it for 10 min to find a clear frequency..or..you could just skip that band and not wait at all.I downgraded the firmware to version 6.45.9 and the problem is solved! Now the 5GHz network is available immediately after starting the router. The problem was 100% in the new version 6.47.2. I will never update to a new version again!Very bad! I have hAP ac, after updating to version 6.47.2 I can no longer connect to the 5GHz network, only the 2.4GHz network is available, although the 5GHz module in the router settings has the status "running". I would never recommend MikroTik products because the software is very unstable!
That likely means your router is in violation of legislation relevant to the DFS and you may receive fine if your local authorities find you. The old firmware probably did not follow DFS specs correctly (or maybe they were updated?).I downgraded the firmware to version 6.45.9 and the problem is solved! Now the 5GHz network is available immediately after starting the router. The problem was 100% in the new version 6.47.2. I will never update to a new version again!Very bad! I have hAP ac, after updating to version 6.47.2 I can no longer connect to the 5GHz network, only the 2.4GHz network is available, although the 5GHz module in the router settings has the status "running". I would never recommend MikroTik products because the software is very unstable!
I have heaps of these around and I am not aware of any trouble introduced in 6.47.2 so I don't understand what would prevent you from upgrading.I am at the version 6.47.1 right now and i can't afford to update to 6.47.2 because of some issues. Maybe the issue still exist in 6.47.2
Device: Mikrotik Hap Ac2
The "problem" is exactly this; MIkrotiks and many other vendors have never properly been in legal compliance with the way DFS-reqired channels (Dynamic Frequency Selection required, the entirety of UNII-2 in the US) is required to be handled.You are also in the 5 GHz world. There are some pitfalls, like the mandatory 1 minute or even 10 minutes radar test period for DFS frequencies. 5 GHz will be totally dead for that time, with interface enabled.. This is not Mikrotik specific, but a mandatory requirement for all wifi equipment sold.
The first setting of my router was two years ago, the problem was discovered after updating to 6.47.2Did you try to setup the config from scratch, or did you just upgrade and it stopped working.I will never update to a new version again!
I have seen some stuff changes when upgrade so you need to manually configure it to get it working.
If 5 GHz did stops working for every one, 6.47.2 would be removed quick.
Works fine fro me.
No, I have always the latest (stable) version, I did not skip new updates. The problem appeared only after updating to firmware 6.47.2@trancenet and other regarding 5Ghz DFS legal compliance. This has nothing to do with 6.47.2 It was change several version back, so trancenet did only see this because he skipped many upgrade.
Probably the problem is related to DFS in the new version 6.47.2, but there were no problems with the previous version. My router not violation of legislation, since the region of the wireless network is set according to my country, I do not use another region;That likely means your router is in violation of legislation relevant to the DFS and you may receive fine if your local authorities find you. The old firmware probably did not follow DFS specs correctly (or maybe they were updated?).I downgraded the firmware to version 6.45.9 and the problem is solved! Now the 5GHz network is available immediately after starting the router. The problem was 100% in the new version 6.47.2. I will never update to a new version again!Very bad! I have hAP ac, after updating to version 6.47.2 I can no longer connect to the 5GHz network, only the 2.4GHz network is available, although the 5GHz module in the router settings has the status "running". I would never recommend MikroTik products because the software is very unstable!
There are plenty of non-DFS channels in 5GHz band, so pick your favourite and you won't have to wait even with the new firmware.
You have not even tested the previous version! You compare it with an older version, from before things changed in the DFS handling.Probably the problem is related to DFS in the new version 6.47.2, but there were no problems with the previous version.
Since you did write that you downgraded to 6.45.9 and did not write what version you did upgrade from, it seems that you completely skipped the 6.46 stabel tree??No, I have always the latest (stable) version, I did not skip new updates. The problem appeared only after updating to firmware 6.47.2@trancenet and other regarding 5Ghz DFS legal compliance. This has nothing to do with 6.47.2 It was change several version back, so trancenet did only see this because he skipped many upgrade.
Read my previous posts again. Before updating to 6.47.2, I had version 6.47.1 installed, there were no problems. The problem appeared immediately after updating to version 6.47.2! For the test, I downgraded back to the latest "long term" version in the router update settings, this decision was adopted after the recommendation to use "long term" firmware, which are stable. Although I'm sure there will be no problems the same on 6.47.1.Since you did write that you downgraded to 6.45.9 and did not write what version you did upgrade from, it seems that you completely skipped the 6.46 stabel tree??No, I have always the latest (stable) version, I did not skip new updates. The problem appeared only after updating to firmware 6.47.2@trancenet and other regarding 5Ghz DFS legal compliance. This has nothing to do with 6.47.2 It was change several version back, so trancenet did only see this because he skipped many upgrade.
https://mikrotik.com/download/changelogs
Please, read my previous posts again. Before updating to 6.47.2, used version 6.47.1, there were no problems. The problem appeared immediately after updating to version 6.47.2! For the test, I downgraded back to the latest "long term" version in the router update settings, this decision was adopted after recommendation to use "long term" firmware, which are stable. Although I'm sure there will be no problems the same on 6.47.1.Since you did write that you downgraded to 6.45.9 and did not write what version you did upgrade from, it seems that you completely skipped the 6.46 stabel tree??No, I have always the latest (stable) version, I did not skip new updates. The problem appeared only after updating to firmware 6.47.2@trancenet and other regarding 5Ghz DFS legal compliance. This has nothing to do with 6.47.2 It was change several version back, so trancenet did only see this because he skipped many upgrade.
https://mikrotik.com/download/changelogs
Yeah i also think that it was just a statistical error more like winbox bug i guess. I just updated mine to 6.47.2. Seems to be better than 6.47.1That likely means your router is in violation of legislation relevant to the DFS and you may receive fine if your local authorities find you. The old firmware probably did not follow DFS specs correctly (or maybe they were updated?).I downgraded the firmware to version 6.45.9 and the problem is solved! Now the 5GHz network is available immediately after starting the router. The problem was 100% in the new version 6.47.2. I will never update to a new version again!Very bad! I have hAP ac, after updating to version 6.47.2 I can no longer connect to the 5GHz network, only the 2.4GHz network is available, although the 5GHz module in the router settings has the status "running". I would never recommend MikroTik products because the software is very unstable!
There are plenty of non-DFS channels in 5GHz band, so pick your favourite and you won't have to wait even with the new firmware.
I have heaps of these around and I am not aware of any trouble introduced in 6.47.2 so I don't understand what would prevent you from upgrading.I am at the version 6.47.1 right now and i can't afford to update to 6.47.2 because of some issues. Maybe the issue still exist in 6.47.2
Device: Mikrotik Hap Ac2
Also, I don't suffer from any issue with CPU spike as you described. As long as the CPU is within few %, you can't possibly call it "spike", merely a statistical error - nothing worth of worrying about.
You mean, the green graph in the top right corner of WinBox? It's WinBox network traffic, not CPU load or anything else.Do anyone experience opening the address-list in Winbox causes the cpu to get loaded? I mean the green graph keeps spiking per second and the cpu stucks at 1%-2% without throughput load. Even turning off all entries in address-list it still happens also turning off all my firewall and mangle rules. I am at the version 6.47.1 right now and i can't afford to update to 6.47.2 because of some issues. Maybe the issue still exist in 6.47.2
The CPU graphic box always to the max and that is the case as long I know Miktrotik.You mean, the green graph in the top right corner of WinBox? It's WinBox network traffic, not CPU load or anything else.Do anyone experience opening the address-list in Winbox causes the cpu to get loaded? I mean the green graph keeps spiking per second and the cpu stucks at 1%-2% without throughput load. Even turning off all entries in address-list it still happens also turning off all my firewall and mangle rules. I am at the version 6.47.1 right now and i can't afford to update to 6.47.2 because of some issues. Maybe the issue still exist in 6.47.2
That was more than a decade ago and that it is a long time.It's still not about CPU: viewtopic.php?f=2&t=27814&p=134483#p134483
But current manual tells the same: https://wiki.mikrotik.com/wiki/Manual:W ... e_OverviewThat was more than a decade ago and that it is a long time.It's still not about CPU: viewtopic.php?f=2&t=27814&p=134483#p134483
This is the most amazing thing I read lately :) .It's still not about CPU: viewtopic.php?f=2&t=27814&p=134483#p134483