Page 1 of 1

Re: v6.37 [current] is released!

Posted: Tue Sep 27, 2016 12:15 pm
by patrick7
Several important bugfixes and improvements which are overdue for a long time :D

Re: v6.37 [current] is released!

Posted: Tue Sep 27, 2016 12:16 pm
by normis
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.

Re: v6.37 [current] is released!

Posted: Tue Sep 27, 2016 12:22 pm
by nz_monkey
RouterOS v7 is currently in early alpha and there is no scheduled release date yet.
:cry:

Re: v6.37 [current] is released!

Posted: Tue Sep 27, 2016 12:29 pm
by Lakis
RouterOS v7 is currently in early alpha and there is no scheduled release date yet.
:cry:
Until than I'll sit on my chair and wait :) while clicking refresh button on mikrotik download page

Re: v6.37 [current] is released!

Posted: Tue Sep 27, 2016 1:09 pm
by notToNew
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.
My Samsung-TV also works with disabled security.
Please tell me if you need any further information, for now i'm reverting to 6.36.3 with wireless-cm2 and enabled security.

Re: v6.37 [current] is released!

Posted: Tue Sep 27, 2016 1:23 pm
by pampi
Hello,

Changeslog says:
lte - added dlink dwm-157 D, dwm-222 support;

Could you please tell me what device-id or vendor-id. I have a DWM-222 with the following id:

1 device="1:2" vendor="Mobile Connect" name="Mobile Connect" serial-number="aa51a87072d6" vendor-id="0x2001" device-id="0xab00" speed="480 Mbps" ports=0 usb-version="2.01"

HEX POE lite, with 6.37 still not recognize it.

Thanks

Re: v6.37 [current] is released!

Posted: Tue Sep 27, 2016 2:00 pm
by haik01
On my RB751U-2HnD upgraded from 6.36.3 to 6.37.

Now the wlan1 interface is MISSING completely. It is not listed. Only the 5 ethernet ports and the bridge is there. I use the 751 only as an AP.

Of course the wireless package is grey, since there is no wifi defined in /interface.

How do I get back to the old 6.36 version? Downgrade button in packages says to reboot and after reboot, it comes back to 6.37 (of course without wlan card).


How to solve this? This is urgent since the 751 is serving a community centre which I convinced that Mikrotik is "as good" the old Cisco Aironet's they had.

Re: v6.37 [current] is released!

Posted: Tue Sep 27, 2016 2:09 pm
by pe1chl
Before you press the downgrade button you must first download the correct package from the archive section
of the download page (routeros for mips) and upload it to the router files section. Then click on downgrade.

Re: v6.37 [current] is released!

Posted: Tue Sep 27, 2016 2:18 pm
by BartoszP
Netinstall ?

Re: v6.37 [current] is released!

Posted: Tue Sep 27, 2016 2:31 pm
by haik01
I do not need Netinstall. I have full connectivity to the router with Winbox.

But I will try the downgrade with the old version.


Edit:

I downgraded to 6.36 and it worked.

For now, no more upgrades to this RB751.... I will wait what Mikrotik support will tell.

Re: v6.37 [current] is released!

Posted: Tue Sep 27, 2016 3:27 pm
by paoloaga
RouterOS v7 is currently in early alpha and there is no scheduled release date yet.
Until then I'll sit on my chair and wait :) while clicking refresh button on mikrotik download page
It is what I am doing already since a while! :-) :-)

Re: v6.37 [current] is released!

Posted: Tue Sep 27, 2016 3:35 pm
by Cha0s
I upgraded a mAP-Lite and a hAP-Lite from 6.36 to 6.37 without any problems with the wireless package (like other users mentioned).

I don't (never) use the combined package and I was using wireless-rep.

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 :)

Re: v6.37 [current] is released!

Posted: Tue Sep 27, 2016 5:38 pm
by strods
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.

Re: v6.37 [current] is released!

Posted: Tue Sep 27, 2016 7:05 pm
by Cha0s
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 :)
Nope, it's not really fixed. nfacctd spews out tons of notices about wrong flows received.
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
Bad sequence numbers?
At least timestamps seem correct.


