Jump to content
OpenSplice DDS Forum

Search the Community

Showing results for tags 'unicast'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • About OpenSplice DDS
    • News and Events
    • Site Feedback
  • Using OpenSplice DDS
    • General
    • Troubleshooting
  • Understanding OpenSplice DDS
    • OpenSplice DDS Slideshows
    • OpenSplice DDS Movies
  • Community
    • Project: SIMD
    • Project: CamelOS
    • Project: DDS Touchstone
    • Project: RESTful DDS
    • Mac OS X

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Company

Found 3 results

  1. Hello, I try to configure OpenSplice to perform discovery with multicast and then data transfert with unicast. I’m using Networking service but I still haven’t found a satisfying configuration. The configuration I’m using is the following: <OpenSplice> <Domain> <Name>ospl_sp_ddsi</Name> <Id>0</Id> <SingleProcess>true</SingleProcess> <Description>Multicast discovery</Description> <Service name="durability"> <Command>durability</Command> </Service> <Service name="cmsoap"> <Command>cmsoap</Command> </Service> <Service name="networking"> <Command>networking</Command> </Service> <Role>PICS</Role> </Domain> <DurabilityService name="durability"> <Network> <Alignment> <TimeAlignment>false</TimeAlignment> <RequestCombinePeriod> <Initial>2.5</Initial> <Operational>0.1</Operational> </RequestCombinePeriod> </Alignment> <WaitForAttachment maxWaitCount="100"> <ServiceName>ddsi2</ServiceName> </WaitForAttachment> </Network> <NameSpaces> <NameSpace name="defaultNamespace"> <Partition>*</Partition> </NameSpace> <Policy alignee="Initial" aligner="true" durability="Durable" nameSpace="defaultNamespace"/> </NameSpaces> </DurabilityService> <TunerService name="cmsoap"> <Server> <PortNr>Auto</PortNr> </Server> </TunerService> <NetworkService name="networking"> <Channels> <Channel enabled="true" name="Reliable" reliable="true"> <PortNr>53400</PortNr> </Channel> <Channel enabled="true" name="BestEffort" reliable="false"> <PortNr>53410</PortNr> </Channel> </Channels> <General> <NetworkInterfaceAddress>eth0</NetworkInterfaceAddress> </General> <Partitioning> <GlobalPartition Address="225.0.0.1"/> </Partitioning> <Discovery Scope="PICS" enabled="true"> <PortNr>3369</PortNr> </Discovery> </NetworkService> </OpenSplice> With this configuration, it seems that the data are sent twice, once to the multicast address (what I’d like to avoid) and once to the unicast address, which badly impacts the transfert time. Could you tell me what I’m doing wrong? Thank you very much in advance!
  2. Dear all, I´m a newbie regarding DDS so apologies if these questions are too obvious for all of you. I started using OpenSpliceDDS one week ago and I am running the examples that are provided in the zip file that is obtained from the website for Linux distributions. There are several examples to study and execute, and I am particularly interested in NetworkPartitions. While I have been able to execute it without using the instructions (compiling Chatter and MessageBoard and executing them after setting the environment variables present in release.com), I was wondering how could I create a unicast connection between the two entities that are shown in the example, which is something that I have failed to do. I have tried two solutions: 1. Exporting the network1.xml configuration file present in the example (as said in the instructions, export OSPL_URI=file://$OSPL_HOME/examples/dcps/NetworkPartitions/etc/network1.xml). It did not work. 2. Modifying the configuration file ospl.xml located in /home/[path]/HDE/x86.linux/etc/config in the general properties part (changing AllowMulticast to false, EnableMulticastLoopback to false and NetworkInterfaceAddress to my IP for local tests). It did not work either. <General> <NetworkInterfaceAddress>AUTO</NetworkInterfaceAddress> <AllowMulticast>true</AllowMulticast> <EnableMulticastLoopback>true</EnableMulticastLoopback> <CoexistWithNativeNetworking>false</CoexistWithNativeNetworking> </General> What should I do to create the unicast connection? For this example I already know the IP addreses (or address if requested locally) that will be used in the communcation. Kind regards.
  3. I'm trying to configure an unicast reliable channel between two nodes on different networks. There's no multicast between them and no broadcast. I'm using Community 5.5.1 Whilst I have managed to send packets between them, it has been impossible to "resend" packets, since when a packet is lost is resent via broadcast or multicast, which means they never reach the other node. I have tried the following configurations: 1) <GlobalPartition Address="UnicastAddress1" MulticastTimeToLive="32"/> In this case on networking.log I can see: 1385604878.204 Construction (4) Incarnated network, currently 1 incarnations active 1385604878.204 Test (4) Using broadcast address 192.168.1.255 for default partition 1385604878.207 Test (1) Creation of sending socket "Channels/Channel[@name=Reliable]" succeeded. 1385604878.208 Test (3) Adding address expression "UnicastAddress1" to partition 0 1385604878.208 Test (4) Adding host "UnicastAddress1" (UnicastAddress1) to partition 0 1385604878.209 Test (4) Using broadcast address 192.168.1.255 for default partition 1385604878.209 Test (1) Creation and binding of receiving socket "Channels/Channel[@name=Reliable]" succeeded. 1385604878.209 Test (3) Adding address expression "UnicastAddress1" to partition 0 1385604878.209 Test (4) Adding host "UnicastAddress1" (UnicastAddress1) to partition 0 A "default partition" with a broadcast address is created. This partition is used for resending packets. I really cannot understand this behavior, because if I would have wanted to use broadcast I would have put it on the configuration. If the product needs a "default partition" it should use the GlobalPartition provided. 2) <GlobalPartition Address="MulticastAddress1, UnicastAddress1" MulticastTimeToLive="32"/> In this case the networking.log is a bit different: 1385985564.119 Construction (4) Incarnated network, currently 1 incarnations active 1385985564.121 Test (3) Adding address expression "MulticastAddress1, UnicastAddress1" to partition 0 1385985564.121 Test (4) Adding host "MulticastAddress1" (MulticastAddress1) to partition 0 1385985564.122 Test (4) Adding host "UnicastAddress1" (UnicastAddress1) to partition 0 1385985564.128 Test (1) Creation of sending socket "Channels/Channel[@name=Reliable]" succeeded. 1385985564.121 Test (3) Adding address expression "MulticastAddress1, UnicastAddress1" to partition 0 1385985564.121 Test (4) Adding host "MulticastAddress1" (MulticastAddress1) to partition 0 1385985564.122 Test (4) Adding host "UnicastAddress1" (UnicastAddress1) to partition 0 No "default partition" is created. ONLY MulticastAddress1 is used for resending packets, ignoring UnicastAddress1 which is also in the partition 0 As a side note the following configuration: <GlobalPartition Address="UnicastAddress1, MulticastAddress1" MulticastTimeToLive="32"/> reverts to the first case. 3) <GlobalPartition Address="MulticastAddress1" MulticastTimeToLive="32"/> <NetworkPartitions> <NetworkPartition Address="UnicastAddress1" Compression="false" Connected="true" MulticastTimeToLive="32" Name="PART"/> </NetworkPartitions> <PartitionMappings> <PartitionMapping DCPSPartitionTopic="PART_CONTROL*.*" NetworkPartition="PART"/> <PartitionMapping DCPSPartitionTopic="PART_DATA*.*" NetworkPartition="PART"/> </PartitionMappings> The networking.log 1385642520.034 Test (2) Read networking partition (PART,UnicastAddress1,Connected) 1385642520.043 Test (1) Creation of sending socket "Channels/Channel[@name=Reliable]" succeeded. 1385642520.044 Test (3) Adding address expression "MulticastAddress1" to partition 0 1385642520.044 Test (4) Adding host "MulticastAddress1" (MulticastAddress1) to partition 0 1385642520.044 Test (3) Adding address expression "UnicastAddress1" to partition 1 1385642520.044 Test (4) Adding host "UnicastAddress1" (UnicastAddress1) to partition 1 1385642520.047 Test (1) Creation and binding of receiving socket "Channels/Channel[@name=Reliable]" succeeded. 1385642520.044 Test (3) Adding address expression "MulticastAddress1" to partition 0 1385642520.044 Test (4) Adding host "MulticastAddress1" (MulticastAddress1) to partition 0 1385642520.044 Test (3) Adding address expression "UnicastAddress1" to partition 1 1385642520.044 Test (4) Adding host "UnicastAddress1" (UnicastAddress1) to partition 1 With this configuration there is another problem: The packets and ACK are sent and received by each node networking process, but the data never reach the applications. There may be something wrong in application QoS, but with the same QoS the data reached the applications in the previous cases. MulticastAddress1 is used for resending packets. Any help would be appreciate. Rodolfo.
×