This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
admin-bwm [2024/10/21 01:00] – [Bandwidth Monitoring] -Formatting-remove bolding from links 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 ====== | ====== Bandwidth Monitoring ====== | ||
- | This menu contains settings for Bandwidth Monitoring features. The menu contains | + | This menu contains settings for Bandwidth Monitoring features. The menu sections |
===== Bandwidth Monitoring ===== | ===== Bandwidth Monitoring ===== | ||
- | [[https:// | + | {{:: |
\\ | \\ | ||
- | **Enable: | + | **Enable: |
+ | |||
+ | (Default: Enabled). | ||
\\ | \\ | ||
- | **Save History Location: | + | **Save History Location: |
\\ | \\ | ||
- | * RAM (Temporary) * - will save Bandwidth Monitoring history files to the router' | + | * RAM (Temporary) * - makes Bandwidth Monitoring |
- | * Since this is temporary storage, **contents | + | * This is temporary storage. **Contents |
* NVRAM - will save Bandwidth Monitoring history to NVRAM. | * NVRAM - will save Bandwidth Monitoring history to NVRAM. | ||
- | * NVRAM is permanent storage. However, but in routers, | + | * NVRAM is permanent storage, but in routers, is often very small. |
- | * JFFS2 - will save monitoring files to a portion of flash RAM formatted with JFFS. | + | * JFFS2 - will save monitoring files to a JFFS-formatted |
* JFFS is a journaling, log-structured file system. | * JFFS is a journaling, log-structured file system. | ||
- | * JFFS partitions are managed in the [[: | + | * JFFS is managed in the [[: |
- | * Space available depends on the router model/ | + | * Space available depends on the router model/ |
* FreshTomato and JFFS2 partitions share space on the same chip. | * FreshTomato and JFFS2 partitions share space on the same chip. | ||
- | * The larger the build, the less space left for JFFS2 partitions. | + | * Larger builds have less space left for JFFS2 partitions. |
- | * The upgrade process rewrites the whole flash chip, so JFFS data are destroyed. | + | * The upgrade process rewrites the whole flash chip. JFFS data are destroyed. |
- | * To avoid this, FreshTomato blocks firmware upgrades until JFFS is disabled.\\ * The above depends on the feature being enabled in the [[admin-access|Admin Access]] | + | * To stop this, FreshTomato blocks firmware upgrades until JFFS is disabled.\\ * This depends on the feature being enabled in [[admin-access|Admin Access]]. |
- | * You must back up the data on JFFS storage before a firmware upgrade. | + | * Data on JFFS storage |
- | * CIFS1 - makes FreshTomato write bandwidth logs to the first external | + | * CIFS1 - makes FreshTomato write bandwidth logs to the first CIFS share. |
- | * CIFS Client | + | * CIFS client |
* CIFS2 - makes FreshTomato write bandwidth data to the second external CIFS share. | * CIFS2 - makes FreshTomato write bandwidth data to the second external CIFS share. | ||
- | * CIFS network shares are configured in the [[: | ||
* Custom Path - Lets you create a custom directory within JFFS2 storage space. | * Custom Path - Lets you create a custom directory within JFFS2 storage space. | ||
- | * When using JFFS2 for other storage | + | * When using JFFS2 for other tasks, this lets you organize storage in folders. |
- | + | ||
- | (Default: RAM). | + | |
\\ | \\ | ||
- | **Save Frequency: | + | **Save Frequency: |
- | The more often data are saved, the less likely they' | + | The more often they' |
\\ | \\ | ||
- | **Save on Shutdown: | + | **Save on Shutdown: |
This prevents data loss. | This prevents data loss. | ||
Line 57: | Line 57: | ||
\\ | \\ | ||
- | **Create New File: | + | **Create New File: |
- | This is useful | + | This helps when switching |
\\ | \\ | ||
- | **Create Backups: | + | **Create Backups: |
- | Backups are put in the same folder as the original files, and given a .bak file ending. (Default: Disabled). | + | Backups are put in the same folder as the original files, and given a ".bak" |
\\ | \\ | ||
- | **First Day of the Month: | + | **First Day of the Month: |
- | Thus, " | + | Thus, " |
\\ | \\ | ||
- | **Excluded Interfaces: | + | **Excluded Interfaces: |
Multiple names must be separated by commas. | Multiple names must be separated by commas. | ||
Line 82: | Line 82: | ||
===== Backup ===== | ===== Backup ===== | ||
- | {{:1d93577512187e108da502690758ed50.png?726}} | + | {{:: |
\\ | \\ | ||
- | Here, you can back up the bandwidth monitoring log file, with whatever | + | 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 |
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 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. | ||
Line 92: | Line 92: | ||
\\ | \\ | ||
- | **Backup: | + | **Backup: |
- | The browser | + | The browser |
Hovering your mouse over the blue word " | Hovering your mouse over the blue word " | ||
Line 103: | Line 103: | ||
===== Restore ===== | ===== Restore ===== | ||
- | {{:058a13734928e6c9e5f9903d262c2d71.png?723}} | + | {{:: |
\\ | \\ | ||
- | The // | + | The // |
- | If you Restore an existing Bandwidth Monitoring log to the same location it was originally | + | 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. |
- | \\ \\ | + | \\ |