What's new in 3.23:

*) fixed installation on fresh disks or VMs;
*) add 802.1ad Service Tag support for VLAN;
*) wireless - fix for RTS/CTS when used together with dynamic ACK timeout;
*) serial ports are now grouped per USB device;
*) added gsm info command to ppp-client;
*) added URL support to fetch tool;
*) added dial-on-demand mode to PPTP & L2TP clients;
*) ssh - now non-interactive console commands can reference variables;
*) fixed TFTP server logging;
*) fixed problem - "/system upgrade" (autoupgrade) did not show proper package
architecture and was unable to fetch new packages;
*) fixed bug - hotspot 'walled garden ip' rules did not work on some boards
after reboot;
*) added '/interface print stats' command;
*) improved support for OSPF as PE-CE routing protocol;
*) added OSPF sham links;
*) fixed a bug in set-bgp-prepend-path routing filter;
*) fixed some MPLS TE reoptimize bugs;
*) added MPLS TE bandwidth management features;
*) netwatch - ignore items with interval 0s, this value was causing
netwatch to fail;
*) routing-test - added new type of gateway argument: ip address together with interface;
*) api - 'disabled' property was not available from api since 3.21, fixed;
*) api - added support for retrieving OID values;
*) api - removed special behaviour of 'find' command under API. Use
'print' command with queries instead of 'find'. This change fixes
scripts that are started from API and contain 'find' command.
*) console - removed support for octal numbers, now string of digits with
a leading zero is interpreted as decimal number;
*) console - added binary ~ operator that matches value against
POSIX extended regular expression;
*) console now accepts decimal numbers with k/K M G T P suffixes for
values of some properties;
*) console - fixed export problems:
if long line is wrapped just before space charater, the space character
has to be escaped, otherwise it is lost;
errors during export generated a comment line that was incorrectly enclosed
in quotes;
*) console - added binary ~ operator that matches value against
POSIX extended regular expression;
*) scheduler - added owner and policy properties; all existing
scheduler entries will get owner name "*sched" and policy
read,write,test;
*) routing-test - allow to specify that route gateway is in the main routing table;
*) added route cache statistics;
*) fixed mesh protocol;
*) graphing - fixed IP address mask display issue for low endian architectures;

The upgrade again not work...
autoupgrade > refresh = nothing.

This not new

Auto Update STILL NOT WORKING

I have tried ROS 3.17, 3.20 and 3.22 on 3 different RB:
no one found 3.23 in ftp server (3.20 is founded).

(sorry for my poor english)

Auto Update STILL NOT WORKING

I have tried ROS 3.17, 3.20 and 3.22 on 3 different RB:
no one found 3.23 in ftp server (3.20 is founded).

as you can see in the first post, it's fixed in 3.23. so 3.23 will be able to recognize and autoupdate to 3.24, 3.25, etc. =)

Auto Update STILL NOT WORKING

I have tried ROS 3.17, 3.20 and 3.22 on 3 different RB:
no one found 3.23 in ftp server (3.20 is founded).

as you can see in the first post, it's fixed in 3.23. so 3.23 will be able to recognize and autoupdate to 3.24, 3.25, etc. =)

sorry for my bad english:

3.13 (for example) detect new 3.14, 3.15 ,3.16 ,3.17, 3.18, 3.19, 3.20 but NOT 3.22 or 3.23.

The problem is not in PREVIOUS 3.22 relases, but in new "compressed/compiled" files.

The fact important for user is that OLD version can detect NEW,
not the NEW detect PLUS NEW...

Manually FTP update all 3.13 / 3.20 (i have +300 RB...) at 3.23 is the problem....

AHTES read again what CHUPAKA posted above ...

AHTES read again what CHUPAKA posted above ...

....and after the router will be upgrade automatically Normis ? This really unconfortable more than 20-30 routers ! Please make some patch we can upgrade to 3.23 easy.

upgrade to v3.23 manually. from then on, the auto upgrade will work.

you can use the Dude to do upgrades too.

you must understand, the fix is in v3.23, your v3.22 has NO FIXES it's still the same as it was.

