This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
admin-bwm [2023/05/13 22:06] – [Bandwidth Monitoring] -formatting-bullet spacing hogwild | admin-bwm [2023/05/14 03:05] (current) – [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 16: | Line 17: | ||
* RAM (Temporary) - This will save Bandwidth Monitoring history files to the router' | * RAM (Temporary) - This will save Bandwidth Monitoring history files to the router' | ||
- | * This is temporary storage, | + | * Since this is temporary storage, contents will disappear after a reboot or crash. |
* NVRAM - This will save Bandwidth Monitoring history to NVRAM. | * NVRAM - This will save Bandwidth Monitoring history to NVRAM. | ||
* 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 Administration/ | + | * JFFS is a journalling, |
- | * Storage space available depends on router | + | * JFFS partitions are managed in the //Administration/// |
+ | * Storage space available depends on your router | ||
* FreshTomato and any JFFS2 partitions share storage space on the same chip. | * FreshTomato and any JFFS2 partitions share storage space on the same chip. | ||
- | * The larger the build, the less space there will be for JFFS2 partitions. | + | * The larger the build, the less space left for JFFS2 partitions. |
- | * The upgrade process | + | * The upgrade process |
- | * To avoid this, FreshTomato | + | * To avoid this, FreshTomato |
- | * You must back up the data on your JFFS storage before a firmware upgrade. | + | * 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. | * CIFS1 - This makes FreshTomato write bandwidth logs to the first external CIFS network share. | ||
- | * CIFS Client connections to CIFS shares are configured in the **[[: | + | * CIFS Client connections to CIFS shares are configured in the **[[: |
- | * CIFS is the Common Internet File System, a version of Microsoft' | + | * |
* CIFS2 - This will let FreshTomato write bandwidth statistics to the second external CIFS share. | * CIFS2 - This will let FreshTomato write bandwidth statistics to the second external CIFS share. | ||
- | * CIFS network shares are configured in the Administration/ | + | * CIFS network shares are configured in the //Administration/// |
- | * 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, | + | * 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, | ||
(Default: RAM). | (Default: RAM). | ||
- | **Save Frequency: | + | **Save Frequency: |
- | **Save on Shutdown: | + | **Save on Shutdown: |
- | **Create New File: | + | **Create New File: |
- | **Create Backups: | + | **Create Backups: |
- | **First Day of the Month: | + | **First Day of the Month: |
- | **Excluded Interfaces: | + | **Excluded Interfaces: |
Line 58: | Line 60: | ||
{{: | {{: | ||
- | 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 71: | Line 79: | ||
{{: | {{: | ||
- | 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 |