Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • I ISP-ng
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Neutrinet
  • VPN
  • ISP-ng
  • Issues
  • #19

Closed
Open
Created Jan 13, 2016 by Tharyrok@TharyrokOwner

Possible race condition during bad connection ending up creating multiple entries in ovpn_clents table and forbid user to connect with his vpn anymore

Created by: Psycojoker

Ohai,

For several users (5 I think) mutliples entries were found in the ovpn_clients table, sometime up to several dozens. Those users wre only using their internet cube, so the probability that they tried to connect several computers at the same time is close to zero.

It is very likely that a entry is not cleaned in the able or something like that and that there is no mecanism right now to handle this situation, therefor the table is filled, never cleaned and the user is never able to connect anymore.

Related part of the code https://github.com/Neutrinet/ISP-ng/blob/01d7be4f229617e5547d43c86c8769d632236309/src/main/java/be/neutrinet/ispng/vpn/Client.java#L53

Assignee
Assign to
Time tracking