vnstat2: 4GB of data added to some interfaces after a reboot
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Package Name
vnstat2
Maintainer
@janh
OpenWrt Version
SNAPSHOT
OpenWrt Target/Subtarget
mediatek/filogic
Steps to Reproduce
Restart router or vnstatd itself.
See also: https://github.com/vergoh/vnstat/issues/40
Actual Behaviour
Observe that vnstat sometimes adds a 4GB of transfer in both directions.
Fix is mentioned here: https://github.com/vergoh/vnstat/issues/40#issuecomment-190922285
What I suggest is to add --sync to the daemon arguments for vnstatd.
Confirmation Checklist
- The package is maintained in this repository.
- I understand that issues related to the base OpenWrt repository or LuCI repository will be closed.
- I am reporting an issue for OpenWrt, not an unsupported fork.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the vnstat2 package definition and the vnstatd daemon arguments, then reproduce the counter increase after a router or vnstatd restart on the stated OpenWrt target. Check the referenced vnstat issue for the suggested --sync behavior; done means the package passes that option and counters no longer gain the spurious 4GB transfer after restart.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, observability
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100