Also using the combined package (it turns out I use it only in two CCRs after all) I am unable to disable the wireless package no matter how many times I reboot the devices.
This happens on two CCR1036. The log file shows the following weird message but the wireless package remains enabled.
 > /log print 
jan/01/1970 03:00:12 system,info disabled wireless@-6.37 
18:54:35 system,info router rebooted 
By weird, I am referring to '@' after wireless.
Both devices were upgraded from v6.36 and had wireless-cm enabled.

It appears that the combined package is the culprit regarding the wireless package problems mentioned by many users.

Re: v6.37 [current] is released!

Posted: Tue Sep 27, 2016 9:05 pm
by steen
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 ?
Since DFC is required by law, I suggest to be careful with your enterprise setup and follow the regulations.
Hello Normis!
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 ?

DFS - more info requested please

Posted: Tue Sep 27, 2016 9:08 pm
by TomjNorthIdaho
May I please get some more detailed information on DFS - specifically how it related to 6.37

I wish to get a much better understanding on DFS and the possible side-effects prior to upgrading my Mikrotik APs to 6.37

Q - Does DFS have any effect on the CPU load (for AP and/or client) ?

Q - Can DFS have an effect on bandwidth throughput (even if it does not auto-change channels) ?

Q - Does DFS have any effect on client devices ?

Q - How does DFS effect the country (country code - available channels ((super-channel)) ) where an AP is located ?

Q - Does DFS have an effect on Super-Channel settings (frequencies) for an AP ?

Q - If an AP has a scan-list of only one frequency, and DFS detects a radar - what happens ?

Q - What happens for DFS to auto-change frequencies/channels on an AP ?

Q - Is it possible that if a Mikrotik (with 3.37 with DFS) is located near a 2-million-watt military/FAA radar system, that DFS can get false positives resulting in changed channels/frequencies on an AP ?

Q - With 6.37 & DFS, is it possible for an AP in a high-noise environment ( TV stations, FM and AM radio stations and many other APs) to trigger a DFS auto-change-channel ?

Q - May we also get any other additional DFS information not specifically asked ?

I really wish to understand clearly what is happening or may happen with DFS and radar ?

Prior to posting, I did some google searching but many of the answers I have found are vague and not clear.

Thank you

North Idaho Tom Jones

Re: v6.37 [current] is released!

Posted: Tue Sep 27, 2016 9:44 pm
by Cha0s
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 :)
Nope, it's not really fixed. nfacctd spews out tons of notices about wrong flows received.
After further testing, by updating pmacct/nfacct to the latest version I don't get any notices any more.
So I guess the problem was with nfacct.

I'll continue my tests to verify that IPFIX is working properly.

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 3:41 am
by scampbell
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 ?
Since DFC is required by law, I suggest to be careful with your enterprise setup and follow the regulations.
Hello Normis!
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 ?
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.

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. :-)

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 8:24 am
by Zorro
Until than I'll sit on my chair and wait :) while clicking refresh button on mikrotik download page
thats sounds quite good plan/strategy.
why don't you add warm cat/tea and/or wife/family/kids to picture ? :) for example(just kidding :).

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 11:00 am
by Raf
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.
Done. We can reproduce it everytime. Check support@mikrotik.com e-mail. Ticket number 2016092822000398.

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 11:22 am
by hebertonlp
OSPF with NBMA Still freezing since 6.32.4 (did I test all version after and the last 6.37 (stable)), wheh start all got perfectly, then some minutes running, all interfaces frozen in /routing ospf interface print (not show nothing and still frozen until Ctrl+C then when i reboot all got work for some minutes)
comands that are frozed:
/routing ospf nbma-neightbor print
/routing ospf interface print.

Until this got frozen all work finely.
I got a network running about 35 OSPF Machines in ver 6.32.4 and the only one problem of this version is the time the network take to up again when a big concentrator is rebooted, and some disconects without reason.

