QNX offers a comprehensive suite of technologies. Based on standard implementation including BSD and KAME, QNX networking technologies have been pre-integrated and fully tested to de-risk development programs and accelerate time to market. QNX networking technologies have been deployed throughout the network from optical repeaters to the world’s highest capacity routing platform.

QNX protocol support includes:

• IPv4/IPv6 (based on NetBSD 4.0)
  
• Security protocol suite
  
  • IPSec, IKE, SSL, SSH, NAT, IP Filtering
    
  • Open cryptography API
    
  • Hardware accleration support
    
• SNMP v1/v2/v3
  
• L2 VLAN, QoS, STP
  
• 802.11a/b/g, WPA, WPA2, WEP
  

For a complete list of protocols and RFCs, click here. Note that QNX is continuously expanding its networking support. Additionally, QNX products are complemented by a broad ecosystem of networking technology partners. If you cannot find the protocols you require, please contact QNX for up to date information.

Transparent Distributed Processing

Extending QNX message passing architecture across virtually any network interconnect technology, QNX Transparent Distributed Processing (TDP) replaces heavier weight messaging infrastructure. QNX TDP provides the ability to seamlessly share resources on a network in a peer-to-peer fashion. The TDP approach provides true location independence of resources, so all software on any node in the network can access any published resource.

Transparent distributed processing provides a framework for the dynamic interconnection of hardware and software resources (message queues, file systems, services, databases) located on remote nodes, using standard messages. Processes running on a single CPU will continue to communicate with each other even if they are subsequently distributed among multiple CPUs, allowing developers to extend resources to networked nodes and simplify the development of multi-node systems.

With this unique capability, developers can create highly robust and fault-tolerant systems that can offer on-demand access to resources on multiple CPUs. If a CPU is not available, a similar resource can be transparently accessed on another CPU — delivering built-in redundancy and load balancing.

Transparent distributed processing replaces the traditional custom messaging infrastructure required to enable inter-process communications — saving time and costs associated with custom development and incremental hardware.

Transparent distributed processing replaces traditional messaging infrastructures, allowing an application to access resources on any other node in the network. Applications and servers can become instantly network distributed without special coding.

Highlights

• Deploy solution in multiple environments
  
  • Ideal for "in the box" networking equipment, where it can be used over backplanes and interconnect technologies
    
  • Useful in industrial control systems applications such as distributed monitoring, management and control
    
• Optimize use of shared resources
  
  • An application running on one node can transparently access any other node's resources - including file systems, message queues, disks, modems, Internet connections, and databases - as if those resources were running on the local CPU
    
  • Enables low packet loss, improves performance for large payloads, and minimizes turnaround time for common small packets
    
  • No additional network code is required
    
• Gain location independence
  
  • Global name service provides central directory of global naming services and location services
    
  • Multiple cards can register for the same service
    
  • Supports location independence by allowing for flexible deployment and partitioning of the application at runtime
    
  • Requires minimal system knowledge to implement because applications or services do not need to be tied to a specific card, which translates to less coding and reduced development time
    
  • Provides automatic supervision and notification of available resources
    
• Deliver built-in redundancy and load balancing
  
  • QNX distributed messaging inherently supports multiple links between CPUs. If one link fails, data will automatically be re-routed over the remaining links, without loss of service
    
  • Network traffic can be load-balanced over all available links, resulting in significantly higher throughput
    
  • Applications can specify a preferred node for data, but if a failure occurs on that node, the data will be transparently load balanced over the remaining functioning nodes
    
• Implement centralized debugging
  
  • Allows developers to query and collect remote data via a single connection to multiple cards, ensuring that data can be accessed even in the event of a broken connection
    
• Support various transports
  

Since QNX distributed messaging operates above the transport layer, it works equally well across LANs, backplanes, proprietary switch fabrics, vehicle buses CAN and MOST, and even the Internet.