search

vergoh / vnstat

vnStat - a network traffic monitor for Linux and BSD
GNU General Public License v2.0
1.41k stars 120 forks source link

New VLANs not discovered #246

Closed szinn closed 1 year ago

szinn commented 1 year ago

I was running vnstat with eth0, eth0.10, eth0.20, eth0.98, eth0.99, eth5

I just added two new VLANs eth0.11 and eth0.12 and restarted vnstat. It did not discover those two VLANs since they were not in the database.

I deleted the DB file and restarted. vnstat discovered them just fine.

Should vnstat have found the new VLANs and added them to the watched list of networks?

vergoh commented 1 year ago

It may depend a little bit on the method of installation but usually, by default, vnStat does automatic interface discovery only during the initial startup when no database exists. After that interfaces that are intended to be monitored can be added manually with vnstat --add -i eth123.

If the intent is to get all new interfaces automatically monitored then the solution is to enable AlwaysAddNewInterfaces from the configuration or modify the daemon to start with the --alwaysadd parameter. This behaviour is also documented near the beginning of the vnstatd man page. Some of these option may not be available if you are using some older release. However, in all cases, it shouldn't be necessary to delete the database file.

szinn commented 1 year ago

I am using the latest version and running on my VyOS router in a container. Thanks for the quick reply