Using Minisatip with Netceiver

Support forum for minisatip
Post Reply
thowa
Posts: 6
Joined: Mon May 15, 2017 10:50 am

Using Minisatip with Netceiver

Post by thowa »

Hi,

I'm came across minisatip while I was looking for a possibility to continue using the Netceiver in my dying Reelbox Avantgard I.

I followed the steps in this thread to compile minisatip.
Compilation finally succeeded and I'm able to start minisatip with out errors.

Code: Select all

e.g. minisatip -n eth1.2:2
How can I see, if minisatip has really found my Netceiver?

Does anybody know, how to configure the network correct for using it with the NetCeiver?
I have two network interfaces eth0 and eth1. I thought using eth0 for my home-network/internet.
On eth1 the netceiver is the only other party and it is directly connected.
Do I have to set up an vlan for the netceiver?
Does it use IPv4 or v6?

Any help is appreciated ;-)
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: Using Minisatip with Netceiver

Post by cata »

Hi,

You can add -f -l -l -l and see the logs (or upload them here).

Thanks
thowa
Posts: 6
Joined: Mon May 15, 2017 10:50 am

Re: Using Minisatip with Netceiver

Post by thowa »

Code: Select all

root@easyVDR:~# minisatip -n eth1.4:2 -f -l -l -l
[15/05 21:45:01.363 main]: minisatip version 0.7.4, compiled with s2api version: 050A
[15/05 21:45:01.363 main]: Built with dvbcsa
[15/05 21:45:01.363 main]: Built without CI
[15/05 21:45:01.363 main]: Built with dvbapi
[15/05 21:45:01.363 main]: Built with AES (OpenSSL)
[15/05 21:45:01.363 main]: Built with tables processing
[15/05 21:45:01.363 main]: Built with satip client
[15/05 21:45:01.363 main]: Built with linux dvb client
[15/05 21:45:01.363 main]: Built with backtrace
[15/05 21:45:01.363 main]: Built with netceiver
[15/05 21:45:01.363 main]: New UDP socket 3 bound to 0.0.0.0:1900
[15/05 21:45:01.363 main]: setting multicast for 239.255.255.250
[15/05 21:45:01.363 main]: New UDP socket 4 bound to 239.255.255.250:1900
[15/05 21:45:01.363 main]: tcp_listen: failed: bind() on address: ANY, port 554 : error Address already in use
[15/05 21:45:01.363 main]: RTSP: Could not listen on port 554

The network is configured like following:

Code: Select all

root@easyVDR:~# ifconfig
eth0      Link encap:Ethernet  Hardware Adresse 00:13:3b:0f:32:4e
          inet Adresse:192.168.178.11  Bcast:192.168.178.255  Maske:255.255.255.0
          inet6-Adresse: fe80::213:3bff:fe0f:324e/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX-Pakete:26014 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:15407 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX-Bytes:4987233 (4.9 MB)  TX-Bytes:8564708 (8.5 MB)

eth1      Link encap:Ethernet  Hardware Adresse 2c:4d:54:ea:54:a0
          inet6-Adresse: fe80::2e4d:54ff:feea:54a0/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST MULTICAST  MTU:1500  Metrik:1
          RX-Pakete:10035 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:5646 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX-Bytes:903150 (903.1 KB)  TX-Bytes:650521 (650.5 KB)

eth1.4    Link encap:Ethernet  Hardware Adresse 2c:4d:54:ea:54:a0
          inet Adresse:10.0.0.1  Bcast:10.0.0.255  Maske:255.255.255.0
          inet6-Adresse: fe80::2e4d:54ff:feea:54a0/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST MULTICAST  MTU:1500  Metrik:1
          RX-Pakete:0 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:448 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX-Bytes:0 (0.0 B)  TX-Bytes:74370 (74.3 KB)

lo        Link encap:Lokale Schleife
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:65536  Metrik:1
          RX-Pakete:6977 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:6977 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:1
          RX-Bytes:26605882 (26.6 MB)  TX-Bytes:26605882 (26.6 MB)
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: Using Minisatip with Netceiver

Post by cata »

Hi

Minisatip is already running.

Run:

killall minisatip
Abd try again.

Thanks
thowa
Posts: 6
Joined: Mon May 15, 2017 10:50 am

Re: Using Minisatip with Netceiver

Post by thowa »

now I'm getting this

Code: Select all

