*) added ability to run non RouterOS in MetaROUTER;
*) improved address-list and layer7 firewall feature support for smp systems;
*) special-login items can now be disabled;
*) fixed special-login to update used-by property of port;
*) fixed USB UPS monitoring on RB433UAH;
*) console - ‘print’ command reuses assigned item numbers;
*) fixed issue with Cisco BGP VPLS when used between 2 RouterOS devices;
*) console - ‘print’ commands have new option ‘follow-only’ that continuously
shows changes like the ‘follow’ option, but does not print all items
at the beginning;
*) api - ‘follow’ and ‘follow-only’ options of ‘print’ commands now work,
‘.dead’ property is reported for deleted items;
*) api - ‘listen’ command now is alias for ‘print’ with ‘follow-only’
opriont set;
*) api - several commands running in parallel could produce intermixed
output, fixed;
*) console and api - fixed problem that caused property values sometimes to
incorrectly have value ‘(unknown)’, this could happen when running
several console or api commands at once;
*) fixed BGP VPLS crash when site-id > 15 used somewhere in network;
*) changed BGP AS path number output format to ASPLAIN;
*) console - new scheduler tasks use trimmed effective user permissions as the
default value of policy, previously default value was “read,write,test”;
*) added ttl matcher to ipv4 firewall;
*) improved dns cache not to allow other RRs in statically configured domains;
*) fixed vlan on bonding;
*) fixed bonding modes balance-alb and balance-tlb;
*) added per-connection-classifier matcher to firewall;
*) fixed wireless Hw. Fragmentation Threshold in WinBox;
*) user manager - added option to specify custom Return URL
for Authorize.Net payments;
*) user manager - write logs to syslog topic manager,account;
*) routing-test - support for per-VRF BGP instance redistribute settings;
*) routing-test - speed up BGP route processing;
*) routing-test - added routing-table configuration to RIP;
I’d appreciate any input as I would really like to use bonding ALB for bonding a fast 5ghz link and a slower 2.4ghz link to be able to utilize the combined bandwidth of both links, or let either one run on their own if the other goes down.
Normis, could you please give some more information on that point? we tried bonding of gigabit links on v~3.20 (in bonding-rr mode), it worked for some hours and then huge packet loss begins. and yes, there were many VLANs on that bonding interface. what exactly changed?
As a matter of fact I do need a doctor and its late at night! A flue or somethin got me just tonight. But even if it hadn’t, I should be angry, and others should be angry too. Stuff doesnt work too often you know.
p.s. prozac? That stuff will erase your identity and make you a pus5y
Its possible. I should look into it, totally. How does a working RouterOS UPnP operation looks like in a trace file? I need to know this to know what to look for. Maybe someone can make one for me?
In Web interface (webbox):
a. Interfaces page returns a connection reset error
b. If there is more than one wlan interface, then start page returns connection reset error (I think this is the same as “a” above, as if there are two wlan, then the start page displayed is interface page)
Have tried upgrade from known working 3.19 to 3.24 with same issues.
Not that I have set that up recently but as far as I know, there are these changes in recent v.3: simple queues does not get activated unless it has some limit set. This is done to optimize CPU usage.
We have several vlan interface for transit customer through our router. All incoming and outgoing traffic to our customer will passthrough that vlan interface.
So we just limit that vlan for their traffic, all ip address will passthrough our router and i don’t need to create ip based queue rule.
I just need to create 1 simple queue rule and i can limit all that we need to limit.
So simple ..
just tried to add simple queue to vlan interface: all is working at least in 3.24, but I did not hear anything bad about 3.23 and queues… try 3.24, if no - then check your configuration
I had RouterOS 3.22 working with simple queues until 04 AM this morning when “upgraded” to 3.24. NO chance to make the queues work yet…
Platform rb433, the 3 LANs are bridged, “Use IP Firewall” checked.
This is a added Queue:
add dst-address=x.x.x.x/32 interface=bridge1 parent=Internet direction=upload priority=8 queue=wireless-default/wireless-default limit-at=2048000/2048000 max-limit=10240000/10240000 burst-limit=0/0 burst-threshold=0/0 burst-time=0s/0s total-queue=wireless-default
I am limiting only the download part (upload to clients, from RB433 point of view).
I repeat, all was fine until changing RouterOS.
Write to support and give them a supout output file. In the meantime consider using Queue Tree or downgrading to ROS 3.23, 3.22 etc. Then tell us what happened.
Am i doing something wrong here when trying to downgrade? : I uploaded routeros-mipsbe-3.22.npk in winbox in “Files” section, then system-packages-downgrade. But there is still 3.24 version up.
