05-06-2008
NetFlow
You could try AdventNet ManageEngine NetFlowAnalyzer. There is a free version that will allow the monitoring of 2 router interfaces. If you plan carefully you can catch all the traffic at least to the internet. It will filter down to the host level also telling you what type of traffic is being used. Some apps you may have to setup the ports and what they're being used for.
manageengine.adventnet.com
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm on T1, is there any way i can check my acctual bandwidth?
Thank you all (3 Replies)
Discussion started by: solvman
3 Replies
2. IP Networking
i have two questions actually...
i need to block certain ports with openbsd and PF in a large lan, the firewall is supposed to be a router between the internet and the first lan switch.
first of all, would this work at all in theory?
second, i tried doing this a few days ago at a huge lan but i... (2 Replies)
Discussion started by: nocturnal
2 Replies
3. IP Networking
Hello,
I was wondering how one would go about regulating bandwidth of a server running RH Linux 8.0 and Apache. I am running a webserver, and want only one person to be able to download one file at a time. So, they can't click about 10 files and soak up lots of bandwidth. Plus, I would like to cap... (2 Replies)
Discussion started by: Phobos
2 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I'm looking for some way to bring up in a shell window a realtime (or something that updates at 10 second intervals or whatever) bandwidth monitor.
I just want something that shows me how much kbps is going in and how much is going out of each interface. Is there something that might... (2 Replies)
Discussion started by: d11wtq
2 Replies
5. UNIX for Advanced & Expert Users
Hi Gurus,
Need to have a way to monitor Bandwidth utilization on Linux servers, running squid .
Have worked on 3rd party monitoring tools like Bandwidth d, Nagios etc.
But we are working to find out a way to monitor this through Sitescope, for which we need to find a file where the... (4 Replies)
Discussion started by: Crazy_murli
4 Replies
6. IP Networking
Hi,
1-What is bandewidth ?
2-How to calculate ?
3-How to measure ? Any free software to measure it ?
Many thanks. (4 Replies)
Discussion started by: big123456
4 Replies
7. Programming
I wish to develop an application to monitor the network traffic of my system.
I wish to know which computer networked to me is using most of the bandwidth. I know the basics of python but do not know how to start the work.. please suggest some good methods to follow. (7 Replies)
Discussion started by: coderhs
7 Replies
8. IP Networking
Many papers, articles and posts about network bandwidth requirements refer to network traffic rules-of-thumb when estimating bandwidth requirements for a new network with an unknown load. I've seen a couple rules for video and VoIP.
I'd be thankful if someone could share any rules-of thumb they... (5 Replies)
Discussion started by: redrider
5 Replies
LEARN ABOUT OSF1
niffconfig
niffconfig(8) System Manager's Manual niffconfig(8)
NAME
niffconfig - Configuration program for the Network Interface Failure Finder (NIFF)
SYNOPSIS
/usr/sbin/niffconfig [-a] [-m] [-r] [-s] [-u] [-v] [-d num] [-o num] [-t num] [interface1 interface2...]
OPTIONS
Adds an interface or interfaces, specified by the interface parameter. You cannot specify the -a option with the -m, -s, -r, or -u options.
Specifies the time period, in seconds, that the traffic monitor thread uses between reads of the interface counters when it suspects there
is a connectivity problem. This number must be smaller than the number given for the -t option. The default time period is 5 seconds. If
num is not specified, niffconfig uses the default. Specifies the total number of traffic-free seconds that must elapse before the traffic
monitor thread determines that a network interface has failed. This number must be at least the sum of the -d option and two times the -t
option. That is, given the default time period for -d and -t, the -o option must be at least 20 seconds. The default time period for this
option is 60 seconds. If num is not specified, niffconfig uses the default. Modifies the timing parameters of an interface that is already
being monitored. Typically, this option is specified along with one or more of -t num, -d num, or -o num options. If none of these parame-
ters are specified, the default value is used. You cannot specify the -m option with the -a, -s, -r, or -u options. Stops monitoring the
specified interface. Obtains the status of the specified interface. Specifies the time period, in seconds, that the traffic monitor
thread delays between reads of the interface counters when the network is running normally. The default time period is 20 seconds. If num
is not specified, niffconfig uses the default. Displays the status of all interfaces currently being monitored to standard out (stdout).
Displays the status, timer values, and description (verbose mode) of all interfaces currently being monitored to standard out (stdout).
DESCRIPTION
The niffconfig command arranges for one or more network interfaces to be monitored for possible loss of connectivity. Timing parameters
that govern how quickly an interface can be declared suspect or dead may be manipulated with this command. You can specify multiple inter-
faces, separated by a space, on the command line. Note, you must be superuser to use the niffconfig command.
Except for the -u and -u options, all niffconfig options require one or more network interfaces to be specified.
EXAMPLES
To add the tu0 and tu1 interfaces to the list of monitored interfaces, enter: # niffconfig -a tu0 tu1 To change the time it takes to
declare failure on the tu1 interface to 90 seconds, enter: # niffconfig -o 90 tu1 To display the status of all interfaces that are being
monitored: # niffconfig -u To stop monitoring the tu0 interface: # niffconfig -r tu0
SEE ALSO
Daemons: niffd(8)
Information: EVM(5), nifftmt(7)
niffconfig(8)