Squiggle Lan Messenger

Squiggle is a free, open source, LAN Messenger that supports: Server-less peer to peer LAN chat No Installation required, just download, unzip and run Groupchat, Broadcast chat and Private chat Bridge for connecting two LANs across subnets or WAN (MESH nodes) Fast (multiple) file transfer Spell Check, Buzz, Emoticons, Audio Alerts and Tray Popups Contact Groups, Display Message, Display Pic, Chat Commands Chat History, Status History Contact Status (on-line, off-line, away…etc.) Voice Chat

You will also need to have installed: Software required: Squiggle Client Squiggle Bridge (optional) This software may be downloaded from the Squiggle home page: https://squiggle.codeplex.com (in the “DOWNLOADS” section) You will also need to have installed: .NET Framework 4.0 http://www.microsoft.com/en-us/download/details.aspx?id=17851 Visual C++ 2010 Redistributable http://www.microsoft.com/en-us/download/details.aspx?id=5555 This information is also available by clicking on the “System Requirements” link on the Squiggle home page.

There are two pieces to Squiggle: Squiggle Client – this is the “application” that you run that provides the chat interface, there is no setup required, all settings should be automatically found and entered when the program is launched. 2. Squiggle Bridge – this is the “bridge” software required to connect to multiple subnets “MESH Nodes” and MUST be run on one computer attached tor each node. It can either be launched like an application (good for troubleshooting) or setup as a Windows service. Listens for any Squiggle Client traffic and routes it to other nodes that are also running a bridge. This does require some manual configuration, I will get into that in the next slide. The current “Stable” version is 3.3 and will be used in the demo

Squiggle Bridge To connect to multiple MESH nodes it is necessary to run Squiggle Bridge on one computer attached to each node. Additional computers attached to the same node only need to be running the Squiggle Client application. In order to allow Squiggle Bridge to “see” the other nodes in the group some configuration is required. Here is an example of the default config file:

<?xml version="1.0"?> <configuration> <configSections> <section name="BridgeConfiguration" type="Squiggle.Bridge.Configuration.BridgeConfiguration, Squiggle.Bridge, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null"/> </configSections> <BridgeConfiguration> <InternalServiceBinding IP="10.58.241.212" Port="1235"/> <ExternalServiceBinding IP="10.58.241.212" Port="1236"/> <PresenceBinding MulticastIP="226.10.11.12" MulticastPort="9998" ServicePort="9997" CallbackPort="9996" /> <Targets> <add IP="10.115.218.213" Port="1236"/> </Targets> </BridgeConfiguration> <system.diagnostics> <!-- <trace autoflush="true" > <listeners> <add name="FileListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="Squiggle.Bridge.log" /> </listeners> </trace> //--> </system.diagnostics> <startup> <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/> </startup> </configuration>

To modify the Squiggle. Bridge. exe To modify the Squiggle.Bridge.exe.config file you will need to do the following: Get the IP Address of each computer in the network that is running the bridge on that node. For this demonstration let us assume we have three nodes and the IP addresses for the computer running the Squiggle Bridge are: (NODE #1) - 10.58.241.212 (NODE #2) - 10.115.218.213 (NODE #3) - 10.117.54.182 On the “local” computer running the bridge for that node find the “<Bridge Configuration>” section and change the default IP address in the lines that have “InternalServiceBinding” and “ExternalServiceBinding” to the IP address of that computer Then in the “<Targets>” section add a new IP line for the additional computers running Squiggle Bridge on the other nodes and add each IP address to a line. So the files should look like this:

(NODE #1) - 10.58.241.212 (NODE #2) - 10.115.218.213 (NODE #3) - 10.117.54.182 <?xml version="1.0"?> <configuration> <configSections> <section name="BridgeConfiguration" type="Squiggle.Bridge.Configuration.BridgeConfiguration, Squiggle.Bridge, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null"/> </configSections> <BridgeConfiguration> <InternalServiceBinding IP="10.58.241.212" Port="1235"/> <ExternalServiceBinding IP="10.58.241.212" Port="1236"/> <PresenceBinding MulticastIP="226.10.11.12" MulticastPort="9998" ServicePort="9997" CallbackPort="9996" /> <Targets> <add IP="10.115.218.213" Port="1236"/> <add IP="10.117.54.182" Port="1236"/> </Targets> </BridgeConfiguration> <system.diagnostics> <!-- <trace autoflush="true" > <listeners> <add name="FileListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="Squiggle.Bridge.log" /> </listeners> </trace> //--> </system.diagnostics> <startup> <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/> </startup> </configuration>

(NODE #1) - 10.58.241.212 (NODE #2) - 10.115.218.213 (NODE #3) - 10.117.54.182 <?xml version="1.0"?> <configuration> <configSections> <section name="BridgeConfiguration" type="Squiggle.Bridge.Configuration.BridgeConfiguration, Squiggle.Bridge, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null"/> </configSections> <BridgeConfiguration> <InternalServiceBinding IP="10.115.218.213" Port="1235"/> <ExternalServiceBinding IP="10.115.218.213" Port="1236"/> <PresenceBinding MulticastIP="226.10.11.12" MulticastPort="9998" ServicePort="9997" CallbackPort="9996" /> <Targets> <add IP="10.58.241.212" Port="1236"/> <add IP="10.117.54.182" Port="1236"/> </Targets> </BridgeConfiguration> <system.diagnostics> <!-- <trace autoflush="true" > <listeners> <add name="FileListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="Squiggle.Bridge.log" /> </listeners> </trace> //--> </system.diagnostics> <startup> <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/> </startup> </configuration>

(NODE #1) - 10.58.241.212 (NODE #2) - 10.115.218.213 (NODE #3) - 10.117.54.182 <?xml version="1.0"?> <configuration> <configSections> <section name="BridgeConfiguration" type="Squiggle.Bridge.Configuration.BridgeConfiguration, Squiggle.Bridge, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null"/> </configSections> <BridgeConfiguration> <InternalServiceBinding IP="10.117.54.182" Port="1235"/> <ExternalServiceBinding IP="10.117.54.182" Port="1236"/> <PresenceBinding MulticastIP="226.10.11.12" MulticastPort="9998" ServicePort="9997" CallbackPort="9996" /> <Targets> <add IP="10.58.241.212" Port="1236"/> <add IP="10.115.218.213" Port="1236"/> </Targets> </BridgeConfiguration> <system.diagnostics> <!-- <trace autoflush="true" > <listeners> <add name="FileListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="Squiggle.Bridge.log" /> </listeners> </trace> //--> </system.diagnostics> <startup> <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/> </startup> </configuration>