This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
admin-bwm [2023/05/13 23:13] – [Bandwidth Monitoring] -condense hogwild | admin-bwm [2023/05/14 02:53] – [Bandwidth Monitoring] -condense hogwild | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Bandwidth Monitoring ====== | ====== Bandwidth Monitoring ====== | ||
- | The Bandwidth Monitoring menu contains settings for Bandwidth Monitoring features. | + | The Bandwidth Monitoring menu contains settings for Bandwidth Monitoring features. |
===== Bandwidth Monitoring ===== | ===== Bandwidth Monitoring ===== | ||
Line 21: | Line 22: | ||
* NVRAM is permanent storage, but is often tiny on routers. | * NVRAM is permanent storage, but is often tiny on routers. | ||
- | * JFFS2 - This will save monitoring files to a portion of flash RAM formatted with the Journalling Flash File System, | + | * JFFS2 - This will save monitoring files to a portion of flash RAM formatted with JFS |
- | * JFFS partitions are managed in the // | + | * JFFS is a journalling, |
+ | * JFFS partitions are managed in the // | ||
* Storage space available depends on router specifications and which build is installed. | * Storage space available depends on router specifications and which build is installed. | ||
* FreshTomato and any JFFS2 partitions share storage space on the same chip. | * FreshTomato and any JFFS2 partitions share storage space on the same chip. | ||
Line 38: | Line 40: | ||
* Custom Path - This allows you to create a custom directory within the JFFS2 storage space. | * 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, and want to organize your storage into folders. | + | * This is useful when using JFFS2 for other storage tasks, and you want to organize your storage into folders. |
(Default: RAM). | (Default: RAM). | ||
Line 59: | Line 61: | ||
{{: | {{: | ||
- | 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) | + | 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 |
- | Hovering your mouse over the blue link entitled | + | **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 " | ||
+ | |||
+ | \\ | ||
+ | |||
+ | \\ | ||
Line 72: | Line 80: | ||
{{: | {{: | ||
- | The Restore section contains a // | + | \\ |
+ | |||
+ | The // | ||
- | If you use the Restore | + | 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 |