We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda CloudGen Firewall

This Firmware Version Is End-Of-Support

Documentation for this product is no longer updated. Please see End-of-Support for CloudGen Firewall Firmware for further information on our EoS policy.

How to Create Interface Groups

  • Last updated on

Processing of access rules does not necessarily need to be associated with the physical network environment on the box level of an F-Series Firewall. On systems equipped with multiple network interfaces, you can explicitly define specific interfaces for usage when a rule comes into action.

An interface group specifies the interface that the source address is allowed to use. When you create access rules, you can use predefined groups, or if you want to reference custom interfaces that are not in the default list, you can create custom interface groups. For each rule an interface may be assigned to origin and destination of the connection request when selected in the Connection Objects settings.

Predefined interface groups

  1. Go to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > Firewall > Forwarding Rules.
  2. From the left menu, expand the Firewall Objects menu and select Interface Groups.

The following predefined network interface objects are available for selection: 

  • Any – With this setting the first interface matching the request is utilized for the connection in accordance with routing configuration. The packet source is not verified. Reply packets might be forwarded through another interface, if multiple interfaces capable of doing so are available. Not to check the physical source of packets might sometimes be needed in very special configurations.

    For security reasons do not use this setting without explicit need.

  • Matching (default) – This setting ensures that arriving packets are processed through the same interface, which will forward the corresponding reply packets. Source and destination addresses are thus only reversed. This method aims at preventing a network attack, in which an attacker might try using internal addresses from outside the internal network (IP spoofing).

    With eventing activated (parameter IP Spoofing set to yes), IP spoofing identification will trigger the events FW IP Spoofing Attempt Detected [4014] and FW Potential IP Spoofing Attempt [4015].

  • RAM, ADSL, DHCP, ISDN, SERIAL, 3G, ... – Explicitly restricts rule processing to the specified dynamic network interface (if installed and configured). 

Create an interface group

  1. Go to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > Firewall > Forwarding Rules.
  2. Click Lock.
  3. Right-click the table and select New.

  4. In the Edit/Create an Interface Group window, enter a descriptive Name for the interface group.
  5. From the Interface drop-down list, select your desired option:
    • match (default) – This setting ensures that arriving packets are processed through the same interface, which will forward the corresponding reply packets. Source and destination addresses are thus only reversed. This method aims at preventing a network attack, in which an attacker might try using internal addresses from outside the internal network (IP spoofing).

      With eventing activated (parameter IP Spoofing set to yes), IP spoofing identification will trigger the events FW IP Spoofing Attempt Detected [4014] and FW Potential IP Spoofing Attempt [4015].

    • any – With this setting the first interface matching the request is utilized for the connection in accordance with routing configuration. The packet source is not verified. Reply packets might be forwarded through another interface, if multiple interfaces capable of doing so are available. Not to check the physical source of packets might sometimes be needed in very special configurations.

      For security reasons do not use this setting without explicit need.

    • eth0 - 4 – Lets you select a specific port.
    • dhcp – Explicitly restricts rule processing to the specified dynamic network interface (if installed and configured).
  6. Click Add to add the interface to the list.
  7. Click OK.
  8. Click Send Changes and Activate.
Last updated on