Differences

This shows you the differences between two versions of the page.

--- bandwidth_monitoring [2021/02/01 04:17]
hogwild [Restore]
+++ bandwidth_monitoring [2021/11/12 00:55] (current)
djk44883 specify device name - not specific Linux name
@@ Line 14: / Line 14: @@
    * RAM (Temporary) - This saves Bandwidth Monitoring history files to the router's RAM. It is temporary, since the contents disappear after a reboot, or a crash.
   * NVRAM - This saves Bandwidth Monitoring history to the router's NVRAM. NVRAM is permanent storage, but is often tiny on routers due to its higher cost.
-  * JFFS2 - This will save monitoring files to a portion of the router's flash RAM that is formatted with the Journalling Flash File System, a log-structured file system. JFFS partitions are created and formatted in the Administration/**JFFS**  menu. The storage space available will depend on the router's specifications, and the type/size of Tomato build installed. Tomato and any JFFS2 partitions occupy storage space on the same chip. Therefore, the larger the Tomato build, the less space there will be for JFFS2 partitions created. The process of firmware upgrades must rewrite the whole flash chip, and data on JFFS is destroyed. To avoid this, Tomato prevents you from allowing a firmware upgrade until JFFS is disabled. You will need to back up the data on your JFFS storage before a firmware upgrade.
+  * JFFS2 - This will save monitoring files to a portion of the router's flash RAM that is formatted with the Journalling Flash File System, a log-structured file system. JFFS partitions are created and formatted in the Administration/**JFFS**  menu. The storage space available will depend on the router's specifications, and the type/size of FreshTomato build installed. FreshTomato and any JFFS2 partitions occupy storage space on the same chip. Therefore, the larger the FreshTomato build, the less space there will be for JFFS2 partitions created. The process of firmware upgrades must rewrite the whole flash chip, and data on JFFS is destroyed. To avoid this, FreshTomato prevents you from allowing a firmware upgrade until JFFS is disabled. You will need to back up the data on your JFFS storage before a firmware upgrade.
-  * CIFS1 - This will make Tomato write bandwidth logs to the first external CIFS network share configured. CIFS Client connections to CIFS shares are configured in the Administration/**CIFS Client**  menu. CIFS is the Common Internet File System, a version of Microsoft's SMB networking protocol.
+  * CIFS1 - This will make FreshTomato write bandwidth logs to the first external CIFS network share configured. CIFS Client connections to CIFS shares are configured in the Administration/**CIFS Client**  menu. CIFS is the Common Internet File System, a version of Microsoft's SMB networking protocol.
-  * CIFS2 - This will let Tomato write bandwidth statistics to the second external CIFS share. CIFS network shares are configured in the Administration/**CIFS Client**  menu.
+  * CIFS2 - This will let FreshTomato write bandwidth statistics to the second external CIFS share. CIFS network shares are configured in the Administration/**CIFS Client**  menu.
   * Custom Path. This allows you to create a custom directory within the JFFS2 storage space. This is useful when you are also using JFFS2 for other storage tasks, and want to organize your storage into folders to keep data separate.
@@ Line 23: / Line 23: @@
 **Save Frequency:**  This specifies how often Bandwith Monitoring saves statistics to disk. (Default: TBD). The more often data is saved, the less likely you are to lose it due to bad events such as power outages or crashes.
-**Save on Shutdown:**  Checking this makes Tomato immediately save bandwidth statistics to disk if Tomato receives a shutdown signal. This prevents data loss.
+**Save on Shutdown:**  Checking this makes FreshTomato immediately save bandwidth statistics to disk if FreshTomato receives a shutdown signal. This prevents data loss.
-**Create New File:**  Checking this will erase your current statistics file and create a new one. This is useful when you switch storage media/locations (such as moving from RAM to CIFS). Tomato must create a new file in order for the statistics to be saved properly.
+**Create New File:**  Checking this will erase your current statistics file and create a new one. This is useful when you switch storage media/locations (such as moving from RAM to CIFS). FreshTomato must create a new file in order for the statistics to be saved properly.
-**Create Backups:**  Enabling this makes Tomato create backup statistics logs. These backups are put in the same folder as the original files, and given a .bak file ending. (Default: Disabled).
+**Create Backups:**  Enabling this makes FreshTomato create backup statistics logs. These backups are put in the same folder as the original files, and given a .bak file ending. (Default: Disabled).
-**First Day of the Month:**  The number entered here sets the first day of the month for Tomato's bandwidth logs. For example, if you entered 3, Tomato would make the third day of each month the first day to be recorded for bandwidth monitoring. This is usually set at 1. However, it is handy for use on certain Internet providers, which log/bill for bandwidth starting on a day other than the first day of the month. (Default: 1).
+**First Day of the Month:**  The number entered here sets the first day of the month for FreshTomato's bandwidth logs. For example, if you entered 3, FreshTomato would make the third day of each month the first day to be recorded for bandwidth monitoring. This is usually set at 1. However, it is handy for use on certain Internet providers, which log/bill for bandwidth starting on a day other than the first day of the month. (Default: 1).
-**Excluded Interfaces:**  Here you can specify the Linux device name of any interfaces whose bandwidth you do not want to have monitored/logged. If you list multiple interfaces, the names should be separated with commas.
+**Excluded Interfaces:**  Here you can specify the device name of any interfaces whose bandwidth you do not want to have monitored/logged. If you list multiple interfaces, the names should be separated with commas.
 ====   ====
@@ Line 53: / Line 53: @@
 {{:058a13734928e6c9e5f9903d262c2d71.png}}
-The Restore section contains a //Browse…// button which allows you go and find existing Bandwidth Monitoring logs you wish to restore to the storage location selected in the //Save History Location// menu. Tomato will expect to find the a Linux/GNU .gz (gzip) archive file.
+The Restore section contains a //Browse…// button which allows you go and find existing Bandwidth Monitoring logs you wish to restore to the storage location selected in the //Save History Location// menu. FreshTomato will expect to find the a Linux/GNU .gz (gzip) archive file.
+If you use the Restore function to restore an existing Bandwidth Monitoring log to the same location it was originally stored, FreshTomato will continue to log bandwidth statistics to the same file, picking up where it left off.
-If you use the Restore function to restore an existing Bandwidth Monitoring log to the same location it was originally store, Tomato will continue to log bandwidth statistics to the same file, picking up where it left off.
-==== Technical notes and troubleshooting. ====

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools