Verze 5.0beta2

[honzam]

What's new in 5.0beta2 (2010-Apr-30 11:35):

*) added wireless distance setting, removed ack-timeout;
*) improved 802.11 operation for outdoor distances;

What's new in 5.0beta2 (2010-Apr-29 12:10):

*) fixed sstp on x86;
*) console - removed 'delay' argument from '/system scheduler add' command;
*) console - remove 'comment=""' values from export;
*) console - updated '/system script job':
- also show active login sessions here;
- new read-only property 'type' with values "command", "login"
or "api-login" for running commands and either kind of login sessions;
- new optional read-only property 'parent' with id of the job that
has spawned this one;
*) console - changed "started" property of '/system script job' to use
local time;
*) console - new property 'type' in '/system script job'
*) console - added '/port remote-access export' command;
*) console - fixed bug that caused "cannot set ..." error when using
some properties in 'find' commands;
*) show old software id in export file header;
*) api - can supply password to '/system/upgrade/upgrade-package-source/add';
*) api - 'print' command was not showing values of some properties
such as 'servers' in "/ip/dns";
*) api - fixed api login sessions not dissapearing from '/user active' after
termination;
*) '/user active' now lists type of api connections as 'api';
*) added support for hardware watchdog on RB1000 & RB800;
*) added support for ASIX AX88xxx based USB Ethernet Adapters on RB4xx;
*) fixed problem - ipv6 traffic was not bridged if ipv6 package was not enabled;
*) fixed getting interface stats in dude;
*) fixed metarouter stability problem on RB400s & RB750s;
*) fixed metarouter - it didn't work on RB1000 with 2Gb;
*) fixed metarouter - it locked up on RB800;
*) fixed problem - SFQ queues did not work on interfaces (wireless) if none
of simple or tree queues were added;
*) fixed RB800 temperature;
*) fixed problem - WinBox crashed while opening VAP interface;
*) dhcp server - fixed possible inactive dhcp server in case of many
dhcp leases with address-pool enabled;
*) dhcp server - show non-printable option 82 agent-circuit-id and
agent-remote-id values in hexadecimal notation
(in the same way as client-id is shown);


Timto prosim adminy o zalozeni threadu verze 5.0 a nebo prideleni prav

[honzam]

Important note:

Beware that 5.0beta2 version is still beta version, and may contain bugs,
therefore should be used on non-critical systems at first. Any issues found
(including crashes, lockups, degradation of performance) should be reported to
support@mikrotik.com, accompanied by supout.rif file.

As of version 5.0beta2 wireless interface "ack-timeout" setting has been
replaced by "distance" setting. Not only distance setting should make
configuration easier, but additionally should improve long link performance,
especially 11n performance. Distance setting does not apply to nstreme
mode.

"distance" can be:
- indoors - standard 802.11
- 1...1000 - approximate distance in km
- dynamic - to be detected automatically upon registration, the same way as
ack-timeout=dynamic before.

Default value of "distance" setting for fresh installs and upgraded systems is
"dynamic", no matter what previous value of "ack-timeout" was. Therefore after
upgrading it is strongly recommended to check what is the dynamic distance
estimate.

It is normal for dynamically estimated distance to be off by a few km from
actual distance and also change from card to card. It is always possible to
change over to static distance setting and find the value that provides the
best performance.

If dynamic distance estimate is erratic: obvious huge difference from actual
distance (>3km), significantly different distance estimate in multiple
registrations between the same devices, it is advised to change over to static
distance setting.

In order to get the benefits of this feature, all devices in wireless network
must be upgraded.

In point-to-multipoint networks, the value of AP distance setting should
reflect the distance to the furthest client.

[Stanislav Hrncir]

Že jste si nevšimli polofunkčního TDMA, v další betě už snad uplněfunkčího to beru ale že by jste si nevšimli funkce frequency offset, kterou posunete kanálové schéma o x jednotek až stovek MHz dolu i nahoru to už je co říct to zas bude rušičů v mezikanálech pokud to teda nešoupnete o 1GHz níž..

[honzam]

Že jste si nevšimli polofunkčního TDMA, v další betě už snad uplněfunkčího to beru ale že by jste si nevšimli funkce frequency offset, kterou posunete kanálové schéma o x jednotek až stovek MHz dolu i nahoru to už je co říct to zas bude rušičů v mezikanálech pokud to teda nešoupnete o 1GHz níž..

To bude asi tim ze to zatim nikdo netestnul o TDMA jsem četl vypada to zajimave

[ppp76]

Že jste si nevšimli polofunkčního TDMA, v další betě už snad uplněfunkčího to beru ale že by jste si nevšimli funkce frequency offset, kterou posunete kanálové schéma o x jednotek až stovek MHz dolu i nahoru to už je co říct to zas bude rušičů v mezikanálech pokud to teda nešoupnete o 1GHz níž..

Tak TDMA sem si nevsiml ani omylem a a ni ho nemuzu nikde najit

[honzam]

Že jste si nevšimli polofunkčního TDMA, v další betě už snad uplněfunkčího to beru ale že by jste si nevšimli funkce frequency offset, kterou posunete kanálové schéma o x jednotek až stovek MHz dolu i nahoru to už je co říct to zas bude rušičů v mezikanálech pokud to teda nešoupnete o 1GHz níž..

Tak TDMA sem si nevsiml ani omylem a a ni ho nemuzu nikde najit

/int wireless set 0 ?
....
tdma-additional-txrxguard
tdma-debug
tdma-override-rate
tdma-override-size
...

[ppp76]

aaaaaaa uz nasli moji radcove
jen ted jdu nekam strachat co a jak se tam nastavuje abych zkusil jak to chodi

[lwq]

aaaaaaa uz nasli moji radcove
jen ted jdu nekam strachat co a jak se tam nastavuje abych zkusil jak to chodi

Hmmm, tak TDMA ? Velmi zajimave, jeste aby to umelo vyuzivat k tomu GPSku a idealne i synchronizovat urcene vysilace ci celou sit. Ta krasa, kdyz by clovek mohl mit celou sit na jedinem kanale ! Oj, "slint"

[hapi]

až na to že se dělili o rychlost nebo ne?