What ports and protocols do Squiggle Bridge use?

Mar 25, 2011 at 11:43 AM

I'm trying out squiggle in a work environment, and am needing to use the Squiggle Bridge to bridge two subnets. In order for me to do this I need to know what ports and protocols the program uses before the network people will open the appropiate ports up, (as I need something definitive from the software supplier). Can you provide me these details to get the bridge working?

Thanks.

PS Very good program by the way and look forward to a future release that will save the chats as in a work environment documenting chats would be handy.

Coordinator
Mar 25, 2011 at 12:11 PM

Detailed instructions on configuring Squiggle bridge are available at http://squiggle.codeplex.com/documentation

Please let me know if it helps.

Mar 25, 2011 at 12:49 PM

Basically I have got to the point of installing the bridge on a computer in each subnet. So I take it from the documentation then the internal IP is the IP of the computer squiggle bridge is installed on, and external is the IP of the other computer on the subnet that has the bridge installed. Is that correct?

Coordinator
Mar 25, 2011 at 2:26 PM

No both of them are the IP of the same bridge node (possibly on different network cards). To enable communication between two disjoint network your bridge node needs to be able to accept connections from both the subnets. Only the IP specified in the target section is of the other bridge node.

Mar 25, 2011 at 8:10 PM
So basically lets say I have two subnets and the bridge is installed on computer 1 with a IP 10.20.30.0 and the other subnets computer 2 IP of 10.20.40.0, would I then leave the rest of the config alone and only enter each others IP address in the target section, or do I need to enter the IP of computer 1 into computer 1's subnet bridge program?
Coordinator
Mar 25, 2011 at 8:27 PM

If your router and firewall allow tcp connections from 10.20.30.0 to 10.20.40.0 then following need to be your configurations

Bridge 1 config (10.20.30.0):

<BridgeConfiguration>
<internalservicebinding ip="10.20.30.0" port="1235" />
<externalservicebinding ip="10.20.30.0" port="1236" />
<channelbinding ip="224.10.11.12" mport="9998" sport="9997" />
<targets>
<add ip="10.20.40.0" port="1236" />
</targets>
</BridgeConfiguration>

Bridge 2 config (10.20.40.0):

<BridgeConfiguration>
<internalservicebinding ip="10.20.40.0" port="1235" />
<externalservicebinding ip="10.20.40.0" port="1236" />
<channelbinding ip="224.10.11.12" mport="9998" sport="9997" />
<targets>
<add ip="10.20.30.0" port="1236" />
</targets>
</BridgeConfiguration>

Mar 30, 2011 at 10:50 AM

I have tried the adjusted config settings, but still no luck in getting the bridge working. Our firewalls are basically blocking the connections. This is where my initial query came in as the network people here can unblock certain ports as long as they have something definitive from which to work with, ie which ports and protocols that the program uses.

Coordinator
Mar 30, 2011 at 11:53 AM

Bridges communicate using TCP protocol and network guys only need to unblock the ports mentioned in externalservicebinding of each bridge node.

Which in your case would be 1236 of both the bridge nodes for communicating with each other. (If you used the above mentioned config).

Apr 4, 2011 at 10:22 AM

Thanks for your help with this, it is much appreciated. I have the ports opened, and have squiggle.bridge installed on two computers(a workstation in one subnet, and on a server in the other subnet) and have altered the config file accordingly. The workstation with the bridge is picking up when someone connects within it's subnet, and the squiggle bridge log shows this and is showing no errors. The other subnet with squiggle bridge installed though is showing errors:

Forward: Sender: 10.20.30.0:9997, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Erorr occured while forwarding presence message to bridge(s): The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
Erorr occured while getting user info from remote bridge for local client: Could not connect to net.tcp://10.20.40.0:1236/squigglebridge. The connection attempt lasted for a time span of 00:00:20.9687500. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.20.40.0:1236.
The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
Erorr occured while forwarding presence message to bridge(s): Could not connect to net.tcp://10.20.40.0:1236/squigglebridge. The connection attempt lasted for a time span of 00:00:20.9843750. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.20.40.0:1236.
The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