All versions after 6.32.4 are doing this problem with NBMA, but in 6.37 i got the frozen in interface print too...

Problem detected in mipsbe, tile and powerpc, other not tested....

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 1:52 pm
by ufm
is that all? :lol:

Nice job. Almost feels like you are near to a final version of v6.... :D
i herad that they are working on version 7.
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.
What is so spacial in v7?
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.

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 1:56 pm
by ufm
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

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 2:01 pm
by normis
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
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.

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 2:14 pm
by ufm
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
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.
Normis, issue not fixed (I can create new video with demonstration in any time. Need?).
Proposed workaround - advance create all needed pppoe interfaces. Nice joke - I have about 6000 active pppoe sessions (and about more than 10000 total pppoe clients).

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 3:42 pm
by steen
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 ?
Since DFC is required by law, I suggest to be careful with your enterprise setup and follow the regulations.
Hello Normis!
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 ?
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.

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. :-)
How can I see if DFS is used and how it operates ?
Can someone define "radar detect", how does the device know it is a radar and how does it distinguish between other wifi network and radars. can it misinterpret ?
Will network and link be less stable using DFS, does anyone have experience of it ?

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 3:56 pm
by normis
If your country has an actual government radar operating at a specific frequency, you are usually not allowed to operate in that frequency, this is why RouterOS will listen on the frequencies, defined in your country regulations tables. It ignores other 802.11 devices, there are patterns how it can detect it is a radar, not a wifi device.

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 4:14 pm
by pe1chl
It ignores other 802.11 devices, there are patterns how it can detect it is a radar, not a wifi device.
The problem is that this does not work very well. This does not appear to be MikroTik-specific, we had issues with TranZeo
and others report issues with Ubiquiti. In some circumstances it works fine, but in some installations there are problems
like "radar detected on all channels" or "spurious radar detection makes it hop after having operated for a long time on some
channel". After making an incorrect hop, it can take time before it finds a usable channel and it can also land on a channel
in use on another link on the same location, also not what you like. DFS adds an unpredictability to the network that many
operators don't like, and on top of that it adds service interruptions. Probably lots of users would appreciate if there was some
more intelligent implementation that still can operate within the legal requirements. E.g. the AP compiles a channel list
in non-volatile memory about detected radar events and the confidence in them, and picks the used channel from the list
of channels without radar in a way that allows the operator some control. (e.g. there are 5 channels without radar, then
the operator can select a preferred channel of operation and the AP will only leave that when it detects new radar on that
channel with high confidence, and will move only to another channel which it has not in its list of radar channels with high confidence,
and maybe some priority list or even interaction with other APs on the same location could be possible)

There should also be some handling of "radar on all channels", e.g. look more closely to the reported events and try to filter
them better for radar/other interference. An AP should not end up in indefinite hopping because of DFS.

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 4:23 pm
by normis
We 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.

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 4:41 pm
by saaremaa
Framed-IPv6-Prefix not work.

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 4:59 pm
by steen
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 ?
Since DFC is required by law, I suggest to be careful with your enterprise setup and follow the regulations.
Hello Normis!
Have you then ensured the DFS settings you enforce by country follows also my country (Sweden), not all the frequencies should have DFS in my country.

