Why do network devices become unreachable after enabling the Synthetic (Browser) module on an On-Premise Poller?

Why do network devices become unreachable after enabling the Synthetic (Browser) module on an On-Premise Poller?

Problem statement and scenario

Network devices may become unreachable from a Linux On-Premise Poller after enabling the Synthetic (Browser) module.
This issue can occur when you use the same On-Premise Poller for both synthetic monitoring and network device monitoring, and the network devices use IP addresses within Docker’s default network range.
For example, a network device with the IP address 172.17.0.0/16 may become unreachable after the Synthetic (Browser) module is enabled on the same Linux On-Premise Poller used to monitor that device.

Why does this happen?

Setting up the Synthetic (Browser) module on a Linux On-Premise Poller automatically downloads and install Docker.
Docker uses the default bridge network subnet 172.17.0.0/16, with the gateway 172.17.0.1. If your network devices have IP addresses within this range, Docker’s network overlaps with your organization’s network.
Because Docker’s bridge network and your organization’s network use overlapping IP address ranges, the On-Premise Poller sends monitoring requests for the affected devices to Docker instead of the devices. As a result, the devices become unreachable from the poller.

Solution

Configure Docker to use a different IP address range that does not conflict with any existing network in your environment, including VPNs and cloud networks.
1. Edit the Docker configuration file
/etc/docker/daemon.json
2. Update the configuration with a non-conflicting IP range.
For example:


{

  "bip": "172.30.0.1/24",

  "default-address-pools": [

    {

      "base": "172.30.0.0/16",

      "size": 24

    }

  ]

}

3. Restart Docker for the changes to take effect:

sudo systemctl restart docker
4. Verify the Docker network configuration and confirm that the new IP address range is being used.
Once the configuration is updated, check whether the affected network devices are reachable.
Always ensure that the selected IP address range does not overlap with any existing network in your environment.

Verify the changes

After updating the Docker configuration and restarting the Docker service, run the following commands to verify the changes:
1. Verify the Docker bridge IP address:

ip addr show docker0
Confirm that the Docker bridge interface displays 172.30.0.1/24, or the IP address range that you have selected.
2. Verify the Docker bridge subnet and gateway:

docker network inspect bridge | grep -E "Subnet|Gateway"

Confirm that the bridge network is using the newly configured IP address range.
3. Check the existing Docker networks:

docker network ls

Review the listed networks to identify any existing Docker networks that may still use the conflicting IP range.
4. Verify the route to the affected network device:

ip route get 172.17.100.241

Replace 172.17.100.241 with the actual IP address of the affected network device.
This is the most important verification step. Confirm that traffic to the affected device is routed through the appropriate network interface and not through Docker’s docker0 bridge.
Once these checks are complete, confirm whether the affected network devices are reachable.

Conclusion

Configuring Docker to use a non-conflicting IP address range allows the On-Premise Poller to reach your network devices while continuing synthetic monitoring.
  1. Synthetic (Browser) module prerequisites and troubleshooting guide for On-Premise Pollers
  2. Configure the On-Premise Poller as a monitoring location for synthetic (browser) monitors