Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[nEdge] Make Traffic Quota persistent after service restart #8882

Open
cory-usap opened this issue Dec 19, 2024 · 1 comment
Open

[nEdge] Make Traffic Quota persistent after service restart #8882

cory-usap opened this issue Dec 19, 2024 · 1 comment

Comments

@cory-usap
Copy link

Environment:

  • OS name: Ubuntu
  • OS version: 20.04
  • Architecture: amd64
  • ntopng version/revision: v.6.2.241209

What happened:

If we restart the server or do a systemctl restart nedge then the traffic quota gets reset to 0

How did you reproduce it?

Set a users daily/weekly/monthly traffic quota to a > 0 value.

Download items that put them over the threshold.

Restart server/service. User now shows 0 quota and can download again.

Notes

I noticed this issue #8706 which is in-relation to RADIUS however we do not have RADIUS configured.

Is the only way to persist traffic bandwidth accounting is with a RADIUS server?

@cardigliano
Copy link
Member

@cory-usap this is expected with the current implementation/design

@cardigliano cardigliano changed the title [nEdge] Traffic Quota Reset after server reboot (or restart of nedge service). [nEdge] Make Traffic Quota persistent after service restart Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants