18 replies to this topic

[Pike_Bishop]

Hi,

 

I use PLI devel from date 22.04.2024 on my Gigablue Quad 4K, i've seeen that streamrelay is included but didn't works for me.

 

I have to say that this is decrypted via a Raspberry Pi4, but that usually works with the right settings.

All you have to do is enter the IP of the Rasberry in the streamrelay settings.

But I only get to see a black image.

Just for information -> in OpenATV-7.4 it works perfectly, in HDF-7.3 it didn't work at the beginning because it even crashed when switching to a streamrelay channel, but that was fixed a day ago and now it works perfectly there too.

Unfortunately, it doesn't work in PLI Devel at the moment.

 

Yes, it is a special case because of the Raspberrry Pi, but since it works in the other images, it must actually also work in the PLI.

With a special icam channel list it also works in the PLI but not via streamrelay.

 

 

regards

Pike

Edited by Pike_Bishop, 25 April 2024 - 19:15.

[WanWizard]

The Enigma streamrelay code is ours, others copied it, so not very likely the code is to blame.

 

Can you request the stream URL (with the RasPI IP) directly from your browser? And does that work? Is that the same URL as Enigma is generating?

There's nothing complex about at, Enigma generales a URL with an IP and a port, and then requests it like any other stream.

 

Is the rest of the Enigma config also ok? For example the ECM decoding settings for streams? And the local oscam has access to the NDS card to decode the channel?

[Pike_Bishop]

Hi,

 

yes i know that this code for streamrelay is from pli, but maybe oatv and hdf have extended the code a bit.

i have the following settings and they are correct in this case because i didn't use dvbapi but instead radegast on my Raspberry Pi4 (you can see it in the picture green framed);

 

 screenshot_2024-04-27_11-01-16.jpg   153.76KB   3 downloads

 

 

the oscam on my Raspberry Pi4 is build with the correct patches for this and all Images as openpli-devel, openatv-7.4, and openhdf-7.3

has a completely identical configuration but on openpli-devel it didn't works (i can see only a black screen if i switch to a streamrelay channel).

but if i use a a special icam channel list like this;

#DESCRIPTION ###### Sky Film icam ######
#SERVICE 1:0:19:83:6:85:21:0:0:0:http%3a//192.168.188.17%3a17999/1%3a0%3a19%3a83%3a6%3a85%3aC00000%3a0%3a0%3a0%3a:Sky Cinema Premiere
#DESCRIPTION Sky Cinema Premiere
#SERVICE 1:0:19:74:9:85:21:0:0:0:http%3a//192.168.188.17%3a17999/1%3a0%3a19%3a74%3a9%3a85%3aC00000%3a0%3a0%3a0%3a:Sky Cinema Action
#DESCRIPTION Sky Cinema Action
#SERVICE 1:0:19:6F:D:85:21:0:0:0:http%3a//192.168.188.17%3a17999/1%3a0%3a19%3a6F%3aD%3a85%3aC00000%3a0%3a0%3a0%3a:Sky Cinema Highlights
#DESCRIPTION Sky Cinema Highlights
#SERVICE 1:0:19:6B:C:85:21:0:0:0:http%3a//192.168.188.17%3a17999/1%3a0%3a19%3a6B%3aC%3a85%3aC00000%3a0%3a0%3a0%3a:Sky Cinema Classics
#DESCRIPTION Sky Cinema Classics
#SERVICE 1:0:19:8B:2:85:21:0:0:0:http%3a//192.168.188.17%3a17999/1%3a0%3a19%3a8B%3a2%3a85%3aC00000%3a0%3a0%3a0%3a:Sky Cinema Family
#DESCRIPTION Sky Cinema Family
#SERVICE 1:0:19:17:4:85:21:0:0:0:http%3a//192.168.188.17%3a17999/1%3a0%3a19%3a17%3a4%3a85%3aC00000%3a0%3a0%3a0%3a:Sky Krimi
#DESCRIPTION Sky Krimi

and if i switch to a channel from this list it works and i have picture and sound.

 

here is the content of the whitelist_streamrelay

(everything looks good but there is neither picture nor sound via streamrelay);

1:0:1:7477:3F0:1:C00000:0:0:0:
1:0:16:101D:451:35:C00000:0:0:0:
1:0:16:16:2:85:C00000:0:0:0:
1:0:19:8B:2:85:C00000:0:0:0:
1:0:19:93:2:85:C00000:0:0:0:
1:0:16:192:2:85:C00000:0:0:0:
1:0:19:206:2:85:C00000:0:0:0:
1:0:19:17:4:85:C00000:0:0:0:
1:0:19:8C:4:85:C00000:0:0:0:
1:0:19:8F:4:85:C00000:0:0:0:
1:0:19:D:6:85:C00000:0:0:0:
1:0:19:76:6:85:C00000:0:0:0:
1:0:19:82:6:85:C00000:0:0:0:
1:0:19:83:6:85:C00000:0:0:0:
1:0:19:74:9:85:C00000:0:0:0:
1:0:19:7A:9:85:C00000:0:0:0:
1:0:19:84:9:85:C00000:0:0:0:
1:0:19:85:9:85:C00000:0:0:0:
1:0:19:71:B:85:C00000:0:0:0:
1:0:19:88:B:85:C00000:0:0:0:
1:0:19:8E:B:85:C00000:0:0:0:
1:0:16:A8:B:85:C00000:0:0:0:
1:0:16:191:B:85:C00000:0:0:0:
1:0:16:194:B:85:C00000:0:0:0:
1:0:16:1C:C:85:C00000:0:0:0:
1:0:19:6B:C:85:C00000:0:0:0:
1:0:19:6C:C:85:C00000:0:0:0:
1:0:19:7C:C:85:C00000:0:0:0:
1:0:19:7E:C:85:C00000:0:0:0:
1:0:16:1B:D:85:C00000:0:0:0:
1:0:19:6E:D:85:C00000:0:0:0:
1:0:19:6F:D:85:C00000:0:0:0:
1:0:19:70:D:85:C00000:0:0:0:
1:0:19:7F:D:85:C00000:0:0:0:
1:0:19:90:D:85:C00000:0:0:0:
1:0:19:65:10:85:C00000:0:0:0:
1:0:19:7B:10:85:C00000:0:0:0:

 

regards

Pike

Edited by Pike_Bishop, 27 April 2024 - 20:32.

[littlesat]

When they extend the code without merging things back they do not play the opensource rules nicely…. Now you have to point us to their changes. The code was made for oscam emu on local box and not for running it on a raspberry py. So we need at least more info about your configuration.

[Dimitrij]

oscam emu

What should the oscam emu configs look like for stream relay?

[WanWizard]

The code was made for oscam emu on local box and not for running it on a raspberry py. So we need at least more info about your configuration.

 

That shouldn't matter, I have also configured an IP other than 127.0.0.1.

 

The only difference is that mine is from a box, so oscam can fetch the stream loallly, while in case of the RasPi, it must fetch the stream over the network, so you have network delay and jitter twice.

 

But as the icam boquet works fine, the problem doesn't seem to be at the RasPi end. But I can't see what the problem can be, streamrelay doesn't do more than convert the service into a URL.

 

@Pike_Bishop,

 

you might want to run a tcpdump on the client box, test both the streamrelay and the icam bouquet entry, and see if you can spot a difference?

[Huevos]

oscam emu

What should the oscam emu configs look like for stream relay?

Why do you need emu? It works fine on regular Oscam.

 

Config (on the server box) something like this. XXXX are the CAIDs in hex.

[streamrelay]
stream_relay_enabled          = 1
stream_relay_ctab             = XXXX,XXXX,XXXX,XXXX

Edited by Huevos, 28 April 2024 - 11:50.

[Huevos]

