123 replies to this topic

[zeros]

If you teach, how do I do that? Or, I'm looking forward when you doing it and then reporting, whether it then works? GStreamer is too complicated for me to change it there.

Edited by zeros, 12 December 2015 - 17:23.

[athoik]

If you teach, how do I do that? Or, I'm looking forward when you doing it and then reporting, whether it then works? GStreamer is too complicated for me to change it there.

I've send an patch for Enigma2 (https://github.com/O...46f5d6b1dee85aa), so by default Enigma2 will send a valid HbbTV User-Agent, so tomorrow all users will get the update and hopefully the fix for User-Agent.


Although I can still "teach you" how to pass the extra headers, it's not complicated.

Append to the url or finalurl something like the following "#User-Agent=" + user_agent before calling eServiceReference.

Here the changes in line 847-849.

                        if finalurl != '':
                                self.service = eServiceReference(4097, 0, finalurl + "#User-Agent=" + user_agent)
                        else:
                                self.service = eServiceReference(4097, 0, url + "#User-Agent=" + user_agent)

[zeros]

And the drums are drumming and trumpets shouts. It works!!!

 

Whether the fix is also added to Vu+ plugin?

 

Many thanks.

Attached Files

•  it-works-now.JPG   82.26KB   8 downloads

Edited by zeros, 13 December 2015 - 15:19.

[athoik]

Update tomorrow and report (it should work for all models without further changes)

[zeros]

Thank you!

[athoik]

So update worked?

[zeros]

Actually it worked before the update, because I followed your tips. After today's update it also remained working (DM7020 HD). I give the feedback of the Vu + Zero on tomorrow (we use it with Sundtek MediaTV Pro USB stick).

Edited by zeros, 14 December 2015 - 22:30.

[zeros]

One of my friend reported that it works now also with openATV. I looked at that, they have also made the change:
std::string user_agent = "Enigma2";
46 + std::string user_agent = "Enigma2 HbbTV/1.1.1 (+PVR+RTSP+DL;openATV;;;)";

[athoik]

Yes, I know.. This is how open source works.

[zeros]

The good news is that the Vu + Zero Hbbtv generally works (remember, this part of the beginning!)! This channel Kanal 2, which we were in here lastly fixed, right now does not work with Vu+Zero. I can't more demand from my father, than the software update :-) I think that this is the Vu+ plugin. For my father is a kind of taking the log a complicated task.
Some reports more -
VTi - NOK
OpenATV + Vu Solo4K box + webkithbbtv plugin - NOK

Attached Files

•  image.png   402.2KB   3 downloads

[athoik]

It is better to know at least that OpenPLi works (by simply updating like your father does).

If there is an issue with boxes with other HbbTV implementation than OpenOpera (like VU+ or ET) we can have a look.

Although it is clear what the problem is and how to fix it (at least for Kanal 2 case).

[zeros]

Yes, many thanks!

[zeros]

Reported that Xtrend ET 10000 + PLi was previously OK (before Your fix). Probay there was it somehow added.

[Frenske]

On my recently fresh flashed (12-12-2015) ET10000 HBBTV still works ok.
After the update at the 13th, HBBTV still wasn't broken.

[zeros]

Hi athoik!

You solved our problem with HbbTV and Kanal 2, a big thanks to you.

Here are two of the HbbTV plugins yet, what waiting for fix:

1) Vu+ plugin HbbTV - it seems like that is a closed plugin (only pyo files) :-(

2) WebkitHbbTV(solo4k) - this we can perhaps fix?

 

Do you think you could help with this WebkitHbbTV(solo4k) also? We can report the results. Sure you have soon the solo4k software available, it would be good to fix the WebkitHbbTV there already.

Attached Files

•  HBBTv.rar   113.5KB   21 downloads

[athoik]

Hi zeros,


Most probably VU+ HbbTV implementation does not rely on Enigma2 to get media. But they do have their own implementation (like ET or DMM does).

Without even touching the code, we can see what goes out the wire...

Assuming that we are using http protocol on port 80 the following command will print the headers we are sending out.
 

tcpdump -A -s 10240 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)'

So before opening the Kanal 2 run the above command and attach the output here.

In case that tcpdump is not installed you can install it using opkg update && opkg install tcpdump command.

So mistery with VU+ HbbTV soon will be demystified too

Edited by athoik, 20 December 2015 - 14:11.

[zeros]

Thank you, I`m going to send this output better PM. I´m not sure whether this can place to the public forum.

[athoik]

Don't worry there are no secrets in the tcpdump output, at least when you are opening Kanal 2.

You can have a look at the log and wipe out any sensitive information.

[athoik]

Hi,

The problem with vusolo4k after receiving tcpdump logs is the User-Agent.
 

19:01:28.255870 IP vusolo4k.local.36739 > 217.146.75.93.http: Flags [P.], seq 696612650:696612831, ack 3144910966, win 229, options [nop,nop,TS val 4294948604 ecr 598427860], length 181: HTTP: GET /kanal2vod/k2hq/clips/ads/Rannarootsi_Talvetooted_Sylt_15s_EST.mp4 HTTP/1.1
E.....@.@.........K]...P).w*.s.v...........
....#.H.GET /kanal2vod/k2hq/clips/ads/Rannarootsi_Talvetooted_Sylt_15s_EST.mp4 HTTP/1.1
Host: download.cdn.mind.ee
Connection: close
icy-metadata: 1
User-Agent: NSPlayer/7.10.0.3059

The requests shall include valid HbbTV User-Agent..

According to HBBTV specification http://www.etsi.org/...796v010101p.pdf the user agent should be like this:
 

7.3.2.4 HTTP User-Agent header 

All outgoing HTTP requests made on behalf of an Hybrid Broadcast Broadband TV application shall include a User-Agent header using the syntax described in this clause. 

The User-Agent header shall include: 

HbbTV/1.1.1 (<capabilities>; [<vendorName>]; [<modelName>]; [<softwareVersion>];  [<hardwareVersion>]; <reserved>)  

Where:
The <capabilities> field consists of zero or more concaten ated Hybrid Broadcast Broadband TV option strings as defined in clause 10.2.4. 
The <vendorName>, <modelName>, <softwareVersion> and <hardwareVersion> fields are the same as the one defined in the  application/oipfRemoteManagement object in the OIPF DAE specification [2] and are optional. 
The <reserved> field is reserved for future extensions. 

This User-Agent header may be extended with other implementation-specific information including other user agent information.
In particular, it is recommended to include the browser user agent information. 

Valid examples of this syntax are: 
User-Agent: HbbTV/1.1.1 (+PVR+DL; Sonic; TV44; 1.32.455; 2.002) Bee/3.5 
User-Agent: HbbTV/1.1.1 (;;;;) 

[zeros]

Thaks again, I'm sure that you've got the right solution.
But since I can't test it myself, then a small tutorial would be a good idea. Either it needs to be changed outside of the plugin?