Networking Introduction
Table of Contents
Expand all | Collapse all
-
- Tap Interfaces
-
- Layer 2 and Layer 3 Packets over a Virtual Wire
- Port Speeds of Virtual Wire Interfaces
- LLDP over a Virtual Wire
- Aggregated Interfaces for a Virtual Wire
- Virtual Wire Support of High Availability
- Zone Protection for a Virtual Wire Interface
- VLAN-Tagged Traffic
- Virtual Wire Subinterfaces
- Configure Virtual Wires
- Configure an Aggregate Interface Group
- Configure Bonjour Reflector for Network Segmentation
- Use Interface Management Profiles to Restrict Access
-
- DNS Overview
- DNS Proxy Object
- DNS Server Profile
- Multi-Tenant DNS Deployments
- Configure a DNS Proxy Object
- Configure a DNS Server Profile
- Use Case 1: Firewall Requires DNS Resolution
- Use Case 2: ISP Tenant Uses DNS Proxy to Handle DNS Resolution for Security Policies, Reporting, and Services within its Virtual System
- Use Case 3: Firewall Acts as DNS Proxy Between Client and Server
- DNS Proxy Rule and FQDN Matching
-
- NAT Rule Capacities
- Dynamic IP and Port NAT Oversubscription
- Dataplane NAT Memory Statistics
-
- Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
- Enable Clients on the Internal Network to Access your Public Servers (Destination U-Turn NAT)
- Enable Bi-Directional Address Translation for Your Public-Facing Servers (Static Source NAT)
- Configure Destination NAT with DNS Rewrite
- Configure Destination NAT Using Dynamic IP Addresses
- Modify the Oversubscription Rate for DIPP NAT
- Reserve Dynamic IP NAT Addresses
- Disable NAT for a Specific Host or Interface
-
- Network Packet Broker Overview
- How Network Packet Broker Works
- Prepare to Deploy Network Packet Broker
- Configure Transparent Bridge Security Chains
- Configure Routed Layer 3 Security Chains
- Network Packet Broker HA Support
- User Interface Changes for Network Packet Broker
- Limitations of Network Packet Broker
- Troubleshoot Network Packet Broker
-
- Enable Advanced Routing
- Logical Router Overview
- Configure a Logical Router
- Create a Static Route
- Configure BGP on an Advanced Routing Engine
- Create BGP Routing Profiles
- Create Filters for the Advanced Routing Engine
- Configure OSPFv2 on an Advanced Routing Engine
- Create OSPF Routing Profiles
- Configure OSPFv3 on an Advanced Routing Engine
- Create OSPFv3 Routing Profiles
- Configure RIPv2 on an Advanced Routing Engine
- Create RIPv2 Routing Profiles
- Create BFD Profiles
- Configure IPv4 Multicast
- Create Multicast Routing Profiles
- Create an IPv4 MRoute
Networking Introduction
Introduces topics in the PAN-OS Networking Administrator’s
Guide
Networking is the fundamental building
block of the firewalls because they must be able to receive data,
process it, and forward it. When configuring the Ethernet ports
on your firewall, you can choose from tap, virtual wire, Layer2,
Layer 3, or AE interface deployments. In addition, to allow you
to integrate into a variety of network segments, you can configure
different types of interfaces on different ports.
To begin networking, you should first access the
Getting Started topic in the PAN-OS
®
Administrator's
Guide. There you learn about segmenting your network and you Configure Interfaces and Zones;
that initial task illustrates how to configure Layer 3 interfaces
to connect to the internet, your internal network, and your data
center applications.This PAN-OS Networking Administrator's Guide elaborates on that
information with topics on how to configure tap, virtual wire, Layer
2, Layer 3, and AE interfaces. After your network interfaces have
been configured, you can Export Configuration Table Data as
a PDF or CSV for internal review or audits.
This guide also explains how the firewall supports multiple virtual
routers to obtain Layer 3 routes to other subnets and to maintain
separate sets of routes. The remaining chapters describe static
routes, dynamic routing protocols, and the major features that support
networking on the firewall.
You may decide to enable Advanced Routing. The Advanced
Routing Engine uses logical routers instead
of virtual routers.