VPN IP addresses Specify subnets to allocate group IP addresses. Optionally define ranges within the subnets

[Zimdx Gsm]

When a VPN asks you to “Specify subnets to allocate group IP addresses” it’s basically asking:

"From which IP address pool should we hand out private IP addresses to connected VPN clients?"

Here’s how to understand and set it up:

---

1. Choosing the Subnet​

• A subnet is a private IP block that your VPN will use for its clients.
• Common examples:
  
  • 10.8.0.0/24 → Gives 254 usable IPs (10.8.0.1 – 10.8.0.254)
  • 192.168.100.0/24 → Gives 254 usable IPs (192.168.100.1 – 192.168.100.254)
• Pick a range that doesn’t conflict with your home/work network or other VPNs.

---

2. Defining Ranges Within the Subnet​

If your VPN software allows, you can restrict the pool to a smaller slice of the subnet.
Example:


Subnet: 10.8.0.0/24<br>Range: 10.8.0.50 - 10.8.0.100<br>

• This means only .50 through .100 will be given to clients.
• Useful if you want to reserve part of the subnet for other purposes (e.g., static IPs for admins).

---

3. Typical Config Examples​

OpenVPN server.conf


server 10.8.0.0 255.255.255.0<br>ifconfig-pool 10.8.0.50 10.8.0.100<br>

WireGuard


[Interface]<br>Address = 10.8.0.1/24<br><br>[Peer]<br>AllowedIPs = 10.8.0.2/32<br>

---

4. Tips​

• Stick to private IP ranges (10.x.x.x, 172.16.x.x to 172.31.x.x, 192.168.x.x).
• Don’t overlap with your LAN — otherwise routing issues may occur.
• Make the pool large enough to handle all expected simultaneous users.
• For multi-location VPNs, use different subnets for each location.

---

If you want, I can give you ready-to-use VPN IP allocation examples for OpenVPN, WireGuard, and SoftEther so you can just paste them in. That way you’ll avoid IP conflicts completely.


Do you want me to prepare those?