Here is the link to the changelog:
http://www.mikrotik.com/download/CHANGELOG_beta
Note, that if you downgrade from beta version to the 2.9 version then you should check your DST-NAT rules - they might be changed. This only applies to the downgrade - upgrade will work fine. You can create a backup file in v2.9 if you want to downgrade later back to v2.9.
CD install and demo licence key is fixed.
correction:
Before the downgrade you MUST disable all your NAT rules with “dst-port” or “scr-port” options
OR ELSE
one port dst-nat rule will became global, all port forwarder and it will be impossible to connect to the router.
Any insight / comment about nstream & CSMA disabled options, that
had been tested by some of your user, and seems this options
has :
High Regards,
Andrei
what did you expect, wonderbutton 
? we just added the requested feature, it does what it is supposed to do. nobody knew what effect it would have
Yes, it does. The theory says so, and
we tried other products with similar feature “CSMA/CA disable” (that using atheros too),
seems have coping good with noise.
What do you do in your journey to add this option ?
Maybe we could give input, what’s maybe missing in the equation ?
High Regards,
Andrei
in theory, when there is so much noise, nothing can force the other end to receive clean data. it just is not possible, no matter what you do on your end. the interference will just be too high.
i am happy, read this change log...
*) made demo mode work;
okay tomorrow will try to install them, with cdimage... i hope is success.
now i still at home....
Dear Normis,
Seems many whitepaper circulating on the Net says the contrary to you.
They said, and have experimented using mad-wifing stripped,
that using software mac and atheros SDR, they could
send the data normally in noisy environment as long you got
high SNR.
Now, the problem with “false syndrom of interference” is
High / Good signal (SNR)
Bad Troughput, and very high latency ?
Why, because you never got any chance to transmit, and always
get in the bottom of the food chain, err “wireless food chain / pecking order then”.
High Regards,
Andrei
We added one more setting for this feature in the next beta (4), but there is nothing more to do. Please supply all further reports with some kind of test results, mystical whitepapers are not proving anything.
Since at least beta2, on RB112s with AR5211 as AP, if a wireless setting is changed some clients (Cisco 350 is one) will not reassociate untill the client card is disabled then enabled.
00:16:00 wireless,info 00:0A:F4:4A:1E:32@wlan1: reassociating
00:16:00 wireless,info 00:0A:F4:4A:1E:32@wlan1: disconnected, ok
00:16:00 wireless,info 00:0A:F4:4A:1E:32@wlan1: connected
00:16:05 wireless,info 00:0A:F4:4A:1E:32@wlan1: reassociating
00:16:05 wireless,info 00:0A:F4:4A:1E:32@wlan1: disconnected, ok
00:16:05 wireless,info 00:0A:F4:4A:1E:32@wlan1: connected
00:16:11 wireless,info 00:0A:F4:4A:1E:32@wlan1: reassociating
00:16:11 wireless,info 00:0A:F4:4A:1E:32@wlan1: disconnected, ok
…etc
Dear Normis,
Could you elaborate more, what’s new setting we could expect
in beta-4 in conjunction with this csma/ca disable operation.
Thank’s in advance.
High Regards,
Andrei
my testing that I posted, it showed that in a noisy enviroment there was very noticable improvment in stabializing the throughput rates. it did NOT significantly improve peak throughput, but average throughput did go up quite noticably. While it’s no WonderButton, it’s a noticable improvment. and it makes it so that I can actually consider using 2.4 for customers (when v3 is final), and that’s the main goal here, make more spectrum usable for us to use to service more customers, for whatever reason it was previously un-useable.
Latency is another story… the latency problems I was seeing have nothing to do with CSMA, they have to do with NStream.
Well some of the whitepapers did the following:
Disable CSMA/CA
Disable ACK timeouts
Disable Retries (only if NStreme does that already)
Shorten the inter-frame spacing / random backoff
Some of them actually had their own MAC layer - like SoftMAC, which actually is a raw data transmitter.
Also, you must remember that it could be the data rate selection algorithm is tuned for Carrier Detection and not for forced transmit. It could be that the speed is being tuned by the noise level / SNR - which didn’t read correctly in beta 2.
Some of them actually had their own MAC layer - like SoftMAC, which actually is a raw data transmitter.
Thank you for your info Direct, maybe MT teams could gain insight
what could they do more in order to make MT more rugged and
could coping in high noise environment.
High Regards,
Andrei
Hi uldis,
is the channel settings fixed in this version of the routeros? As you probably know the channels selection is wrong (when you select the channel set accordingly to the country).
Thank you
Not yet. Probably it will be in the next version.
how about accessing the wireless menu in winbox from windows XP? I’ve got 4 different computers it crashes on the instant I select wireless, interface → wlan1 works, but not the wireless button on the left.
I tried it under Windows Vista, works fine 
what do you mean for the next version? next beta of 3.0 or you mean in 3.1?
Thank you
P.S. it’s really important to have it asap…
pdf,
Next 3.0 beta version.
As far as I know, the releases come in the following manner:
2.9—>3.0 etc.
3.0 beta is between 2.9 and 3.0, because 3.0 is on development stage now.
