Add ADSL Interfaces for Single Firewalls

You can configure ADSL Interfaces on some legacy Forcepoint NGFW appliances.

Note: ADSL Interfaces are only supported on specific legacy Forcepoint NGFW appliances that have an integrated ADSL network interface card.

You can only configure one ADSL Interface for each Single Firewall. ADSL Interfaces are not supported on Firewall Clusters.

The supported ADSL standards are ANSI T1.413 issue 2n, G.dmt, G.lite, ADSL2 DMT, ADSL2 G.lite, Annex A, and Annex B.

Use the number of the ADSL port on the appliance as the Interface ID of the ADSL Interface. For information about mapping the ADSL port on the appliance, see the relevant Hardware Guide.

For more details about the product and how to configure features, click Help or press F1.

Steps

  1. Right-click a Single Firewall and select Edit Single Firewall.
  2. In the navigation pane on the left, select Interfaces.
    The Interfaces pane opens on the right.
  3. Right-click the empty space and select New > ADSL Interface.
  4. Define the ADSL Interface properties.
  5. Click OK.
    The ADSL Interface is added to the interface list.

Next steps

You are now ready to add IP addresses for the Single Firewall.

ADSL Interface Properties dialog box

Use this dialog box to configure properties for ADSL Interfaces.

Note: ADSL Interfaces are only supported on specific legacy Forcepoint NGFW appliances that have an integrated ADSL network interface card.
Option Definition
General tab
Interface ID Select the number of the ADSL port on the appliance as the Interface ID. The Interface ID is automatically mapped to the ADSL port on the engine’s ADSL card during the initial configuration of the engine.
Zone

(Optional)

 Select the network zone to which the interface belongs. Click Select to select an element, or click New to create an element.
MTU

(Optional)

The maximum transmission unit (MTU) size on the connected link. Either enter a value between 400–65535 or select a common MTU value from the list.

If the interface is a Physical Interface, the same MTU is automatically applied to any VLANs created under it.

The default value (also the maximum standard MTU in Ethernet) is 1500. Do not set a value larger than the standard MTU, unless you know that all devices along the communication path support it.

To set the MTU for a Virtual NGFW Engine, you must configure the MTU for the interface on the Master NGFW Engine that hosts the Virtual NGFW Engine, then refresh the policy on the Master NGFW Engine and the Virtual NGFW Engine.
Comment

(Optional)

 A comment for your own reference.
Option Definition
QoS Mode

(Optional)

Defines how QoS is applied to the link on this interface.

If Full QoS or DSCP Handling and Throttling is selected, a QoS policy must also be selected. If Full QoS is selected, the throughput must also be defined.

If the interface is a Physical Interface, the same QoS mode is automatically applied to any VLANs created under it.

QoS Policy

(When QoS Mode is Full QoS or DSCP Handling and Throttling)

The QoS policy for the link on this interface.

If the interface is a Physical Interface, the same QoS policy is automatically selected for any VLANs created under it.

Note: If a Virtual Resource has a throughput limit defined, the interfaces on the Virtual NGFW Engine that use a QoS policy all use the same policy. The policy used in the first interface is used for all the interfaces.
Interface Throughput Limit

(When QoS Mode is Full QoS)

Enter the throughput for the link on this interface as megabits per second.

If the interface is a Physical Interface, the same throughput is automatically applied to any VLANs created under it.

The throughput is for uplink speed (outgoing traffic) and typically must correspond to the speed of an Internet link (such as an ADSL line), or the combined speeds of several such links when connected to a single interface.

CAUTION:
Make sure that you set the interface speed correctly. When the bandwidth is set, the NGFW Engine always scales the total amount of traffic on this interface to the bandwidth you defined. This scaling happens even if there are no bandwidth limits or guarantees defined for any traffic.
CAUTION:
The throughput for a Physical Interface for a Virtual NGFW Engine must not be higher than the throughput for the Master NGFW Engine interface that hosts the Virtual NGFW Engine. Contact the administrator of the Master NGFW Engine before changing this setting.
Option Definition
ADSL Settings section
VCI Enter the VCI (Virtual Channel Identifier) value according to the configuration information provided by your ISP.
VPI Enter the VPI (Virtual Path Identifier) value according to the configuration information provided by your ISP.
Multiplexing Mode Select VC (Virtual Circuit) or LLC (Logical Link Control) according to the configuration information provided by your ISP.
Comment

(Optional)

 A comment for your own reference.
Option Definition
Advanced tab

(All optional settings)

Override Engine's Default Settings When selected, the default settings of the NGFW Engine are overridden.
SYN Rate Limits
  • Default — The interface uses the SYN rate limits defined for the NGFW Engine on the Advanced Settings branch of the Engine Editor.
  • None — Disables SYN rate limits on the interface.
  • Automatic — This is the recommended mode if you want to override the general SYN rate limits defined on the Advanced Settings branch of the Engine Editor. The NGFW Engine calculates the number of allowed SYN packets per second and the burst size (the number of allowed SYNs before the NGFW Engine starts limiting the SYN rate) based on the NGFW Engine’s capacity and memory size.
  • Custom — Enter the values for Allowed SYNs per Second and Burst Size.
Allowed SYNs per Second Defines the number of allowed SYN packets per second.
Burst Size The number of allowed SYNs before the NGFW Engine starts limiting the SYN rate.

We recommend that you set the burst size to be at least one tenth of the Allowed SYNs per Second value. If the burst size is too small, SYN rate limits do not work. For example, if the value for Allowed SYNs per Second is 10000, set the value for Burst Size to at least 1000.

Enable Log Compression

By default, each generated Antispoofing and Discard log entry is logged separately and displayed as a separate entry in the Logs view. Log Compression settings allow you to define the maximum number of separately logged entries. When the defined limit is reached, a single antispoofing log entry or Discard log entry is logged. The single entry contains information about the total number of the generated Antispoofing log entries or Discard log entries. After this log entry, the logging returns to normal and all generated entries are once more logged and displayed separately. Log Compression is useful when the routing configuration generates a large volume of antispoofing logs or the number of Discard logs becomes high.

For each event type, Antispoofing or Discard, you can define:
  • Log Rate (Entries/s) — The maximum number of entries per second. The default value for antispoofing entries is 100 entries/s. By default, Discard log entries are not compressed.
  • Burst Size (Entries) — The maximum number of matching entries in a single burst. The default value for antispoofing entries is 1000 entries. By default, Discard log entries are not compressed.
Set to Default Returns all changes to the log compression settings to the default settings.