This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
admin-bwm [2023/05/13 21:41] – [Backup] -resize screenshot to 726x78 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 7: | Line 8: | ||
[[https:// | [[https:// | ||
- | **Enable:** This turns on the Bandwith Monitoring feature. (Default: Enabled). | + | \\ |
- | **Save History Location:** This menu allows you choose where Bandwidth Monitoring | + | **Enable:** Checking this turns on the Bandwidth Monitoring |
- | | + | **Save History Location:** From this menu, you choose where Bandwidth Monitoring history files are saved. |
- | * NVRAM - This saves Bandwidth Monitoring history to the router' | + | |
- | * JFFS2 - This will save monitoring files to a portion of the router' | + | 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 **[[: | + | |
- | * CIFS2 - This will let FreshTomato write bandwidth statistics to the second external CIFS share. 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, | + | * Since this is temporary |
+ | |||
+ | * 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, | ||
+ | * JFFS partitions are managed | ||
+ | * Storage | ||
+ | * FreshTomato and any JFFS2 partitions | ||
+ | * The larger the build, the less space left for JFFS2 partitions. | ||
+ | * The upgrade process | ||
+ | * To avoid this, FreshTomato | ||
+ | * 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 **[[: | ||
+ | * | ||
+ | * CIFS2 - This will let FreshTomato write bandwidth statistics to the second external CIFS share. | ||
+ | * 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 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 37: | 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 " | ||
+ | |||
+ | \\ | ||
+ | |||
+ | \\ | ||
===== Restore ===== | ===== Restore ===== | ||
- | {{: | + | {{: |
+ | |||
+ | \\ | ||
- | 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 |