RTI Secure WAN Transport - Community RTI Connext Users
Contents
1. are permitted provided that the following conditions are met 1 Redistributions of source code must retain the above copyright notice this list of conditions and the fol lowing disclaimer 2 Redistributions in binary form must reproduce the above copyright notice this list of conditions and the following disclaimer in the documentation and or other materials provided with the distribution 3 All advertising materials mentioning features or use of this software must display the following acknowledgment This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit http www openssl org 4 The names OpenSSL Toolkit and OpenSSL Project must not be used to endorse or promote products derived from this software without prior written permission For written permission please contact openssl core opensslLorg 5 Products derived from this software may not be called OpenSSL nor may OpenSSL appear in their names without prior written permission of the OpenSSL Project 6 Redistributions of any form whatsoever must retain the following acknowledgment This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit http www openssl org THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABIL ITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED I2. time by using a participant ID limit of zero when configur ing the initial peer descriptors Third Party Licenses For example when the peer descriptor wan 1 10 10 1 150 is specified DDS will try to contact five participants with the same WAN ID in different ports Usually there is only one participant using the same WAN ID Although the other four par ticipants will never be reachable the application still tries to establish communica tion with them by contacting the STUN server You can reduce the number of participants to which the application will try to con tact to one by using a participant ID limit of zero in the peer descriptor For exam ple O wan 1 10 10 1 150 For additional information on peer descriptors see the Discovery chapter in the RTI Core Libraries and Utilities User s Manual Third Party Licenses This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit http www openssLorg Copyright c 1998 2011 The OpenSSL Project All rights reserved The OpenSSL toolkit stays under a dual license i e both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit See below for the actual license texts Actually both licenses are BSD style Open Source licenses In case of any license issues related to OpenSSL please contact openssl core opensslL org Redistribution and use in source and binary forms with or without modification
3. DK 1 7 i86Linux2 6gcc4 1 1jdk Linux 5 0 2 6 kernel a gcc 4 1 1 x64Linux2 6gcc4 1 1 x Java Platform Standard Edition JDK 1 7 x64Linux2 6gcc4 1 1jdk 4 a gcc 4 6 3 i86Linux3 xgcc4 6 3 5 Ubuntu Server 12 04 E Java Platform Standard Edition JDK 1 7 i86Linux3 xgcc4 6 3jdk LTS a gcc 4 6 3 x64Linux3 xgcc4 6 3 E Java Platform Standard Edition JDK 1 7 x64Linux3 xgcc4 6 3jdk Wind River Linux 4 2 6 kernel x64 gce 4 4 1 x64WRLinux2 6gcc4 4 1 xs amp QNX Neutrino 6 5 x86 qcc 4 4 2 with GNU C libraries i86QNX6 5qcc_gpp4 4 2 2 Ultra gcc3 4 2 sparcSol2 10gcc3 4 2 Solaris 2 10 F 3 SPARC Java Platform Standard Edition JDK 1 7 sparcSol2 10jdk Windows 2003 Visual Studio 2005 SP 1 i86Win32VS2005 n z Windows Vista 32 bit Visual Studio 2005 SP 1 C CLI C i86Win32dotnet2 0 z Edition x86 8 0 or 9 0 Windows XT Java Platform Standard Edition JDK 1 7 i86Win32jdk Professional Table 1 2 lists an additional target library for which RTI offers custom support If you are inter ested in using this platform please contact your local RTI representative or email sales rti com Custom Supported Platforms Operating System CPU Compiler RTI Architecture Abbreviation NI Linux Real Time 3 2 ARM Cortex A9 gcc 4 4 1 armv7AngstromLinux3 2gcc4 4 1 cortex a9 Compatibility 3 2 Table 3 1 Compatibility RTI Secure WAN Transport is an optional prod
4. N NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT INDIRECT INCIDENTAL SPE CIAL EXEMPLARY OR CONSEQUENTIAL DAMAGES INCLUDING BUT NOT LIMITED TO PROCURE MENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY WHETHER IN CONTRACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE This product includes cryptographic software written by Eric Young eay cryptsoft com This product includes software written by Tim Hudson tjh cryptsoft com
5. RTI Secure WAN Transport Core Libraries and Utilities Release Notes Version 5 1 0 t l Your systems Working as one 2013 Real Time Innovations Inc All rights reserved Printed in U S A First printing December 2013 Trademarks Real Time Innovations RTI and Connext are trademarks or registered trademarks of Real Time Innovations Inc All other trademarks used in this document are the property of their respective owners Copy and Use Restrictions No part of this publication may be reproduced stored in a retrieval system or transmitted in any form including electronic mechanical photocopy and facsimile without the prior written permission of Real Time Innovations Inc The software described in this document is furnished under and subject to the RTI software license agreement The software may be used or copied only under the terms of the license agreement Technical Support Real Time Innovations Inc 232 E Java Drive Sunnyvale CA 94089 Phone 408 990 7444 Email support rti com Website https support rti com Release Notes Table 1 1 Table 1 2 Supported Platforms This release of RTI Secure WAN Transport is supported on the architectures listed in Table 1 1 Supported Platforms RTI Architecture Operating System CPU Compiler Abbreviation 86 gcc 4 1 1 i86Linux2 6gcc4 1 1 x Red Hat Enterprise Java Platform Standard Edition J
6. metric TCP server some connections were closed and never reopened preventing the discovery of DDS entities and or the delivery of user data This problem has been resolved RTI Issue ID COREPLG 178 Available Documentation 6 7 Available Documentation The following documentation is provided with the Connext distribution The paths show where the files are located after Connext has been installed in lt NDDSHOME gt LI RTI Secure WAN Transport Installation Guide lt NDDSHOME gt doc pdf RTI_Secure_WAN_InstallationGuide pdf also available for download from RTI s Customer Portal LI RTI Core Libraries and Utilities User s Manual lt NDDSHOME gt doc pdf RTI_CoreLibrariesAndUtilities_UsersManual pdf LI RTI Secure WAN Transport API Reference HTML documentation Open lt NDDSHOME gt ReadMe html then select Secure WAN Transport L Example code lt NDDSHOME gt example lt language gt helloWorldWAN Known Issues J When communicating over some networks the WAN and Secure Transport plug ins may fail to send data larger than the MTU maximum transmission unit size available for the network This is especially likely over wide area networks This scenario is also a suggested configuration of the DTLS protocol according to the DTLS specification which is IETF RFC 4347 If problems occur while sending large packets set the maximum_message_size transport property to the MTU of your network minus 28 by
7. re updating the transport property message_size_max so that it is consistent across all platforms 2 The value 65507 represents the maximum user payload size that can be sent as part of a UDP packet Compatibility In Connext 5 1 0 the default value for message_size_max for this transport has changed Secure WAN Transport also uses this value Consequently Secure WAN Transport 5 1 0 is not off the shelf compatible with applications running older versions of this transport See the Core Libraries and Utilities Release Notes for instructions on how to resolve the compatibility issue with older Con next and RTI Data Distribution Service applications What s Fixed in 5 1 0 5 2 5 3 5 4 What s Fixed in 5 1 0 Error dtls message too big when Sending Data over DTLS When sending data over the DTLS transport you may have seen the following error message NDDS_Transport_DTLS Connection_send OpenSSL error 1410c13e DTLS1 WRITE APP DATA BYTES dtls message too big This message happens because the OpenSSL DTLS maximum message size is 16384 bytes This issue has been resolved by enforcing that the DTLS transport property parent message_size_max must be no more than 16384 bytes therefore preventing the error from ever happening RTI Issue ID COREPLG 39 Unable to Set DTLS send_socket_buffer_size to Less than Default When using the DTLS transport setting the DTLS send_socket_buffer_size to a value less than
8. tes for the DTLS header and set up your application according to the Large Data Use Cases How To provided in the online HTML documentation For example for an MTU size of 1500 bytes for standard Ether net set maximum_message_size to 1500 28 1472 One instance of this problem for which there is no workaround is the case where the dis covery packets are larger than your network s MTU This could occur if user data propa gated properties or type codes are configured L An application using the WAN transport may appear to hang for several minutes if the WAN server is shut down and not restarted before the application tries to contact it or if the application is unable to communicate with the WAN server Two scenarios under which the application tries to contact the STUN server are during shut down and while establishing a connection with the initial peers This issue is due to a sequence of synchronous STUN transactions with the STUN server If you need to run WAN transport without a STUN server here are some recommenda tions e Decrease the blocking time by decreasing the number of STUN retransmissions To do so change the property stun_number_of_retransmissions For example a change from the default of 7 retries to 5 retries will result in a total period of 3 1 seconds per synchronous operation Note however that this may impact the ability to reliably set up connections to peers over a WAN e Decrease the blocking
9. the default of 9216 would result in the following errors and create_participant would fail D0000 ENABLE NDDS Transport _UDPv4_ Property verify send_socket_buffer_ size lt message size max D0000 ENABLE NDDS Transport_UDPv4_newI Invalid transport properties D0000 ENABLE NDDS Transport _DTLS newI Failed to allocate base UDPv4 transport D0000 ENABLE DDS DomainParticipantConfigurator_ setup _custom_transports cr eate custom transport plugin D0000 ENABLE DDS_DomainParticipantConfigurator_enable install transport plugin aliases custom transports D0000 ENABLE DDS DomainParticipant_enableI enable transport configurator DDSDomainParticipant _impl createI ERROR Failed to auto enable entity DomainParticipantFactory_impl create participant create failure creat ing participant These errors would occur even if you set the DTLS message_size_max to be less than or equal to the value of the DTLS send_socket_buffer_size This issue has been resolved RTI Issue ID COREPLG 171 Memory Leak in DTLS Transport A graceful shutdown of a DomainParticipant that was using the DTLS transport and had commu nicated with other DomainParticipants over DTLS may not have properly freed all DTLS trans port resources resulting in a memory leak This issue has been resolved RTI Issue ID COREPLG 172 Failed to Reopen Closed Connections in Asymmetric TCP When a large number of clients connected to an asym
10. uct for use with RTI Connext formerly RTI Data Distribution Service with the same version number What s New in 5 1 0 New Platforms This release adds support for the following platforms L QNX Neutrino 6 5 0 SP1 L Ubuntu Server 12 04 LTS LJ Wind River Linux 4 2 6 kernel New Default Transport Settings Some of the default settings for a number of the provided transport plugins have changed to provide better out of the box performance By increasing the out of the box performance in most cases you will not have to modify these settings or keep them in sync across all Connext applications and services within your system The default values for message_size_max send_socket_buffer_size and recv_socket_buffer_size have changed Table 3 1 shows the old and new default values WAN Transport Changes New Default bytes Old Default bytes Non INTEGRITY INTEGRITY Platforms Platforms message_size_max 9216 655072 9216 send_socket_buffer_size 9216 131072 131072 recv_socket_buffer_size 9216 131072 131072 1 Due to limits imposed by the INTEGRITY platform the new default settings for all INTEGRITY platforms are treated differently than other platforms Please see the RTI Core Libraries and Utilities Platform Notes for more infor mation on the issues with increasing the message_size_max default values on INTEGRITY platforms Notice that interoperation with INTEGRITY platforms will requi
Download Pdf Manuals
Related Search