How to configure Squiggle Bridge

To connect two networks with the bridge you need Squiggle bridge to be installed on a machine in each network as a windows service.
To install the bridge execute the following command on command prompt (in bridge directory).

Squiggle.Bridge -i

Now change the BridgeConfiguration section of Squiggle.Bridge.exe.config file on both the nodes to point to each other like so:

<BridgeConfiguration>
<InternalServiceBinding ip="127.0.0.1" port="1235" />
<ExternalServiceBinding ip="127.0.0.1" port="1236" />
<PresenceBinding MulticastIP="224.10.11.12" MulticastPort="9998" ServicePort="9997" CallbackPort="9996" />
<targets>
<add ip="127.0.0.1" port="1234" />
</targets>
</BridgeConfiguration>

InternalServiceBinding refers to the IP and (TCP) Port used by bridge to talk to the nodes with in its own network
ExternalServiceBinding refers to the IP and (TCP) Port used by bridge to talk to the other bridge across the network. (The two bridges should be able to communicate with each other using their ExternalServiceBinding)
channelbinding refers to the multicast IP and udp and tcp port used by bridge to talk to the nodes with in its own network.

Please note that PresenceBinding, InternalServiceBinding and ExternalServiceBinding all point to different IPs of the same bridge node (possibly on different network cards).

In the target section you have to specify the (ExternalServiceBinding) ip and port of other bridges that this bridge needs to talk to.
So if you have 2 bridges and 2 networks then each bridge will have one target node specified containing the ExternalServiceBinding of the other bridge.

Make sure the service is running on both the nodes and then signing Squiggle on a client on each network. Both clients should be able to see each other now.

Last edited Dec 21, 2012 at 7:39 AM by hasankhan, version 5

Comments

PRKELLY Nov 28, 2016 at 7:20 PM 
In attempting to start the bridge service on another PC i get the following error: The Squiggle Bridge service on the local computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

Any input on this?

missviv2 Mar 18, 2015 at 4:58 PM 
The first comment and the instructions have all of the necessary information for connecting 2 or more different subnets. However, the Windows service "SquiggleBridge" is not started automatically from the installation using "Squiggle.Bridge -i". You need to go into your Windows services and start it on each computer that you made a node in each subnet. It is set to start automatically in the settings, but that is only upon a restart of your computer. I hope this helps!

stevegerrish Jun 4, 2013 at 2:51 PM 
Here's an example of a working config that connects 3 different subnets

************************************************CONFIG 1************************************************************
Server on 172.16.0.0/24 Subnet

<BridgeConfiguration>
<InternalServiceBinding ip="172.16.0.242" port="1235" />
<ExternalServiceBinding ip="172.16.0.242" port="1236" />
<PresenceBinding MulticastIP="224.10.11.12" MulticastPort="9998" ServicePort="9997" CallbackPort="9996" />
<targets>
<add ip="192.168.220.239" port="1237" />
<add ip="172.16.2.253" port="1238" />
</targets>
</BridgeConfiguration>

************************************************END CONFIG 1******************************************************

************************************************CONFIG 2************************************************************
Server on 192.168.220.0/24 Subnet

<BridgeConfiguration>
<InternalServiceBinding ip="192.168.220.239" port="1235" />
<ExternalServiceBinding ip="192.168.220.239" port="1237" />
<PresenceBinding MulticastIP="224.10.11.12" MulticastPort="9998" ServicePort="9997" CallbackPort="9996" />
<targets>
<add ip="172.16.0.242" port="1236" />
<add ip="172.16.2.253" port="1238" />
</targets>
</BridgeConfiguration>

************************************************END CONFIG 2******************************************************

************************************************CONFIG 3************************************************************
Server on 172.16.2.0/23 Subnet

<BridgeConfiguration>
<InternalServiceBinding ip="172.16.2.253" port="1235" />
<ExternalServiceBinding ip="172.16.2.253" port="1238" />
<PresenceBinding MulticastIP="224.10.11.12" MulticastPort="9998" ServicePort="9997" CallbackPort="9996" />
<targets>
<add ip="172.16.0.242" port="1236" />
<add ip="192.168.220.239" port="1237" />
</targets>
</BridgeConfiguration>

************************************************END CONFIG 3******************************************************

Hope this helps!

edwardally Jan 21, 2013 at 8:06 AM 
Hi,

I think I not manage to get it done for 3 or more network configuration. any help? Thanks

hasansarif Jun 27, 2012 at 11:23 AM 
Hi,

Can u give me an example..

I have two network 192.168.0.1/24 and 192.168.3.1/24 both are connected. here how can i use squiggle.

Please suggest.

bugmenot2 Feb 22, 2012 at 11:04 AM 
The situation here in my case is that we don't have static IPs on some PC's as we need to connect from remote locations to office. I don't think the Bridge or Multicast option would work in this case. If yes, please let me know. Thanks

hasankhan Dec 30, 2011 at 5:53 AM 
You can connect as many networks with Bridge as you want. You just need to add the servers in Targets section of the config file. We kept it server-less so that installing it would be very easy and you wouldn't need permission from your network admin to run this.

manighani Oct 14, 2011 at 11:23 AM 
i want to know that if there is a way that i can connect 3 or more network with bridge and why dont you made a server for your software so that multiple network can connect to each other, by the way this software is excellent