Messages

1

24.1 Legacy Series / Re: vnStat statistic tabs empty

« on: February 13, 2024, 09:40:51 pm »

I haven't yet managed to reproduce the issue but I suspect it has something to do with the way the plugin has been implemented. At least the "Interface" setting has some sort of misunderstanding in its implementation as it's modifying the "Interface" keyword in the vnStat configuration file when set and leaving it out when nothing is selected. The help text claims "Set the interface to listen on." while in reality the "Interface" configuration selects only the interface that is expected to be shown in the command outputs when none is specified and when the automatic selection doesn't result in the expected interface getting selected. The daemon will always ignore this setting when it selects which interfaces to monitor. I can also see that it hasn't been configured to automatically start monitoring all new interfaces after the first startup so it will have only visibility of those interfaces that were present when first enabled. "Reset" may also misbehave as it doesn't appear to be stopping the daemon first before removing the database directory.

Check "Web GUI", "General" and "Backend" logs from System -> Log Files after first visiting any of the vnStat tabs that are empty. In the logs, you'll want to search for "vnstat" using the "Notice" log level. The "General" log should show that the daemon has started and hasn't produced any error. There's a line starting with "Monitoring" which will list all the interfaces that are currently being monitored. For the plugin page not working, I'd expect there to be some error or other clue of the issue in either the "Web GUI" or "Backend" log.

If those don't show anything unexpected, you could also try clearing the interface selecting on the General tab for the plugin and hitting save. That will result in the configuration file getting recreated from an old version template but without the "Interface" line which then forces the default interface output selection back to play. If the traffic tabs still show no content after this and the logs don't contain anything relevant then the issue is somewhere deeper within the plugin's implementation.

2

21.1 Legacy Series / Re: VNStats limited to 4 interfaces?

« on: August 14, 2021, 08:04:20 pm »

Hi, author of vnStat (not the OPNsense plugin) here with some clarifications;

1) The "Interface" setting in the configuration file does indeed only matter if there's no interface being specified on the command line. If "-i" or "--iface" is used then that configuration value gets ignored.

2) It's correct that "--dbiflist" shows all the interfaces currently in the database and those are being monitored by default. As a result, it's fair to assume the plugin's settings don't modify the database and all interfaces get monitored by default regardless of what has been selected for the plugin.

3) The reason why "vtnet3+vtnet2+vtnet1+vtnet0" works but "vtnet4+vtnet3+vtnet2+vtnet1+vtnet0" doesn't is because vnStat follows the Linux kernel maximum interface name length of 31 characters and adding the 5th interface resultings in the string being longer than the supported maximum. That + syntax results in the output of a sum of the given interfaces. I'm however not sure why the relevant error message wasn't show, "Error: Interface name is limited to 31 characters." is what you'd get from the command line if the "-i" parameter was being used.

4) It's worth noting that --enable/--disable aren't reboot proof as the daemon will automatically re-enable all interfaces that are available on startup.