root@easyVDR:~# minisatip -n eth1:1 -f -l -l -l
[16/05 22:31:31.653 main]: minisatip version 0.7.4, compiled with s2api version: 050A
[16/05 22:31:31.654 main]: Built with dvbcsa
[16/05 22:31:31.654 main]: Built without CI
[16/05 22:31:31.654 main]: Built with dvbapi
[16/05 22:31:31.654 main]: Built with AES (OpenSSL)
[16/05 22:31:31.654 main]: Built with tables processing
[16/05 22:31:31.654 main]: Built with satip client
[16/05 22:31:31.654 main]: Built with linux dvb client
[16/05 22:31:31.654 main]: Built with backtrace
[16/05 22:31:31.654 main]: Built with netceiver
[16/05 22:31:31.654 main]: New UDP socket 3 bound to 0.0.0.0:1900
[16/05 22:31:31.654 main]: setting multicast for 239.255.255.250
[16/05 22:31:31.654 main]: New UDP socket 4 bound to 239.255.255.250:1900
[16/05 22:31:31.654 main]: Mutex init 0x640e20
[16/05 22:31:31.654 main]: Mutex init 0x228c7d8
[16/05 22:31:31.654 main]: sockets_add: handle 3 (type 0) returning socket index 0 [0.0.0.0:0] read: 0x40859b
[16/05 22:31:31.654 main]: Mutex init 0x228cf88
[16/05 22:31:31.654 main]: sockets_add: handle 4 (type 0) returning socket index 1 [0.0.0.0:0] read: 0x40859b
[16/05 22:31:31.654 main]: Mutex init 0x228d0b8
[16/05 22:31:31.654 main]: sockets_add: handle 5 (type 2) returning socket index 2 [0.0.0.0:0] read: 0x40844a
[16/05 22:31:31.654 main]: Mutex init 0x228d1e8
[16/05 22:31:31.654 main]: sockets_add: handle 6 (type 2) returning socket index 3 [0.0.0.0:0] read: 0x40844a
[16/05 22:31:31.654 main]: Mutex init 0x228d318
[16/05 22:31:31.654 main]: sockets_add: handle -2 (type 0) returning socket index 4 [0.0.0.0:0] read: 0x40859b
[16/05 22:31:31.654 main]: set_socket_thread: thread ead36700 for sockets 4
[16/05 22:31:31.654 main]: Mutex init 0x228d578
[16/05 22:31:31.654 main]: sockets_add: handle -2 (type 0) returning socket index 5 [0.0.0.0:0] read: 0x40859b
[16/05 22:31:31.654 main]: set_socket_thread: thread ead36700 for sockets 5
[16/05 22:31:31.654 main]: Mutex init 0x642d20
[16/05 22:31:31.654 main]: Mutex init 0x228d6a8
[16/05 22:31:31.654 main]: sockets_add: handle -2 (type 0) returning socket index 6 [0.0.0.0:0] read: 0x40859b
[16/05 22:31:31.654 main]: Mutex init 0x642b60
[16/05 22:31:31.654 main]: starting init_all_hw 0
[16/05 22:31:31.654 main]: Mutex init 0x6415a0
[16/05 22:31:31.654 signal]: Starting select_and_execute on thread ID ead36700, thread_name signal
[16/05 22:31:32.410 main]: REEL: Search for 1 Netceiver on eth1... ######
Found NetCeiver: fe80::208:54ff:fe54:b197
        Tuner: Conexant CX24116 DVB-S2, Type 4
        Tuner: Conexant CX24116 DVB-S2, Type 4

[16/05 22:31:32.410 main]: netceiver: adding [AD0 DVB-S2] [AD1 DVB-S2]
[16/05 22:31:32.410 main]: Mutex init 0x228e158
[16/05 22:31:32.411 main]: netceiver: creating DVR pipe for adapter 0  -> dvr: 9
[16/05 22:31:32.411 main]: deleting pids on adapter 0, sid -1, pids=NULL
[16/05 22:31:32.411 main]: netceiver: add a new receiver instance for adapter 0
[16/05 22:31:32.411 main]: clearing type and pat processed for adapter 0
[16/05 22:31:32.411 main]: Mutex init 0x229ec98
[16/05 22:31:32.411 main]: sockets_add: handle 9 (type 5) returning socket index 7 [0.0.0.0:0] read: 0x408552
[16/05 22:31:32.411 main]: set_socket_thread: thread e8d32700 for sockets 7
[16/05 22:31:32.411 main]: pthread_setschedparam failed with error 22
[16/05 22:31:32.411 main]: done opening adapter 0 delivery systems: dvbs2 dvbs undefined undefined
[16/05 22:31:32.411 main]: Mutex init 0x228efe8
[16/05 22:31:32.411 AD0]: Starting select_and_execute on thread ID e8d32700, thread_name AD0
[16/05 22:31:32.411 main]: netceiver: creating DVR pipe for adapter 1  -> dvr: 11
[16/05 22:31:32.411 main]: deleting pids on adapter 1, sid -1, pids=NULL
[16/05 22:31:32.411 main]: netceiver: add a new receiver instance for adapter 1
[16/05 22:31:32.411 main]: clearing type and pat processed for adapter 1
[16/05 22:31:32.411 main]: Mutex init 0x22adc78
[16/05 22:31:32.411 main]: sockets_add: handle 11 (type 5) returning socket index 8 [0.0.0.0:0] read: 0x408552
[16/05 22:31:32.412 main]: set_socket_thread: thread dbfff700 for sockets 8
[16/05 22:31:32.412 main]: pthread_setschedparam failed with error 22
[16/05 22:31:32.412 main]: done opening adapter 1 delivery systems: dvbs2 dvbs undefined undefined
[16/05 22:31:32.412 main]: done init_hw 1
[16/05 22:31:32.412 main]: FE 1 mapped to Adapter 0, sys dvbs2
[16/05 22:31:32.412 main]: FE 2 mapped to Adapter 1, sys dvbs2
[16/05 22:31:32.412 main]: Initializing with 2 devices
[16/05 22:31:32.412 main]: Starting select_and_execute on thread ID ecbd7900, thread_name main
[16/05 22:31:32.412 AD1]: Starting select_and_execute on thread ID dbfff700, thread_name AD1
[16/05 22:31:32.512 main]: ssdp_discovery: bootid: 16 deviceid: 1 http: 192.168.178.11:8080
Which is not bad. The Netceiver has been detected with both tuners ;-)