Swedish PTS (http://pts.se) says the following regarding 5GHz band (I can ask them for an official documentation about it, what is available on their website is in Swedish):
Channel: 36, 40, 44, 48 Frequency: 5,17-5,25GHz Low Band, max 200mW, no DFS
Channel: 52, 56, 60, 64 Frequency: 5,25-5,35GHz Middle Band, max 200mW, no DFS
Channel: 100-140 Frequency: 5,47-5-725GHz H-Band, Max 1 W ERP. DFS & TPC
Channel: 149, 153, 157, 161, 165 Frequency: 5,725-5,875GHz High Band, Max 25 mW no DFS no TPC

I would like to be able see the actual settings for each frequency in the router board, how do I do that ?

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 5:01 pm
by normis
You can see which frequencies are coded in the driver with this command:
[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
          
We keep the settings up to date.

edit: for short range devices (srd), in EU, you can use this country legally:
[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

edit2: we use 27 instead of 30dbm, because RouterOS does not support TPC

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 5:11 pm
by onnoossendrijver
Is TPC support on the RouterOS roadmap?

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 6:17 pm
by bratislav
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.

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 6:18 pm
by Cha0s
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.
Yeap, same here.

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 7:10 pm
by steen
You can see which frequencies are coded in the driver with this command:
[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
          
We keep the settings up to date.

edit: for short range devices (srd), in EU, you can use this country legally:
[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

edit2: we use 27 instead of 30dbm, because RouterOS does not support TPC
Looks ok, except that you have DFS on:
Channel: 52, 56, 60, 64 Frequency: 5,25-5,35GHz Middle Band, max 200mW, no DFS

Which says no DFS, why ?

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 8:19 pm
by steen
Hello Normis!

I do not get same result as you when checking for DFS:

[admin@liuyun] > 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
5250-5330/a,an20,an40,ac20,ac40,ac80,ac160(23dBm)/passive
5490-5710/a,an20,an40,ac20,ac40,ac80,ac160(27dBm)/passive
5190-5310/a-turbo(20dBm)
5180-5300/a-turbo(20dBm)
5520-5680/a-turbo(27dBm)/passive
5510-5670/a-turbo(27dBm)/passive
902-927/b,g,g-turbo,gn20,gn40(30dBm)

[admin@liuyun] > system package print
Flags: X - disabled
# NAME VERSION SCHEDULED
0 multicast 6.37
1 routeros-mipsbe 6.37
2 system 6.37
3 ipv6 6.37
4 wireless 6.37
5 X hotspot 6.37
6 dhcp 6.37
7 X mpls 6.37
8 routing 6.37
9 ppp 6.37
10 security 6.37
11 advanced-tools 6.37

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 8:44 pm
by rextended
Bug: extension channel eeCe and eCee are reversed on winbox wireless/channels (or are reversed on terminal???)

Bug (yes): removed DFS choice: Is more simple block dfs settings to country settings, like now on 6.37, but give the possibility to create un-Lockpack for set dfs as wanted...
How I can use now DFS without radar detect on selected wireless/channels???
How I can use now DFS with radar detect on other channels not on country-list???

Re: v6.37 [current] is released!

Posted: Wed Sep 28, 2016 9:36 pm
by TomjNorthIdaho
We 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.
O - thank god for your post re superchannel

This info is great !

I have one of my towers that has a 2-million+ watt radar system near-by (a couple hundred feet away). When it hits my APs, almost all channels on all bands take a quick blink.
FYI - By all bands - I literally mean 700 MHz, 900 MHz, 2.3 GHz all the way up through 6 GHz. The bleed over on all channels is totally crazy !!!
FYI - the EMI/RFI noise is so high - that even an Ethernet cable tester shows there is traffic on the cable, although I am standing there with both ends of the cable in my hands with an Ethernet cable tester connected to the cable !!!



North Idaho Tom Jones

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 12:41 am
by 1gremlin7
After 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.

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 4:26 am
by scampbell
I can also confirm the wireless upgrade problem when upgrading to 6.37.

In this case going from 6.24 using wireless-fp, the upgrade went through but afterward I had wireless 6.37, wireless 6.24 and wireless-fp 6.24 all present and disabled.

Uninistalling via CLI did not remove them.

Downgrading to Bugfix 6.34.6 version got the radio going again.

I checked what packages were installed after the bugfix had rebooted and it only showed the 6.34.6 wireless options.

I decided to try an upgrade form the bugfix but that still failed showing wireless 6.24 still present ???

Back to 6.34.6 until it's sorted :-)

Other devices running happily on 6.36.3 have upgraded to 6.37 without problem. And our office AP has been running much better since upgrading to 6.37 so it is not all bad !!

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 10:00 am
by zobde
Hi All,
from my side after the upgrade all is working as before except a "cosmetic" issue.
Statistics on wlan is now 0 while before the upgrade it was working.
I am using CAPSMAN and this happen on RB951Ui-2HnD that is the manager while on CAP RB941-2nD and RB952Ui-5ac2nD the issue is not present

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 10:13 am
by normis
steen
I do not get same result as you when checking for DFS:
Looks like you found a bug. Thanks! The info command apparently hides some stuff for no reason. It still operates correctly though. Will fix.

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 10:18 am
by uldis
Bug: extension channel eeCe and eCee are reversed on winbox wireless/channels (or are reversed on terminal???)
We can't reproduce this problem. Tell us exactly what command you execute and what you see in the console and winbox.

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 11:29 am
by noib
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?

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 11:46 am
by honzam
Files in download archive now missing. http://www.mikrotik.com/download/archive
Why? :shock:

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 11:55 am
by normis
Files in download archive now missing. http://www.mikrotik.com/download/archive
Why? :shock:
Links missing, not files. And Changelog missing too.
We are working on something for the download site, unfortunately, some things got broken. We will fix soon.

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 12:35 pm
by pe1chl
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 think it is normal that in this case you use 1 physical and 3 virtual APs for the 4 networks you want to run.

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 12:53 pm
by honzam
After upgrade to 6.37 with DFS, when I change frekvency --> then is AP with fixed frequency (5620Mhz) 10minutes detecting radar (without clients) and after 10minutes is runnig AP. It is normal?

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 1:14 pm
by normis
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?
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).

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 2:03 pm
by honzam
Thank you for the explanation

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 2:13 pm
by honzam
deleted

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 2:23 pm
by normis
Yes, it's normal, it is following ETSI requirement.
You should exclude this frequency from the scan list, and it will not scan for 10 minutes. Or you can use superchannel or another country to avoid DFS altogether, but for this, you can get into trouble.

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 2:25 pm
by steen
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?
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).
Hello Folks!

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.

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 2:28 pm
by normis
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.
Are they configured to use the 5650MHz radar frequency? Are they even allowed to do that?

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 2:48 pm
by pe1chl
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.

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)

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 2:49 pm
by athurdent
AVM products do in fact wait for 10 minutes if one selects channel 116 and above. Just wondering why the hAP AC set to "Ceee" on channel 116 only waits for one minute as it potentially uses the Radar frequencies on "eee"?

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 3:06 pm
by noib
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 think it is normal that in this case you use 1 physical and 3 virtual APs for the 4 networks you want to run.
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 have just tested with a 6.34, wlan without SSID, 2 virtual AP. Quickset->upgrade->reboot: after reboot, my wlan interface is disabled and in default configuration. Mikrotik is seriously messing up with this version :(

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 3:12 pm
by normis
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)
I will get back to you on this, will investigate.

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 5:15 pm
by Lakis
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?
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).
Hello Folks!

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.
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.
Like Microwave it works on 2.4Ghz output power up to 50W but its legal to use in your home
But If you place LINKSYS WRT1900ACS in to the weatherproof box and place it outside on the tower and use frequency that required DFC that is illegal

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 5:25 pm
by umicsa
Something is wrong with wireless package. It disconnects more frequently from AP that previous wireless-cm2. The best wireless was at MT5.x !

Yeah i got some of the wireless problem
the wireless package can not be enabled .
So i downgraded to 6.36

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 9:15 pm
by dadoremix
Net install and working again
I have also that problem on rb951



Sent from my iPhone using Tapatalk Pro

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 9:17 pm
by radekb32
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 problem from v 6.36.3. My routerboard is hex lite.
Did Mikrotik do something with /ip settings rp_filter?

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 9:28 pm
by TomjNorthIdaho
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

Re: v6.37 [current] is released!

Posted: Thu Sep 29, 2016 11:49 pm
by JHV
DHCPv6 still not working as expected.

Image

My ISP enforces all 24 hours a disconnect. IPv4 address and IPv6 prefix is dynamic, but it takes 20 minutes until a new prefix is obtained.
Last working Router OS was v 6.33.6.

More details here: http://forum.mikrotik.com/viewtopic.php?f=2&t=109473

By the way, when can we expect a working prefix delegation according to RFC 7084?
Mikrotik and IPv6 ist still a very painful experience.

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 1:14 am
by n21roadie
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 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 gone

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 4:13 am
by TomjNorthIdaho
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

...

Any ideas ? Anybody else experienced this ?

North Idaho Tom Jones
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 gone
It makes me wonder if there could be an old left over mikrotik filesystem that might be invisible or somehow not in the directory.
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

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 5:32 am
by 105547111
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

...

Any ideas ? Anybody else experienced this ?

North Idaho Tom Jones
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 gone
It makes me wonder if there could be an old left over mikrotik filesystem that might be invisible or somehow not in the directory.
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
Yeah :) - I think there needs to be a tool to show and remove these phantom packages....

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 6:27 am
by RomesJr
good evening! I have a problem for me, and really, I'm using the 6.7 version and watched the logs that apaerece the following message: autentication failed: peer didn't Respond to CHAP challenge, then immediately my clients vain unplugging and so return to connect when I restart the ccr1036, you guys can help me ?????

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 6:57 am
by scampbell
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 suspect it is an issue when wireless and wireless-fp are both present initially. So prior to 6.33 approx.

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 Image


