Client Static IP - OpenVPN

Hi Everyone,

Our customer needs to configure Remote User Access with OpenVPN assigning Static IPs to the client users.
They cannot use DHCP Server it will be in conflict with company policies.

Is it possible to implement this feature in future?

Thank you,
Cristian

1 Like

+1 needed for the same reason but also adding Subnet settings would be good as well

1 Like

+1 Need this for the same reasons. OpenVPN clients need to be reachable at all time and this is disrupting services.

It’s possible to do this with OpenVPN servers, so it should be relatively easy to integrate with IC2.

Any updates on this?

Would love to see this feature as well.

Is this being considered?

We have a plan to include this feature in the next firmware release, hopefully, we will see something materialize when the next firmware version (tentatively, version 8.5.2) is available…

3 Likes

We would love to have certificate based openVPN as well, not username/password based.

1 Like

A way to integrate static IPs when using radius would be a big benefit as well!

2 Likes

Is this still on track for the 8.5.2 release?

@WeiMing many folks still waiting to hear if we’ll be able to assign static IPs to OpenVPN clients as opposed to relying on DHCP. Will this be in the up coming 5.8.2 release? I didn’t see it in the beta yet so I’m concerned we’ll need to wait even longer. Just knowing if and when would be great if Peplink can let us all know.

@hasherati first of all, I would like to apologize for the inaccurate information I shared earlier. The feature will be included in 8.5.2 is RUA - DHCP reservation based on user ID, which allows you to reserve an IP per RUA - Username defined in RUA - Local User Accounts. It should achieve the objective but in a different approach.

NOTE:
RUA = Remote User Access (L2TP IPsec, PPTP, OpenVPN).

Our team is working on it to make sure it will be ready as part of firmware 8.5.2 standard feature. Stay tuned.

1 Like

That’s great news and I think will work well for many of the use cases in this thread. I’m hoping that if the solution is based on DHCP, that we can use it such that DHCP will not assign IPs to anything else in the LAN and will not conflict another DHCP server that is already serving IPs to clients. I have a separate DHCP server (not the Peplink) that gives IP addresses to LAN clients. Will this be a problem?

@hasherati and all, I must admit I should do a better job with thorough verification prior to providing the update. :man_bowing:

After double confirming with the team, we need to defer the feature to post- 8.5.2 GA (very soon), as some work in progress and couldn’t make it on time.

Probably we could look at the possibility of a special firmware option after 8.5.2 is GA, and work it out via a support ticket.

1 Like

No major issue if scopes don’t overlap.