https://www.welivesecurity.com/2020/08/ ... sdropping/Can we have more information on CVE-2020-3702 and what it is.
More should I patch now or later type of question.
When using Mac Address to login returns error message:ERROR could not connect to 192.168.10.88
ERROR could not connect to XX:xx:XX:32:xx:68
I might be off here but my understanding is that this is a feature in the Linux kernel and version 6 will not upgrade the kernel without major overall I think this will be a V7 feature we have to wait for,MikroTik is there any chance to add wireguard in v6?
You had the same issues with 6.47.2 if I remember correctly? I wonder if this is more for you setup. I have a couple of these switches and I do not have this problem but I run them on Long-Term. I keep all my switches on this release to not have to patch as often.Switch CRS326-24G-2S+
Software upgrade successful from v6.47.2 TO v6.47.3 but after upgrade no longer able to login using Winbox to upgrade the firmware -- showing the following error message:When using Mac Address to login returns error message:ERROR could not connect to 192.168.10.88ERROR could not connect to XX:xx:XX:32:xx:68
This condition started with v6.47.2 and now has carried over to v6.47.3
To resolve I had to remove the power supply and reinsert the power supply after which I was able to upgrade the firmware.
@KindisYou had the same issues with 6.47.2 if I remember correctly? I wonder if this is more for you setup. I have a couple of these switches and I do not have this problem but I run them on Long-Term. I keep all my switches on this release to not have to patch as often.
I know just that I have not heard that many complain and I have not noticed this on any other units running ARM platform, equal or similar to that of CRS326-24G-2s+RM.@KindisYou had the same issues with 6.47.2 if I remember correctly? I wonder if this is more for you setup. I have a couple of these switches and I do not have this problem but I run them on Long-Term. I keep all my switches on this release to not have to patch as often.
If you read my post properly you would have noticed that I stated that this behavior started with v6.47.2 :-)
No problem with v6.47.1 insofar as using Winbox and updating software and Firmware ... issue surfaced with v.6.47.2
Normally for production Switches I would stay with Long-Term but because this is my LAB work where I want to see MikroTik issues I play the upgrade game.
Did you tried that SFP in a other device? It could be read error.
Or did you downgraded to the previous version to see if the SFP worked again?
/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
is it for which WIFI models? High power can damage devices as previously stated by Mikrotik.wireless - allow setting "tx-power" up to 40;
Did you sent a support request to support@mikrotik.com? It takes a while (days) before you get a specific reply.Of course, tried it with two different Mikoritik product and different fw version, everywhere do the same.
In other branded network device (like TPlink, Dahua) works well but no more in Mikrotik.
Three pieces of SFPs was in the device while firware upgrade was running, all of these do the same.
Did you tried that SFP in a other device? It could be read error.
Or did you downgraded to the previous version to see if the SFP worked again?
That is why I always let it go some weeks before I upgrade, and only after testing it on a similar device that has same config and software version.Note to self - never upgrade ROS unless you are on site.
Did you sent a support request to support@mikrotik.com? It takes a while (days) before you get a specific reply.Of course, tried it with two different Mikoritik product and different fw version, everywhere do the same.
In other branded network device (like TPlink, Dahua) works well but no more in Mikrotik.
Three pieces of SFPs was in the device while firware upgrade was running, all of these do the same.
Did you tried that SFP in a other device? It could be read error.
Or did you downgraded to the previous version to see if the SFP worked again?
Wy is this removed? Is it comming in a seperate tool?*) netinstall - removed "Flashfig" from Netinstall;
I'm seeing wireless problems with hAP ac^2 since I upgraded to 7.1beta2 and I wonder if it is the same kind of thing. After some time the devices remain connected but no traffic flows, unless they recognise a not working network and blacklist it. I only can recover with disable/enable on wlan1/2, depending on which one is failing. Usually works for 5 to 20 hours before I notice it is going on again in some or all devices, either or both interfaces.> wireless - fixed potential wireless driver issue related to CVE-2020-3702
Interesting, my years stable hap ac 5g needed a power cycle twice (reboots wouldn't correct it) after 6.47.2 upgrade, now I've upgraded to .3, 2 android devices wont even connect any more.
I'm seeing wireless problems with hAP ac^2 since I upgraded to 7.1beta2 and I wonder if it is the same kind of thing. After some time the devices remain connected but no traffic flows, unless they recognise a not working network and blacklist it. I only can recover with disable/enable on wlan1/2, depending on which one is failing. Usually works for 5 to 20 hours before I notice it is going on again in some or all devices, either or both interfaces.> wireless - fixed potential wireless driver issue related to CVE-2020-3702
Interesting, my years stable hap ac 5g needed a power cycle twice (reboots wouldn't correct it) after 6.47.2 upgrade, now I've upgraded to .3, 2 android devices wont even connect any more.
Enviado desde mi Redmi Note 5 mediante Tapatalk
Samsung Galaxy S8+, I didn't see anything in Log, no disconnections, but it looked like packet loss (like "DNS error" -> then in 2 seconds a page opens successfully; or cannot connect via MikroTik App to the router, 2-3 attempts later - it connects successfully).Anyone experiencing wifi issues with this release, could you please specify which exact devices are having connectivity issues? Please check the logs and find out the reason why the device is disconnected.
I am expierincing Wi-Fi issues on a hap ac^2 on default wireless settings. Had no issues until 6.47.3. There are no tx/rx errors or any weird entries in the logs as far as I can tell.Anyone experiencing wifi issues with this release, could you please specify which exact devices are having connectivity issues? Please check the logs and find out the reason why the device is disconnected.
Have you tried to restart the device again and see if it works?I've Winbox 3.27 on Wine (ubuntu) and I can't log in to any device after upgrading them to 6.47.3. It stays at "Logging in" and nothing is happening.
Of course, devices are accessible by in.ex. SSH but winbox is missing. From windows I still can log in. Trying older winbox didn't work.
Strange thing is that if I don't upgrade device, in.ex. from 6.47.2 to 6.47.3 I can log in by winbox (wine - ubuntu).
If I upgrade device to 6.47.3, I can't log in from ubuntu anymore.
No, you can't. Chateau requires ROS v7.x and can't be downgraded to 6.x.Obvious questions perhaps: a) but should I downgrade? and b) if the consensus is yes, can some share a link instructions on the simplest way give Winbox won't let you
Hopefully next release. Too bad this was ignored. Security researcher reported the issue in time.Update on this CVE-2020-11881