Basically the server that the bridge is installed on is a proxy server, and wondered if this might need to be entered into the config file someplace as I think that is what is causing the errors?

Coordinator
Apr 4, 2011 at 11:28 AM
Can you send me the log file of the second faulty bridge node?
Hasan

On Mon, Apr 4, 2011 at 1:22 PM, jw35 <notifications@codeplex.com> wrote:

From: jw35

Thanks for your help with this, it is much appreciated. I have the ports opened, and have squiggle.bridge installed on two computers(a workstation in one subnet, and on a server in the other subnet) and have altered the config file accordingly. The workstation with the bridge is picking up when someone connects within it's subnet, and the squiggle bridge log shows this and is showing no errors. The other subnet with squiggle bridge installed though is showing errors:

Forward: Sender: 10.20.30.0:9997, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Erorr occured while forwarding presence message to bridge(s): The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
Erorr occured while getting user info from remote bridge for local client: Could not connect to net.tcp://10.20.40.0:1236/squigglebridge. The connection attempt lasted for a time span of 00:00:20.9687500. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.20.40.0:1236.
The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
Erorr occured while forwarding presence message to bridge(s): Could not connect to net.tcp://10.20.40.0:1236/squigglebridge. The connection attempt lasted for a time span of 00:00:20.9843750. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.20.40.0:1236.
The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

Basically the server that the bridge is installed on is a proxy server, and wondered if this might need to be entered into the config file someplace as I think that is what is causing the errors?

Read the full discussion online.

To add a post to this discussion, reply to this email (squiggle@discussions.codeplex.com)

To start a new discussion for this project, email squiggle@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com


Apr 4, 2011 at 12:51 PM

The subnet with the server above in my previous post is the faulty bridge node. The bridge node on the workstation which seems to look ok and is not producing errors is posted below:

Broadcast: Sender: 10.20.30.51:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Broadcast: Sender: 10.20.30.50:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Broadcast: Sender: 10.20.30.50:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.UserUpdateMessage
Broadcast: Sender: 10.20.30.60:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Broadcast: Sender: 10.20.30.50:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.UserUpdateMessage                                            Forward: Sender: 10.20.40.79:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Forward: Sender: 10.20.40.159:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Forward: Sender: 10.20.40.82:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Forward: Sender: 10.20.40.51:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Forward: Sender: 10.20.40.57:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Forward: Sender: 10.20.40.87:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage

On checking the faulty bridge node it is now showing the following error:

Erorr occured while getting user info for a4b7b08f-3046-5c5e-93e4-77cd0050e2b3@10.20.40.1:1236: There was no endpoint listening at net.tcp://10.20.40.1:1236/squigglepresence that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Forward: Sender: 10.20.40.1:9997, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage

 

Coordinator
Apr 4, 2011 at 7:08 PM

Looking at the error it seems that the faulty bridge contains 10.20.40.1 in the target node section of the config but there is no bridge on that node.
Can you confirm the IPs of the machines and their respective config that they are correct?

And since one of your bridge nodes appears to be working correctly so are the clients of that subnet able to see people from other subnet?

Apr 5, 2011 at 10:21 AM

The IP of the faulty bridge(Proxy Server-10.20.40.0) should have read 10.20.40.0. I was trying a different IP setup to take into account the proxy server, but recieved the same error:

Erorr occured while getting user info for a4b7b08f-3046-5c5e-93e4-77cd0050e2b3@10.20.40.0:1236: There was no endpoint listening at net.tcp://10.20.40.0:1236/squigglepresence that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Forward: Sender: 10.20.40.0:9997, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage

I also checked the other bridge node(Workstation-10.20.30.0), and am now also getting the same error as above but with the 10.20.30.0 IP. People from the other subnets are not showing up on the Squiggle IM, but in the bridge log it was showing the Forward senders IP addresses of the 10.20.40.0 subnet previously. ie:

Forward: Sender: 10.20.40.159:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Forward: Sender: 10.20.40.82:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage

When setting up squiggle bridge, is it best to have all users logged off the network, and the Squiggle IM off?

