v6.36rc [release candidate] is released, wireless-fp package is discontinued!

[strods]

Note: wireless-fp package is discontinued in this version. It needs to be uninstalled/disabled before upgrade. Use wireless-rep or wireless-cm2 instead.

What’s new in 6.36rc3 (2016-Apr-19 11:33):

*) bonding - do not corrupt bonding statistics on configuration changes;
*) bonding - fixed crash when vlan parent mtu is higher than bonding mtu;
*) ethernet - do not allow mtu to be higher than l2mtu and l2mtu to be higher than max-l2mtu (reduce automatically on upgrade if it was wrong before);
*) firewall - added udplite, dccp, sctp connection tracking helpers;
*) switch - fixed switch compact export;
*) traffic-flow - added ipfix support (RFC5101 and RFC5102);
*) wireless - wireless-fp is discontinued, it needs to be uninstalled/disabled before upgrade;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

[gius64]

PLEASE make wireless-fp auto replaced by wireless-cm2. Otherwise it will be a pain to upgrade all CPEs in the network to 6.36
And… Could you please release a changelog for wireless-fp → wireless-cm2?

[kometchtech]

have the USB disk is not detected by the RB3011.

[Ticket#2016041966000617]

[jarda]

@gius64

PLEASE make wireless-fp auto replaced by wireless-cm2. Otherwise it will be a pain to upgrade all CPEs in the network to 6.36
And… Could you please release a changelog for wireless-fp → wireless-cm2?

You can install cm2 before update. Then switch the packages and update afterwards. I agree that automatic wireless packages switch during the update would be much more convenient.

[gius64]

@jarda

@gius64

PLEASE make wireless-fp auto replaced by wireless-cm2. Otherwise it will be a pain to upgrade all CPEs in the network to 6.36
And… Could you please release a changelog for wireless-fp → wireless-cm2?

You can install cm2 before update. Then switch the packages and update afterwards. I agree that automatic wireless packages switch during the update would be much more convenient.

Sure, but you have to manually (or automatically in batch) change package.
It’s not so simple and you have to schedule both wireless package change and RouterOS upgrade.

[andriys]

@gius64

Could you please release a changelog for wireless-fp → wireless-cm2?

As far as I’m aware the only major difference between the two is the supported version of CAPsMAN. Otherwise they should be functionally equivalent. If you happen to used CAPsMAN v1, there are upgrade instruction on the wiki.

[andriys]

@gius64

you have to schedule both wireless package change and RouterOS upgrade.

That’s true, but you don’t have to do that at the same time- start doing the former now already, if you feel like.

Having said that, automatic upgrade from old wireless or wireless-fp to wireless-cm2 would be much appreciated, of course.

[doneware]

@andriys

@gius64

Could you please release a changelog for wireless-fp → wireless-cm2?

As far as I’m aware the only major difference between the two is the supported version of CAPsMAN. Otherwise they should be functionally equivalent. If you happen to used CAPsMAN v1, there are upgrade instruction on the wiki.

yes, but doing auto-upgrade with manually added packages (e.g. not the bundled in main package) will fail as wireless-fp-x.xx-arch.npk will not be on the distribution site.

[anuser]

I´d like to request a feature for wireless-rep package:

• Is it possible to show the username (beside the MAC address) for all connected clients within CAPSMAN window?
  (It would be helpful to see on which access point a client is connected when users calling support and complains about connectivity issues they have…)

[105547111]

Can on 6.36 final release a forced changeover from wireless-fp to wireless-cm2?

[whyfly]

@anuser

I´d like to request a feature for wireless-rep package:

• Is it possible to show the username (beside the MAC address) for all connected clients within CAPSMAN window?
  (It would be helpful to see on which access point a client is connected when users calling support and complains about connectivity issues they have…)

+1

I have a few more requests:
Is it possible to show CCQ for each connected client? Or dropped / retransmitted frames percentage?
Is it possible to perform background scan for each remote radio?
(It would be helpful to see connection quality statistics as well as channel usage statistics within CAPSMAN window)

[anuser]

Let´s summarize the feature requests for wireless-rep:

@whyfly

Is it possible to show CCQ for each connected client? Or dropped / retransmitted frames percentage?
Is it possible to perform background scan for each remote radio?
(It would be helpful to see connection quality statistics as well as channel usage statistics within CAPSMAN window)

@anuser

show the username (beside the MAC address) for all connected clients within CAPSMAN window?
)

