Feature #14213
closed
Set range for random Gateway and network used for OpenVPN connections
0%
Description
When I create a new OpenVPN client (VPN --> OpenVPN --> Clients), assign it to an interface it becomes a gateway. The network range that is assigned to it is random and from my 10.x.x.x range (LAN IP range). the range can be any class A Range and the Gateway is always the first IP. This is not a bad thing.
Can you add a feature where I can specify the pool from where the random ranges are pulled from so I can add a little bit of admin control on the ranges.
Some examples of the setting and the created networks would:
- Range Pool: 10.200.x.x
- 10.200.17.1/24
- 10.200.123.1/24
- Range Pool: 10.200.45.x
- 10.200.45.1/24
- 10.200.45.1/24
- 10.200.240.1/24
So I think allow Class A and Class B pools (as above) and does not have to be in the same IP range as the router.
Updated by Jim Pingle about 2 years ago
- Status changed from New to Rejected
The address assigned to a client is set by the server to which it connects or set static in the tunnel network field. Nothing on the firewall itself randomly assigns an address to a client interface. The client has no say over what it gets assigned, if it assigns something outside the range the server wants, it wouldn't be able to communicate with the server.