Coordinator
Apr 6, 2011 at 6:44 PM

Users being online shouldn't matter much in theory but to isolate the problem maybe its a good idea to start the bridges while no one is online (as you mentioned).

If your faulty node is 10.20.40.0 then I wonder why is it trying to connect to its own self. It should be trying to find endpoints on the other node.

Apr 7, 2011 at 5:14 PM

I am trying to setup Squiggle Bridge within my office and I am having similar problems.  Squiggle works fine in both networks and users can see each other.  I have a question about the settings of the client vs bridge.  In the client the default settings (Squiggle settings - Connections) are

Presense port: 9998
Chat port: 9999

but in Bridge the settings are

Local Chat Service: 192.168.2.61:1235
Remote Chat Service: 192.168.2.61:1236
Channel MCast: 224.10.11.12:9998
Channel Service: 192.168.2.61:9997

Is it correct that the Chat port (9999) and the Channel Service port (9997) are different?

My logs also seem to show that the Bridge is connecting to itself.

 

Coordinator
Apr 7, 2011 at 5:42 PM

jvanderpluijm please show me both the config file if possible

Yes all ports can be different.

Apr 7, 2011 at 5:49 PM

Thank you for your quick response! Here are the config files:
<BridgeConfiguration>
<internalservicebinding ip="192.168.2.61" port="1235" />
<externalservicebinding ip="192.168.2.61" port="1236" />
<channelbinding ip="224.10.11.12" mport="9998" sport="9997" />
<targets>
<add ip="89.0.0.2" port="1236" />
</targets>
</BridgeConfiguration>
and
<BridgeConfiguration>
<internalservicebinding ip="89.0.0.2" port="1235" />
<externalservicebinding ip="89.0.0.2" port="1236" />
<channelbinding ip="224.10.11.12" mport="9998" sport="9997" />
<targets>
<add ip="192.168.2.61" port="1236" />
</targets>
</BridgeConfiguration>
We have a proxy/firewall between these networks and all ports are open between these computers.
Great project, keep up the good work!

From: hasankhan [email removed]
Sent: Thursday, April 07, 2011 2:43 PM
To: Jeff van der Pluijm
Subject: Re: What ports and protocols do Squiggle Bridge use? [squiggle:251183]

From: hasankhan

jvanderpluijm please show me both the config file if possible

Yes all ports can be different.

Coordinator
Apr 7, 2011 at 6:52 PM

I've reproduced the issue on my end I'm working on it to solve it.

Thank you for reporting it and sorry for any inconvenience caused.

I'll update this thread as soon as I fix it.

Regards


Hasan

Coordinator
Apr 7, 2011 at 7:49 PM

I've fixed the issue in bridge.

Please download the latest bridge and replace your existing copies with it.
Keep your configuration same and try now.

Coordinator
Apr 7, 2011 at 7:51 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Apr 7, 2011 at 10:16 PM

The fixed you provided work!  Thank you Hasan.

Jeff

Coordinator
Apr 8, 2011 at 5:03 AM

Jeff (ivanderpluijm) and jw35

You may be the first user who has successfully deployed the bridge.
If you're using it on official network and allowed to share the success story then please send me a line or two explaining how it has helped you so I can quote you on my blog.

Apr 8, 2011 at 9:24 AM

Well I'm a bit closer now to making this work. I tried the updated bridge and it took a bit for both subnets to see each other. The Squiggle IM on each subnet showed the users from the other subnet, but when attempting to send a message it would come up as failed to send. I then stopped the bridge services, cleared the logs, and restarted. After a restart of the bridges I cannot get the users to show up again on the contact list. At the moment on the server with the bridge on it is coming up with:

The connection attempt lasted for a time span of 00:00:21. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.20.30.0:1236.
Erorr occured while forwarding presence message to bridge(s): The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
Erorr occured while getting user info from remote bridge for local client: Cannot access a disposed object.
Object name: 'System.ServiceModel.Channels.ServiceChannel'.
Erorr occured while forwarding presence message to bridge(s): Cannot access a disposed object.
Object name: 'System.ServiceModel.Channels.ServiceChannel'.
Replay: Sender: 10.20.40.0:9997, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Erorr occured while forwarding presence message to bridge(s): Cannot access a disposed object.
Object name: 'System.ServiceModel.Channels.ServiceChannel'.
Erorr occured while forwarding presence message to bridge(s): The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

