OverviewWhen accelerating connections, Exinda appliances forward an accelerated packet from device to device with the appropriate options. As a result, the Exinda needs an IP of the corresponding peer to send the packets to during the connection. In a case where an appliance has multiple IP addresses, the firmware is designed to always send WAN Memory packets to the IP of another Exinda Peer that is associated with its default gateway. This information is the information that is shared in the Community.
For example, if an Exinda Peer is configured with two IPs - 192.168.10.10/24 on bridge 2 and 10.10.10.10/24 on eth1 and the default gateway is configured for 192.168.10.1, once the community has joined, the other appliances in the community will always attempt to send WM packets to 192.168.10.10. Please ensure the default gateway is always associated with the interface that you want to use for your WM/Community for acceleration.
There is no way to change this IP destination. Even if the other IPs are reachable through ping, even if the appliance has configured TCP Acceleration for NO Auto-Discovery, and even if the Auto-Discovery IP is manually set, each Exinda's WAN Memory will always attempt to communicate to other WAN Memories by sending port 8013 packets destined to their IPs associated with their default gateways.