LAN communication is no longer possible. This affects:

• Local communication between devices that are connected to the SecureEdge Pro's LAN.
• Remote communication over VPN to any device connected to the SecureEdge Pro's LAN.

The SecureEdge Pro runs Docker, which uses virtual network interfaces with their own IP range. This is active even when there are no Docker containers.

Something is conflicting with this Docker IP range, resulting in communication over LAN breaking. This can have the following causes:

• The SecureEdge Pro's own LAN IP range conflicts with the Docker IP range.
• A device connected to the SecureEdge Pro's LAN is running Docker and that is using the same IP range as the SecureEdge Pro's Docker IP range.

The Docker IP ranges used by the SecureEdge Pro are 172.17.x.y and 10.188.x.y. Below is a more technical in-depth explanation about the in-use Docker IP range(s).

To resolve this issue:

• Make sure that the SecureEdge Pro's LAN IP address is not in the same IP range that Docker uses (172.17.x.y and 10.188.x.y).
  • If it does conflict, first change the IP settings of your LAN connected devices to a new IP range and lastly change the SecureEdge Pro's LAN IP address. This way you ensure that you can still remotely access your devices after this change.
  • If the SecureEdge Pro's LAN IP address is in the IP range 172.17.x.y, you can alternatively upgrade the firmware to 2026.02 or higher and then remove and recreate all Docker containers or upgrade and then factory reset the SecureEdge Pro. This way you can keep your LAN IP range.
• Make sure that there are no devices (computers) connected to the SecureEdge Pro's LAN that are running Docker on the same IP range that the SecureEdge Pro's Docker uses (172.17.x.y and 10.188.x.y).