Network Stack SDK Version 2.12.1 (August 29 2025) - Release Notes#

RS9116

The Netstack software development kit (SDK) provides robust network protocol support, including TCP/IP, UDP, and DNS capabilities for embedded applications.

Click here for earlier releases.

Release Summary#

Key Features | API Changes | Bug Fixes | Chip Enablement

Key Features#

None

API Changes#

Enhanced DNS functionality with automatic DHCP configuration, improved asynchronous query support.

Bug Fixes#

  • DNS server addresses are now automatically configured when DNS mode is enabled.

  • Updated rsi_send API documentation for error handling clarity.

Chip Enablement#

None

Key Features#

None

New Features | Enhancements | Removed Features | Deprecated Features

Note: See Feature Matrix for a list of any applicable APIs, examples, software variants, modes, hardware, and host interfaces for each feature.

New Features#

None

Enhancements#

Enhanced DNS request handling by introducing the rsi_dns_req_async API for asynchronous, non-blocking DNS resolution.

Removed Features#

None

Deprecated Features#

None

API Changes#

New APIs | Modified APIs | Removed APIs | Deprecated APIs

New APIs#

None

Modified APIs#

None

Removed APIs#

None

Deprecated APIs#

None

Bug Fixes#

ID Issue Description GitHub / Salesforce Reference (if any) Affected Chip Revision, Hardware, Host Interfaces
1440307 Updated rsi_send API documentation for error handling clarity. None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
1478550 DNS server addresses are now automatically configured when DNS mode is enabled. None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI

Chip Enablement#

None

Application Example Changes#

New Examples | Modified Examples | Removed Examples | Deprecated Examples

New Examples#

None

Modified Examples#

None

Removed Examples#

None

Deprecated Examples#

None

Known Issues and Limitations#

ID Issue or Limitation Description GitHub / Salesforce Reference (if any) Workaround (if any) Affected Chip Revision, Hardware, Host Interfaces
NA Embedded MQTT does not support reassembly of fragmented MQTT packets. MQTT transactions may fail if fragmented packets are received from the broker. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA TLS handshakes may occasionally fail due to incorrect ECC curve parameter generation, resulting in a BBD2 error. The issue resolves on the next attempt. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA MQTT disconnects may occur during firmware updates if powersave is enabled. Disable powersave during the update and re-enable it after completion. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA All GCM-based cipher suites are software-implemented and may exhibit limited performance. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA The recommended MQTT publish payload is 1 kB. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA If HTTP server functionality is enabled, do not use port 80 for the MQTT client. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA Randomize the client port if using rapid connect/disconnect of the MQTT session on the same client port with powersave. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA Secure TLS renegotiation is not supported in the embedded networking stack. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA In WPA2 enterprise security mode, getting wireless statistics using rsi_wlan_get() API has restrictions. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA The wlan_throughput_bt_spp_ble_dual_role example is not supported on bare metal platforms. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA In concurrent mode, communication loss could occur on the STA application when, simultaneously, multiple clients are connected to the APUT. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA IP address conflict detection has limitations in STA + AP concurrent mode, and failures are not reported to host. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA mqtt_client and mqtt_client_v6 applications do not support the SDIO host interface. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA If a corrupted firmware image is received during OTA updates via TCP/HTTP, the module may become unresponsive on the next bootup. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA TLS connection problems may occur when attempting to revoke public and private keys using existing keys. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA Observed STA + BT (connected) test cases not getting throughput results prints in TeraTerm. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA Observed inconsistency in TCP and UDP - Rx throughputs in AP alone mode. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA Observed duplicate IPv6 address is assigned to multiple STAs in AP mode. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI
NA Ping timeouts may occur when configured with a 1-second timeout. None None
  • Hardware boards: All
  • Chip revision: All
  • Host interface: UART, SPI