I have just upgraded a RB333 board with the newest software V3.6 and have noticed that the connection tracking is not effected when I specify which time-out to use. Currently this setting is stuck on 5 days which is way to long form this application. I would like to have it set for 6 hours. I wish you all would have a more stable version for the RB333. Could you possibly put out a V2.9 for the 333 Boards? what can i do to fix the connection tracking it seems to be weighing down my boards CPU??
You dont have to go back all the way to 2.9, i went back to 3.4 and it is OK. Maybe you can try even version 3.5 but i'm not sure So, I guess this is another TODO item for version 3.7 fix connection tracking
please please please, if you find something thats broken and downgrading fixes it then reproduce it and sent the supout to support <at> mikrotik.com. How do you expect it to get fixed if you don't report it?
I have written about this problem before, and I'm 100% sure that it's a bug from ver 3.6 and MT support team must know it, so I don't think we should report this with a supout.rif file to MT support.
if you know 100% sure that they know it then your right, however, how can you be so sure they know it? : ) Also, the Mikrotik staff that reads these forums isn't always the same staff that fixes bugs (or reports them for that matter).
downgrading to V3.4 today, just a bummer that the new firmware has issues with things that the V3.5, V3.4 ....... never had. you would think that the newest firmware would be based from the one previous like V3.6 would then be based from V3.5 and so forth. guess this is not how the team @ Mikrotik upgrades software. Thank you all for the insight.
Anytime changes are made there's a possibility of bug/problem arising. Let them know of the bug and I'm sure they'll get it fixed. Look at previous bugs, someone finds it, reports it, usually in the next version it's taken care of.