UDP Socket
The UDP Socket plugin addresses connection-oriented communication challenges by enabling applications to communicate over a network without the need to establish traditional peer-to-peer connections. Operating in true connectionless mode, it allows a single UDP socket to efficiently interact with multiple remote nodes simultaneously, making it ideal for tasks like device discovery and network-wide messaging.
Capabilities
Required
| Required for working with connectionless UDP sockets. |
Optional
| Required for establishing IPv6 connections. |
Basic Setup
- In IO Ninja, click the “New Session” dropdown and select “UDP Socket”.
- Select a remote address to connect to (IP-address or hostname) and a port.
- Click the “Open Socket” button, to the right of the “Local port” selection field.
- Analyze the log as UDP packets are received.
- Adjust settings as needed via the “Settings” button (see “Settings” section below for details).
Settings
| Setting | Description | Default |
|---|---|---|
| Remote address | Remote address to connect to (IP address or host name, optionally followed by a semicolon and a port). | |
| Remote port (default) | Remote port to connect to (if not specified in the remote address). | |
| Auto-switch remote address | Automatically switch remote address upon receiving a datagram. | False |
| Adapter | Local network adapter to bind to. Pick one from the list of installed network adapters (or bind to all installed IP4 or all IP6 adapters at once). |
All IPv4 adapters |
| Local port | Local port to bind to. Setting this to 0 auto-selects an available port. |
|
| Reuse address | Allow multiple sockets to share the same local address. Maps to the SO_REUSEADDR socket option. Please note, the support and details of implementation for this option are highly platform-specific. |
False |
| UDP broadcast | Toggle whether or not to allow broadcast packets to be transmitted. | True |
Read parallelism
(Windows-only)
|
Maximum number of read requests to issue in parallel. Having more than one pending read at a time helps with increasing read throughput when incoming data arrives in rapid streams (after filling one user buffer, the kernel can immediately switch to the next one without any waiting). Increasing this number beyond 4 usually won’t yield any extra performance gains. | 4 |
| Read block size (B) | The size of each individual read block submitted to the underlying transport. | 4KB |
| RX buffer size (B) | The full size of the incoming data (RX) buffer. Affects read throughput. | 16KB |
| TX buffer size (B) | The full size of the outbound data (TX) buffer. Affects write throughput. | 16KB |
| RX buffer full notifications | Toggle warnings in log about the incoming data (RX) buffer getting full. | False |
Note
An example of an adapter dropdown on a typical Windows laptop is shown below:
