Feature Request: Support for per ‑CCD subnet definitions

--===============3772920921700472094==
Content-Type: multipart/alternative; boundary="000000000000e4cd1a0648f97d91"

--000000000000e4cd1a0648f97d91
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello OpenVPN team,

I would like to request a new feature related to client=E2=80=91specific
configuration (CCD). Currently, CCD files allow assigning a static IP or
iroute directives, but they do not support defining a dedicated subnet per
client.

Our use case requires each client to receive its own isolated subnet (for
example, for routing multiple internal services behind a single client).
Ideally, the server would allow specifying a unique subnet inside each CCD
file, and automatically handle route advertisement and conflict checks.

This would significantly simplify setups where clients represent remote
networks rather than single hosts.

Could you please consider adding support for per=E2=80=91CCD subnet definit=
ions in
a future release?

Thank you for your work and for considering this request.

Best regards, Dmitry

--000000000000e4cd1a0648f97d91
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><p><span style=3D"white-space-collapse: preserve;">Hello O=
penVPN team,</span></p><p><span style=3D"white-space-collapse: preserve;">I=
 would like to request a new feature related to client=E2=80=91specific con=
figuration (CCD).
Currently, CCD files allow assigning a static IP or <code>iroute</code> dir=
ectives, but they do not support defining a dedicated subnet per client.</s=
pan></p><p><span style=3D"white-space-collapse: preserve;">Our use case req=
uires each client to receive its own isolated subnet (for example, for rout=
ing multiple internal services behind a single client). Ideally, the server=
 would allow specifying a unique subnet inside each CCD file, and automatic=
ally handle route advertisement and conflict checks.</span></p><p><span sty=
le=3D"white-space-collapse: preserve;">This would significantly simplify se=
tups where clients represent remote networks rather than single hosts.</spa=
n></p><p><span style=3D"white-space-collapse: preserve;">Could you please c=
onsider adding support for per=E2=80=91CCD subnet definitions in a future r=
elease?</span></p><p><span style=3D"white-space-collapse: preserve;">Thank =
you for your work and for considering this request.</span></p><p><span styl=
e=3D"white-space-collapse: preserve;">Best regards,
Dmitry</span></p></div>

--000000000000e4cd1a0648f97d91--


--===============3772920921700472094==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============3772920921700472094==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Openvpn-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openvpn-users

--===============3772920921700472094==--