Coordinator
Apr 8, 2011 at 7:08 PM

Please wait for 2.6 version of Squiggle which will be released shortly. Hopefully all your bridge problems will be solved in that.

Thank you for your patience.

Coordinator
Apr 8, 2011 at 8:51 PM

Squiggle 2.6 has been released.

Please try the new Squiggle and its Bridge.

Apr 12, 2011 at 7:11 PM

Hello Hasan,
I was looking for an IM tool for our company's Information Technology team that would be simple to manage and secure. Squiggle covered these requirements. With no server to install or maintain the setup was a breeze; simply run the client and start communicating. The UI has nice graphics and a simple layout that user-friendly. The Squiggle Bridge companion service enabled us to link our branch office employees which facilitates our internal communication. Simple, secure, perfect.
Jeff


From: hasankhan [email removed]
Sent: Friday, April 08, 2011 2:04 AM
To: Jeff van der Pluijm
Subject: Re: What ports and protocols do Squiggle Bridge use? [squiggle:251183]

From: hasankhan

Jeff (ivanderpluijm) and jw35

You may be the first user who has successfully deployed the bridge.
If you're using it on official network and allowed to share the success story then please send me a line or two explaining how it has helped you so I can quote you on my blog.

Coordinator
Apr 12, 2011 at 7:24 PM

Thanks Jeff

I've posted it on my blog here http://www.overroot.com/blog/?p=347

Apr 26, 2011 at 12:45 PM

I've tried the new Squiggle bridge and clients but still am unable to send a message over the Squiggle bridge. The Squiggle IM on each subnet shows the users from the other subnet, but when attempting to send a message it would come up as failed to send on the one subnet(10.20.40.0), and when attempting to send from the other subnet(10.20.30.0) it does not come up as fail, but the message does not arrive on the other end.

Coordinator
Apr 26, 2011 at 12:52 PM
Can you please share the error log?
Apr 26, 2011 at 1:17 PM

I don't see an error log on this new version(client/bridge)? Where is the log's now kept?


From: hasankhan [notifications@codeplex.com]
Sent: 26 April 2011 13:52
To: bvcsjwicks
Subject: Re: What ports and protocols do Squiggle Bridge use? [squiggle:251183]

From: hasankhan

Can you please share the error log?
Coordinator
Apr 26, 2011 at 3:51 PM
In new version error logging is disabled by default you can enable it by uncommenting the following snippet in Squiggle.Bridge.exe.config

<!--
<trace autoflush="true" >
<listeners>
<add name="FileListener"
type="System.Diagnostics.TextWriterTraceListener"
initializeData="Squiggle.Bridge.log" />
</listeners>
</trace>
-->

By removing the <!-- and --> marks

Also please share the logs of both the bridges with their corresponding config files

Thanks

Hasan
Apr 27, 2011 at 12:25 PM

Hi thanks for the reply. I have the logs of both bridges with their config files pasted below:

Subnet 1

Forward: Sender: 10.20.40.79:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Forward: Sender: 10.20.40.57:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Forward: Sender: 10.20.40.88:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Forward: Sender: 10.20.40.87:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Forward: Sender: 0.1.0.5:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
Erorr occured while getting user info for e0b7f357-e666-4122-b9ce-cdc8a49adbe6@0.1.0.5:9999: Cannot access a disposed object.
Object name: 'System.ServiceModel.Channels.ServiceChannel'.
Erorr occured while getting user info for e0b7f357-e666-4122-b9ce-cdc8a49adbe6@0.1.0.5:9999: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
Erorr occured while getting user info for e0b7f357-e666-4122-b9ce-cdc8a49adbe6@0.1.0.5:9999: Could not connect to net.tcp://0.1.0.5:9999/squigglepresence. The connection attempt lasted for a time span of 00:00:01.0937500. TCP error code 10061: No connection could be made because the target machine actively refused it 0.1.0.5:9999.
Forward: Sender: 10.20.40.91:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Forward: Sender: 10.20.40.59:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Forward: Sender: 10.20.40.73:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Forward: Sender: 10.20.40.66:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage

