Network Totals

[geffers]

Folks,

I use a Pi Zero for a headless ADS-B project, it is headless and just chugs away in the background.

I am curious as to how much data it sends on a daily basis and wonder which network tool I could use to monitor. I know of some that will give current transfer rates etc but I'd like to see how much is being sent.

I do use ntop on a different machine but not sure if or how it can monitor a different device.

Thanks in advance,

Geffers

[W. H. Heydt]

The command "ifconfig" shows accumulated traffic for each network interface.

[pcmanbob]

Here a python2 program I used to collect the amount data sent from one of my pi's, it originally updated every 60 seconds and only output the info in the terminal , but I have changed it to update every hour and output the info to a file ( /home/pi/TX_bytes.txt)

now there is no error trapping and it assumes you only have one network interface active.

posting here in case its of use to you, this is the stretch version if you need it for Jessie let me know.

Code: Select all

#!/usr/bin/python
# for Raspbian Stretch
import subprocess
import time
resultline = ""
value = ""
oldbytes = 0

def getifc():
    global resultline
    p = subprocess.Popen("ifconfig | grep 'TX packets'", stdout=subprocess.PIPE, shell=True)
    (output, err) = p.communicate()
    status = p.wait()
    resultline = output
    
def getbytes():
    global resultline , value
    data = resultline.split(" ")
    c = 0
    while True:
        # test for bytes value
        if data[c] == "bytes":
            value = float(data[c+1])
            if value > 0:
                break
            
        c = c + 1

getifc()
getbytes()
oldbytes = value        
        
while True:
    getifc()
    getbytes()
    newbytes = value
    sentbytes = newbytes - oldbytes
    dsentbytes = str(int(sentbytes))
    sentkib = sentbytes/1024
    dsentkib = str("%.2f" % sentkib)

    dataoutput = "bytes sent in last hour = " + dsentbytes + " (" + dsentkib + " KiB)"
    file = open("/home/pi/TX_bytes.txt","a")
    file.write(dataoutput + "\n")
    file.close()    
    oldbytes = newbytes
    time.sleep (3600)
    

[geffers]

The command "ifconfig" shows accumulated traffic for each network interface.

Thank you, that worked a treat, didn't realise TX bytes were an accumulation.

Geffers

[geffers]

Here a python2 program I used to collect the amount data sent from one of my pi's, it originally updated every 60 seconds and only output the info in the terminal , but I have changed it to update every hour and output the info to a file ( /home/pi/TX_bytes.txt)

now there is no error trapping and it assumes you only have one network interface active.

posting here in case its of use to you, this is the stretch version if you need it for Jessie let me know.

That will be very useful.

I currently an now using ifconfig | grep "TX bytes" and just write it to a log file every hour but I am trying to learn terminal and python scripts so will try your's out.

Thank you.

Geffers

[allfox]

I was told ifconfig is the old working stuff. There is a reinvented wheel:

ip -s link

It's NEW

[pcmanbob]

I was told ifconfig is the old working stuff. There is a reinvented wheel:

ip -s link

It's NEW

Tried the new wheel

Code: Select all

pi@StretchTest:~ $ ip -s link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT               group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    RX: bytes  packets  errors  dropped overrun mcast
    0          0        0       0       0       0
    TX: bytes  packets  errors  dropped carrier collsns
    0          0        0       0       0       0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mo              de DEFAULT group default qlen 1000
    link/ether b8:27:eb:ea:9b:2f brd ff:ff:ff:ff:ff:ff
    RX: bytes  packets  errors  dropped overrun mcast
    2974       22       0       0       0       0
    TX: bytes  packets  errors  dropped carrier collsns
    9099       55       0       0       0       0

think I prefer the old one contains more information and easier to search and pick out data using a python program.

Code: Select all

pi@StretchTest:~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.16  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::bb67:3a18:6c31:133b  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:ea:9b:2f  txqueuelen 1000  (Ethernet)
        RX packets 55  bytes 5677 (5.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 77  bytes 12535 (12.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[geffers]

I was told ifconfig is the old working stuff. There is a reinvented wheel:

ip -s link

It's NEW

Tried the new wheel

think I prefer the old one contains more information and easier to search and pick out data using a python program.

Yep, think I prefer the older wheel.

Geffers