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

RADIUS Accounting for OpenVPN #3694

Closed
adrianschneider94 opened this issue Sep 3, 2019 · 2 comments
Closed

RADIUS Accounting for OpenVPN #3694

adrianschneider94 opened this issue Sep 3, 2019 · 2 comments
Labels
feature Adding new functionality help wanted Contributor missing / timeout

Comments

@adrianschneider94
Copy link

adrianschneider94 commented Sep 3, 2019

Guidelines

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md

[x] I have searched the existing issues and I'm convinced that mine is new.

tl;dr

I‘d like OpenVPN to support RADIUS accounting.

Use case

I want to do authentication/authorization for OpenVPN in the following manner:

  • User starts VPN
  • opnsense sends auth request to RADIUS
  • RADIUS responds with an IP from a IP pool (one pool per authorization group)
  • With the IP the firewall can determine the access rights of the authenticated user

This approach works fine so far, the only problem is that the ip pool must operate blindly. Without support for accounting RADIUS will never know when an IP gets released what can then lead to IP collisions.

I‘m happy to contribute myself, but would need some advice on how it would best fit into the current architecture.

@AdSchellevis
Copy link
Member

Hi @adrianschneider94,

A good starting point could be to check how the other connector you found (https://github.com/brainly/openvpn-auth-radius) handles accounting, there workflow probably is different than ours, but maybe we can collect some ideas from it.

Our generic authentication system is explained in detail here https://docs.opnsense.org/development/components/authentication.html, we do offer accounting for captive portal, which you can find here https://github.com/opnsense/core/blob/master/src/opnsense/scripts/OPNsense/CaptivePortal/process_accounting_messages.php

Since there are more authentication options possible per server, there might be a small challenge in finding out where to send the messages, but maybe you should start simple and try to send accounting messages to all supported authentication servers using data received from openvpn.

Best regards,

Ad

ref :https://forum.opnsense.org/index.php?topic=14073.msg64734

@AdSchellevis AdSchellevis added the feature Adding new functionality label Sep 3, 2019
@AdSchellevis
Copy link
Member

This issue has been automatically timed-out (after 180 days of inactivity).

For more information about the policies for this repository,
please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.

If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.

@AdSchellevis AdSchellevis added the help wanted Contributor missing / timeout label Mar 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Adding new functionality help wanted Contributor missing / timeout
Development

No branches or pull requests

2 participants