Talk:Tomato Firmware/Menu Reference

Bandwidth log size
The article says: "The bandwidth monitor history is just /.../ WAN port monthly history, WAN port daily history for the current month and intraday history (for vlan1, eth1, br0, eth0 & vlan0) captured over the last 24 hours. For this reason the backup file does not grow in size once it has reached about 133 Bytes." Sounds impossible.

I guess tomato only saves WAN monthly and daily in/out byte counts and no intraday history nor device-specific history?

I would also like to hear some numbers about the claim that saving to NVRAM or JFFS is dangerous. Is it so that using JFFS is much safer since the JFFS2 file system takes care of distributing the wear evenly throughout the large JFFS partition? I would calculate that if the memory can withstand 10,000 write cycles (I have heard that nowadays average flash memory can even withstand 100,000 cycles) and the size of the JFFS partition is 1 MB and the file is no more than 1 KB then the log can be saved at least 10,000,000 times, which makes over 1000 years if the log is saved every hour — so JFFS seems a pretty safe option (at least if the JFFS partition is not full of some other files (but maybe JFFS2 can do wear-leveling in those situations as well)). I do not know the details of the design of JFFS2 and its overhead, though.--84.50.143.71 (talk) 21:52, 24 June 2010 (UTC)

Classification (QoS)
Per the section describing the QoS -> Classification (qos-classify.asp) page: "Similarly, the order of rules can affect performance. For example, if an L7 rule is qualified as UDP this will help performance. But, if it is moved below the DNS rule (with a classification of 'Highest'), it will prevent packet inspection of all DNS connections which are also UDP." First of all "the DNS rule" is never defined and so this illustration does not clarify. It raises more questions. I suspect that the order of rules at this qos-classify.asp page is significant but I cannot find any better documentation. So here is a very specific clarifying question: I suspect that the earliest rule in the list takes effect.
 * If a packet matches two (or more) rules in the list specified at the qos-classify.asp page then does the earliest rule (in the list) take effect or does the latest rule take effect?

This behaviour would be consistent with my understanding that when no rule in the list matches for a given packet then the Default class specified on the QoS -> Basic Settings (qos-settings.asp) page takes effect.

Najevi (discuss • contribs) 02:32, 31 October 2012 (UTC)