upgrade to v3.23 manually. from then on, the auto upgrade will work.

you can use the Dude to do upgrades too.

you must understand, the fix is in v3.23, your v3.22 has NO FIXES it's still the same as it was.

Ok, i have understand: I must use The Dude, but is possible make in future "Auto Upgrade" in WinBox or "/system update" work again on older version (3.20 and older) ? Obviously the problem is in the npk packages (size? checksum? new format? I do not know... but PARTIAL downloaded npk are founed by auto upgrade...).

Thanks for your works. (And sorry for my bad english)...

we can't modify your old version. it's not possible, it would require you to reinstall it.

new npk format - new rake to tread upon =)

p.s. it's hidden advertisement of The Dude!

we can't modify your old version. it's not possible, it would require you to reinstall it.

This is my last post about that.
I do not wanna be ******.

The point is:
NOT modify OLD version for DETECT NEW,
but MODIFY NEW to be DETECTED BY OLD. (3.13 detect 3.20 ...)

the old version doesn't understand new packages. we can't teach it.

Since the upgrading to 3.23 no 3G modems work.. USB ports 1 and 2 nolonger show, log states unable to aquire serial port.

I have tested with E220's and E169's alll working correctly with 3.17..

Also tried with fresh clean install no change.

Lee

configuration change is needed, see changelog. new wiki will follow shortly.

Ok I understand that is the case due to the GSM-Info note in the log...

Its not very helpful tho that the Wiki Info is not released at the time of the software.. It like driving blind..

Dangerous.

Lee

Since the upgrading to 3.23 no 3G modems work.. USB ports 1 and 2 nolonger show, log states unable to aquire serial port.

I have tested with E220's and E169's alll working correctly with 3.17..

Also tried with fresh clean install no change.

Lee

My E180 on x86 still works on 3.23!

article updated:
http://wiki.mikrotik.com/wiki/Option_Gl ... _USB_Modem

It's meaning that now we can use AT commands with ppp client connected??

AND it installs on my sata drive without a hitch.
Thanks.

What's new in 3.23:
*) wireless - fix for RTS/CTS when used together with dynamic ACK timeout;

Can anyone say what was the problem that required this fix and what was the impact?

What's new in 3.23:
*) wireless - fix for RTS/CTS when used together with dynamic ACK timeout;

Can anyone say what was the problem that required this fix and what was the impact?

maybe this
http://forum.mikrotik.com/viewtopic.php?f=7&t=29275

What's new in 3.23:
*) wireless - fix for RTS/CTS when used together with dynamic ACK timeout;

Can anyone say what was the problem that required this fix and what was the impact?

maybe this
http://forum.mikrotik.com/viewtopic.php?f=7&t=29275

I am dying to deploy this release because I have lots of hidden clients, but good judgement tells me to wait a few more days

FYI:

Huawei E156 3G modem on 3.23:

Command Channel: 2
Data Channel: 0
Info Channel: 1

[mramos@WRAP-3G] > int ppp-client info 3G_NET
pin-status: "READY"
manufacturer: "huawei"
model: "E156"
revision: "11.604.09.01.149"
serial-number: "356368020595709"
activity-status: "call in progress"
functionality-status: "minimum"
gprs-mode: "B - EDGE"
current-operator: "3G_NET"
signal-level: "-95 dBm"

Actually the modem is locked to 3G modes and frequencies (e.g HSDPA/WCDMA @ 2.1GHz). I don't know why ppp-client info reports gprs-mode "B-EDGE" because it's disabled by AT commands and stored on modem flash. Of course a disabled radio (e.g 850MHz) will report a signal-level so low as -95dBm. This modem is quadriband (850, 900, 1800 & 2100 MHz).

With this new aproach to 3G modems on 3.23, it's not possible to use serial-terminal when ppp-client is up. I upgraded from 3.21 to 3.23 and at 3.21 I use to run serial-terminal on USB2 to snif RSSI and other modem info such as TX/RX bytes, up-time, etc.

Where is the WCDMA signal-level reading?