ChangeLog proprietary-extensions

Is the ChangeLog detailed and accurate enough?

  • Yes
  • Needs a little more work
  • It’s the main reason I am scared to upgrady my equipment
  • It’s so bad, it makes me want to buy C* products…
0 voters

So I was going through the 532 I just upgraded to 2.9.27, and noticed a new option under wireless called proprietary-extensions, and afer some reading I see it deals with compatibality between Intel Centrino wireless cards and MT APs pre and post 2.9.25… yet as I look through the change log for 2.9.25 I don’t see this potentialy very serious issue mentioned! In fact, it’s not listed anywhere in the change log for ANY version…

proprietary-extensions > (pre-2.9.25 | post-2.9.25; default: post-2.9.25) - the method to insert additional information (MikroTik proprietary extensions) into the wireless frames. This option is needed to workaround incompatibility between the old (pre-2.9.25) method and new Intel Centrino PCI-Express cards
pre-2.9.25 - include extensions in the form accepted by older RouterOS versions. This will include the new format as well, so this mode is compatiblewith all RouterOS versions. This mode is incompatible with wireless clients built on the new Centrino wireless chipset and may as well be incompatible with some other stations
post-2.9.25 - include extensions in the form accepted by MikroTik RouterOS starting from veriosn 2.9.25, and compatible with all known wireless clients



What’s new in 2.9.25:

*) added missing ‘/ip dhcp-server alert get’ command;
*) fixed DHCP server to work with some non-RFC compliant DHCP clients;
*) improved robustness of serial port UPS handling; fixed value exponent
handling for USB UPS;
*) fixed problem with static ARP entries not added after reboot
on some interfaces;
*) graphing web interface is now a valid xhtml 1.0;
*) added support for Novatel Wireless CDMA card;
*) speed up route table updates in routing-test;
*) fixed crash in routing-test (introduced in 2.9.19);
*) fixed crash in user-manager if download-limit is used and radius packet
logging is enabled;
*) fixed handling of disabled packages by console setup;

is anyone else starting to get quite frustrated by the poor documentation regarding the changelog???

This was quite an issue as i had two clients who i was telling that their equpiment was at fault.

I had no idea this was a problem that had either been recognized or fixed.

While mikrotik has EXCELLENT documentation in general, this issue is of such importance that i would have expected them to make it more clear.

joe