Phone Lines icon GFI Support

Articles in this section

See more

Configuring Internal Subnets as Internal Network Objects

Author: Timothy Parker Updated

Overview

For the Exinda appliance to determine the traffic direction, all internal subnets should be defined as internal network objects.

After identifying the subnets as internal network objects, as traffic passes through the appliance, the Exinda appliance determines packet direction based on certain rules.

This article provides the process to change a network object to an internal object and also the rules on which the Exinda appliance determines the packet direction.

 

Information

Rules

 

Rule

Result

Packet's source IP matches an Internal Network Object.

AND

Packet's destination IP DOES NOT match an Internal Network Object.

The packet is classified as outbound traffic.

Packet's source IP DOES NOT match an Internal Network Object.

AND

Packet's destination IP matches an Internal Network Object.

The packet is classified as inbound traffic.

Packet's source IP matches an Internal Network Object.

AND

Packet's destination IP matches an Internal Network Object.
  • Traffic flowing from the lower IP to the higher IP is classified as outbound traffic.
  • Traffic flowing from the higher IP to the lower IP is classified as inbound traffic.

Packet's source IP DOES NOT match an Internal Network Object.

AND

Packet's destination IP DOES NOT match an Internal Network Object.
  • Traffic flowing from the lower IP to the higher IP is classified as outbound traffic.
  • Traffic flowing from the higher IP to the lower IP is classified as inbound traffic.

 

Process

  1. On your browser, open the Exinda Web UI (https://<Exinda_IP_address>).
  2. Key in the Username and Password.
  3. Click Login.
  4. Click Objects > Network.
  5. To change a network object to an internal object, click Edit and change the location to Internal.
  6. Click Apply Changes.