Sent from my iPhone using Tapatalk

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 6:59 am
by scampbell
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 suspect it is an issue when wireless and wireless-fp are both present initially. So prior to 6.33 approx.

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 Image


Sent from my iPhone using Tapatalk
Just reread your post and saw you started at 6.36 ???


Sent from my iPhone using Tapatalk

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 7:40 am
by TomjNorthIdaho
WARNING !!!

There is definitely a problem with the upgrade to 6.37 !!!
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

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 9:19 am
by dadoremix
Like i say before
Only netinstall helps you for 6.37


Sent from my iPhone using Tapatalk Pro

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 9:35 am
by notToNew
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.
At another office i have several (>40) IP-Surveillance-Cams, most are not compatible with the new wireless-package (I did not test all...).

6.36.3 with wireless-cm2 works.

So please consider creating a bugfixes "6.36.4" !!!
so i can stay with wireless-cm2, untill the current wireless-package is stabilized.

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 11:37 am
by strods
We just released 6.38rc. Please test if wireless package issues are gone:
http://forum.mikrotik.com/viewtopic.php ... 96#p560196

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 11:57 am
by notToNew
We just released 6.38rc. Please test if wireless package issues are gone:
http://forum.mikrotik.com/viewtopic.php ... 96#p560196
No Progress with 6.38rc7 ant Intel Pro 2200BG...
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) 

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 12:09 pm
by strods
notToNew - I was talking about wireless package being disabled after upgrade and/or that it was not possible to disable it.

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 3:25 pm
by normis
disconnected, extensive data loss
This means your signal is bad. Maybe the upgrade forced the DFS and your device is now using a different frequency?

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 3:53 pm
by notToNew
disconnected, extensive data loss
This means your signal is bad. Maybe the upgrade forced the DFS and your device is now using a different frequency?
Don't think so. Frequency-mode is superchannel, country=no_country_set.
I had the same problem with 6.36.3 and wireless-rep package with old DFS-behaviour.

