Home
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running QNX Neutrino 7.1.
OS Components & Operations
Core Networking Stack User's Guide
This guide introduces you to the QNX Neutrino Core Networking stack and its manager, io-pkt.
Transparent Distributed Processing
Using TDP over IP
TDP supports two modes of communications: one directly over Ethernet, and one over IP.

QNX Momentics IDE User's Guide
This User's Guide describes version 7.1 of the Integrated Development Environment (IDE) that's part of the QNX Momentics tool suite.
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running QNX Neutrino 7.1.
- Quickstart Guide
- OS Components & Operations
  - Adaptive Partitioning User's Guide
  - Boot Optimization Guide
    The Boot Optimization Guide describes techniques you can use to reduce the time from your board's initial power on until you have a fully functional QNX system running on the board.
  - Building Embedded Systems
    The Building Embedded Systems guide is intended for developers who are developing or building BSPs for QNX Neutrino RTOS embedded systems.
  - Core Networking Stack User's Guide
    This guide introduces you to the QNX Neutrino Core Networking stack and its manager, io-pkt.
    - Overview
    - Packet Filtering
    - IP Security and Hardware Encryption
      The io-pkt-v4-hc and io-pkt-v6-hc stack variants include full, built-in support for IPsec.
    - Wi-Fi Configuration
    - Transparent Distributed Processing
      - Using TDP over IP
        TDP supports two modes of communications: one directly over Ethernet, and one over IP.
    - Network Drivers
    - Utilities, Managers, and Configuration Files
      The utilities, drivers, configuration files, and so on listed below are associated with io-pkt.
    - Writing Network Drivers for io-pkt
      This appendix is intended to help you understand and write network drivers for io-pkt.
    - A Hardware-Independent Sample Driver: sam.c
    - Additional information
    - Glossary
  - Customizing a BSP
    While QNX provides Board Support Packages (BSPs) for many common platforms and their individual variants, in some cases, you need a BSP for a board that QNX does not provide. If this is the case, you can modify a QNX BSP or develop your own.
  - Device Publishers Developer's Guide
  - High Availability Framework Developer's Guide
  - High-Performance Networking Stack (io-sock) User's Guide
    This guide contains instructions for implementing and using the QNX Neutrino High-Performance Networking Stack and its manager, io-sock.
  - Instant Device Activation
  - Migrating to QNX SDP 7.1
  - PCI Server User's Guide
  - Persistent Publish/Subscribe Developer's Guide
  - Platform-independent Publish/Subscribe Developer's Guide
    This guide is intended for application developers who want to use the Platform-independent Publish Subscribe (PiPS) framework to exchange information with other applications. First, the overall PiPS design and data-exchange model are explained. Then, tutorials on using PiPS are given. These tutorials cover key tasks such as selecting a publish-subscribe provider to use and writing plugins that read and write custom data types.
  - QDB Developer's Guide
  - QNX Helpers Developer's Guide
    These libraries provide QNX helpers, including helpers that assist with logging, string conversion, and number and type sizes.
  - SMMUMAN User's Guide
  - System Analysis Toolkit (SAT) User's Guide
  - System Architecture
    The System Architecture guide accompanies the QNX Neutrino RTOS and is intended for both application developers and end-users.
  - Technotes
  - User's Guide
    The QNX Neutrino User's Guide is intended for all users of a QNX Neutrino RTOS system, from system administrators to end users.
- Audio & Graphics API
- Multimedia
- Networking Middleware
- Programming
- Sensor Framework
- System Security Guide
  The QNX System Security Guide is intended for both system integrators who are responsible for the security of a QNX Neutrino RTOS system and developers who want to create a QNX Neutrino resource manager free from vulnerabilities.
- Utilities & Libraries
QNX Hypervisor
The QNX Hypervisor allows you to run multiple OSs on a target system so you can separate critical and non-critical functions, support a wide variety of applications, and reduce hardware costs.
QNX Software in the Cloud
QNX Software in the Cloud enables developers to use the QNX software in Amazon Web Services (AWS) and Microsoft Azure (Azure).
QNX Advanced Virtualization Frameworks User's Guide
This User's Guide is aimed at all systems integrators and developers who want to design and build embedded systems using the QNX Advanced Virtualization Frameworks.
Typographical Conventions, Support, and Licensing
This section describes the typographical conventions used throughout the documentation and explains how to obtain technical support.

Using TDP over IP

TDP supports two modes of communications: one directly over Ethernet, and one over IP.

The straight to Ethernet L4 layer is faster and more dynamic than the IP layer, but it isn't possible to route TDP packets out of a single layer-2 domain. By using TDP over IP, you can connect to any remote machine over the Internet as follows:

TDP must use the DNS resolver to get an IP address from a hostname (i.e., use the resolve=dns option). Configure the local host name and domain, and then make sure that gethostbyname() can resolve all the host names that you want to talk to (including the local machine):
- Use hostname to set the host name.
- Use setconf to set the _CS_DOMAIN configuration string to indicate your domain.
- If the hosts aren't in a DNS database, create an appropriate name to host resolution file in /etc/hosts which includes the fully qualified node name (including domain) and change the resolver to use the host file instead of using the DNS server (e.g., setconf _CS_RESOLVE lookup_file_bind).
  For more information on name resolution, see the description of Name servers in the TCP/IP Networking chapter of the QNX Neutrino User's Guide.

Start (or mount) Qnet with the bind=ip,resolve=dns options. For example:

io-pkt-v4-hc -de1000 -pqnet bind=ip,resolve=dns

or:

mount -Tio-pkt -o bind-ip,resolve=dns full_path_to_dll/lsm-qnet.so

With raw Ethernet transport, names automatically appear in the /net directory. This doesn't happen with TDP over IP; as you perform TDP operations (e.g. ls /net/host1), the entries are created as required.

Page updated: March 12, 2026