1. Home
    2. GlobalProtect
    3. GlobalProtect Administrator's Guide
    4. Set Up the GlobalProtect Infrastructure
    5. Create Interfaces and Zones for GlobalProtect
    End-of-Life (EoL)

    Create Interfaces and Zones for GlobalProtect

    You must configure the following interfaces and zones for your GlobalProtect infrastructure:
    • GlobalProtect portal
      —Requires a Layer 3 or loopback interface for the GlobalProtect clients’ connection. If the portal and gateway are on the same firewall, they can use the same interface. The portal must be in a zone that is accessible from outside your network, for example: DMZ.
    • GlobalProtect gateways
      —The interface and zone requirements for the gateway depend on whether the gateway you are configuring is external or internal, as follows:
      • External gateways
        —Requires a Layer 3 or loopback interface and a logical tunnel interface for the client to establish a VPN tunnel. The Layer 3/loopback interface must be in an external zone, such as DMZ. A tunnel interface can be in the same zone as the interface connecting to your internal resources (for example trust). For added security and better visibility, you can create a separate zone, such as corp-vpn. If you create a separate zone for your tunnel interface, you must create security policies that enable traffic to flow between the VPN zone and the trust zone.
      • Internal gateways
        —Requires a Layer 3 or loopback interface in your trust zone. You can also create a tunnel interface for access to your internal gateways, but this is not required.
    For tips on how to use a loopback interface to provide access to GlobalProtect on different ports and addresses, refer to Can GlobalProtect Portal Page be Configured tobeAccessed on any Port?
    For more information about portals and gateways, see About the GlobalProtect Components.
    1. Configure a Layer 3 interface for each portal and/or gateway you plan to deploy.
      If the gateway and portal are on the same firewall, you can use a single interface for both.
      As a best practice use static IP addresses for the portal and gateway.
      Do not attach an interface management profile that allows HTTP, HTTPS, Telnet, or SSH on the interface where you have configured a GlobalProtect portal or gateway because this enables access to your management interface from the Internet. Follow the Best Practices for Securing Administrative Access to ensure that you are securing administrative access to your firewalls in a way that will prevent successful attacks.
      1. Select
        Network
        Interfaces
        Ethernet
         or
        Network
        Interfaces
        Loopback
         and then select the interface you want to configure for GlobalProtect. In this example, we are configuring ethernet1/1 as the portal interface.
      2. (Ethernet only) Select
        Layer3
         from the
        Interface Type
         drop-down.
      3. On the
        Config
         tab, select the zone to which the portal or gateway interface belongs as follows:
        • Place portals and external gateways in an untrust zone for access by hosts outside your network, such as l3-untrust.
        • Place internal gateways in an internal zone, such as l3-trust.
        • If you have not yet created the zone, select
          New Zone
           from the
          Security Zone
           drop-down. In the Zone dialog, define a
          Name
           for the new zone and then click
          OK
          .
      4. In the
        Virtual Router
         drop-down, select
        default
        .
      5. To assign an IP address to the interface, select the
        IPv4
         tab, click
        Add
         in the IP section, and enter the IP address and network mask to assign to the interface, for example 208.80.56.100/24.
      6. To save the interface configuration, click
        OK
        .
    2. On the firewall(s) hosting GlobalProtect gateway(s), configure the logical tunnel interface that will terminate VPN tunnels established by the GlobalProtect agents.
      IP addresses are not required on the tunnel interface unless you require dynamic routing. In addition, assigning an IP address to the tunnel interface can be useful for troubleshooting connectivity issues.
      Be sure to enable User-ID in the zone where the VPN tunnels terminate.
      1. Select
        Network
        Interfaces
        Tunnel
         and click
        Add
        .
      2. In the
        Interface Name
         field, specify a numeric suffix, such as
        .2
        .
      3. On the
        Config
         tab, expand the
        Security Zone
         drop-down to define the zone as follows:
        • To use your trust zone as the termination point for the tunnel, select the zone from the drop-down.
        • (Recommended) To create a separate zone for VPN tunnel termination, click
          New Zone
          . In the Zone dialog, define a
          Name
           for new zone (for example, corp-vpn), select the
          Enable User Identification
           check box, and then click
          OK
          .
      4. In the
        Virtual Router
         drop-down, select
        None
        .
      5. (Optional) If you want to assign an IP address to the tunnel interface, select the
        IPv4
         tab, click
        Add
         in the IP section, and enter the IP address and network mask to assign to the interface, for example 10.31.32.1/32.
      6. To save the interface configuration, click
        OK
        .
    3. If you created a separate zone for tunnel termination of VPN connections, create a security policy to enable traffic flow between the VPN zone and your trust zone.
      For example, the following policy rule enables traffic between the corp-vpn zone and the l3-trust zone.
    4. Save the configuration.

    Recommended For You

    Recommended Videos

    Recommended videos not found.

    © 2022 Palo Alto Networks, Inc. All rights reserved.

    Techdocs Logo