v6.37 [current] is released!

[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…

[ufm]

@Lakis

@azfar

@paulct

is that all?

Nice job. Almost feels like you are near to a final version of v6…

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.

[ufm]

@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

[normis]

@ufm

@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.

[ufm]

@normis

@ufm

@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.

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

[steen]

@scampbell

@steen

@normis

@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 ?

[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.

[pe1chl]

@normis

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.

[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.

[saaremaa]

Framed-IPv6-Prefix not work.

[steen]

@normis

@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 ?

[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

[onnoossendrijver]

Is TPC support on the RouterOS roadmap?

[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.

@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.

[Cha0s]

@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.

@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.

Yeap, same here.

[steen]

@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

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 ?

[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

[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???

[TomjNorthIdaho]

@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.

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

[1gremlin7]

After upgrade CHR 6.36.3 → 6.37 on Hyper-V Router OS dont work properly. Ethernet dont work. System crashes when any manipulation with Ethernet. Clean image vhdx don`t work too.