<?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.20.40.0" port="1235" />
    <externalservicebinding ip="10.20.40.0" port="1236" />
    <channelbinding ip="224.10.11.12" mport="9998" sport="9997" />
    <targets>
      <add ip="10.20.30.0" port="1236" />
    </targets>
  </BridgeConfiguration>
  <system.diagnostics>
    <trace autoflush="true" >
      <listeners>
        <add name="FileListener"
           type="System.Diagnostics.TextWriterTraceListener"
           initializeData="Squiggle.Bridge.log" />
      </listeners>
    </trace>
    <!--
    <sources>
      <source name="System.ServiceModel" switchValue="Warning" propagateActivity="true" >
        <listeners>
          <add name="xml"/>
        </listeners>
      </source>
    </sources>   
    <sharedListeners>
      <add name="xml"
           type="System.Diagnostics.XmlWriterTraceListener"
           initializeData="Squiggle.Bridge.svclog" />
    </sharedListeners>
    -->
  </system.diagnostics>
</configuration>

Subnet 2


Replay: Sender: 10.20.40.73:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Replay: Sender: 10.20.30.0:9997, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Replay: Sender: 10.20.40.66:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Replay: Sender: 10.20.30.0:9997, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Replay: Sender: 10.20.40.65:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Erorr occured while getting user info from remote bridge for local client: Object reference not set to an instance of an object.
Erorr occured while getting user info from remote bridge for local client: Object reference not set to an instance of an object.
Erorr occured while getting user info from remote bridge for local client: This request operation sent to net.tcp://10.20.40.0:1236/squigglebridge did not receive a reply within the configured timeout (00:01:00).  The time allotted to this operation may have been a portion of a longer timeout.  This may be because the service is still processing the operation or because the service was unable to send a reply message.  Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.
Erorr occured while getting user info from remote bridge for local client: Object reference not set to an instance of an object.
Replay: Sender: 10.20.30.0:9997, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Replay: Sender: 10.20.40.87:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Replay: Sender: 10.20.30.0:9997, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Replay: Sender: 10.20.40.125:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Forward: Sender: 10.20.30.0:9999, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage
Replay: Sender: 10.20.40.0:9997, Message: Squiggle.Chat.Services.Presence.Transport.Messages.KeepAliveMessage

<?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.20.30.0" port="1235" />
    <externalservicebinding ip="10.20.30.0" port="1236" />
    <channelbinding ip="224.10.11.12" mport="9998" sport="9997" />
    <targets>
      <add ip="10.20.40.0" port="1236" />
    </targets>
  </BridgeConfiguration>
  <system.diagnostics>
    <trace autoflush="true" >
      <listeners>
        <add name="FileListener"
           type="System.Diagnostics.TextWriterTraceListener"
           initializeData="Squiggle.Bridge.log" />
      </listeners>
    </trace>
    <!--
    <sources>
      <source name="System.ServiceModel" switchValue="Warning" propagateActivity="true" >
        <listeners>
          <add name="xml"/>
        </listeners>
      </source>
    </sources>   
    <sharedListeners>
      <add name="xml"
           type="System.Diagnostics.XmlWriterTraceListener"
           initializeData="Squiggle.Bridge.svclog" />
    </sharedListeners>
    -->
  </system.diagnostics>
</configuration>

Coordinator
Apr 28, 2011 at 8:00 AM

Hi jw35

It seems your nodes in the subnet can directly connect to each other and the only problem you have is unavailability of multicast support.
In this case you should be using multicast service instead of bridge.

http://squiggle.codeplex.com/wikipage?title=How%20to%20configure%20Squiggle%20Multicast&referringTitle=Documentation

Also it seems to me that some of the clients in your network are not updated.
Please double check and make sure that all the clients latest 2.6.8 and then install multicast service on just one machine in any of the two subnets.

That will definitely solve your problem.