*) route - make connected routes inactive when interface has no link;
*) ipsec - changing or removing unused peer or proposal config won’t flush active SAs;
*) console - add ‘without-paging’ to more ‘print’ commands;
*) route - automatically repair FIB inconsistencies;
*) ipsec mode-cfg - unity split include support;
*) ipsec policy - template matching for policy generation;
*) metarouter: fixed occasional lockups on mipsbe boards;
*) fixed crash when bridge filter rule had action=return for rule in builtin chain;
*) traffic-flow - fixed deadlock and crash on multicore;
*) fixed memory leak on CCR with PPPoE interfaces;
*) improved PPPoE interface encapsulation performance;
*) fixed queues - total amount of traffic passing through queues sometimes was about 1Gbit;
Hi Normis
Very nice to see the updated ROS 6rc14
Very interesting bug with Atheros 9344. What’s new in 3.07 firmware
Only one question - and when we can change the DTIM interval for SSID (default is 1 and cannot be changed by software - no option) to 2 or higher?
A lot of client side devices looses the battery power very fast because of Mikrotik DTIM is selected 1.
In 5.25 release I had asked the same before.
Please answer.
Temporary workaround: create new bridge, put the problematic ether interface in that bridge. Add the VLANs with interface=that bridge so that bridge software would now be taking care of vlan tagging etc. instead of the NIC driver. (Note: the VLANs are not bridge ports of the mentioned bridge. They can be bridge ports of another bridge)
@MT I will send you the supout.rif file taken when problem is observed.
p.s. it may be vlan offload bug or otherwise Intel bug in my opinion !!! (where MT could choose the driver, tweaks, they have in ROS, maybe NIC firmware or if they can - patch the damn driver (patching of NIC firmware is also a possibility))
P.S. 2: Intel PRO/1000 NIC driver in RouterOS 5.22 did not have this problem
after upgrade from rc13 no more connectivity via Vlan on RB1100AHx2
it is a shame that MT does not really test those releases !!!
i would like to get some money for testing and wasting time with this buggy stuf !
it seems that Mikrotik OS gets worse from release to release
sorry but i have enought !!
hey mikrotik why dont you try to fix all the errors first an then bring new features ???
it is a release candidate for sure - but major things like Vlans should work…
and also with 5.24 we have even more sudden reboots of the boxes and no answers or fixes
and MT sell routers where you cant use a final ROS ( CCR )
