Layer 3 Subinterface
Table of Contents
Layer 3 Subinterface
- Network > Interfaces > Ethernet
For each Ethernet port configured as a physical Layer 3 interface, you can define additional
logical Layer 3 interfaces (subinterfaces). You can create a Layer 3 subinterface for a
PPPoE client for IEEE 802.1Q VLAN when your ISP uses an 802.1Q VLAN tag on a PPPoE
subinterface.
You can also configure Layer 3 subinterfaces for an SD-WAN AE interface. Create an SD WAN
AE interface group, select the group and Add Subinterface, and
specify the following information.
To configure a PA-7000
Series Layer 3 Interface, select a physical interface, Add
Subinterface, and specify the following information.
Layer 3 Subinterface Settings | Configured In | Description |
|---|---|---|
Interface Name | Layer3 Subinterface | The read-only Interface Name field
displays the name of the physical interface you selected. In the
adjacent field, enter a numeric suffix (1 to 9,999) to identify
the subinterface. |
Comment | Enter an optional description for the subinterface. | |
Tag | Enter the VLAN tag (1 to 4,094) for the
subinterface. For ease of use, use the same number as the numeric
suffix for the Interface Name. | |
Netflow Profile | If you want to export unidirectional IP
traffic that traverses an ingress subinterface to a NetFlow server,
select the server profile or click Netflow Profile to
define a new profile (see Device
> Server Profiles > NetFlow). Select None to
remove the current NetFlow server assignment from the subinterface. | |
Virtual Router | Assign a virtual router to the interface,
or click Virtual Router to define a new one
(see Network
> Virtual Routers). Select None to
remove the current virtual router assignment from the interface. | |
Virtual System | If the firewall supports multiple virtual
systems and that capability is enabled, select a virtual system
(vsys) for the subinterface or click Virtual System to
define a new vsys. | |
Security Zone | Select a security zone for the subinterface,
or click Zone to define a new zone. Select None to
remove the current zone assignment from the subinterface. | |
Enable SD-WAN | Select to enable SD-WAN on the Layer3 subinterface for
a Layer 3 interface or an SD-WAN AE interface group. | |
Enable Bonjour Reflector | (PA-220, PA-800, and PA-3200 series
only) When you enable this option, the firewall forwards Bonjour multicast
advertisements and queries received on and forwarded to this interface
to all other L3 and AE interfaces and subinterfaces where you enable
this option. This helps ensure user access and device discoverability
in network environments that use segmentation to route traffic for security
or administrative purposes. You can enable this option on up to
16 interfaces. | |
Type | Select the method for assigning an IPv4
address to the subinterface:
Firewalls
that are in a high availability (HA) active/active configuration
don’t support DHCP Client. Based on your IP address
method selection, the options displayed in the tab will vary. | |
IP | Add and perform one
of the following steps to specify a static IP address and network mask
for the interface.
You
can enter multiple IP addresses for the interface. The forwarding
information base (FIB) your system uses determines the maximum number
of IP addresses. Delete an IP address
when you no longer need it. | |
| Enable |
|
Enable the PPPoE subinterface.
|
| Username |
|
Enter the Username for the authentication type you will select.
|
| Password |
|
Enter the Password for the authentication type you will select and
then Confirm Password.
|
| Authentication |
|
Select the type of authentication for the PPPoE subinterface:
|
| Static Address |
|
Specify a Static Address to request that the PPPoE server assign that
IPv4 address for the subinterface. (The PPPoE server may assign the
requested address or a different address at its discretion.) Default
is None.
|
| automatically create default route pointing to peer |
|
Creates a default route that points to the default gateway that the
PPPoE server provides.
|
| Default Route Metric |
|
Enter the default route metric (priority level) of the PPPoE
connection; range is 1 to 65,535; default is 10. A route with a
lower number has higher priority during route selection. For
example, a route with a metric of 10 is used before a route with a
metric of 100.
|
| Access Concentrator |
|
Enter the name of the Access Concentrator that your ISP provided, if
any (string value of 0 to 255 characters). The firewall will connect
with this Access Concentrator.
|
| Service |
|
Enter the Service that your ISP provided, if any (string value of 0
to 255 characters).
|
| Passive |
|
If you want the PPPoE client (firewall) to wait for the PPPoE server
to initiate a connection, select Passive. If Passive is not
selected, the firewall is allowed to initiate a connection.
|
Enable | Select to activate the DHCP client on the interface. | |
Automatically create default route pointing
to default gateway provided by server | Select to automatically create a default
route that points to the default gateway that the DHCP server provides. | |
Send Hostname | Select to have the firewall (as a DHCP client)
send the hostname of the interface (Option 12) to the DHCP server.
If you Send Hostname, by default, then the hostname of the firewall
is the choice in the hostname field by default. You can send that
name or enter a custom hostname (64 characters maximum including
uppercase and lowercase letters, numbers, periods, hyphens, and underscores. | |
Default Route Metric | (Optional) For the route between
the firewall and DHCP server, you can enter a route metric (priority
level) to associate with the default route and to use for path selection
(range is 1 to 65535; there is no default). The priority level increases
as the numeric value decreases. | |
Show DHCP Client Runtime Info | Select Show DHCP Client Runtime Info to
display all settings received from the DHCP server, including DHCP
lease status, dynamic IP address assignment, subnet mask, gateway,
and server settings (DNS, NTP, domain, WINS, NIS, POP3, and SMTP). | |
Enable IPv6 on the interface | Select to enable IPv6 addressing on this interface. | |
Interface ID | Enter the 64-bit extended unique identifier
(EUI-64) in hexadecimal format (for example, 00:26:08:FF:FE:DE:4E:29).
If you leave this field blank, the firewall uses the EUI-64 generated
from the MAC address of the physical interface. If you enable the Use
interface ID as host portion option when adding an address,
the firewall uses the interface ID as the host portion of that address. | |
Type | Select the type of IPv6 address: Static, DHCPv6 Client,
or Inherited. | |
Address | Add an IPv6 address
and prefix length (for example, 2001:400:f00::1/64). You can alternatively
select an IPv6 address object or create a new address object. | |
Enable address on interface | Select to enable the IPv6 address on the interface. | |
Use interface ID as host portion | Select to use the Interface ID as
the host portion of the IPv6 address. | |
Anycast | Select to include routing through the nearest node. | |
Send Router Advertisement | Select to enable router advertisement (RA)
for this IP address. (You must also Enable Router Advertisement on
the interface.) For details on RA, see Enable Router Advertisement
in this table. The remaining fields apply if you Send
Router Advertisement.
| |
Accept Router Advertised Route | Select to allow the DHCPv6 Client to accept
the RA from the DHCPv6 server. | |
Default Route Metric | Enter a default route metric for the route
from the interface to the ISP; range is 1 to 65,535; default is 10. | |
Preference | Select the preference of the DHCPv6 Client
interface (low, medium,
or high) so that, in the event you have two
interfaces (each connected to a different ISP for redundancy), you
can assign the interface to one ISP a higher preference than the
interface to the other ISP. The ISP connected to the preferred interface
will be the ISP that provides the delegated prefix to send to a
host-facing interface. If the interfaces have the same preference,
both ISPs provide a delegated prefix and the host decides which prefix
to use. | |
Enable IPv6 Address | Enable the IPv6 Address received for this
DHCPv6 Client. | |
Non-Temporary Address | Request a Non-Temporary Address for the
firewall to assign to this DHCPv6 Client interface that faces the delegating
router and ISP. A Non-Temporary Address has a longer lifespan than
a Temporary Address. A Non-Temporary Address can be renewed. Whether you request a Non-Temporary Address
or Temporary Address for the interface is based on your discretion
and the capability of the DHCPv6 server; some servers can provide
only a temporary address. The best practice is to select both Non-Temporary Address
and Temporary Address, in which case the firewall will prefer the
Non-Temporary Address. | |
Temporary Address | Request a Temporary Address for the firewall
to assign to this DHCPv6 Client interface that faces the delegating
router and ISP. Select Temporary Address for a greater level of
security because the address is intended to be used for a short
period of time. A Temporary Address may or may not be renewed. | |
Rapid Commit | Select to use the DHCP process of Solicit
and Reply messages, rather than the process of Solicit, Advertise, Request,
and Reply messages. | |
Enable Prefix Delegation | Enable Prefix Delegation to allow the firewall
to support prefix delegation functionality. This means that the interface
accepts a prefix from the upstream DHCPv6 server and places the
prefix into the Prefix Pool you select, from which the firewall
delegates a prefix to a host via RA. The ability to enable or disable
prefix delegation for an interface allows the firewall to support
multiple ISPs (one ISP per interface). Enabling prefix delegation
on this interface controls which ISP provides the prefix. | |
DHCP Prefix Length Hint | Select to enable the firewall to send a
preferred DHCPv6 prefix length to the DHCPv6 server. | |
DHCP Prefix Length (bits) | Enter the preferred DHCPv6 prefix length
in the range from 48 to 64 bits, which is sent as the hint to the DHCPv6
server. Requesting a prefix length of 48, for example,
leaves 16 bits remaining for subnets (64-48), which indicates you
require many subdivisions of that prefix to delegate. On the other
hand requesting a prefix length of 63 leaves 1 bit for delegating
only two subnets. Of the 128 bits, there are still 64 more bits
for host address. | |
Prefix Pool Name | Enter a name for the prefix pool where the
firewall stores the received prefix. The name must be unique and contain
a maximum of 63 alphanumeric characters, hyphens, periods, and underscores. Use a prefix pool name that reflects the ISP
for easy recognition. | |
Name | Add a pool by entering
a pool Name. The name can be a maximum of 63 alphanumeric characters,
hyphens, periods, and underscores. | |
Address Type | Select one:
| |
Enable on Interface | Enable the address on the interface. | |
Prefix Pool | Select the Prefix Pool from which to get
the GUA. | |
Assignment Type | Select the assignment type:
| |
Send Router Advertisement | Select to send router advertisements (RAs)
from the interface to the LAN hosts. | |
On-Link | Select if systems that have addresses within
the prefix are reachable without a router. | |
Autonomous | Select if systems can independently create
an IPv6 address by combining the advertised prefix with an Interface
ID. | |
Enable Duplication Address Detection | Select to enable duplicate address detection
(DAD), then configure the other fields in this section. | |
DAD Attempts | Specify the number of DAD attempts within
the neighbor solicitation interval (NS Interval)
before the attempt to identify neighbors fails (range is 1 to 10;
default is 1). | |
Reachable Time (sec) | Specify the length of time, in seconds,
that the client will use to assume a neighbor is reachable after
receiving a Reachability Confirmation message (range is 10 to 36,000; default
is 30). | |
NS Interval (sec) | Specify the Neighbor Solicitation (NS) interval,
which is the number of seconds for DAD attempts before failure is indicated
(range is 1 to 3,600; default is 1). | |
Enable NDP Monitoring | Select to enable Neighbor Discovery Protocol (NDP) monitoring. When enabled, you can select NDP
( 
| |
Enable Router Advertisement | To provide Neighbor Discovery on IPv6 interfaces, select
and configure the other fields in this section. IPv6 DNS clients
that receive the router advertisement (RA) messages use this information. RA
enables the firewall to act as a default gateway for IPv6 hosts
that are not statically configured and to provide the host with
an IPv6 prefix for address configuration. You can use a separate
DHCPv6 server in conjunction with this feature to provide DNS and
other settings to clients. This is a global setting for the
interface. If you want to set RA options for individual IP addresses, Add and
configure an Address in
the IP address table. If you set RA options for any IP address,
you must Enable Router Advertisement for
the interface. | |
Min Interval (sec) | Specify the minimum interval, in seconds,
between RAs that the firewall will send (range is 3 to 1,350; default is
200). The firewall will send RAs at random intervals between the
minimum and maximum values you configure. | |
Max Interval (sec) | Specify the maximum interval, in seconds,
between RAs that the firewall will send (range is 4 to 1,800; default is
600). The firewall will send RAs at random intervals between the
minimum and maximum values you configure. | |
Hop Limit | Specify the hop limit to apply to clients
for outgoing packets (range is 1 to 255; default is 64). Enter 0
for no hop limit. | |
Link MTU | Specify the link maximum transmission unit
(MTU) to apply to clients. Select unspecified for
no link MTU (range is 1,280 to 9,192; default is unspecified). | |
Reachable Time (ms) | Specify the reachable time (in milliseconds)
that the client will use to assume a neighbor is reachable after receiving
a reachability confirmation message. Select unspecified for
no reachable time value (range is 0 to 3,600,000; default is unspecified). | |
Retrans Time (ms) | Specify the retransmission timer that determines
how long the client will wait (in milliseconds) before retransmitting
neighbor solicitation messages. Select unspecified for
no retransmission time (range is 0 to 4,294,967,295; default is unspecified). | |
Router Lifetime (sec) | Specify how long, in seconds, the client
will use the firewall as the default gateway (range is 0 to 9,000;
default is 1,800). Zero specifies that the firewall is not the default gateway.
When the lifetime expires, the client removes the firewall entry
from its Default Router List and uses another router as the default
gateway. | |
Router Preference | If the network segment has multiple IPv6
routers, the client uses this field to select a preferred router.
Select whether the RA advertises the firewall router as having a High, Medium (default),
or Low priority relative to other routers
on the segment. | |
Managed Configuration | Select to indicate to the client that addresses
are available via DHCPv6. | |
Other Configuration | Select to indicate to the client that other
address information (for example, DNS-related settings) is available via
DHCPv6. | |
Router Preference | Set Router Preference in case there are
two or more interfaces on different routers sending RAs to a host. High, Medium,
or Low is the priority that the RA advertises
indicating the relative priority and the host uses the prefix from
the higher prioritized router. | |
Managed Configuration | Select to indicate to the client that addresses
are available via DHCPv6. | |
Other Configuration | Select to indicate to the client that other
address information (such as DNS-related settings) is available
via DHCPv6. | |
Consistency Check | Select if you want the firewall to verify
that RAs sent from other routers are advertising consistent information on
the link. The firewall logs any inconsistencies in a system log;
the type is ipv6nd. | |
Include DNS information in Router Advertisement | Select for the firewall to send DNS information
in NDP router advertisements from this IPv6 Ethernet subinterface. The
other DNS Support fields in this table are visible only after you
select this option. | |
Server | Add one or more recursive DNS
(RDNS) server addresses for the firewall to send in NDP router advertisements
from this IPv6 Ethernet interface. RDNS servers send a series of
DNS look up requests to root DNS and authoritative DNS servers to ultimately
provide an IP address to the DNS client. You can configure
a maximum of 8 RDNS Servers that the firewall sends—in order listed
from top to bottom—in an NDP router advertisement to the recipient, which
then uses them in the same order. Select a server and Move
Up or Move Down to change the
order of the servers or Delete a server from
the list when you no longer need it. | |
Lifetime | Enter maximum number of seconds after the
IPv6 DNS client receives the router advertisement before the client
can use an RDNS server to resolve domain names (range is Max Interval
(sec) to twice Max Interval; default is 1,200). | |
Domain Search List | Add one or more domain names
(suffixes) for the DNS search list (DNSSL). Maximum length is 255
bytes. A DNS search list is a list of domain suffixes that
a DNS client router appends (one at a time) to an unqualified domain
name before it enters the name into a DNS query, thereby using a
fully qualified domain name in the query. For example, if a DNS
client tries to submit a DNS query for the name “quality” without
a suffix, the router appends a period and the first DNS suffix from
the DNS search list to the name and transmits the DNS query. If
the first DNS suffix on the list is “company.com”, the resulting
query from the router is for the fully qualified domain name “quality.company.com”. If
the DNS query fails, the router appends the second DNS suffix from
the list to the unqualified name and transmits a new DNS query.
The router uses the DNS suffixes until a DNS lookup is successful
(ignores the remaining suffixes) or until the router has tried all
of suffixes on the list. Configure the firewall with the suffixes
that you want to provide to the DNS client router in a Neighbor
Discovery DNSSL option; the DNS client receiving the DNSSL option uses
the suffixes in its unqualified DNS queries. You can configure
a maximum of 8 domain names (suffixes) for a DNS search list option
that the firewall sends—in order listed from top to bottom— in an
NDP router advertisement to the recipient, which uses them in the
same order. Select a suffix and Move Up or Move
Down to change the order or Delete a suffix
when you no longer need it. | |
Lifetime | Enter the maximum number of seconds after
the IPv6 DNS client receives the router advertisement that it can
use a domain name (suffix) on the DNS search list (range is the
value of Max
Interval (sec) to twice the Max Interval; default is 1,200). | |
DNS Recursive Name Server | Enable and select:
If you choose Manual, Add the
IPv6 address of a recursive DNS (RDNS) Server for the
firewall to send in NDP router advertisements from this IPv6 VLAN
interface. RDNS servers send a series of DNS lookup requests to
root DNS servers and authoritative DNS servers to ultimately provide
an IP address to the DNS client. You can configure a maximum
of eight RDNS servers that the firewall sends— in the order listed
from top to bottom—in an NDP router advertisement to the recipient, which
then uses them in the same order. Select a server and Move
Up or Move Down to change the
order of the servers or Delete a server from
the list when you no longer need it. Enter a Lifetime in
seconds, which is the maximum length of time the client can use
the specific RDNS server to resolve domain names. Range is 4 to 3,600;
default is 1,200. | |
Domain Search List | Enable and select:
If you choose Manual, Add and
configure one or more Domain names (suffixes)
for the DNS search list (DNSSL). The maximum suffix length is 255 bytes. A
DNS search list is a list of domain suffixes that a DNS client router
appends (one at a time) to an unqualified domain name before it
enters the name into a DNS query, thereby using a fully qualified
domain name in the DNS query. For example, if a DNS client tries
to submit a DNS query for the name “quality” without a suffix, the
router appends a period and the first DNS suffix from the DNS search
list to the name and then transmits the DNS query. If the first
DNS suffix on the list is “company.com”, the resulting DNS query
from the router is for the fully qualified domain name “quality.company.com”. If
the DNS query fails, the router appends the second DNS suffix from
the list to the unqualified name and transmits a new DNS query.
The router tries DNS suffixes until a DNS lookup is successful (ignores
the remaining suffixes) or until the router has tried all of suffixes
on the list. Configure the firewall with the suffixes that
you want to provide to the DNS client router in a Neighbor Discovery DNSSL
option; the DNS client receiving the DNSSL option uses the suffixes
in its unqualified DNS queries. Enter a Lifetime in
seconds, which is the maximum length of time the client can use
the specific Domain Search List. Range is 4 to 3,600; default is 1,200. You
can configure a maximum of eight domain names (suffixes) for a DNS
search list that the firewall sends—in order listed from top to
bottom—in an NDP router advertisement to the recipient, which uses
those addresses in the same order. Select a suffix and Move Up or Move
Down to change the order or Delete a suffix
from the list when you no longer need it. | |
SD-WAN Interface Profile | Select an SD-WAN Interface Profile to assign
to this subinterface or create a new profile. | |
Management Profile | Management Profile—Select
a profile that defines the protocols (for example, SSH, Telnet,
and HTTP) you can use to manage the firewall over this interface.
Select None to remove the current profile
assignment from the interface. | |
MTU | Enter the maximum transmission unit (MTU)
in bytes for packets sent on this interface (range is 576 to 9,192; default
is 1,500). If machines on either side of the firewall perform Path
MTU Discovery (PMTUD) and the interface receives a packet exceeding
the MTU, the firewall returns an ICMP fragmentation needed message to
the source indicating the packet is too large. | |
Adjust TCP MSS | Select to adjust the maximum segment size
(MSS) to accommodate bytes for any headers within the interface MTU
byte size. The MTU byte size minus the MSS Adjustment Size equals
the MSS byte size, which varies by IP protocol:
Use these settings to
address the case where a tunnel through the
network requires a smaller MSS. If a packet has more bytes than
the MSS without fragmentation, this setting enables the adjustment. Encapsulation
adds length to headers so it helps to configure the MSS adjustment
size to allow bytes for such things as an MPLS header or tunneled
traffic that has a VLAN tag. | |
IP Address MAC Address | To add one or more static Address Resolution Protocol
(ARP) entries, Add an IP address and its
associated hardware [media access control (MAC)] address. To delete
an entry, select the entry and click Delete.
Static ARP entries reduce ARP processing. | |
IPv6 Address MAC Address | To provide neighbor information for Neighbor Discovery
Protocol (NDP), Add the IP address and MAC
address of the neighbor. | |
Enable NDP Proxy | Enable Neighbor Discovery Protocol (NDP)
proxy for the interface. The firewall will respond to ND packets requesting
MAC addresses for IPv6 addresses in this list. In the ND response,
the firewall sends its own MAC address for the interface so that
the firewall will receive the packets meant for the addresses in
the list. It is recommended that you enable NDP proxy if you are
using Network Prefix Translation IPv6 (NPTv6). If you selected Enable
NDP Proxy, you can filter numerous Address entries
by entering a filter and clicking Apply Filter (gray arrow). | |
Address | Add one or more IPv6 addresses,
IP ranges, IPv6 subnets, or address objects for which the firewall
will act as NDP proxy. Ideally, one of these addresses is the same
address as that of the source translation in NPTv6. The order of
addresses does not matter. If the address is a subnetwork,
the firewall will send an ND response for all addresses in the subnet,
so we recommend you also add the IPv6 neighbors of the firewall and
then click Negate to instruct the firewall
not to respond to these IP addresses. | |
Negate | Negate an address
to prevent NDP proxy for that address. You can negate a subset of
the specified IP address range or IP subnet. | |
Settings | Select Settings to
make the DDNS fields available to configure. | |
Enable | Enable DDNS on the interface. You must initially enable
DDNS to configure it. (If your DDNS configuration is unfinished,
you can save it without enabling it so that you don’t lose your
partial configuration.) | |
Update Interval (days) | Enter the interval (in days) between updates
that the firewall sends to the DDNS server to update IP addresses mapped
to FQDNs (range is 1 to 30; default is 1). The firewall
also updates DDNS upon receiving a new IP address for the interface
from the DHCP server. | |
Certificate Profile | Create a Certificate Profile to
verify the DDNS service. The DDNS service presents the firewall with
a certificate signed by the certificate authority (CA). | |
Hostname | Enter a hostname for the interface, which
is registered with the DDNS Server (for example, host123.domain123.com,
or host123). The firewall does not validate the hostname except
to confirm that the syntax uses valid characters allowed by DNS
for a domain name. | |
Vendor | Select the DDNS vendor (and version) that
provides DDNS service to this interface:
If you select an older version of a DDNS service
that the firewall indicates will be phased out by a certain date,
move to the newer version. The Name and Value fields
that follow the vendor name are vendor-specific. The read-only fields
notify you of parameters that the firewall uses to connect to the
DDNS service. Configure the other fields, such as a password that the
DDNS service provides to you and a timeout that the firewall uses
if it doesn’t receive a response from the DDNS server. | |
IPv4 tab - IP | Add the IPv4 addresses configured on the
interface and then select them. You can select only as many IPv4 addresses
as the DDNS provider allows. All selected IP addresses are registered
with the DDNS provider (Vendor). | |
IPv6 tab - IPv6 | Add the IPv6 addresses configured on the
interface and then select them. You can select only as many IPv6 addresses
as the DDNS provider allows. All selected IP addresses are registered
with the DDNS provider (Vendor). | |
Show Runtime Info | Displays the DDNS registration: DDNS provider, resolved
FQDN, and the mapped IP address(es) with an asterisk (*) indicating
the primary IP address. Each DDNS provider has its own return codes
to indicate the status of the hostname update, and a return date,
for troubleshooting purposes. |