Details
In a recent use case the DHCP server on the network was configured in the IP range 169.254.X.Y and the 24.X.Y and 25.X.Y releases of DataMan Setup Tool did not auto-detect the reader on the Home Tab anymore.
Background:
The 169.254.0.0/16 IP range is reserved by RFC 3927 for Link-Local addressing. Devices use this range automatically when no DHCP server is available. This mechanism is commonly known as APIPA (Automatic Private IP Addressing) in Windows, or more generally "Link-Local Addressing."
Issues when using this range via a DHCP server:
- Misuse of a reserved range:
If a router or DHCP server actively assigns IPs from this range, it violates the RFC standard and contradicts the expectations of many devices and networking protocols. Problems with UDP-based discovery protocols:
Many devices (e.g., printers, cameras, IoT devices) ignore or mishandle the 169.254.x.y range for regular communication, as it is typically treated as a fallback only. As a result, UDP broadcasts (e.g., SSDP, mDNS, Bonjour, Profinet, etc.) often don’t work reliably in this IP range.
- Routing and gateway issues:
The Link-Local range is non-routable by design. If you use it in your network, communication across subnets or via gateways will not work, as routers do not forward Link-Local traffic. - Troubleshooting becomes confusing:
If 169.254.x.y addresses are assigned intentionally, it’s no longer clear whether a device is using this address due to a network failure (e.g., no DHCP) or because it was explicitly configured to do so. This makes diagnostics more difficult.
Conclusion:
Yes, using the 169.254.0.0/16 range via DHCP is problematic. It can cause serious issues with UDP discovery protocols, routing, device communication, and troubleshooting.
Recommendation:
Use one of the RFC 1918 private IP address ranges instead:
- 192.168.0.0/16
- 10.0.0.0/8
- 172.16.0.0 – 172.31.255.255
These ranges are specifically designed for private networks and are widely supported and expected by networking equipment.