IPv4 WAN Types

Once an interface has been assigned, in most cases it will require an IP address. For IPv4 connections, the following choices are available: Static IPv4, DHCP, PPP, PPPoE, PPTP, and L2TP. These options are selected using the IPv4 Configuration Type selector on an interface page (e.g. Interfaces > WAN).

None

When IPv4 Configuration Type is set to None, IPv4 is disabled on the interface. This is useful if the interface has no IPv4 connectivity or if the IP address on the interface is being managed in some other way, such as for an OpenVPN or GIF interface.

Static IPv4

With Static IPv4, the interface contains a manually configured IP address. When chosen, three additional fields are available on the interface configuration screen: IPv4 Address, a CIDR subnet mask selector, and the IPv4 Upstream Gateway field.

To configure the interface for static IPv4 on an internal interface (e.g. LAN, DMZ):

  • Select Static IPv4 under IPv4 Configuration Type
  • Enter the IPv4 address for the interface into the IPv4 address box
  • Choose the appropriate subnet mask from the CIDR drop-down after the address box
  • Do not select an IPv4 Upstream Gateway

To configure the interface for static IPv4 on a WAN type interface:

  • Select Static IPv4 under IPv4 Configuration Type

  • Enter the IPv4 address for the interface into the IPv4 address box

  • Choose the appropriate subnet mask from the CIDR drop-down after the address box

  • Perform one of the following to use a gateway on the interface:

    • Select an IPv4 Upstream Gateway from the list, OR

    • Click fa-plus Add a new gateway to create a new gateway if one does not already exist. Clicking that button displays a modal form to add the gateway without leaving this page. Fill in the details requested on the new form:

      Default Gateway:
       If this is the only WAN or will be a new default WAN, check this box. The default IPv4 and IPv6 gateways work independently of one another. The two need not be on the same circuit. Changing the default IPv4 gateway has no effect on the IPv6 gateway, and vice versa.
      Gateway Name:The name used to refer to the gateway internally, as well as in places like Gateway Groups, the Quality Graphs, and elsewhere.
      Gateway IPv4:The IP address of the gateway. This address must be inside of the same subnet as the Static IPv4 address when using this form.
      Description:A bit of text to indicate the purpose of the gateway.
      • Click fa-plus Add

Note

Selecting an IPv4 Upstream Gateway from the drop-down list or adding and selecting a new gateway will make pfSense treat this interface as a WAN type interface for NAT and related functions. This is not desirable for internal interfaces such as LAN or a DMZ. Gateways may still be used on internal interfaces for the purpose of static routes without selecting an IPv4 Upstream Gateway here on the interfaces screen.

DHCP

When an interface is set to DHCP, pfSense will attempt automatic IPv4 configuration of this interface via DHCP. This option also activates several additional fields on the page. Under most circumstances these additional fields may be left blank.

Hostname:

Some ISPs require the Hostname for client identification. The value in the Hostname field is sent as the DHCP client identifier and hostname when requesting a DHCP lease.

Alias IPv4 Address:
 

This value used as a fixed IPv4 alias address by the DHCP client since a typical IP Alias VIP cannot be used with DHCP. This can be useful for accessing a piece of gear on a separate, statically numbered network outside of the DHCP scope. One example would be for reaching a cable modem management IP address.

Reject Leases From:
 

An IPv4 address for a DHCP server that should be ignored. For example, a cable modem that hands out private IP addresses when the cable sync has been lost. Enter the private IP address of the modem here, e.g. 192.168.100.1 and the firewall will never pick up or attempt to use a an IP address supplied by the specified server.

Advanced Configuration:
 

Enables options to control the protocol timing. In the vast majority of cases this must be left unchecked and the options inside unchanged.

Protocol Timing:
 The fields in this area give fine-grained control over the timing used by dhclient when managing an address on this interface. These options are almost always left at their default values. For more details on what each field controls, see the dhclient man page
Presets:Has several options for preset protocol timing values. These are useful as a starting point for custom adjustments or for use when the values need to be reset back to default values.
Configuration Override:
 

Enables a field to use a custom dhclient configuration file. The full path must be given. Using a custom file is rarely needed, but some ISPs require DHCP fields or options that are not supported in the pfSense GUI.

PPP Types

The various PPP-based connection types such as PPP, PPPoE, PPTP, and L2TP are all covered in detail earlier in this chapter (PPPs). When one of these types is selected here on the interfaces screen, their basic options can be changed as described. To access the advanced options, follow the link on this page or navigate to Interfaces > (assign) on the PPPs tab, find the entry, and edit it there.