Any idea how to get them included into easyVDR3.0
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: Using Minisatip with Netceiver

Post by cata »

If easyvdr is vdr, you need to install vdr-plugin-satip.
thowa
Posts: 6
Joined: Mon May 15, 2017 10:50 am

Re: Using Minisatip with Netceiver

Post by thowa »

I have installed the plugin and activated it in vdr.
What comes next?

The "Menu" shows

Code: Select all

0 SAT>IP  not used
1 SAT>IP  not used
2 SAT>IP  not used
3 SAT>IP  not used
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: Using Minisatip with Netceiver

Post by cata »

Hi,

is minisatip and vdr-plugin-satip in the same network ?

Otherwise you can specify the server manually: https://github.com/rofafor/vdr-plugin-s ... ter/README

Thanks
thowa
Posts: 6
Joined: Mon May 15, 2017 10:50 am

Re: Using Minisatip with Netceiver

Post by thowa »

I was playing around with network interfaces and other stuff.
Now I'm again getting:

Code: Select all

root@easyVDR:~# minisatip -n eth1.4:2 -f -l -l -l
[20/05 08:59:20.682 main]: minisatip version 0.7.4, compiled with s2api version: 050A
[20/05 08:59:20.682 main]: Built with dvbcsa
[20/05 08:59:20.682 main]: Built without CI
[20/05 08:59:20.682 main]: Built with dvbapi
[20/05 08:59:20.682 main]: Built with AES (OpenSSL)
[20/05 08:59:20.682 main]: Built with tables processing
[20/05 08:59:20.682 main]: Built with satip client
[20/05 08:59:20.682 main]: Built with linux dvb client
[20/05 08:59:20.682 main]: Built with backtrace
[20/05 08:59:20.682 main]: Built with netceiver
[20/05 08:59:20.682 main]: New UDP socket 3 bound to 0.0.0.0:1900
[20/05 08:59:20.683 main]: setting multicast for 239.255.255.250
[20/05 08:59:20.683 main]: New UDP socket 4 bound to 239.255.255.250:1900
[20/05 08:59:20.683 main]: tcp_listen: failed: bind() on address: ANY, port 554 : error Address already in use
[20/05 08:59:20.683 main]: RTSP: Could not listen on port 554
I already tried

Code: Select all

killall minisatip
without success. I'm still getting the above output.

Network interfaces:

Code: Select all

root@easyVDR:~# ifconfig
eth0      Link encap:Ethernet  Hardware Adresse 00:13:3b:0f:32:4e
          inet Adresse:192.168.178.11  Bcast:192.168.178.255  Maske:255.255.255.0
          inet6-Adresse: fe80::213:3bff:fe0f:324e/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX-Pakete:797 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:619 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX-Bytes:133071 (133.0 KB)  TX-Bytes:166283 (166.2 KB)

eth1      Link encap:Ethernet  Hardware Adresse 2c:4d:54:ea:54:a0
          inet6-Adresse: fe80::2e4d:54ff:feea:54a0/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX-Pakete:677 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:472 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX-Bytes:60930 (60.9 KB)  TX-Bytes:55770 (55.7 KB)

eth1.4    Link encap:Ethernet  Hardware Adresse 2c:4d:54:ea:54:a0
          inet Adresse:10.0.0.1  Bcast:10.0.0.255  Maske:255.255.255.0
          inet6-Adresse: fe80::2e4d:54ff:feea:54a0/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX-Pakete:0 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:96 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX-Bytes:0 (0.0 B)  TX-Bytes:13457 (13.4 KB)

lo        Link encap:Lokale Schleife
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:65536  Metrik:1
          RX-Pakete:361 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:361 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:1
          RX-Bytes:36523 (36.5 KB)  TX-Bytes:36523 (36.5 KB)
What is wrong/missing?

Thanks a lot
thowa
Posts: 6
Joined: Mon May 15, 2017 10:50 am

Re: Using Minisatip with Netceiver

Post by thowa »

I guess ninisatip was still running as service and I assume killall wount stop services right?

Code: Select all

service minisatip stop
solved the problem for me
Post Reply