Media diagnostics · Primary-source explanation; examples are illustrative. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Distinguish local categories
RFC 4193 defines unique local IPv6 addresses for communication within a site or a limited set of interconnected sites. They are not expected to be routed on the global internet, but they can be routed internally. This distinction matters when a local media server is on a different managed subnet. Calling every nonpublic IPv6 address link local can lead to an incorrect explanation of why one internal path should or should not work.
Describe the intended route
In an original conceptual example, a media server and a television sit on two authorised internal subnets with routing between them. Unique local addressing can fit that design, while the network policy still decides which traffic is permitted. Record the actual destination category and intended routed path. Do not assume that a protocol name or address prefix overrides segmentation rules, nor that a successful route establishes automatic device discovery across the same boundary.
Keep global reachability separate
A unique local address used successfully inside the site does not become a public internet destination merely because it is written in full IPv6 notation. External access would require its own documented design and permission. Preserve the address family and network context in private support records, sharing only necessary details. This article resolves a scope distinction; it is not a recommendation to expose a home media server or evidence that changing an address can alter streaming account access.