Feature Request: Multiple named `--ifconfig-pool` pools with dynamic group-based selection

Aperta
#1,076 14 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
c
Ambito
networking

Direzione di ricerca

Inizia esaminando la gestione esistente di --ifconfig-pool, la configurazione CCD, i blocchi di configurazione client-auth e il tracciamento integrato dei pool. Determina come devono integrarsi i pool denominati, la selezione per client, il comportamento di fallback, l’esaurimento, la segnalazione dello stato e il rilascio alla disconnessione. Il lavoro è completato quando il comportamento è specificato, implementato in questi percorsi e coperto dai test pertinenti.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

duplicate feature

Problem Statement

Modern OpenVPN deployments increasingly use external authentication — OAuth2/OIDC (openvpn-auth-oauth2), LDAP, RADIUS. Users authenticate and authorize via groups/roles, and each group needs its own IP subnet for:

  • Firewall rules (MikroTik, iptables) based on source subnet
  • Monitoring and session tracing
  • Quality of Service policies
  • Access segregation to internal resources

Example use-case:

Group Required subnet
support 10.8.3.0/24
all (regular VPN) 10.8.0.0/24
Administrators 10.8.0.0/24 with per-user static IP

Currently OpenVPN supports only a single pool via --server or --ifconfig-pool. There is no mechanism to define multiple pools and dynamically select which pool to assign an IP from based on the client's group/role.

Current Workarounds and Their Limitations

1. CCD + static IPs (ifconfig-push)

Each profile/group gets a CCD file with ifconfig-push. However:

  • This is a static assignment, not a pool — all users in the same group would get the same IP, which doesn't work for concurrent connections.
  • Per-user CCD files don't scale (N users = N files to manage).
  • No dynamic IP allocation — you must manually manage the address space.
2. client-connect script with external IPAM

A custom script can maintain its own pool DB and issue ifconfig-push via the management interface. Drawbacks:

  • OpenVPN is unaware of this external pool — no conflict detection with --ifconfig-pool.
  • No integration with OpenVPN's built-in pool tracking.
  • Requires external locking and persistence mechanisms.
  • Duplicates functionality that should be in the core.
3. client-auth (MDA) + ifconfig-push

When using the management interface (e.g. openvpn-auth-oauth2), the client-auth command can include a config block with ifconfig-push. This works, but:

  • There's no way to say "give me any free IP from pool X" — you must hardcode the IP.
  • The selected profile/group info is available at auth time but cannot be used to select a pool dynamically.
4. Profile selector + per-profile static IPs (our current setup)

Our current setup:

  • /etc/openvpn-auth-oauth2/client-config/Access_VPN_all.conf — no ifconfig-push, IP from the default pool
  • /etc/openvpn-auth-oauth2/client-config/Access_VPN_support.conf — ifconfig-push 10.8.3.10
  • Per-user CCD for admins — ifconfig-push 10.8.3.12

The CEL expression in openvpn-auth-oauth2 v2 correctly selects the config file based on Keycloak groups, but all users from the support group still get the same static IP. This is fine for our current scale, but it doesn't scale to multiple concurrent users per group without IP conflicts.

Proposed Feature: Named --ifconfig-pool pools with dynamic selection

Server configuration

Allow defining multiple named pools in server.conf:

ifconfig-pool support 10.8.3.0 255.255.255.0 10.8.3.10-10.8.3.250
ifconfig-pool all     10.8.0.0 255.255.255.0 10.8.0.10-10.8.0.250

Where the syntax could be:

ifconfig-pool <name> <network> <netmask> [<start-ip>-<end-ip> | <size>]

If no explicit start/end range is given, the pool auto-calculates from the network.

Per-client pool selection

Add a new option for CCD files and client-auth config blocks:

# In CCD file:
ifconfig-pool "support"

# Or in client-auth config block sent via management interface:
ifconfig-pool "all"

When ifconfig-pool "name" is present instead of ifconfig-push, OpenVPN would:

  1. Look up the named pool
  2. Allocate the next free IP from that pool
  3. Track the allocation (including in the status file)
  4. Release on disconnect (same as the existing pool mechanism)
Priority/fallback behavior
  • If a client has both ifconfig-pool "name" in CCD and the server has a matching pool — use it.
  • If the named pool doesn't exist or is exhausted — fall back to the default --ifconfig-pool.
  • If ifconfig-push is also present — ifconfig-push takes precedence (backward compatibility).
Integration with client-auth (management interface)

This is especially important for OAuth2 flows. When openvpn-auth-oauth2 calls:

client-auth CID KID\n
ifconfig-pool "support"\n
END\n

OpenVPN would allocate from the support pool instead of the default one.

Benefits
  • No code changes needed in auth plugins — the plugin already sends config blocks; it just needs the ability to specify a pool name instead of a hardcoded IP.
  • Backward compatible — existing --ifconfig-pool without a name becomes the default pool.
  • Scales — multiple users in the same group each get a unique IP from their group's subnet.
  • Integrates with status file, conflict detection, and pool tracking.
  • CCD-friendly — group-level CCD files can use ifconfig-pool "name" instead of per-user ifconfig-push.

Use Cases Beyond OAuth2 Groups

  • RADIUS pools — RADIUS server could return a pool attribute (e.g. Framed-Pool).
  • Multi-tenant servers — different customers on the same OpenVPN instance get IPs from different subnets.
  • Certificate-based — different certificate OUs could map to different pools via CCD.

Related

  • openvpn-auth-oauth2 issue #896 — "Different IP pools per group" (feature request in the auth plugin, but the real limitation is in OpenVPN core)
Lingua principale
C
Stelle
14.8k
Fork
3.4k
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenVPN/openvpn

Tutte le issue di OpenVPN/openvpn

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.