Skip to content

Host Network Setup

The host and AUTD3 communicate over UDP on IPv6 link-local addresses. The UDP port on the device side is 44336.

No IP address needs to be configured on the host NIC, and no root / administrator privileges are required. The following settings are needed, however.

IPv6 must be enabled on the NIC the AUTD3 is attached to. A NIC with IPv6 disabled gets no link-local address and cannot communicate.

  • Windows: make sure “Internet Protocol Version 6 (TCP/IPv6)” is checked in the adapter properties
  • Linux: make sure ip -6 addr show dev <if> shows an address starting with fe80::

The replies of the devices come from a different address than the (multicast) destination the host sent to. Depending on the firewall settings, the replies may be dropped. Therefore, allow inbound traffic from UDP source port 44336 on the NIC the AUTD3 is attached to.

With ufw, allow it as follows.

sudo ufw allow in on <if> proto udp from fe80::/10 port 44336

Replace <if> with the name of the NIC the AUTD3 is attached to (e.g. enp3s0).

Add an inbound rule in Windows Defender Firewall.

  1. Choose Inbound Rules → New Rule → Custom
  2. Choose UDP as the protocol type and set Remote port to 44336
  3. Choose Allow the connection and apply it to the network profile of the NIC the AUTD3 is attached to

From PowerShell (as administrator) it can be added as follows.

New-NetFirewallRule -DisplayName "AUTD3" -Direction Inbound -Protocol UDP -RemotePort 44336 -Action Allow

If the application firewall is enabled, allow inbound connections for the application that uses AUTD3 (when using it from Python or dotnet, for those executables).

Interrupt moderation (interrupt coalescing) on the NIC increases and spreads the receive latency. It can delay a reply by hundreds of µs or more and cause frames to be sent again, so disabling it is recommended.

  • Linux: sudo ethtool -C <if> rx-usecs 0
  • Windows: open the adapter properties in Device Manager and set “Interrupt Moderation” under Advanced to “Disabled”