Start a conversation

Network Objects Determining Traffic Direction

Overview

For an Exinda appliance to determine traffic direction, you must define all internal subnets as internal network objects.

This article details how these network objects can be edited and provides the comparison rules necessary for the location of an IP packet relative to an internal network object.

 

Information

  • Network objects can be edited from Configuration > Objects > Network > Network Objects.
  • After identifying the subnets as internal network objects, as traffic passes through the appliance, the appliance looks at the source IP and destination IP of the packet and matches them to the network objects.
    • This determines whether the source IP and destination IP should be considered internal or external, determining the packet direction.
  • Consider the following rules when comparing the location of an IP packet relative to an internal network object:

Source IP

Destination IP

Result
Internal External The packet is classified as outbound traffic.
External Internal The packet is classified as inbound traffic.
Internal Internal
  • 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.
External External
  • 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.



Related Article

Accelerating Traffic with WCCP

Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted
  3. Updated

Comments