currently Fort Firewall has replaced the combination of TMeter & Simplewall for me because it elegantly combines both uses - a local traffic limiter as well as a powerful application-based firewall.
The only thing that I am missing is an option to change the averaging interval of the traffic graph or at least the update rate (at least up to 30-60s) so it can make streaming bandwidth usage more presentable instead of a graph spikes jumping up and down to 0 because of most services like Youtube downloading chunks in bursts.
So I additionally use "Net Traffic Portable" as a standalone traffic graph tool just for that.
Example graph attached. Every column represents an averaging over 10 seconds.
It would be good if there were options available to smoothen the Fort Firewall graph to custom intervals and also choose between bit/byte/iByte basis for the dynamic scaling but possibly even choose all-time fixed unit of measure (i.e. MiB/s , KiB/s, MB/s, KB/s, Mbit/s, Kbit/s...). Currently it is always in *bps which is not an optimal human readable unit to have a feeling for.
If something like that, in accordance to your preferred design, is feasible for you to do. Thanks!
Hi,
currently Fort Firewall has replaced the combination of TMeter & Simplewall for me because it elegantly combines both uses - a local traffic limiter as well as a powerful application-based firewall. The only thing that I am missing is an option to change the averaging interval of the traffic graph or at least the update rate (at least up to 30-60s) so it can make streaming bandwidth usage more presentable instead of a graph spikes jumping up and down to 0 because of most services like Youtube downloading chunks in bursts.
So I additionally use "Net Traffic Portable" as a standalone traffic graph tool just for that. Example graph attached. Every column represents an averaging over 10 seconds.
It would be good if there were options available to smoothen the Fort Firewall graph to custom intervals and also choose between bit/byte/iByte basis for the dynamic scaling but possibly even choose all-time fixed unit of measure (i.e. MiB/s , KiB/s, MB/s, KB/s, Mbit/s, Kbit/s...). Currently it is always in *bps which is not an optimal human readable unit to have a feeling for.
If something like that, in accordance to your preferred design, is feasible for you to do. Thanks!