Hi,
ordex wrote
So there might be some reason why the assignment cannot be kept. Maybe the server log will say something (I'd suggest to use verb 4 to get extra info)
Probably the keepalive mechanism?
.
See the manual for the directives:
https://build.openvpn.net/man/openvpn-2.5/openvpn.8.html
And wiki:
https://community.openvpn.net/openvpn/wiki/HOWTO#ExpandingthescopeoftheVPNtoincludeadditionalmachinesoneithertheclientorserversubnet
Possibly a "better" way is to assign static tunnel IPs to clients via ccd.
This can be for
all or
not all clients.
Clients need a unique certificate.
client-config-dir /etc/openvpn/ccd
If for
all clients one can add:
ccd-exclusive
Then use:
topology subnet
server 10.8.0.0 255.255.255.0 'nopool'
ifconfig-pool 10.8.0.16 10.8.0.254
In this case .16 till .254 are dynamically allocated and .2 till .15 can be used for static assignment.
Adjust as needed.
.0, .1 and .255 cannot be assigned to clients in this case (for recent OpenVPN version, if older .254 also cannot be assigned).
I would also look into --explicit-exit-notify.
For the above one needs to remove:
ifconfig-pool-persist ipp.txt