We have 28 devices/users on the RMS VPN platform. Some device need to communicate together so they need a static IP address. My problem is there’s no reserved IP Addressed pool to be configured or no DHCP pool to be set. I though when a STATIC IP is configured the DHCP server will just jump to the next one when a new device required an IP address.
The result is we’re getting VPN IP Address conflict for almost all STATIC IP address configured. After doing tests, the RMS DHCP server doesn’t care about static IP… it’s just overlap…
Should I configure manually every device static IP?
The image below shows the pairs of IP addresses that can be configured on your VPN endpoints. You must use these static IP addresses from the /30 subnet. To set a static IP address, go to the RMS VPN Hub settings, select Clients, and click the cogwheel to set a static IP address for the device in the list (under actions).
Our IT explains to me the /30 use. This doesn’t solve the issue at all with Static IP address conflict. We set static IP address exactly the way described in the available pair ** “To set a static IP address, go to the RMS VPN Hub settings, select Clients, and click the cogwheel to set a static IP address for the device in the list (under actions).” **
The DHCP doesn’t care at all about static IP and create IP address conflict which make a lot of communication trouble.
Any router has DHCP reservation/exclusion why don’t you just add that?