The 2 Devices have 2m distance, a newer intel wifi with the same distance works, this legacy-device does not work.
After downgrade to wireless-cm2, connecting both devices is no problem.

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 3:57 pm
by notToNew
disconnected, extensive data loss
This means your signal is bad. Maybe the upgrade forced the DFS and your device is now using a different frequency?
... you can have access to a device in a lab-enviroment, as the current production-system stays on 6.36.3 with wireless-cm2.
maybe you have better debugging-possibillities?

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 8:24 pm
by miharoot
after two days working on 6.37 without any load
Image
on the previous versions I two years have not seen such a.

Re: v6.37 [current] is released!

Posted: Fri Sep 30, 2016 8:39 pm
by rextended
Bug: extension channel eeCe and eCee are reversed on winbox wireless/channels (or are reversed on terminal???)
We can't reproduce this problem. Tell us exactly what command you execute and what you see in the console and winbox.
Is wrong on winbox (probably) on on terminal?
Affect ALL routeros version where wireless/channel are present, not only 6.37 or 6.36.3

Image

Re: v6.37 [current] is released!

Posted: Sat Oct 01, 2016 3:11 am
by TomjNorthIdaho
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

Re: v6.37 [current] is released!

Posted: Sat Oct 01, 2016 3:12 am
by TomjNorthIdaho
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

