- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
04-08-2026 10:55 AM
04-09-2026 02:27 AM
This behavior is usually related to DHCP issues or endpoint network probing. Traffic to/from APIPA (169.254.0.0/16) should not normally reach the internet zone.
Explanation
If endpoints fail to obtain an IP address from DHCP, they may fall back to APIPA and attempt DHCP discovery or local communication. Due to the default route, this traffic can be forwarded toward the internet (untrust) zone and appear in the firewall logs.
In other cases, if the traffic is not DHCP-related, it may be generated by operating system probing or background network processes.
Recommendation
• Verify DHCP functionality and ensure endpoints can reach the DHCP server
• Investigate affected endpoints for misconfiguration
• Block APIPA traffic toward/from the internet zone as it is non-routable
Summary
APIPA traffic seen toward the internet zone is typically caused by DHCP failure or OS probing behavior. It is recommended to troubleshoot DHCP and block APIPA traffic at the firewall.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

