with latest commit dvbapi not working anymore

[holli73]

hello,

i did a fresh clone and build - but now minisatip is not connecting to oscam at all - it looks like that -o is not taken? if i revert to my prev. the same start command is working and minisatip is connecting right after start...

any idea?

thanks holli

working version
2023/02/21 23:27:38 5E595C28 c   (dvbapi) Using TCP listen socket, API forced to DVBAPIv3 (0), userconfig boxtype: 11
2023/02/21 23:37:10 5E595C28 c   (dvbapi) Client connected: 'minisatip/v1.1.5-c750f4c' (protocol version = 2)

not connecting at all:
Minisatip Version: 1.2.83~25ef1f6 -- Build date/time: Feb 21 2023 | 23:41:52

[lars18th]

any idea?

Check if you have compiled the fresh version with the same config parameters that with the previous working version. Or execute both with -l general and compare the first lines. I don't have any problem with last versions using the dvbapi.

[holli73]

hello,

the only difference is openssl?

holli@satip:~/BUILD/minisatip/minisatip-master$ ./minisatip -f -l general
[22/02 11:48:37.759 main]: Adapter sources format parameter missing, using defaults for all adapters!
[22/02 11:48:37.759 main]: minisatip version v1.1.5-c750f4c, compiled in May 22 2021 09:56:54, with s2api version: 050B
[22/02 11:48:37.759 main]: Built with dvbcsa
[22/02 11:48:37.759 main]: Built with CI
[22/02 11:48:37.759 main]: Built with dvbapi
[22/02 11:48:37.759 main]: Built with AES (OpenSSL)
[22/02 11:48:37.759 main]: Built with tables processing
[22/02 11:48:37.759 main]: Built with pmt processing
[22/02 11:48:37.759 main]: Built with satip client
[22/02 11:48:37.759 main]: Built with linux dvb client
[22/02 11:48:37.759 main]: Built with backtrace
[22/02 11:48:37.759 main]: Built without netceiver
[22/02 11:48:37.759 main]: Built without ddci
[22/02 11:48:37.759 main]: Built without t2mi
[22/02 11:48:37.759 main]: tcp_listen: failed: bind() on address: ANY [0.0.0.0], port 554 : error Permission denied
holli@satip:~/BUILD/minisatip/minisatip-master$ ./minisatip-latest -f -l general
[22/02 11:48:56.432 main]: minisatip version 1.2.84~5634b4d, compiled in Feb 22 2023 11:40:40, with s2api version: 050B
[22/02 11:48:56.432 main]: Built with dvbcsa
[22/02 11:48:56.432 main]: Built with CI
[22/02 11:48:56.432 main]: Built with dvbapi
[22/02 11:48:56.432 main]: Built with tables processing
[22/02 11:48:56.432 main]: Built with pmt processing
[22/02 11:48:56.432 main]: Built with satip client
[22/02 11:48:56.432 main]: Built with linux dvb client
[22/02 11:48:56.432 main]: Built with backtrace
[22/02 11:48:56.432 main]: Built without netceiver
[22/02 11:48:56.432 main]: Built with ddci
[22/02 11:48:56.432 main]: Built without t2mi
[22/02 11:48:56.432 main]: Command line: ./minisatip-latest -f -l general
[22/02 11:48:56.432 main]:  LOG  of the module enabled: general
[22/02 11:48:56.432 main]: mkdir /var failed
[22/02 11:48:56.432 main]: mkdir /var/cache failed
[22/02 11:48:56.432 main]: mkdir /var/cache/minisatip failed
[22/02 11:48:56.432 main]: tcp_listen: failed: bind() on address: ANY [0.0.0.0], port 554 : error Permission denied
holli@satip:~/BUILD/minisatip/minisatip-master$

so i tried to change argument by argument and it looks like - if after ther port ',10' is used no connect to oscam - i was using it for some time - now it is not working anymore - was there a change?

-a 8:0:0 -D 1 -e 0-7 -E -o 192.168.248.248:11234,10 -x 8080 -m 661122334455 -O -y 554 -c 0:0,1:0,2:0,3:0,4:0,5:0,6:0,7:0 &
vs working one:
-a 8:0:0 -D 1 -e 0-7 -E -o 192.168.248.248:11234 -x 8080 -m 661122334455 -O -y 554 -c 0:0,1:0,2:0,3:0,4:0,5:0,6:0,7:0 &

thanks holli

[lars18th]

Hi @holli73 ,

Therefore, the problem is because you need to use -o 192.168.248.248:11234,10 instead of -o 192.168.248.248:11234. In this case I can't help you because I don't use this offset option. Anyway, ask to @catalinii (the main developer). Perhaps he can help you.

Regards.

[catalinii]

can you upload the log ? ./minisatip -f -l http ....

[holli73]

@catalinii

attached is the log as requested

if i remove ,10 it works - it looks like since icam v9 - i do not need the offset so far. minisatip.txt

[catalinii]

I found this in your log: New TCP socket 23 connected to 192.16:9000 is it possible that copy paste went wrong ? Can you try re-writing by hand ?

[Jalle19]

Closing due to inactivity. @holli73 please re-open if you still have issues.