Hi,
On 22/01/18 09:21, Gert Doering wrote:
On Sun, Jan 21, 2018 at 11:08:39PM +0100, Alarig Le Lay wrote:
I run a 2.4.4 server. Each client have an address from a pool given with
the server option
server 89.234.186.64 255.255.255.224
I now would like to add another range (because the first is almost
full), but if I put another line 'server 80.67.190.128 255.255.255.224',
the first is not taken in account anymore.
How can I work around this?
Right now this can not be done inside OpenVPN - it can only handle one
pool, you you need one single bigger pool.
What you can do is to assign the IP addresses *outside* OpenVPN by
running a --client-connect script (see manpage) which gets an IP address
and creates an "ifconfig-push" config line (thus, overruling OpenVPN
pool assignment). How that is done depends very much on local needs.
as an afterthought to Gert's answer: do you really need to hand out
public IPs to all your clients? I'd hand out private IPs and then
possibly use some iptables rules to map private IPs to public IPs.
Handing out public IPs is only necessary if the *clients* need to be
reachable via the internet (i.e. incoming traffic).
HTH,
JJK
------------------------------------------------------------------------------
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
