Differences

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

--- admin-bwm [2024/09/24 02:33] – [Restore] -formatting hogwild
+++ admin-bwm [2024/11/29 00:00] (current) – [Restore] -Replace screenshot with: "administration-bandwidth_monitor-restore-2024.3.png" @ 472 hogwild
@@ Line 1: / Line 1: @@
 ====== Bandwidth Monitoring ======
-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.
+This menu contains settings for Bandwidth Monitoring features. The menu sections include Bandwidth Monitoring, Backup (of monitoring statistics in rstats format) and Restore.
 ===== Bandwidth Monitoring =====
-[[https://wiki.freshtomato.org/lib/exe/detail.php?id=bandwidth_monitoring&media=cfd1bdbc52340668d45a53409a426089.png|{{:cfd1bdbc52340668d45a53409a426089.png?724}}]]
+{{::bandwidth_monitor-bandwidth_monitor-2024.3.png?679}}
  \\
-**Enable:** Checking this turns on the Bandwidth Monitoring feature. (Default: Enabled).
+**Enable:** turns on the Bandwidth Monitoring feature.
-**Save History Location:** From this menu, you choose where Bandwidth Monitoring history files are saved.
+(Default: Enabled).
-The options include:
+ \\
-  * RAM (Temporary) - This will save Bandwidth Monitoring history files to the router's RAM.
+**Save History Location:** lets you choose where Bandwidth Monitoring history files are saved.
-    * 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.
+  * RAM (Temporary) * - makes Bandwidth Monitoring save history files to RAM.
-    * JFFS is a journalling, log-structured file system.
+    * This is temporary storage. **Contents will disappear after a reboot/crash**.
-    * 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.
+  * NVRAM - will save Bandwidth Monitoring history to NVRAM.
-    * CIFS Client connections to CIFS shares are configured in the **[[:admin-cifs|CIFS Client]]** menu.
+    * NVRAM is permanent storage, but in routers, is often very small.
-    *
-  * 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.
+  * JFFS2 - will save monitoring files to a JFFS-formatted portion of flash RAM.
-    * This is useful when using JFFS2 for other storage tasks, so you can organize the storage into folders.
+    * JFFS is a journaling, log-structured file system.
+    * JFFS is managed in the [[:jffs|JFFS]] menu.
+    * Space available depends on the router model/build.
+    * FreshTomato and JFFS2 partitions share space on the same chip.
+    * Larger builds have less space left for JFFS2 partitions.
+    * The upgrade process rewrites the whole flash chip. JFFS data are destroyed.
+    * To stop this, FreshTomato blocks firmware upgrades until JFFS is disabled.\\ * This depends on the feature being enabled in [[admin-access|Admin Access]].
+    * Data on JFFS storage must be backed up before a firmware upgrade.
-(Default: RAM).
+  * CIFS1 - makes FreshTomato write bandwidth logs to the first CIFS share.
+    * CIFS client connections to CIFS shares are configured in [[:admin-cifs|CIFS Client]].
+  * CIFS2 - makes FreshTomato write bandwidth data to the second external CIFS share.
-**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.
+  * Custom Path - Lets you create a custom directory within JFFS2 storage space.
+    * When using JFFS2 for other tasks, this lets you organize storage in folders.
-**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 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.
+**Save Frequency:** specifies how often Bandwidth Monitoring saves logs.
-**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).
+The more often they're saved, the less likely they'll be lost due to adverse events like power outages or crashes.
-**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 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.
+**Save on Shutdown:** makes FreshTomato save bandwidth logs immediately if it sees a shutdown signal.
+This prevents data loss.
+ \\
+**Create New File:** erases the current log file and creates a new one.
+This helps when switching storage locations (say, moving from RAM to CIFS). FreshTomato must create a new file for logs to save properly.
+ \\
+**Create Backups:** enabling this makes FreshTomato create backup logs.
+Backups are put in the same folder as the original files, and given a ".bak" file ending. (Default: Disabled).
+ \\
+**First Day of the Month:** sets the first day of the month for bandwidth logs.
+Thus, "3" means FreshTomato makes the third day of each month the first day it records bandwidth monitoring. This is useful with ISPs that log/bill for bandwidth starting on a day other than the first of the month. (Default: 1).
+ \\
+**Excluded Interfaces:** specifies the device names of interfaces whose bandwidth not to monitor/log.
+Multiple names must be separated by commas.
 ===== Backup =====
-{{:1d93577512187e108da502690758ed50.png?726}}
+{{::administration-bandwidth_monitor-backup-2024.3.png?616}}
  \\
-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.
+Here, you can back up the bandwidth monitoring log file, to any file name you wish. FreshTomato creates a default filename, but clicking the cursor in the field lets you change it. After clicking Save, the new filename will take effect.
 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.
-**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.
+**Backup:** clicking this downloads the log file to your browser.
- \\
+The browser opens a window asking you to Open or Save the file. Generally, click Save and the browser prompts you to browse to the location to save the log.
+Hovering your mouse over the blue word "link" makes your browser display the full backup file path in the status area. It will also prompt you where to store the existing Bandwidth Monitor backup file.
  \\
@@ Line 77: / Line 103: @@
 ===== Restore =====
-{{:058a13734928e6c9e5f9903d262c2d71.png?723}}
+{{::administration-bandwidth_monitor-restore-2024.3.png?472}}
  \\
-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.
+The //Browse…// button lets you find existing Bandwidth Monitoring logs to restore to the location selected in the //Save History Location// dropdown. FreshTomato will expect to find a GNU .gz (gzip) archive file.
+If you Restore an existing Bandwidth Monitoring log to the same location it was first stored, FreshTomato will continue to log bandwidth statistics to the same file, continuing 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