Understanding Sidewinder client address pools
Understanding Sidewinder client address pools
Figure 2-6. VPN association implemented using client address pool
You may choose to implement your VPN using Sidewinder client address pools. Client address pools are reserved virtual IP addresses, recognized as internal addresses of the trusted network. Addresses in this pool are configured on Sidewinder and assigned (or "pushed") to a VPN client (per VPN configuration) when the VPN connection is started. Client traffic within the protected network appears to come from the virtual IP address pool. Only Sidewinder knows the client’s real IP address.
Client address pool
10.1.1.1
10.1.1.2(reserved for Client Y)
10.1.1.254 |
|
|
| VPN | |
Sidewinder |
|
| |||
|
| Client A | |||
Trusted | Internet | V | N |
| |
burb | burb | P |
| ||
|
|
| |||
Internal |
| Internet | VPN | ||
network |
| ||||
| VPN | ||||
Proxies |
| Client Y | |||
|
|
| |||
Virtual | VPN |
| |||
burb | VPN | ||||
|
| ||||
|
|
|
| Client Z |
Virtual IP address mappings using this client address pool.
VPN Client | Virtual IP Address |
A | Next available within the pool |
Y10.1.1.2
ZNext available within the pool
One of the reasons for using client address pools is that they simplify the management of VPN clients. They allow the firewall to manage certain configuration details on behalf of the client. This enables a remote client to initiate a VPN connection even if the client has not preconfigured itself for the connection.
When using client address pool, all the
Authentication information (e.g. a password or certificate)
Planning Your VPN Configuration | |
|
|