How is the Security Gateway VPN Domain created?

The following diagram illustrates how a VPN1 SecureClient user tries to establish a VPN with hosts in the external_net and internal_net from the Internet. How is the Security Gateway VPN Domain created?

The following diagram illustrates how a VPN1 SecureClient user tries to establish a VPN with hosts in the external_net and internal_net from the Internet.

How is the Security Gateway VPN Domain created?

A.
Internal Gateway VPN Domain = Internal_net
External VPN Domain = external net + external gateway object + internal_net.

B.
Internal GatewayVPN Domain = Internal_net
External Gateway VPN Domain = external_net + internal gateway object

C.
Internal GatewayVPN Domain = Internal_net
External Gateway VPN Domain = internal_net + external_net

D.
Internal GatewayVPN Domain = Internal_net
External Gateway VPN Domain = internal VPN Domain + internal gateway object + external_net

Explanation:

For the remoteaccess client to make it through to the internalnet, he must first connect to the corporate_gw. From there, he must route and have access to talk with the internal_gw or he will never get into the internal net. Answer A does not include the internal_gw in the “external vpn domain”, so the connection would never make it in!

Just like the “internal gateway vpn domain” does NOT include the gateway protecting it, the “external gateway vpn domain” doe not need the corporate_gw either.



Leave a Reply 0

Your email address will not be published. Required fields are marked *