Linux – Bandwidth Monitoring

command linemonitoringnetworking

I just need to get how much bandwidth is used in 3 or 4 days. Do you have any application in the terminal to do it?

I'd prefer if it didn't use SNMP.

I found iptraf, wireshark, cacti, but they were not what I am looking for.

Of course I need to save my results; for a single computer, not a network.

It's very important that I can see the total size of inbound and outboud traffic.
What solutions are there for me?

Best Answer

You know you already have that with ifconfig right?

Ifconfig keeps counters about your incomming and outgoing bandwidth on each interface by default. Usually you can't reset counters except rebooting (with a few exceptions)

From console you can easily leave a cron running each three days and saving results to a file for later check. Something like this:

date >> ~/bw.log && ifconfig eth0|grep byte >> ~/bw.log

Will produce this kind of output per run on the file bw.log at users home.

Thu Oct 18 03:44:05 UTC 2012
      RX bytes:414910161 (395.6 MiB)  TX bytes:68632105 (65.4 MiB)

My two cents...

Related Solutions

CentOS – How to Limit the Bandwidth Used by a Process

You can use iptables to mark a packet (--pid-owner ...), then use tc to shape the traffic. Also "--sid-owner" can be used to include threads and children of that process.

http://www.frozentux.net/iptables-tutorial/iptables-tutorial.html#OWNERMATCH

Match --pid-owner
Kernel 2.3, 2.4, 2.5 and 2.6
Example iptables -A OUTPUT -m owner --pid-owner 78
Explanation This match is used to match packets based on the Process ID (PID) that was responsible for them. This match is a bit harder to use, but one example would be only to allow PID 94 to send packets from the HTTP port (if the HTTP process is not threaded, of course). Alternatively we could write a small script that grabs the PID from a ps output for a specific daemon and then adds a rule for it. For an example, you could have a rule as shown in the Pid-owner.txt example

Monitor mode wifi only seeing broadcast packets

Look at your post, especially the message

(monitor mode enabled on mon0)

So... capture on mon0, NOT wlan0!

ie:

airmon-ng start wlan0
airodump-ng mon0

.. you'll notice no channel-hopping. You'll need a workaround to get it grabbing the full spectrum! Sooo...

airodump-ng mon0

airmon-ng stop wlan0      # gets channel hopping going (but obviously stops wlan0)

airodump-ng mon0

Best Answer

Related Solutions

CentOS – How to Limit the Bandwidth Used by a Process

Monitor mode wifi only seeing broadcast packets

Related Question