This menu contains settings for Bandwidth Monitoring features. The menu contains sections including Bandwidth Monitoring, Backup (of monitoring statistics in rstats format) and Restore.

Enable: Turns on the Bandwidth Monitoring feature. (Default: Enabled).

Save History Location: Allows you to choose where Bandwidth Monitoring history files are saved.

• RAM (Temporary) * - makes Bandwidth Monitoring save history files to RAM.
  • This is temporary storage. Contents will disappear after a reboot/crash.

• NVRAM - will save Bandwidth Monitoring history to NVRAM.
  • NVRAM is permanent storage. However, but in routers, it is often very small.

• JFFS2 - will save monitoring files to a JFFS-formatted portion of flash RAM.
  • JFFS is a journaling, log-structured file system.
  • JFFS is managed in the 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.
  • You must back up the data on JFFS storage before a firmware upgrade.

• CIFS1 - makes FreshTomato write bandwidth logs to the first CIFS share.
  • CIFS client connections to CIFS shares are configured in CIFS Client.
• CIFS2 - makes FreshTomato write bandwidth data to the second external CIFS share.

• 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.

(Default: RAM).

Save Frequency: Specifies how often Bandwidth Monitoring saves logs. (Default: TBD).

The more often data are saved, the less likely they'll be lost due to adverse events like power outages or crashes.

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 media/locations (say, moving from RAM to CIFS). FreshTomato must create a new file for logs to be saved 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. (Default: 1). This is useful with ISPs that log/bill for bandwidth starting on a day other than the first of the month.

Excluded Interfaces: Specifies the device names of interfaces whose bandwidth not to monitor/log.

Multiple names must be separated by commas.

Here, you can back up the bandwidth monitoring log file, with whatever name you wish. FreshTomato creates a default filename, but clicking the cursor in the field lets you change the file name. 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 this button downloads the log file to your browser.

The browser will open a window prompting 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.

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.

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.