Distinguish provider and household translation
Your home router may translate local traffic before the provider applies another translation layer. The router's WAN address can therefore differ from the address reported by an external lookup. The shared-address range 100.64.0.0/10 is reserved for this kind of provider use, although a single displayed address is not a complete topology audit.
Do not publish addresses unnecessarily or assume that another customer sharing an outward address has access to your account. Account credentials, session controls and provider network separation are different mechanisms.
Identify the actual requirement
An application that initiates normal outbound media requests does not automatically need a dedicated public IPv4 address. A remote-access or hosting feature that needs unsolicited inbound traffic may have different requirements. Obtain those requirements from its official documentation.
If playback fails, keep the observed message and stage. A provider-shared address is context, not proof of a block or rate limit. Only the relevant operator can confirm whether an address-based rule affected the request.
Ask a precise provider question
If inbound reachability is genuinely required, ask the internet provider what addressing and supported alternatives are available. Do not promise a free public address, a static address or a particular fee. Those are current plan-specific facts.
For an illustrative support record, “router WAN address differs from external lookup; ordinary browsing works; programme request returns 403” keeps three observations distinct. “CGNAT makes IPTV impossible” is an unsupported generalization and obscures the actual permission response.
Interpret shared-address symptoms conservatively
A rate-limit or security decision can sometimes involve an outward address, but the relevant operator must confirm its actual rule. Do not assume that all customers sharing an address are blocked whenever one request fails. Preserve the response code, time and account stage so the operator can examine its own logs.
If the internet provider changes the outward address during reconnects, a later successful request may be correlated with that change without proving causation. The upstream service may also have recovered, a token may have refreshed or the requested resource may differ. Keep those possibilities visible in the incident record.
A public-address option, if offered, also has commercial and security implications. Ask the provider for current availability, cost and conditions before ordering it. A viewer should not incur that expense based only on a generic claim that every streaming application requires inbound connectivity.
Related questions
Will port forwarding on my router bypass carrier-grade NAT?
Not generally. A home-router rule cannot by itself control an upstream provider's translation or create a public inbound route.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- RFC 6598 — Relevant protocol definition only; household workflows and numerical examples are editorial.
