Does Paramount+ require IPv6 ?

mutluit · Fri Dec 09, 2022 9:47 pm

Hi all,
recently I subscribed to the streaming provider Paramount+ [........],
and I was able to watch some films inside the WebBrowser. But today it no longer starts any of the films.
It gives "error code 3304". I asked their support, but they have, as usual with such streaming providers, no clue and just say to reboot the router (LOL!

.
My further analysis shows that it cannot connect to this mysterious address of them:

[09/Dec/2022:20:11:52 +0100] "CONNECT 8cb691e535702e64106a3948d54b901798889ee3.ipv6.cws.conviva.com:443 HTTP/1.1" 503 7322

I added this address to my firewall but it still does not function: pinging that address brings error:

$ ping 8cb691e535702e64106a3948d54b901798889ee3.ipv6.cws.conviva.com
connect: Network is unreachable

It looks like it's an IPv6 address.
Unfortunately in my LAN IPv6 is disabled. So I would need to enable it, but it's much work I'm afraid.

But the question is, is IPv6 suddenly really required with this streaming provider? Or is it rather maybe a bug of them?
B/c I wonder why it did work yesterday w/o this problem.

Has anybody else encountered this problem and can give tips to solve it?

My environment:
MikroTik small router hAP ac^2 with RouterOS 6.47.10.
Linux PCs with FireFox and Google Chrome WebBrowsers

Sob · Fri Dec 09, 2022 11:22 pm

It doesn't seem likely that something would require IPv6 and wouldn't be able to work without it. Such service would be inaccesible to 2/3 users (global average).

mutluit · Fri Dec 09, 2022 11:25 pm

It doesn't seem likely that something would require IPv6 and wouldn't be able to work without it. Such service would be inaccesible to 2/3 users (global average).

Yes, I agree.
But then how to explain this bug? Yesterday it worked, today it no longer works, inbetween nothing here has changed.

The only difference I can find in the log file is this:
Yesterday it gave for the said address this HTTP status code:
404 Not Found
"The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible."

Today it gives:
503 Service Unavailable
"The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.[28]"

S.a. https://en.wikipedia.org/wiki/List_of_HTTP_status_codes

But this status code change can be the result of me adding the address to the firewall.

MikroUser · Sat Dec 10, 2022 12:41 am

nslookup 8cb691e535702e64106a3948d54b901798889ee3.ipv6.cws.conviva.com

Name:    8cb691e535702e64106a3948d54b901798889ee3.ipv6.cws.conviva.com
Addresses:  2620:10b:7001:10::106
          2620:10b:7002:14::108
          2620:10b:7001:10::109
          2620:10b:7002:14::107

domain 8cb691e535702e64106a3948d54b901798889ee3.ipv6.cws.conviva.com
have only aaaa records *(ipv6)
and dont have A records (ipv4)

So this domain works only with ipv6 networks.

MikroUser · Sat Dec 10, 2022 12:44 am

You can ask your provider for enabling ipv6, or try use ipv4-to-ipv6 tunnel, its free here https://tunnelbroker.net

mutluit · Sat Dec 10, 2022 2:56 am

Code: Select all
nslookup 8cb691e535702e64106a3948d54b901798889ee3.ipv6.cws.conviva.com

Name:    8cb691e535702e64106a3948d54b901798889ee3.ipv6.cws.conviva.com
Addresses:  2620:10b:7001:10::106
          2620:10b:7002:14::108
          2620:10b:7001:10::109
          2620:10b:7002:14::107
domain 8cb691e535702e64106a3948d54b901798889ee3.ipv6.cws.conviva.com
have only aaaa records *(ipv6)
and dont have A records (ipv4)

So this domain works only with ipv6 networks.

Thanks for this analysis.
It confirms my suspicion that it indeed seems to require IPv6.

I already have a global IPv6 address, but it seems either the routing is not working or DNS6 is not specified as ping6 does not work:
# ping6 ipv6.google.com
connect: Network is unreachable

My PC gets a global IPv6 address from the ISP router as follows (in /etc/network/interfaces via this line: iface eth0 inet6 auto):

# ifconfig
eth0      Link encap:Ethernet  HWaddr 20:1a:06:5f:c0:3d  
          inet addr:192.168.254.4  Bcast:192.168.254.255  Mask:255.255.255.0
          inet6 addr: 2a02:8108:9300:3b8:221a:6ff:fe5f:c03d/64 Scope:Global
          inet6 addr: fe80::221a:6ff:fe5f:c03d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:173804 errors:0 dropped:4809 overruns:0 frame:0
          TX packets:38281 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:211916206 (202.0 MiB)  TX bytes:4585990 (4.3 MiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:70810 errors:0 dropped:0 overruns:0 frame:0
          TX packets:70810 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:162976444 (155.4 MiB)  TX bytes:162976444 (155.4 MiB)


# route -6
Kernel IPv6 routing table
Destination                    Next Hop                   Flag Met Ref Use If
2a02:8108:9300:3b8::/64        ::                         UAe  256 0     0 eth0
fe80::/64                      ::                         U    256 0     0 eth0
::/0                           ::                         !n   -1  1  7181 lo
::1/128                        ::                         Un   0   5    32 lo
2a02:8108:9300:3b8::/128       ::                         Un   0   1     0 lo
2a02:8108:9300:3b8:221a:6ff:fe5f:c03d/128 ::                         Un   0   1     0 lo
fe80::/128                     ::                         Un   0   1     0 lo
fe80::221a:6ff:fe5f:c03d/128   ::                         Un   0   1     0 lo
ff00::/8                       ::                         U    256 4    30 eth0
::/0                           ::                         !n   -1  1  7181 lo

Can someone please tell me how to fix this. Thx.

Btw, funny: the DNS server of my ISP router says it does not know the said address:

# nslookup 8cb691e535702e64106a3948d54b901798889ee3.ipv6.cws.conviva.com
Server: 192.168.254.254
Address: 192.168.254.254#53

Non-authoritative answer:
*** Can't find 8cb691e535702e64106a3948d54b901798889ee3.ipv6.cws.conviva.com: No answer

accarda · Sat Dec 10, 2022 8:29 am

It seems like you don't have the default route being set on your client.

I'm using IPv6 and on my machine I have defined the default route manually (I have assigned manually IPv6 addresses) and I can ping that IPv6 address.
This is also that domain being resolved.

; <<>> DiG 9.11.5-P4-5.1+deb10u8-Raspbian <<>> @127.0.0.1 -p 5335 8cb691e535702e64106a3948d54b901798889ee3.ipv6.cws.conviva.com AAAA
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60937
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1472
;; QUESTION SECTION:
;8cb691e535702e64106a3948d54b901798889ee3.ipv6.cws.conviva.com. IN AAAA

;; ANSWER SECTION:
8cb691e535702e64106a3948d54b901798889ee3.ipv6.cws.conviva.com. 106 IN AAAA 2620:10b:7001:10::106
8cb691e535702e64106a3948d54b901798889ee3.ipv6.cws.conviva.com. 106 IN AAAA 2620:10b:7002:14::107
8cb691e535702e64106a3948d54b901798889ee3.ipv6.cws.conviva.com. 106 IN AAAA 2620:10b:7002:14::108
8cb691e535702e64106a3948d54b901798889ee3.ipv6.cws.conviva.com. 106 IN AAAA 2620:10b:7001:10::109

;; Query time: 0 msec
;; SERVER: 127.0.0.1#5335(127.0.0.1)
;; WHEN: Sat Dec 10 07:20:43 CET 2022
;; MSG SIZE  rcvd: 202

This is my route -6 for this client:

Kernel IPv6 routing table
Destination                    Next Hop                   Flag Met Ref Use If
ip6-localhost/128              [::]                       U    256 2     0 lo
2001:470:xyzw:y::/64           [::]                       U    202 1     0 eth0
fe80::/64                      [::]                       U    256 1     0 eth0
[::]/0                         2001:470:xyzw:y::x         UG   1   5     0 eth0
ip6-localhost/128              [::]                       Un   0   7     0 lo
pi.hole/128                    [::]                       Un   0   3     0 eth0
pi.hole/128                    [::]                       Un   0   3     0 eth0
ff00::/8                       [::]                       U    256 5     0 eth0
[::]/0                         [::]                       !n   -1  1     0 lo

MikroUser · Sat Dec 10, 2022 9:21 am

because you are using ipv4 dns,
try set first dns - ipv6, second dns - ipv4

im using cloudflare ipv6 dns: 2606:4700:4700::1111

Sat Dec 10, 2022 4:20 pm

Such service would be inaccesible to 2/3 users (global average).

IPv6 deployment rates are fairly well correlated with GDP; the low-ranked countries on one measure tend to be the low-ranked countries on the other. Paramount’s accountants might’ve chosen to leave some small fraction of dollars on the table.

Hollywood has decades of treating different regions of the world differently.

mutluit · Sat Dec 10, 2022 7:55 pm

Thanks everybody.

I now have managed to get IPv6 working, but...
unfortunately it did not fix the said problem with this streaming site.

I would like to hear of other Linux users who can use it successfully.
In the mean time I'll research the said "error code 3304" further on the net.
I have no problems with the other streaming services like Netflix, AmazonPrime, DisneyPlus, except with this ParamountPlus!

gotsprings · Sat Dec 10, 2022 7:57 pm

Didn't read any of these post.

NO

mutluit · Sun Dec 11, 2022 2:06 am

Problem finally solved!

IPv6 was not required. It just requires only a "recent" webbrowser, ie. ideally the latest version.
Mine was a little bit old (Google Chrome v92). After updating to the latest v108 it now works fine.
My Linux OS (Debian v9 "stretch") is a little bit old too, so I could install the latest Chrome version only after installing
a component library from the backports-repository. Ie. this issue:

dpkg: dependency problems prevent configuration of google-chrome-stable:
google-chrome-stable depends on libgbm1 (>= 17.1.0~rc2); however:
Version of libgbm1:amd64 on system is 13.0.6-1+b2.

Luckily v18 of that component was in the "stretch-backports" repository. After installing it,
then also the latest Chrome version did install successfully.

Now the Paramount+ streaming finally works well in my Debian Linux v9 ("stretch").
As said, IPv6 was not required.

But: it seems that one still needs to do these steps:
1) disable HW-acceleration
2) allow ads (ie. disable ad-blockers) [can also be done on a per site basis]
3) enable pop-ups [can also be done on a per site basis]

See also fixing "error code 3304" at these sites:
https://help.paramountplus.com/s/articl ... -Paramount
https://www.minitool.com/news/paramount ... -3205.html

Does Paramount+ require IPv6 ? [SOLVED]

Does Paramount+ require IPv6 ?

Re: Does Paramount+ require IPv6 ?

Re: Does Paramount+ require IPv6 ?

Re: Does Paramount+ require IPv6 ?

Re: Does Paramount+ require IPv6 ?

Re: Does Paramount+ require IPv6 ?

Re: Does Paramount+ require IPv6 ?

Re: Does Paramount+ require IPv6 ?

Re: Does Paramount+ require IPv6 ?

Re: Does Paramount+ require IPv6 ?

Re: Does Paramount+ require IPv6 ?

Re: Does Paramount+ require IPv6 ? [SOLVED]

Who is online