I don't understand what he is doing. Why does he need Oscam on the Raspberry Pi client? The decryption should all happen on the server. And it does work. We have tested this extensively on E2 clients and even android clients running kodi.

 

Using the box IP and port 17999 it works 100%.

[littlesat]

You do not need oscam emu, but oscam emu gives you extra’s on top of the same.

[Dimitrij]

stream_relay_enabled          = 1

This default?

[Dimitrij]

[radegast]
port = 9090
allowed = 127.0.0.1,192.168.0.0-192.168.255.255
user = icam

oscam/scam-emu openPli not suppport radegast

[Pike_Bishop]

Hi guys,

 

@Huevos

I don't understand what he is doing. Why does he need Oscam on the Raspberry Pi client? The decryption should all happen on the server. And it does work. We have tested this extensively on E2 clients and even android clients running kodi.

 

First a Info to this methode;

This method is intended for weak boxes so that the Raspberry PI4 takes over the decryption.

However, you can of course also share to other boxes in this way.

 

It does not require any oscam on the E2 box itself, the oscam with the icam patches on the Raspberry Pi is sufficient

 

so which configs did you need ?

i post the oscam configs from the Raspberry Pi here

 

oscam.conf;

[radegast]
port                          = 9090
allowed                       = 127.0.0.1,192.168.0.0-192.168.255.255
user                          = raspipi

[streamrelay]
stream_source_auth_user       = raspipi
stream_client_source_host     = 1
stream_ecm_delay              = 1
stream_emm_enabled            = 0
stream_relay_ctab             = 098D

oscam.server;

[reader]
label                         = emulator
protocol                      = emu
device                        = emulator
disablecrccws_only_for        = 0E00:000000
caid                          = 0500,0604,0E00,1010,1801,2600,2602,2610
detect                        = cd
ident                         = 0500:000000,007400,007800,021110,023800;0604:000000;0E00:000000;1010:000000;1801:000000,001101,002111,007301;2600:000000;2602:000000;2610:000000
group                         = 1
emmcache                      = 2,1,2,1
emu_auproviders               = 0604:010200;0E00:000000;1010:000000;2610:000000

the reader for the sky card is also in the oscam.server and active.

 

oscam.user;

[account]
user                          = raspipi
group                         = 1,2,3,4,5

And here is a picture of a setting in oscam that is absolutely necessary for this methode;

 raspipi4_config.jpg   83KB   5 downloads

 

 

@WanWizard

you might want to run a tcpdump on the client box, test both the streamrelay and the icam bouquet entry, and see if you can spot a difference?

ok i will test this.

 

 

@Dimitrij

oscam/scam-emu openPli not suppport radegast

if i said for this methode you didn't need oscam on the e2box.

 

 

regards

Pike

Edited by Pike_Bishop, 29 April 2024 - 20:21.

[twol]

Total overkill - my main lounge box (gbquad4K) supports stream relay (DE/UK) directly via oscam, plus a zgemma H9 running as a client of the gbquad4k server.
Both handle stream relay services without issues. 

[Pike_Bishop]

no, isn't overkill, that is your opinion and is not helpful.

as i said it's good for weak boxes with little power, otherwise it didn't works with this boxes.

and also you can share it with this methode to other boxes.

 

yes you can also use a other E2 box to share it but then this box (the server) must always be switched on, which means power consumption.

the Raspberry of course also needs power but much less than an E2 box, especially if it only serves as an oscam server.

Edited by Pike_Bishop, 1 May 2024 - 18:09.

[Pike_Bishop]

if i switch to a icam channel from my icam channelllist and make a;

tcpdump -c 50 -i eth0 port 17999

it comes this (this works channels become light);

tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
19:38:01.357528 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 2847537166:2847538614, ack 1564649825, win 508, options [nop,nop,TS val 3529909277 ecr 11348], length 1448
19:38:01.357580 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [P.], seq 1448:6016, ack 1, win 508, options [nop,nop,TS val 3529909277 ecr 11348], length 4568
19:38:01.357593 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 6016, win 18166, options [nop,nop,TS val 11350 ecr 3529909277], length 0
19:38:01.359525 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 6016:7464, ack 1, win 508, options [nop,nop,TS val 3529909279 ecr 11350], length 1448
19:38:01.359578 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [P.], seq 7464:12032, ack 1, win 508, options [nop,nop,TS val 3529909279 ecr 11350], length 4568
19:38:01.359594 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 12032, win 18166, options [nop,nop,TS val 11352 ecr 3529909279], length 0
19:38:01.361530 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 12032:13480, ack 1, win 508, options [nop,nop,TS val 3529909281 ecr 11352], length 1448
19:38:01.361571 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [P.], seq 13480:18048, ack 1, win 508, options [nop,nop,TS val 3529909281 ecr 11352], length 4568
19:38:01.361586 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 18048, win 18166, options [nop,nop,TS val 11354 ecr 3529909281], length 0
19:38:01.363528 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 18048:19496, ack 1, win 508, options [nop,nop,TS val 3529909283 ecr 11354], length 1448
19:38:01.363574 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [P.], seq 19496:24064, ack 1, win 508, options [nop,nop,TS val 3529909283 ecr 11354], length 4568
19:38:01.363589 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 24064, win 18166, options [nop,nop,TS val 11356 ecr 3529909283], length 0
19:38:01.365528 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 24064:25512, ack 1, win 508, options [nop,nop,TS val 3529909285 ecr 11356], length 1448
19:38:01.365570 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 25512:29856, ack 1, win 508, options [nop,nop,TS val 3529909285 ecr 11356], length 4344
19:38:01.365582 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 29856, win 18166, options [nop,nop,TS val 11358 ecr 3529909285], length 0
19:38:01.365598 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [P.], seq 29856:30080, ack 1, win 508, options [nop,nop,TS val 3529909285 ecr 11356], length 224
19:38:01.365626 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 30080, win 18166, options [nop,nop,TS val 11358 ecr 3529909285], length 0
19:38:01.367519 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 30080:31528, ack 1, win 508, options [nop,nop,TS val 3529909287 ecr 11358], length 1448
19:38:01.367546 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 31528:34424, ack 1, win 508, options [nop,nop,TS val 3529909287 ecr 11358], length 2896
19:38:01.367554 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 34424, win 18166, options [nop,nop,TS val 11360 ecr 3529909287], length 0
19:38:01.367574 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [P.], seq 34424:36096, ack 1, win 508, options [nop,nop,TS val 3529909287 ecr 11358], length 1672
19:38:01.367581 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 36096, win 18166, options [nop,nop,TS val 11360 ecr 3529909287], length 0
19:38:01.369552 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 36096:37544, ack 1, win 508, options [nop,nop,TS val 3529909289 ecr 11360], length 1448
19:38:01.369585 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 37544:40440, ack 1, win 508, options [nop,nop,TS val 3529909289 ecr 11360], length 2896
19:38:01.369600 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 40440, win 18166, options [nop,nop,TS val 11362 ecr 3529909289], length 0
19:38:01.369625 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [P.], seq 40440:42112, ack 1, win 508, options [nop,nop,TS val 3529909289 ecr 11360], length 1672
19:38:01.369632 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 42112, win 18166, options [nop,nop,TS val 11362 ecr 3529909289], length 0
19:38:01.371548 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 42112:43560, ack 1, win 508, options [nop,nop,TS val 3529909291 ecr 11362], length 1448
19:38:01.371574 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 43560:46456, ack 1, win 508, options [nop,nop,TS val 3529909291 ecr 11362], length 2896
19:38:01.371583 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 46456, win 18166, options [nop,nop,TS val 11364 ecr 3529909291], length 0
19:38:01.371602 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [P.], seq 46456:48128, ack 1, win 508, options [nop,nop,TS val 3529909291 ecr 11362], length 1672
19:38:01.371609 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 48128, win 18166, options [nop,nop,TS val 11364 ecr 3529909291], length 0
19:38:01.373549 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 48128:49576, ack 1, win 508, options [nop,nop,TS val 3529909293 ecr 11364], length 1448
19:38:01.373575 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 49576:52472, ack 1, win 508, options [nop,nop,TS val 3529909293 ecr 11364], length 2896
19:38:01.373582 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 52472, win 18166, options [nop,nop,TS val 11366 ecr 3529909293], length 0
19:38:01.373601 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [P.], seq 52472:54144, ack 1, win 508, options [nop,nop,TS val 3529909293 ecr 11364], length 1672
19:38:01.373608 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 54144, win 18166, options [nop,nop,TS val 11366 ecr 3529909293], length 0
19:38:01.375539 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 54144:55592, ack 1, win 508, options [nop,nop,TS val 3529909295 ecr 11366], length 1448
19:38:01.375560 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 55592:57040, ack 1, win 508, options [nop,nop,TS val 3529909295 ecr 11366], length 1448
19:38:01.375568 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 57040, win 18166, options [nop,nop,TS val 11368 ecr 3529909295], length 0
19:38:01.375591 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [P.], seq 57040:60160, ack 1, win 508, options [nop,nop,TS val 3529909295 ecr 11366], length 3120
19:38:01.375598 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 60160, win 18166, options [nop,nop,TS val 11368 ecr 3529909295], length 0
19:38:01.377549 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 60160:61608, ack 1, win 508, options [nop,nop,TS val 3529909297 ecr 11368], length 1448
19:38:01.377569 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 61608:63056, ack 1, win 508, options [nop,nop,TS val 3529909297 ecr 11368], length 1448
19:38:01.377577 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 63056, win 18166, options [nop,nop,TS val 11370 ecr 3529909297], length 0
19:38:01.377600 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [P.], seq 63056:66176, ack 1, win 508, options [nop,nop,TS val 3529909297 ecr 11368], length 3120
19:38:01.377607 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 66176, win 18166, options [nop,nop,TS val 11370 ecr 3529909297], length 0
19:38:01.379539 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 66176:67624, ack 1, win 508, options [nop,nop,TS val 3529909299 ecr 11370], length 1448
19:38:01.379558 IP 192.168.188.17.17999 > 192.168.188.11.44760: Flags [.], seq 67624:69072, ack 1, win 508, options [nop,nop,TS val 3529909299 ecr 11370], length 1448
19:38:01.379565 IP 192.168.188.11.44760 > 192.168.188.17.17999: Flags [.], ack 69072, win 18166, options [nop,nop,TS val 11372 ecr 3529909299], length 0
50 packets captured
87 packets received by filter
0 packets dropped by kernel

if i switch than to a streamrelay channel and make the same tcpdump it comes only this;

tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
19:41:47.152266 IP 192.168.188.17.17999 > 192.168.188.11.44766: Flags [F.], seq 336125439, ack 1917298500, win 508, options [nop,nop,TS val 3530133082 ecr 206848], length 0
19:41:47.191344 IP 192.168.188.11.44766 > 192.168.188.17.17999: Flags [.], ack 1, win 457, options [nop,nop,TS val 235184 ecr 3530133082], length 0

and it does not jump back to the prompt.

 

difficult to determine other differences

but I always see P at the top of the flags and F at the bottom if it doesn't work

 

 

regards

Pike

Edited by Pike_Bishop, 1 May 2024 - 18:51.

[WanWizard]

The F flag means it a FIN packet.

 

So Oscam immediately closes the connection.

[Pike_Bishop]

And that's why it doesn't work via a streamrelay channel, right?

What else can I do?

 

 

regards

Pike

[WanWizard]

It is oscam that provides the streamrelay, so you need to find out why oscam on 192.168.188.11 does that.

[Pike_Bishop]

Hmm , ja mal gucken. Danke