Gert is right ... On 19/01/17 22:33, Gert Doering wrote: > What you can do is trigger a client disconnect/reconnect via management > interface - that shouldn't cause more than a 2-3s hickup for the > user (if the receives the same IP address)...
... and this is the "lo-tech" approach, which definitely will work.
Using --client-connect or --client-config-dir on the server side, you
can also provide predictable VPN IP addresses. The former can be used
for a dynamic approach while the latter one for static configuration of
VPN client IP addresses.
The over-engineered approach [1] is to run a special script in the
client which is kicked off by --route-up. This script connects to a
related server-side process which can push route updates on-the-fly as
requirements changes. And then have a --route-pre-down script which
stops this process when the client disconnects.
There might even be it already exists such routing daemons ... I've
never really looked into this automated routing configuration stuff
outside of what dhcpd and radvd can do - neither of those two are really
relevant in this use-case.
[1] I'm pretty good at those, not all of my crazy ideas are really
worth considering though - most likely this one as well. So,
try the "lo-tech" variant first and see if that works well enough.
--
kind regards,
David Sommerseth
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
