The software would need to be on the router itself so that it can intercept all traffic that is originating from the LAN (Local Area Network) and is directed at the WAN (Wide Area Network, the Internet), some higher end (home) routers have this feature, or you could see if your router supports a third-party firmware and flash that, which most likely supports it.
The other (more complex) way is to put a device in between your router’s LAN port (usually called the Default Gateway in software terms) and the rest of your devices on the network so that it intercepts all the traffic and then forwards it to the router. This is a technique known as “Man in the Middle”.
If you want to simply know if devices are “phoning home”, and potentially blocking those requests, you can use a service like NextDNS or PiHole (on a Raspberry Pi, or in Docker) to block the attempt. This happens because the device doesn’t know where to send the info.
The software would need to be on the router itself so that it can intercept all traffic that is originating from the LAN (Local Area Network) and is directed at the WAN (Wide Area Network, the Internet), some higher end (home) routers have this feature, or you could see if your router supports a third-party firmware and flash that, which most likely supports it.
The other (more complex) way is to put a device in between your router’s LAN port (usually called the Default Gateway in software terms) and the rest of your devices on the network so that it intercepts all the traffic and then forwards it to the router. This is a technique known as “Man in the Middle”.
If you want to simply know if devices are “phoning home”, and potentially blocking those requests, you can use a service like NextDNS or PiHole (on a Raspberry Pi, or in Docker) to block the attempt. This happens because the device doesn’t know where to send the info.