Differences

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

--- admin-bwm [2023/05/13 21:40] – [Bandwidth Monitoring] -resized screenshot to 724x231 hogwild
+++ admin-bwm [2023/05/14 03:05] (current) – [Bandwidth Monitoring] -condense hogwild
@@ Line 1: / Line 1: @@
 ====== Bandwidth Monitoring ======
-The Bandwidth Monitoring menu contains settings for Bandwidth Monitoring features. It is divided into sections which include Bandwidth Monitoring, Backup (of monitoring statistics in rstats format) and Restore.
+The Bandwidth Monitoring menu contains settings for Bandwidth Monitoring features. This menu contains sections including Bandwidth Monitoring, Backup (of monitoring statistics in rstats format) and Restore.
 ===== Bandwidth Monitoring =====
@@ Line 7: / Line 8: @@
 [[https://wiki.freshtomato.org/lib/exe/detail.php?id=bandwidth_monitoring&media=cfd1bdbc52340668d45a53409a426089.png|{{:cfd1bdbc52340668d45a53409a426089.png?724}}]]
-**Enable:** This turns on the Bandwith Monitoring feature. (Default: Enabled).
+ \\
-**Save History Location:** This menu allows you choose where Bandwidth Monitoring history files are saved.
+**Enable:** Checking this turns on the Bandwidth Monitoring feature. (Default: Enabled).
-  * 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.
+**Save History Location:** From this menu, you choose where Bandwidth Monitoring history files are saved.
-  * 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|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 build, the less space there will be for JFFS2 partitions. The firmware upgrade process 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.
+The options include:
-  * 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 **[[:admin-cifs|CIFS Client]]** menu. CIFS is the Common Internet File System, a version of Microsoft's SMB networking protocol.
-  * CIFS2 - This will let FreshTomato write bandwidth statistics to the second external CIFS share. CIFS network shares are configured in the Administration/**[[:admin-cifs|CIFS Client]]**  menu.
+  * RAM (Temporary) - This will save Bandwidth Monitoring history files to the router's RAM.
-  * 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 separate data.
+    * Since this is temporary storage, contents will disappear after a reboot or crash.
+  * NVRAM - This will save Bandwidth Monitoring history to NVRAM.
+    * NVRAM is permanent storage, but is often tiny on routers.
+  * JFFS2 - This will save monitoring files to a portion of flash RAM formatted with JFS.
+    * JFFS is a journalling, log-structured file system.
+    * JFFS partitions are managed in the //Administration///**[[:jffs|JFFS]]** menu.
+    * Storage space available depends on your router hardware and the build installed.
+    * FreshTomato and any JFFS2 partitions share storage space on the same chip.
+    * The larger the build, the less space left for JFFS2 partitions.
+    * The upgrade process rewrites the whole flash chip, so data on JFFS is destroyed.
+    * To avoid this, FreshTomato stops you from upgrading firmware until JFFS is disabled.
+    * You must back up the data on JFFS storage before a firmware upgrade.
+  * CIFS1 - This makes FreshTomato write bandwidth logs to the first external CIFS network share.
+    * CIFS Client connections to CIFS shares are configured in the **[[:admin-cifs|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///**[[:admin-cifs|CIFS Client]]** menu.
+  * Custom Path - This allows you to create a custom directory within the JFFS2 storage space.
+    * This is useful when using JFFS2 for other storage tasks, so you can organize the storage into folders.
 (Default: RAM).
-**Save Frequency:**  This specifies how often Bandwith Monitoring saves statistics. (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 Frequency:**  This specifies how often Bandwidth Monitoring saves logs. (Default: TBD). The more often data is saved, the less likely it will be lost due to adverse events like power outages or crashes.
-**Save on Shutdown:**  Checking this makes FreshTomato immediately save bandwidth statistics if FreshTomato receives a shutdown signal. This prevents data loss.
+**Save on Shutdown:**  Checking this makes FreshTomato save bandwidth logs immediately if it 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). FreshTomato must create a new file in order for the statistics to be saved properly.
+**Create New File:**  Checking this erases your current log file and creates 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 logs to be saved properly.
-**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).
+**Create Backups:**  Enabling this makes FreshTomato create backup logs. The 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 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).
+**First Day of the Month:**  This value sets the first day of the month for bandwidth logs. For example, if you enter 3, FreshTomato makes the third day of each month the first day it records bandwidth monitoring. (Default: 1). This is useful with certain ISPs which log/bill for bandwidth starting on a day other than the first of the month.
-**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.
+**Excluded Interfaces:**  Here, you specify the device name of any interfaces whose bandwidth you don't want to be monitored/logged. If you list more than one, the names must be separated by commas.
 ===== Backup =====
-{{:1d93577512187e108da502690758ed50.png?774}}
+{{:1d93577512187e108da502690758ed50.png?726}}
-Here you can (re)name the backup bandwidth monitoring file, and back it up to a location you choose. In the empty field, you will see the default name of the statistics log file. If you click your cursor into that field, you can edit the filename given to the log file. Remember to click Save and wait for the changes to take effect.
+ \\
-Backup files are are saved in the standard Linux GNU .gz (gzip) file format. This is an archive format, similar to .zip, and can be easily opened by many programs across Windows, Linux, Macintosh and other systems.
+Here you can back up the bandwidth monitoring log file, naming it whatever you choose. FreshTomato creates a default filename, but clicking the cursor in the field lets you edit the log's filename. After you click Save, the new file name will take effect.
-**Backup:** Clicking on the Backup button will download the file to your web browser. The browser should open a window prompting you to either Open or Save the file. Generally, you choose Save, at which point your browser prompts you to browse for the location to save the backup log.
+Backup files are are saved in the GNU .gz (gzip) format. This is an archive format, similar to .zip. It can be easily opened by programs in Windows, Linux, and MacOS.
-Hovering your mouse over the blue link entitled "link" will make your browser display the full path of the Bandwidth Monitor backup file location in the browser's status area. Clicking on the blue "link" link will also prompt you for where you want to store the existing Bandwidth Monitor backup file.
+**Backup:** Clicking on the Backup button will download the log file to your browser. The browser will open a window prompting you to Open or Save the file. Generally, you click Save, and the browser prompts you to browse to the location to save the backup log.
+Hovering your mouse over the blue "link" will make your browser display the full path of the backup file location in the browser's status area. It will also prompt you for where to store the existing Bandwidth Monitor backup file.
+ \\
+ \\
 ===== Restore =====
-{{:058a13734928e6c9e5f9903d262c2d71.png?771}}
+{{:058a13734928e6c9e5f9903d262c2d71.png?723}}
+ \\
-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.
+The //Browse…// button lets you find existing Bandwidth Monitoring logs to restore to the location selected in the //Save History Location// menu. FreshTomato will expect to find a 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 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, continuing where it left off.

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools