Squiggle uses a network communication protocol called UDP Multicast. It allows Squiggle to send one message that is read by multiple machines in the network. Sometimes UDP multicasting doesn't work because of the following reasons
  • UDP multicast has been disabled on router
  • Your machines are in different subnets

If only UDP multicast is unavailable but your machines are able to make direct TCP connections then you can install Multicast service in one of the nodes of the network and configure all clients to point to the IP of that machine for multicasting. All clients then talk to that machine for sending a message to multiple recipients and then that service routes the message to appropriate machines.

Chat messages however continue to be sent directly to recipients.


While Multicast Service solves the problem of unavailability of UDP communication protocol but it Squiggle still needs direct TCP connection between clients for chat messages. Sometimes direct TCP connection is also not possible because client are across WAN or network firewall settings don't allow such connections. In this case you can install the bridge service on one machine of each network that your clients are part of. These bridges then make direct TCP connections and all messages are routed from bridge of one network to the bridge of the second network and the second bridge finally routes the message to appropriate node.

This helps you keep only single port open across two networks or subnets.

Last edited Dec 31, 2013 at 5:13 AM by hasankhan, version 4


No comments yet.