2.9RC1 will be released soon.....

subj

Can you give us a date? I am hoping that there will be some fixes for the Wireless in 2.4Ghz AP mode. We have 3 RB532 waiting to go in, but clients won’t stay associated in 2.9beta18/19. We have another type of SBC that we downgraded to 2.8.27 that doesn’t have this problem.

~D

no.but its forking in mikrotik lab.you can see it on test router http://demo.mt.lv login demo without password.you can see it: /in wi mon wlan1-uplink
in RouterOS field

???
There is 2.8.26

If you issue the quoted monitor command, you can see the remote end is running a version labeled “2.9rc1”…

We’ll wait, we’ll see…

for now there is:

Router v2.8.26
Login:

a monitior command is when you type monitor and not login :)))

I bet Alex meant this:

[normis@demo.mt.lv] > interface wireless monitor wlan1-uplink
                 status: connected-to-ess
                   band: 5ghz
              frequency: 5300
                tx-rate: 48Mbps
                rx-rate: 48Mbps
                   ssid: flatant
                  bssid: 00:0B:6B:31:08:B9
             radio-name: 000B6B3108B9
        signal-strength: -78
     tx-signal-strength: -73
                 tx-ccq: 15
                 rx-ccq: 13
    current-ack-timeout: 28
       current-distance: 28
               wds-link: no
                nstreme: no
           framing-mode: none
       routeros-version: 2.9rc1
                last-ip: 159.148.172.204

[normis@demo.mt.lv] >

anyway, the RC is on the download page aleady … (but it is not really a RC cause at the last moment we found an issue, so careful with bridge firewall)

what, still no comments?

wow… my first comment is - when you really develop final version 2.9 - you’l get a box of good polish beer from me :stuck_out_tongue:

hard to say anything more at this time (just seeing RC1)

anyway - seeing RC1 I understand, I should already get ready for shoping beer :smiley:

regards and good luck!!!
kj

I have a comment. Looking at the change log I don’t see any wireless fixes. We have a routerboard that was running 2.9beta19 setup up as an ap-bridge using the atheros AR5213 card. All customers have 26db “SNR”(We used a spectrum analyzer on the sector to get the noise level) or better on this AP. Customer will associate and then disconnect after a couple seconds and we get this error:

00:27:24 wireless,info W2: disconnected 0:2:6f:8:a4:c1, extensive data loss

Using a Wrapboard loaded with 2.9beta19 does the same thing. Downgrading the software to 2.8.27with the same wireless setup, no more disconnects. Also on our routerboards running 2.9beta18, it did not see our prism cards. NL-2511MP +

My feeling is you have some more bugs to work out before a final release!!!

as always: please make a supout.rif file at the time the problem is happening and send the file to support along with detailed description of the setup. make sure you are running the latest version.

Will do!!!