1. Home
  2. Wanos Admin Guide
  3. Troubleshooting
  4. Peer Down

Peer Down

Items to check for whenever peers are down.

 

peerstatus

By default, Wanos is in bridge/switch mode. This means traffic flows through Wanos transparently as if it was a single cable.

In a simple point to point deployment, no configuration is essential to get the peers online. No traffic policies, are needed and it will work with a simple plug and play operation. For initial testing, it is recommended to start with this deployment. In its simplest form the only requirements for Wanos to start working are the default/factory settings, wan0 cabled to the router side and LAN to LAN traffic flows in both directions via both Wanos bridges. IP Address and Gateway is highly recommended, but not absolutely essential to get started.

To ensure the correct operation of the bridge deployment, consider the following:

Test with TCP Traffic:

  • Peers are triggered by the start of non-encrypted TCP traffic between the two optimized sites.
  • If peers initially do not discover each other when testing with CIFS/SMB, reboot one of the test Windows machines.

Cabling & Port Roles:

  • To avoid the possibility of a network loop, ensure that wan0 and lan0 does not connect to the same network segment or VLAN.
  • Verify that the network cables connected to wan0 and lan0 are correct. wan0 connects to the WAN Router and lan0 to the Server or Workstation LAN. Use Switch Interface Port Roles to swap ports if needed.

network networkinterfaces

 

 

  • Check Wanos Logs for Peer detected on lan0 message.

diagnostics-logging-peerdetected

 

Promiscuous Mode

  • Verify that Promiscuous Mode is enabled in ESXi on Port Group level. Avoid promiscuous mode at vSwitch level. For Hyper-V and other hyper-visors use mac-spoofing or bridging

ESXi Promiscuous Mode

 

  • Ping other Wanos peers or end to end machines to ensure that communication is successful.

Ping Peers

 

Firewalls

  • Some firewalls strip TCP Options. If this is suspected, configure the Firewall to allow TCP Option 76 or configure Wanos for Tunnel mode. It is recommended to configure the firewalls to preserve TCP Option 76 over enabling Tunnel mode.
  • Some firewall may block IPComp traffic. If this is suspected, configure the Firewall to allow IPComp or enable UDP encapsulation on all ends.

systemsettings optimizationsettings encap

 

Traffic Flow Direction

  • Traffic needs to flow through both devices in both directions. Check the Dashboard and Interface traffic graphs to ensure all traffic that needs to be optimized flows through the appliance. Lan0 and Wan0 graphs will be mirror images of each other. Ensure that traffic to the remote side and traffic from the remote side flows through the appliance. Verify this on both sides of the link.

dashboard optimized

 

Peer Timeout

The time to wait for optimized traffic before declaring a peer idle. If the timeout expires, traffic to the remote peer will be bypassed until the peer comes online. Peers detect each other with TCP Option 76. To trigger peers to come online, start a new TCP session.

Increase the peer timeout if required. Alternatively, to enable peers to remain in the Active state while communicating via control channel, configure: CONTROL_TRAFFIC_KEEPALIVE=true in /tce/etc/wanos/wanos.conf

systemsettings-optimizationsettings-peertimeout




Was this article helpful to you? Yes No

How can we help?