1 The latest version of this FAQ is available at
3 https://humdi.net/vnstat/FAQ
10 A snapshot of the FAQ (updated 13.4.2019):
13 I managed to get invalid data into the database after ... playing around with
14 the system clock / doing some strange network experiments / having the cron
15 entry not properly configured. Is there a database editor available?
17 Nothing vnStat specific is available. The sqlite3 command can be used to
18 read and modify the database.
21 How do I stop monitoring an interface?
23 Execute "vnstat --remove -i interfacename" with correct permissions.
26 How do I uninstall vnStat?
28 You only need to run 'make uninstall' in the directory that comes when the
29 .tar.gz is extracted. Just make sure it's the same version you have
30 installed. If you've used a binary package included with the distribution
31 then refer to intructions provided by the package manager.
34 What is this KiB/MiB/GiB/TiB thing?
36 See http://en.wikipedia.org/wiki/Binary_prefix#Prefixes and UnitMode
37 option in the configuration file.
40 Is the MB value reported by vnStat 10^6 or 2^20 bytes?
42 2^20 bytes. The prefix can be configured to show MiB from the configuration
43 file instead of MB if that looks better.
46 What does the 'estimated' value mean?
48 The estimated value is an calculated average that tries to predict the total
49 traffic for the current day/month based on previous traffic. This estimate
50 works fairly well if the monitored interface has constant traffic of the same
51 magnitude (like game servers). It can't predic peaks but the accuracy
52 usually gets better by the end of the day/month.
55 Why isn't the estimated value shown with --json or xml outputs?
57 Those features only dump the database and since the estimate is always
58 calculated in real time, there's no reason to write it into the database.
61 How is the estimated value calculated?
63 estimate = ( x / y ) * z
65 x = traffic so far for the day/month
66 y = passed minutes/hours ...
67 z = total minutes/hours ...
72 If the latest version isn't being used then test if the issue can still
73 be replicated with the latest or latest development version. If the issue
74 can still be reproduced, check if there's already an issue open in GitHub.
75 If not then using https://github.com/vergoh/vnstat/issues for reporting new
76 issues is suggested. Any bug report should at least include an explanation
77 about how the bug can be reproduced. Also include information about the used
78 distribution, kernel (uname -a), compiler (gcc --version) and network
79 interface card. Read the report again before sending it. :)