Configuring internal subnets as internal network objects

For the Exinda Appliance to determine 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 the following rules:

Rule	Result
Packet's source IPInternet protocol matches an Internal Network Object AND Packet's destination IP DOES NOT match an Internal Network Object	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	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.

1. On your browser, open the Exinda Web UI (https://Exinda_IP_address).
2. Key-in the User and Password.
3. Click Login.

4. Click Objects > Network.
5. To change a network objecta logical definition created and stored in the Exinda lilbrary, can represent any network component to an internal object, click Edit and change the location to Internal.
6. Click Apply Changes.