Re: v6.37 [current] is released!

Posted: Sat Oct 01, 2016 10:17 am
by Miracle
Dynamic queue from hotspot get wrong priority
I tried to set priority 6,7,8, not specified then update user profile, reset hotspot server but priority of dynamic queue still 1

Image

Re: v6.37 [current] is released!

Posted: Sat Oct 01, 2016 10:20 am
by rwmajx
After 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

Re: v6.37 [current] is released!

Posted: Sat Oct 01, 2016 5:33 pm
by patrickmkt
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 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.

Re: v6.37 [current] is released!

Posted: Sat Oct 01, 2016 9:13 pm
by miharoot
again, after 24 hours
Image
will have to roll back to 34

Re: v6.37 [current] is released!

Posted: Sun Oct 02, 2016 6:20 pm
by xherbert
Hi,

after upgrade to 6.37 (from 6.36.something) my RB493G is not reachable. Neither winbox or netinstall is able to see it. I tried to make a reset by short-circuiting the on board reset "button" while attaching the power adapter but that doesn't seem to be working either (the beeps seems to be the same as normal install). I don't have serial cable to attach to RS232 to try.
Any ideas what might went wrong or what else I could try to re-live my RB again?

Thank you for any help.
Herbert

Re: v6.37 [current] is released!

Posted: Sun Oct 02, 2016 6:22 pm
by sstyle
I also have a lot of wireless issues with 6.37. MacBook and printer HP working worse. Wireless-cm2 was stable. How to downgrade to 6.36? Thanks.

upd: did it.

Re: v6.37 [current] is released!

Posted: Sun Oct 02, 2016 9:31 pm
by n21roadie
[quote="strods"]We just released 6.38rc. Please test if wireless package issues are gone:
http://forum.mikrotik.com/viewtopic.php ... 96#p560196[/quote]

I upgraded to 6.38rc and have wireless operational again but in packages is V6.19 wireless ??
Something is very wrong with both V6.37 and V6.38 ??

Re: v6.37 [current] is released!

Posted: Mon Oct 03, 2016 9:27 am
by strods
If you see multiple wireless packages after upgrade on your device then the spare one will disappear after next reboot.

Re: v6.37 [current] is released!

Posted: Mon Oct 03, 2016 9:47 am
by sstyle
If you see multiple wireless packages after upgrade on your device then the spare one will disappear after next reboot.
Did you plan to restore cm2 packet? 6.37 very unstable with Apple devices

Re: v6.37 [current] is released!

Posted: Mon Oct 03, 2016 10:00 am
by uldis
If you see multiple wireless packages after upgrade on your device then the spare one will disappear after next reboot.
Did you plan to restore cm2 packet? 6.37 very unstable with Apple devices
Please tell us more detailed in what kind of setup the Apple devices are unstable?

Re: v6.37 [current] is released!

Posted: Mon Oct 03, 2016 10:06 am
by sstyle
Please tell us more detailed in what kind of setup the Apple devices are unstable?
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.

Re: v6.37 [current] is released!

Posted: Mon Oct 03, 2016 10:24 am
by uldis
Please tell us more detailed in what kind of setup the Apple devices are unstable?
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.
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?

Re: v6.37 [current] is released!

Posted: Mon Oct 03, 2016 10:26 am
by sstyle
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?
Printer use 2.4Ghz, MacBook - 5Ghz. Encryption AES. Sure I can. Wait a moment.

upd: check your mailbox.

Re: v6.37 [current] is released!

Posted: Mon Oct 03, 2016 3:41 pm
by strods