RouterOS v7 is currently in early alpha and there is no scheduled release date yet.
Until than I'll sit on my chair and wait while clicking refresh button on mikrotik download pageRouterOS v7 is currently in early alpha and there is no scheduled release date yet.
My Samsung-TV also works with disabled security.who are having issues with legacy client on new wireless packages
For test purposes please disable any wireless security profiles, and see if it improves situation.
It is what I am doing already since a while!Until then I'll sit on my chair and wait while clicking refresh button on mikrotik download pageRouterOS v7 is currently in early alpha and there is no scheduled release date yet.
Nope, it's not really fixed. nfacctd spews out tons of notices about wrong flows received.Also I gave IPFIX a try on x86 and seems to be working properly now. Bugs mentioned here seem to have been fixed.
I'll test it more extensively when time allows for it
INFO: expecting flow '16' but received '2' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '17' but received '3' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '18' but received '4' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '19' but received '5' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '20' but received '6' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '21' but received '7' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '22' but received '8' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '23' but received '9' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '24' but received '10' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '25' but received '11' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '26' but received '12' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '27' but received '13' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '28' but received '14' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '29' but received '15' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '30' but received '16' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '31' but received '17' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '32' but received '18' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '33' but received '19' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '34' but received '20' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '35' but received '21' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '36' but received '22' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '37' but received '23' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '38' but received '24' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '39' but received '25' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '40' but received '26' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '41' but received '27' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '42' but received '28' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '43' but received '29' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '44' but received '30' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '45' but received '31' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '46' but received '32' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '47' but received '33' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '48' but received '34' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '49' but received '35' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '50' but received '36' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '51' but received '37' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '52' but received '38' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '53' but received '39' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '54' but received '40' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '55' but received '41' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '56' but received '42' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '57' but received '43' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '58' but received '44' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '59' but received '45' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '60' but received '46' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '61' but received '47' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '62' but received '48' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '63' but received '60' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '60' but received '95' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '110' but received '99' collector=0.0.0.0:2055 agent=X.X.X.X:0
INFO: expecting flow '114' but received '100' collector=0.0.0.0:2055 agent=X.X.X.X:0
> /log print
jan/01/1970 03:00:12 system,info disabled wireless@-6.37
18:54:35 system,info router rebooted
Hello Normis!Since DFC is required by law, I suggest to be careful with your enterprise setup and follow the regulations.Hello Folks!
We have been running an wireless enterprise environment for many years, we had to fully stop the update of all our devices since it has been announced that DFS mode has been put on based on which country you set.
But how can I see if DFS is activated on my devices which I tested to upgrade ?
After further testing, by updating pmacct/nfacct to the latest version I don't get any notices any more.Nope, it's not really fixed. nfacctd spews out tons of notices about wrong flows received.Also I gave IPFIX a try on x86 and seems to be working properly now. Bugs mentioned here seem to have been fixed.
I'll test it more extensively when time allows for it
I upgraded a wireless link yesterday that had been running DFS on 6.36.3 to 6.37 and it stayed in "Detecting Radar" Status. I had to use Superchannel to manually set it. Under 6.36.3 the DFS picked a channel, waited a while to see if radar was present then went into operational mode.Hello Normis!Since DFC is required by law, I suggest to be careful with your enterprise setup and follow the regulations.Hello Folks!
We have been running an wireless enterprise environment for many years, we had to fully stop the update of all our devices since it has been announced that DFS mode has been put on based on which country you set.
But how can I see if DFS is activated on my devices which I tested to upgrade ?
I understand that, we have been running this successfully for nearly 8 years now, but before I even think on upgrade the relatively big wireless infrastructure and network I would in some way understand how this can impact us. If network becomes totally unstable and useless, so will our business so to say.
Till someone can tell me this, all production units will stay on the level they are today.
Anyone out there who can tell their experience by enabling DFS ?
thats sounds quite good plan/strategy.Until than I'll sit on my chair and wait while clicking refresh button on mikrotik download page
Done. We can reproduce it everytime. Check support@mikrotik.com e-mail. Ticket number 2016092822000398.Everyone who did lose wireless package or sees it as disabled after upgrade - can you please write to support@mikrotik.com and provide precise steps which you executed to reach such situation. From which version did you upgrade? What kinds of packages precisely were installed on device? How did you upgrade (with check-for-updates, with manual file upload)?
We are testing all kinds of packages and upgrade combinations and are not being able to reproduce such situation. Any information would be very helpful.
Fix Ticket#2014122166000217, for example. It's very annoynig bug (ROS lost packets when add or remove any type interface). Support promises fix it in v7.What is so spacial in v7?i herad that they are working on version 7.is that all?
Nice job. Almost feels like you are near to a final version of v6....
and version 7 isn't a joke.
thats what Mr. Janis said in USA's MuM in april 2016.
i am wondering what are they trying to create.
RouterOS v7 will have a new linux kernel, which will allow for more hardware support, and some features and fixes that were not possible before.
RouterOS v7 is currently in early alpha and there is no scheduled release date yet.
I am not sure, but from that ticket it seems that any issues were fixed, and you received some advice how to improve your setup. The support agent said that other systems work with such number of users.RouterOS v7 will have a new linux kernel, which will allow for more hardware support, and some features and fixes that were not possible before.
RouterOS v7 is currently in early alpha and there is no scheduled release date yet.
Ticket#2014122166000217
Normis, issue not fixed (I can create new video with demonstration in any time. Need?).I am not sure, but from that ticket it seems that any issues were fixed, and you received some advice how to improve your setup. The support agent said that other systems work with such number of users.RouterOS v7 will have a new linux kernel, which will allow for more hardware support, and some features and fixes that were not possible before.
RouterOS v7 is currently in early alpha and there is no scheduled release date yet.
Ticket#2014122166000217
How can I see if DFS is used and how it operates ?I upgraded a wireless link yesterday that had been running DFS on 6.36.3 to 6.37 and it stayed in "Detecting Radar" Status. I had to use Superchannel to manually set it. Under 6.36.3 the DFS picked a channel, waited a while to see if radar was present then went into operational mode.Hello Normis!Since DFC is required by law, I suggest to be careful with your enterprise setup and follow the regulations.Hello Folks!
We have been running an wireless enterprise environment for many years, we had to fully stop the update of all our devices since it has been announced that DFS mode has been put on based on which country you set.
But how can I see if DFS is activated on my devices which I tested to upgrade ?
I understand that, we have been running this successfully for nearly 8 years now, but before I even think on upgrade the relatively big wireless infrastructure and network I would in some way understand how this can impact us. If network becomes totally unstable and useless, so will our business so to say.
Till someone can tell me this, all production units will stay on the level they are today.
Anyone out there who can tell their experience by enabling DFS ?
On sites using DFS we set the scan range from "default" to "5500-5680" which is the range that requires DFS. Failing to do this had our links coming up all over the spectrum from 5180 - 5825 even though we started at 5500.
The problem is that this does not work very well. This does not appear to be MikroTik-specific, we had issues with TranZeoIt ignores other 802.11 devices, there are patterns how it can detect it is a radar, not a wifi device.
Hello Normis!Since DFC is required by law, I suggest to be careful with your enterprise setup and follow the regulations.Hello Folks!
We have been running an wireless enterprise environment for many years, we had to fully stop the update of all our devices since it has been announced that DFS mode has been put on based on which country you set.
But how can I see if DFS is activated on my devices which I tested to upgrade ?
[admin@MikroTik] > interface wireless info country-info
country: sweden
ranges: 2402-2482/b,g,gn20,gn40(20dBm)
2417-2457/g-turbo(20dBm)
5170-5250/a,an20,an40,ac20,ac40,ac80,ac160(20dBm)/passive,indoor
5250-5330/a,an20,an40,ac20,ac40,ac80,ac160(23dBm)/dfs,passive
5490-5710/a,an20,an40,ac20,ac40,ac80,ac160(27dBm)/dfs,passive
5190-5310/a-turbo(20dBm)/dfs
5180-5300/a-turbo(20dBm)/dfs
5520-5680/a-turbo(27dBm)/dfs,passive
5510-5670/a-turbo(27dBm)/dfs,passive
902-927/b,g,g-turbo,gn20,gn40(30dB
[admin@MikroTik] > interface wireless info country-info "etsi 5.7-5.8 srd"
ranges: 5725-5875/a,an20,an40,ac20,ac40,ac80,ac160(14dBm)/outdoor
Everyone who did lose wireless package or sees it as disabled after upgrade - can you please write to support@mikrotik.com and provide precise steps which you executed to reach such situation. From which version did you upgrade? What kinds of packages precisely were installed on device? How did you upgrade (with check-for-updates, with manual file upload)?
We are testing all kinds of packages and upgrade combinations and are not being able to reproduce such situation. Any information would be very helpful.
Yeap, same here.My upgrade went well but the problem I have is that I can not disable wireless package, that is I can flag it for disablement but after reboot it is enabled again.
Everyone who did lose wireless package or sees it as disabled after upgrade - can you please write to support@mikrotik.com and provide precise steps which you executed to reach such situation. From which version did you upgrade? What kinds of packages precisely were installed on device? How did you upgrade (with check-for-updates, with manual file upload)?
We are testing all kinds of packages and upgrade combinations and are not being able to reproduce such situation. Any information would be very helpful.
Looks ok, except that you have DFS on:You can see which frequencies are coded in the driver with this command:
We keep the settings up to date.Code: Select all[admin@MikroTik] > interface wireless info country-info country: sweden ranges: 2402-2482/b,g,gn20,gn40(20dBm) 2417-2457/g-turbo(20dBm) 5170-5250/a,an20,an40,ac20,ac40,ac80,ac160(20dBm)/passive,indoor 5250-5330/a,an20,an40,ac20,ac40,ac80,ac160(23dBm)/dfs,passive 5490-5710/a,an20,an40,ac20,ac40,ac80,ac160(27dBm)/dfs,passive 5190-5310/a-turbo(20dBm)/dfs 5180-5300/a-turbo(20dBm)/dfs 5520-5680/a-turbo(27dBm)/dfs,passive 5510-5670/a-turbo(27dBm)/dfs,passive 902-927/b,g,g-turbo,gn20,gn40(30dB
edit: for short range devices (srd), in EU, you can use this country legally:
edit2: we use 27 instead of 30dbm, because RouterOS does not support TPCCode: Select all[admin@MikroTik] > interface wireless info country-info "etsi 5.7-5.8 srd" ranges: 5725-5875/a,an20,an40,ac20,ac40,ac80,ac160(14dBm)/outdoor
O - thank god for your post re superchannelWe always continue to improve the wireless driver, and since DFS is now mandatory, we will of course dedicate more time to improve it as well.
Keep reporting any issues you see and send them to support@mikrotik.com
As a workaround, you can use a different country setting or superchannel mode to go back to no-dfs, but I recommend not doing this in certain countries.
Looks like you found a bug. Thanks! The info command apparently hides some stuff for no reason. It still operates correctly though. Will fix.I do not get same result as you when checking for DFS:
We can't reproduce this problem. Tell us exactly what command you execute and what you see in the console and winbox.Bug: extension channel eeCe and eCee are reversed on winbox wireless/channels (or are reversed on terminal???)
Links missing, not files. And Changelog missing too.Files in download archive now missing. http://www.mikrotik.com/download/archive
Why?
I think it is normal that in this case you use 1 physical and 3 virtual APs for the 4 networks you want to run.With 6.37 I am unable to set up a wlan interface without SSID; i get error "failure: ssid must be specified for AP mode". Indeed i have no SSID on the real wlan interface, i got 4 virtual APs. Is it normal behaviour?
When using 5600-5650MHz, ETSI requires to search for 10 minutes, this is in the regulations. You should use some other frequency, or modify your scan list to avoid the most common radar frequency range (this one).After upgrade to 6.37 with DFS, when I change frekvency --> then is AP with fixed frekvency (5620Mhz) 10minutes detecting radar (without clients) and after 10minutes is runnig AP. It is normal?
Hello Folks!When using 5600-5650MHz, ETSI requires to search for 10 minutes, this is in the regulations. You should use some other frequency, or modify your scan list to avoid the most common radar frequency range (this one).After upgrade to 6.37 with DFS, when I change frekvency --> then is AP with fixed frekvency (5620Mhz) 10minutes detecting radar (without clients) and after 10minutes is runnig AP. It is normal?
Are they configured to use the 5650MHz radar frequency? Are they even allowed to do that?How come that my LINKSYS WRT1900ACS Dual Band router neither ASUS RT-AC5300 nor does D-Link DWL-8600AP Unified Wireless N Dual Band PoE AP or Cisco Aironet 1852E have a 10 minute delay before starting ? They all are available after device has booted, thats say within 2-3 minutes as most worse.
These are all indoor units that will probably operate by default on the low channels where DFS is not required, and can investigate the radar situation later.How come that my LINKSYS WRT1900ACS Dual Band router neither ASUS RT-AC5300 nor does D-Link DWL-8600AP Unified Wireless N Dual Band PoE AP or Cisco Aironet 1852E have a 10 minute delay before starting ? They all are available after device has booted, thats say within 2-3 minutes as most worse.
Well this is not funny at all, i have hundreds of AP with that kind of configuration, i'll have to update them manually (delete virtual AP, configure wlan, change bridge) ?I think it is normal that in this case you use 1 physical and 3 virtual APs for the 4 networks you want to run.With 6.37 I am unable to set up a wlan interface without SSID; i get error "failure: ssid must be specified for AP mode". Indeed i have no SSID on the real wlan interface, i got 4 virtual APs. Is it normal behaviour?
I will get back to you on this, will investigate.Also note that ETSI specifies those radar checks to happen at "installation or re-installation" time, not at boot time. So an AP is allowed to store the
results in nonvolatile memory and use them after boot, maybe conditional on a time-of-last-operation timestamp.
(so it re-checks the frequency when it detects that it has been booted after a longish period of no operation)
Because This routers/ap are for indoor use as pe1chl wrote. I was also confused about that, Lots of people are baying tons of wireless equipment that don't support DFC, I find 2.4Ghz routers (US standard) with max eirp 1W but max allowed in EU is 200mW, this is what our Telecom is doing they are giving tomson routers (for free) with 1W output power. My local authority told me at my home I can use 5Ghz frequency without DFC at max output power that device support, and there is no law that can stop me.Hello Folks!When using 5600-5650MHz, ETSI requires to search for 10 minutes, this is in the regulations. You should use some other frequency, or modify your scan list to avoid the most common radar frequency range (this one).After upgrade to 6.37 with DFS, when I change frekvency --> then is AP with fixed frekvency (5620Mhz) 10minutes detecting radar (without clients) and after 10minutes is runnig AP. It is normal?
How come that my LINKSYS WRT1900ACS Dual Band router neither ASUS RT-AC5300 nor does D-Link DWL-8600AP Unified Wireless N Dual Band PoE AP or Cisco Aironet 1852E have a 10 minute delay before starting ? They all are available after device has booted, thats say within 2-3 minutes as most worse.
Something is wrong with wireless package. It disconnects more frequently from AP that previous wireless-cm2. The best wireless was at MT5.x !
I have exactly the same problem from v 6.36.3. My routerboard is hex lite.Hmmm,
Upgraded my main router to 6.37. Port forwarding didn't work somehow. The firewall counters do go up, but servers are not reachable form the outside (conntrack issue? forward rules?). VPN servers and tunnels work fine... Reverting to 6.34.6 and everything is back to normal.
I had no time to investigate further since I am in a remote location and don't want to risk a lockout.
I have exactly the same issue with a 912UAG-5HPnD , after I upgrading to V6.37 from V6.36 two disabled wireless packages one is V6.19, on downgrading to 6.36 wireless is functional again and V6.19 wireless package is goneI just had a really strange problem with the upgrade from 6.36 to 6.37
When I did the upgrade (using the Mikrotik check-for-upgrade via winbox), the Mikrotik (RB435G) did the upgrade to 6.37
however in Winbox, there was no Wireless section
In packages there were two wireless packages, one was 6.37 and the other was 6.20 - both were disabled
I could not in-install either package.
I then downgraded back to 6.36 and the Wireless selection in Winbox came back and there was only one wireless package.
I then upgraded to 6.37 again and again I had the exact same problem. Downgrading back to 6.36 again made everything correct again.
I repeated this process two more times and had the exact same problems again.
Sooo I am stuck with a Mikrotik running 6.36 than can not upgrade to 6.37 - really strange.
I am afraid to keep playing with it because this is an ip/audio link to a remote FM radio station (88.3 KWIS FM) we operate.
I am confused on where the 6.20 wireless package keeps coming from every time I upgrade to 6.37
It is not in the files I see prior to upgrade from 6.36 to 6.37
In the last few days - I upgraded hundreds of Mikrotiks from 6.36 to 6.37 and only ran into this problem on one Mikrotik this morning
Any ideas ? Anybody else experienced this ?
North Idaho Tom Jones
It makes me wonder if there could be an old left over mikrotik filesystem that might be invisible or somehow not in the directory.I have exactly the same issue with a 912UAG-5HPnD , after I upgrading to V6.37 from V6.36 two disabled wireless packages one is V6.19, on downgrading to 6.36 wireless is functional again and V6.19 wireless package is goneI just had a really strange problem with the upgrade from 6.36 to 6.37
When I did the upgrade (using the Mikrotik check-for-upgrade via winbox), the Mikrotik (RB435G) did the upgrade to 6.37
...
Any ideas ? Anybody else experienced this ?
North Idaho Tom Jones
Yeah - I think there needs to be a tool to show and remove these phantom packages....It makes me wonder if there could be an old left over mikrotik filesystem that might be invisible or somehow not in the directory.I have exactly the same issue with a 912UAG-5HPnD , after I upgrading to V6.37 from V6.36 two disabled wireless packages one is V6.19, on downgrading to 6.36 wireless is functional again and V6.19 wireless package is goneI just had a really strange problem with the upgrade from 6.36 to 6.37
When I did the upgrade (using the Mikrotik check-for-upgrade via winbox), the Mikrotik (RB435G) did the upgrade to 6.37
...
Any ideas ? Anybody else experienced this ?
North Idaho Tom Jones
For me - in the past - several upgrade ago - I was running that version of ROS that had the old 6.20 wireless package. But from 6.20 to the next newer ROS, the 6.20 wireless package no longer showed up anymore.
Something strange is going on here !!! Is it a bug ? Is it a corrupt mikrotik filesystem ? Is it a new un-documented feature (another name for a bug) ???
North Idaho Tom Jones
I suspect it is an issue when wireless and wireless-fp are both present initially. So prior to 6.33 approx.I just had a really strange problem with the upgrade from 6.36 to 6.37
When I did the upgrade (using the Mikrotik check-for-upgrade via winbox), the Mikrotik (RB435G) did the upgrade to 6.37
however in Winbox, there was no Wireless section
In packages there were two wireless packages, one was 6.37 and the other was 6.20 - both were disabled
I could not in-install either package.
I then downgraded back to 6.36 and the Wireless selection in Winbox came back and there was only one wireless package.
I then upgraded to 6.37 again and again I had the exact same problem. Downgrading back to 6.36 again made everything correct again.
I repeated this process two more times and had the exact same problems again.
Sooo I am stuck with a Mikrotik running 6.36 than can not upgrade to 6.37 - really strange.
I am afraid to keep playing with it because this is an ip/audio link to a remote FM radio station (88.3 KWIS FM) we operate.
I am confused on where the 6.20 wireless package keeps coming from every time I upgrade to 6.37
It is not in the files I see prior to upgrade from 6.36 to 6.37
In the last few days - I upgraded hundreds of Mikrotiks from 6.36 to 6.37 and only ran into this problem on one Mikrotik this morning
Any ideas ? Anybody else experienced this ?
North Idaho Tom Jones
Just reread your post and saw you started at 6.36 ???I suspect it is an issue when wireless and wireless-fp are both present initially. So prior to 6.33 approx.I just had a really strange problem with the upgrade from 6.36 to 6.37
When I did the upgrade (using the Mikrotik check-for-upgrade via winbox), the Mikrotik (RB435G) did the upgrade to 6.37
however in Winbox, there was no Wireless section
In packages there were two wireless packages, one was 6.37 and the other was 6.20 - both were disabled
I could not in-install either package.
I then downgraded back to 6.36 and the Wireless selection in Winbox came back and there was only one wireless package.
I then upgraded to 6.37 again and again I had the exact same problem. Downgrading back to 6.36 again made everything correct again.
I repeated this process two more times and had the exact same problems again.
Sooo I am stuck with a Mikrotik running 6.36 than can not upgrade to 6.37 - really strange.
I am afraid to keep playing with it because this is an ip/audio link to a remote FM radio station (88.3 KWIS FM) we operate.
I am confused on where the 6.20 wireless package keeps coming from every time I upgrade to 6.37
It is not in the files I see prior to upgrade from 6.36 to 6.37
In the last few days - I upgraded hundreds of Mikrotiks from 6.36 to 6.37 and only ran into this problem on one Mikrotik this morning
Any ideas ? Anybody else experienced this ?
North Idaho Tom Jones
I saw the exact same thing you did.
I haven't been game to try this but as a suggestion on older versions upgrade to 6.34.6 Bugfix first (or 6.36.3 if available) then try 6.37 ?
I've reported this to MikroTik along with a supout.rif so hopefully a fix will be forthcoming [emoji3]
Sent from my iPhone using Tapatalk
At another office i have several (>40) IP-Surveillance-Cams, most are not compatible with the new wireless-package (I did not test all...).who are having issues with legacy client on new wireless packages
For test purposes please disable any wireless security profiles, and see if it improves situation.
No Progress with 6.38rc7 ant Intel Pro 2200BG...We just released 6.38rc. Please test if wireless package issues are gone:
http://forum.mikrotik.com/viewtopic.php ... 96#p560196
10:54:46 wireless,debug wlan1: 00:12:F0:6E:XX:XX attempts to associate
10:54:46 wireless,debug wlan1: 00:12:F0:6E:XX:XX not in local ACL, by default accept
10:54:46 wireless,info 00:12:F0:6E:XX:XX@wlan1: connected
10:54:49 wireless,info 00:12:F0:6E:XX:XX@wlan1: disconnected, extensive data loss
10:54:49 wireless,debug wlan1: 00:12:F0:6E:XX:XX attempts to associate
10:54:49 wireless,debug wlan1: reject 00:12:F0:6E:XX:XX, banned (last failure - extensive data loss)
10:54:53 wireless,debug wlan1: 00:12:F0:6E:XX:XX attempts to associate
10:54:53 wireless,debug wlan1: reject 00:12:F0:6E:XX:XX, banned (last failure - extensive data loss)
10:54:56 wireless,debug wlan1: 00:12:F0:6E:XX:XX attempts to associate
10:54:56 wireless,debug wlan1: 00:12:F0:6E:XX:XX not in local ACL, by default accept
10:54:56 wireless,info 00:12:F0:6E:XX:XX@wlan1: connected
10:56:26 wireless,info 00:12:F0:6E:XX:XX@wlan1: disconnected, extensive data loss
10:56:26 wireless,debug wlan1: 00:12:F0:6E:XX:XX attempts to associate
10:56:26 wireless,debug wlan1: reject 00:12:F0:6E:XX:XX, banned (last failure - extensive data loss)
10:56:30 wireless,debug wlan1: 00:12:F0:6E:XX:XX attempts to associate
10:56:30 wireless,debug wlan1: reject 00:12:F0:6E:XX:XX, banned (last failure - extensive data loss)
10:56:32 wireless,debug wlan1_master: start background scan
10:56:33 wireless,debug wlan1: 00:12:F0:6E:XX:XX attempts to associate
10:56:33 wireless,debug wlan1: reject 00:12:F0:6E:XX:XX, banned (last failure - extensive data loss)
10:56:35 wireless,debug wlan1_master: background scan complete, must select network
10:56:35 wireless,debug wlan1_master: no network that satisfies connect-list, by default choose with strongest signal
10:56:35 wireless,debug wlan1_master: failed to select network
10:56:35 wireless,debug wlan1_master: did not find better AP
10:56:36 wireless,debug wlan1: 00:12:F0:6E:XX:XX attempts to associate
10:56:36 wireless,debug wlan1: 00:12:F0:6E:XX:XX not in local ACL, by default accept
10:56:36 wireless,info 00:12:F0:6E:XX:XX@wlan1: connected
10:56:40 wireless,info 00:12:F0:6E:XX:XX@wlan1: disconnected, extensive data loss
10:56:40 wireless,debug wlan1: 00:12:F0:6E:XX:XX attempts to associate
10:56:40 wireless,debug wlan1: reject 00:12:F0:6E:XX:XX, banned (last failure - extensive data loss)
10:56:43 wireless,debug wlan1: 00:12:F0:6E:XX:XX attempts to associate
10:56:43 wireless,debug wlan1: reject 00:12:F0:6E:XX:XX, banned (last failure - extensive data loss)
10:56:47 wireless,debug wlan1: 00:12:F0:6E:XX:XX attempts to associate
10:56:47 wireless,debug wlan1: reject 00:12:F0:6E:XX:XX, banned (last failure - extensive data loss)
10:56:50 wireless,debug wlan1: 00:12:F0:6E:XX:XX attempts to associate
10:56:50 wireless,debug wlan1: reject 00:12:F0:6E:XX:XX, banned (last failure - extensive data loss)
10:56:53 wireless,debug wlan1: 00:12:F0:6E:XX:XX attempts to associate
10:56:53 wireless,debug wlan1: reject 00:12:F0:6E:XX:XX, banned (last failure - extensive data loss)
This means your signal is bad. Maybe the upgrade forced the DFS and your device is now using a different frequency?disconnected, extensive data loss
Don't think so. Frequency-mode is superchannel, country=no_country_set.This means your signal is bad. Maybe the upgrade forced the DFS and your device is now using a different frequency?disconnected, extensive data loss
... you can have access to a device in a lab-enviroment, as the current production-system stays on 6.36.3 with wireless-cm2.This means your signal is bad. Maybe the upgrade forced the DFS and your device is now using a different frequency?disconnected, extensive data loss
Is wrong on winbox (probably) on on terminal?We can't reproduce this problem. Tell us exactly what command you execute and what you see in the console and winbox.Bug: extension channel eeCe and eCee are reversed on winbox wireless/channels (or are reversed on terminal???)
WARNING !!! EDIT - UPDATE - v38rc worked
There is definitely a problem with the upgrade to 6.37 !!! ((EDIT - Problem appears to be resolved with v6.38rc))
Be prepared to loose about 5 percent of your remote Mikrotik clients when you upgrade from 6.36 with wireless-rep package !
I noticed this problem today and posted the problem. Now after upgrading hundreds of remote clients a few days ago, I am starting to get customers calling me saying they are down. After going to some customers to investigate the problem, I discovered the exact same problem after the upgrade to 6.37. Where there is an older wireless package also listed. You can not enable or delete/remove/un-install either wireless package. The ONLY thing you can do is perform a downgrade to an older version of ROS.
ALSO - then after the downgrade - you then need to restore your latest backup -or- reconfigure everything to do with your wlan
North Idaho Tom Jones
WARNING !!! EDIT - UPDATE - v38rc worked
There is definitely a problem with the upgrade to 6.37 !!! ((EDIT - Problem appears to be resolved with v6.38rc))
Be prepared to loose about 5 percent of your remote Mikrotik clients when you upgrade from 6.36 with wireless-rep package !
I noticed this problem today and posted the problem. Now after upgrading hundreds of remote clients a few days ago, I am starting to get customers calling me saying they are down. After going to some customers to investigate the problem, I discovered the exact same problem after the upgrade to 6.37. Where there is an older wireless package also listed. You can not enable or delete/remove/un-install either wireless package. The ONLY thing you can do is perform a downgrade to an older version of ROS.
ALSO - then after the downgrade - you then need to restore your latest backup -or- reconfigure everything to do with your wlan
North Idaho Tom Jones
EDIT - Update - Good News
Working with a problem Mikrotik that every time lost the wireless interface when upgrading from 6.36 to 6.37 which resulted in two different versions of the wireless package (one was new at 6.37 and the old was 6.20 (where ever the 6.20 came from I have noo idea). Both wireless packages were disabled and the only recovery was to downgrade to 6.36 then restore the last backup configuration.
What worked was upgrading from 6.36 to 6.38rc7
The wireless link came back
However - there was still the older disabled wireless 6.20 package
I did another reboot - when it came back then everything looked good - there was no longer a second older wireless package.
North Idaho Tom Jones
I had the same problemAfter upgrade CHR 6.36.3 --> 6.37 on Hyper-V Router OS don`t work properly. Ethernet don`t work. System crashes when any manipulation with Ethernet. Clean image vhdx don`t work too.
I had the same problem, unable to remove any old wireless package left in 6.37. I had to downgrade the router, remove the wireless package, then reupdate.I just had a really strange problem with the upgrade from 6.36 to 6.37
When I did the upgrade (using the Mikrotik check-for-upgrade via winbox), the Mikrotik (RB435G) did the upgrade to 6.37
however in Winbox, there was no Wireless section
In packages there were two wireless packages, one was 6.37 and the other was 6.20 - both were disabled
I could not in-install either package.
I then downgraded back to 6.36 and the Wireless selection in Winbox came back and there was only one wireless package.
I then upgraded to 6.37 again and again I had the exact same problem. Downgrading back to 6.36 again made everything correct again.
I repeated this process two more times and had the exact same problems again.
Sooo I am stuck with a Mikrotik running 6.36 than can not upgrade to 6.37 - really strange.
I am afraid to keep playing with it because this is an ip/audio link to a remote FM radio station (88.3 KWIS FM) we operate.
I am confused on where the 6.20 wireless package keeps coming from every time I upgrade to 6.37
It is not in the files I see prior to upgrade from 6.36 to 6.37
In the last few days - I upgraded hundreds of Mikrotiks from 6.36 to 6.37 and only ran into this problem on one Mikrotik this morning
Any ideas ? Anybody else experienced this ?
North Idaho Tom Jones
Did you plan to restore cm2 packet? 6.37 very unstable with Apple devicesIf you see multiple wireless packages after upgrade on your device then the spare one will disappear after next reboot.
Please tell us more detailed in what kind of setup the Apple devices are unstable?Did you plan to restore cm2 packet? 6.37 very unstable with Apple devicesIf you see multiple wireless packages after upgrade on your device then the spare one will disappear after next reboot.
With 6.37 It needs more time to connect. When I open the lid of macbook I should wait about 1min. With 6.36 it is much faster. Also my printer by HP, when I connect it to 220V, it power on and shows on display that it connect to WiFi, but ip-address like 169.254...xx (I do not remember exact digits). And after 2-3min it gets normal ip-address. With 6.36 it also much faster. About 10-15 sec.Please tell us more detailed in what kind of setup the Apple devices are unstable?
What setup you have on the AP? 2.4ghz or 5ghz? Encryption or not?With 6.37 It needs more time to connect. When I open the lid of macbook I should wait about 1min. With 6.36 it is much faster. Also my printer by HP, when I connect it to 220V, it power on and shows on display that it connect to WiFi, but ip-address like 169.254...xx (I do not remember exact digits). And after 2-3min it gets normal ip-address. With 6.36 it also much faster. About 10-15 sec.Please tell us more detailed in what kind of setup the Apple devices are unstable?
Printer use 2.4Ghz, MacBook - 5Ghz. Encryption AES. Sure I can. Wait a moment.What setup you have on the AP? 2.4ghz or 5ghz? Encryption or not?
Maybe you could send the support output file of the config to support@mikrotik.com so we could try to reproduce this problem?