Media diagnostics · Primary-source explanation; examples are illustrative. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Answer which interface would be used
When a Linux computer has several network interfaces, a connected cable is not by itself proof that a media request will use that path. The iproute2 manual distinguishes listing the route table from using ip route get for a particular destination. The latter resolves the route as the kernel sees it and can expose the selected interface and source context. This is a more precise initial question than randomly disabling adapters until something changes.
Keep lookup and reachability separate
The documented get operation does not send packets to the destination. Therefore its successful output cannot establish that a remote service is reachable or that an HTTPS request succeeds. An illustrative report can say that a lookup selected the wired interface while a later permitted connection attempt failed. Those observations do not conflict: the first concerns local routing selection, and the second concerns an actual attempted communication along a path.
Preserve context before changing routes
Record the destination address, the relevant output and whether the application has special network binding or policy context. Avoid publishing private source addresses unnecessarily. Do not copy add, delete or flush commands from a manual as a generic viewing fix; those perform different actions from inspection. A route lookup can narrow an investigation of unexpected interface use, but it is not a universal test of bandwidth, DNS correctness, server status or subscription validity.