• vendor OUI auto naming
• custom names for CAP devices
• centralized ressource monitoring / statistics ([CPU, RAM, amount of connected clients for each CAP device], total amount of connected devices, frequency band usage, “rogue devices” using the same frequency band or the same SSID per CAP device,…)

[andriys]

@anuser

• custom names for CAP devices

What do you mean? Is ‘/system identity’ on a CAP device not what you need?

[nkourtzis]

@anuser

Let´s summarize the feature requests for wireless-rep:

@whyfly

Is it possible to show CCQ for each connected client? Or dropped / retransmitted frames percentage?
Is it possible to perform background scan for each remote radio?
(It would be helpful to see connection quality statistics as well as channel usage statistics within CAPSMAN window)

@anuser

show the username (beside the MAC address) for all connected clients within CAPSMAN window?
)

• vendor OUI auto naming
• custom names for CAP devices
• centralized ressource monitoring / statistics ([CPU, RAM, amount of connected clients for each CAP device], total amount of connected devices, frequency band usage, “rogue devices” using the same frequency band or the same SSID per CAP device,…)

My post with CAPsMAN feature requests in the 6.35rc thread:

@nkourtzis

Requests for CAPsMAN bug fixes and new features, based on my experience with the current RC version:

1. {Nice to have} Add “CCQ”, P Throughput" and “Signal to Noise”, “Encryption” and “Group Encryption” and “WMM Enabled” fields to CAPsMAN Registration Table.

2. {Feature} Add “Frequency Mode”, “WMM Support”, “Multicast Buffering”, “Keepalive frames”, “Adaptive Noise Immunity” and “AMPDU Priorities” to CAPsMAN Config Settings.

3. {BUG} Make “Multicast Helper=full” in CAPsMAN slave interfaces work (now the interfaces stay in default setting).

4. {BUG} Make “Country=no_country_set” work on CAPsMAN 5GHz 802.11ac interfaces (it works on 2.4GHz, but on 5GHz ones it results in “no supported band” error message, regardless of the band and frequency settings).

5. {Feature} Add a scan/freq usage feature in CAPsMAN, with an aption to run in the background. Right now, if one wants to scan, they have to detach the physical interface from the Manager, do the scan and re-attach it. [In the future, use this info to auto-adjust CAP channels and power levels.]

6. {Annoying} Stop CAPsMAN from creating virtual interfaces on CAPs with name “wlanXXX” where XXX is a number which is incremented every time the interface is disabled and re-enabled.

7. {Nice to have} Let the user rename the virtual interfaces on the CAPs, like he/she can do with physical interfaces.

[nkourtzis]

Also: Since upgrading from 6.35rc48 to 6.35, my hAP acting as CAPsMAN loses the association with some of the CAPs after a few hours (<1 day), even though the CAPs are accessible from the hAP. The CAPs that have dissassociated stop publishing any wlans. A reboot of the problematic CAPs fixes the problem: they appear again in the “Remote CAP” table. This has happened three times within two days, while had never happened before. I don’t know whether this is of any relevance, but free disk space on the hAP is low, to about 1.4MB, even though there are no files taking up any significant space. Sometimes I even get error messages from User Manager because of low space.

All devices are running on 6.35 stable.

I am publishing this here because it has to be worked on in this version.

[uldis]

nkourtzis, this problem is reproduced and fixed. We hope we will be able to release a fixed version today.

[honzam]

@105547111

Can on 6.36 final release a forced changeover from wireless-fp to wireless-cm2?

+1

[jondavy]

please add into the CapsMan Registration Table fields:
CCQ, RadioName, Distance,
and the option to scan for free frequencies for each cap
and also the Channel Width 10mhz

I use CapsMan to have a centralized management of all my sectors and customers with SXT of my Wisp
so the request of the CCQ and RadioName
and in some sector still in use migrated 10mhz

[nkourtzis]

@uldis

nkourtzis, this problem is reproduced and fixed. We hope we will be able to release a fixed version today.

Good news, but…

When was this bug introduced and how did it make it into the “stable” version? It is not a rare bug. Possibly you should start remaining to the last RC, the one which can ACTUALLY be named Release Candidate, for a few days without making any further additions, just bug fixing, before releasing it as stable. Even from rc48 and rc49 to the stable, there were additions which could introduce new bugs.

[andriys]

@nkourtzis

When was this bug introduced and how did it make it into the “stable” version?

What you call “stable” is called “bugfix only” by Mikrotik guys. And it is version 6.32.4 at the moment. Please read release branch descriptions at the top of official download page. CAPsMAN is rock solid in 6.32.4 with wireless-cm2 for me.