hello,
what are the differences between v11 and v12 ? Probably managing some change_log for n-streme would be helpful 
thnx, mp3turbo.
I was just thinking the same
yeah, I have problems installing v12 - installation fails on three machines stating always the same : something like “package installation script failed - couldn’t install”…
Anyone else experiencing this?
btw, original 2.8.13 wireless file has date aug/11, time 13:35 ; after trying to install n-streme v12, this file is changed to aug/11, time 15:09 - does it mean that despite of “package installation script failed” error this package is installed ? I’m going to try it, but I don’t have wireless card handy…
probably someone from mikrotik could have a look at this…
thanks !
yes, the script error is shown, but the package installs fine. we tested it and it works despite the log message.
thanks, normis, confirmed : works. Nstreme options are available and functional.
Can you tell us what are updates from v11 ? We are particularly looking for packet-loss cure for 2.4GHz…
Just a quick question, is the G-Turbo selection only meant to work with another Mikrotik box, or will client boxes (non-Mikrotik) also be able to connect) Am referring to using it in non-nstreme mode.
I’d guess mikrotik only.
John, another observation : when I choose dynamic-size on AP, client shows exact-size → probably bug.
All other modes are working as expected (ie. fast-frames shows fast-frames, exact shows exact).
mp3turbo2 did you try this new N-Streme testing revision 12 in real life enviroment with superg? I tried v 11 and it didnt work (wery well)
hi folks,
another observation : very high cpu usage with nstreme v12. Basically doing nothing, just 20-100kbit/s (=2.5 - 12.5kB/s) thru wireless interface and… cpu utilization around 45%, occasional spikes above 55% !!! There are no rules, no pptp, no ciphering, no NAT - simply nothing, this is just plain router, installed in five minutes. Configured IP addresses for interfaces, set ssid, switched on g-turbo and nstreme with framer-police=best-fit (tried dynamic, exact size) and framer-limit=4000. No WEP. All else left on default. P2/400, 512kB cache, 440bx chipset, plenty of ram, 3com 905 fast ethernet or intel pro100 show the same, no HDD activity. Unbelievably high CPU usage disappears when using standard drivers, but there is unusable g-turbo (packetloss).
Another problem : pings. They jump all-around between 2ms and ~100ms on empty (!) link, usually like 2,3,4,80,40,2,18,20,2,2,3,60,19,2,3,2,80,60,3,3,2 etc. Few small ones, one or two big… Clean environment, this is not cause by interference.
bye, mp3turbo.
… forget those jumping pings, please - it was wireless card… sorry.
so did you try super g on x km link lets say? how much did you get?