setting up the server part.

247 views

Skip to first unread message

emmi

unread,

Dec 9, 2011, 4:33:58 AM12/9/11

to vtuner-en-user

Hey, i really need some help, i have tried searching the group and
also the net for at wiki or howto with the server part..
can you please provide us with a wiki/howto guide.
thx

br
/Emmi

Emil Axfors

unread,

Dec 9, 2011, 4:35:28 AM12/9/11

to vtuner-...@googlegroups.com

Me!?
I need help to :)
I have not get it working.
Got 2 DM800C that i want to connect but cant get picture and dont know whats wrong.
Do you got a woring toolchaain and can comile mips?

2011/12/9 emmi <emmi...@gmail.com>

--
Med Vänliga Hälsningar
Emil Axfors

E-post:
em...@axfors.se
Mobiltelefon: 070-4054199

Honza Petrouš

unread,

Dec 9, 2011, 6:42:49 AM12/9/11

to vtuner-...@googlegroups.com

2011/12/9 Emil Axfors <em...@axfors.se>:

> Me!?
> I need help to :)
> I have not get it working.
> Got 2 DM800C that i want to connect but cant get picture and dont know whats
> wrong.
> Do you got a woring toolchaain and can comile mips?
>
>
>
>
> 2011/12/9 emmi <emmi...@gmail.com>
>>
>> Hey, i really need some help, i have tried searching the group and
>> also the net for at wiki or howto with the server part..
>> can you please provide us with a wiki/howto guide.
>> thx

Very simple mini-HOWTO:

Server part is very easy. You have to start vtunerd userland deamon
on server, nothing more.

Currently, there is the only way to change debug level in the server
- use environment variable VTUNERD_DEBUG_LEVEL. The vtunerd
expect zero or n*4 parameters, which 'n' means number of devices.
If no parameters are given, then default variant '1 0 0 0 0' is used
(what means, in ordered occurence: 1=one dvb device, 0=adapter0,
0=frontend0, 0=demux0, 0=dvr0)

So, if you want to use for vtunerd /dev/dvb/adapter1, then the command
like looks like '1 1 0 0 0'. And if you want to get debug level higher, then
you have to start this way "export VTUNERD_DEBUG_LEVEL=4; vtunerd 1 1 0 0 0"

I hope it helps you a bit.

But don't hesitate to ask more

Honza

SnorreDK

unread,

Dec 9, 2011, 6:59:44 AM12/9/11

to vtuner-en-user

OK.
Can you explain more in detail how to setup the serverpart in dm800?
i want to use the org dvb-c tuner in dm800 as server.
How do i know what vtuner x x x x x to choose.

What do you mean with "userland deamon"
Do i need to create a scrip thats kills enigma2 and then starts
vtunerd.
How should it look?
I have really been struggeling with all this for a long time now.

On 9 Dec, 12:42, Honza Petrouš <jpetr...@gmail.com> wrote:
> 2011/12/9 Emil Axfors <e...@axfors.se>:

>
>
>
>
>
>
>
>
>
> > Me!?
> > I need help to :)
> > I have not get it working.
> > Got 2 DM800C that i want to connect but cant get picture and dont know whats
> > wrong.
> > Do you got a woring toolchaain and can comile mips?
>

> > 2011/12/9 emmi <emmice...@gmail.com>

Honza Petrouš

unread,

Dec 9, 2011, 7:26:50 AM12/9/11

to vtuner-...@googlegroups.com

> Can you explain more in detail how to setup the serverpart in dm800?
> i want to use the org dvb-c tuner in dm800 as server.
> How do i know what vtuner x x x x x to choose.

DM800 has only one dvb device (/dev/dvb/adapter0/), so
it could be possible to start it without parameters.
For debug check I recommend to start with debug enabled, so,
if you copy the binary to the /usr/local/bin, then:

export VTUNERD_DEBUG_LEVEL=4; /usr/local/bin/vtunerd.mipsel

Of course, you have to disable enigma2 before.

> What do you mean with "userland deamon"

In two words it is tools running in the background.
More detailed definitions you can find here:
http://en.wikipedia.org/wiki/Daemon_%28computing%29

> Do i need to create a scrip thats kills enigma2 and then starts
> vtunerd.

Exactly.

> How should it look?

May be simpler would be to switch to the different run level
(by init). I can't help you more because I'm not using dreambox
as server.

Onother way can be to modify start_enigma2.sh startup script
(if it occurs in your dreambox image distribution) and add there
some conditional startup - or enigma2 or vtunerd.mipsel

> I have really been struggeling with all this for a long time now.

Show me what did you do exactly and how is output
of your work. Then I can help you more deeply.

Honza

Emmi

unread,

Dec 9, 2011, 8:35:07 AM12/9/11

to vtuner-...@googlegroups.com

I have a question normaly the enigma2 software handles every thing tvtuner sat informations and so on, but if we kill enigma2 and starts vtuner how will it get the different informations

Honza Petrouš

unread,

Dec 9, 2011, 9:05:04 AM12/9/11

to vtuner-...@googlegroups.com

2011/12/9 Emmi <emmi...@gmail.com>:

> I have a question normaly the enigma2 software handles every thing tvtuner sat informations and so on, but if we kill enigma2 and starts vtuner how will it get the different informations

I think you misunderstood how the thing works.

Vtuner is client-server networking project. You have to have
one or more servers (any linux PC with internal DVB PCI card or USB stick
or commercial box like NessieDVB from www.nessiedvb.com)
and one or more clients (any HD dreambox or linux PC desktop).

On server side you have running only vtunerd and on client
side there is DVB application (enigma, vdr, mythtv, ...)
and vtunerc.

Honza

Emmi

unread,

Dec 9, 2011, 9:15:52 AM12/9/11

to vtuner-...@googlegroups.com

Let me se if I have understand you correct server sends the satellite signal to the client that decodes it or?

I thought that the server (in my case a dreambox) streams the channels as a iptv box and client views the channels and switch channel..

Honza Petrouš

unread,

Dec 9, 2011, 9:50:41 AM12/9/11

to vtuner-...@googlegroups.com

2011/12/9 Emmi <emmi...@gmail.com>:

> Let me se if I have understand you correct server sends the satellite signal to the client that decodes it or?
>
> I thought that the server (in my case a dreambox) streams the channels as a iptv box and client views the channels and switch channel..

Server "only" serves his tuner. All necessary (watching tv, zapping,
scanning, recording)
is done on client side. Server is rather "dumb", only provide DVB
adapter (tuner).

Honza

Emmi

unread,

Dec 9, 2011, 11:19:40 AM12/9/11

to vtuner-...@googlegroups.com

So the server that are connected to the satellite sendes det satellite signal over LAN to the other box(client), then acts like it physical connected to the satellite.. Right or?

SnorreDK

unread,

Dec 9, 2011, 11:22:50 AM12/9/11

to vtuner-en-user

ok.
The yellow front diod is on= connected, but no picture.
After gemini5 have booted i put it in stanby and do as follow:

init 3
export VTUNERD_DEBUG_LEVEL=4; /usr/sbin/vtunerd.mipsel

Output of DM800C (server)

root@dm800:/usr/sbin# export VTUNERD_DEBUG_LEVEL=4; /usr/sbin/
vtunerd.mipsel
vtunerd: [1158 ../../vtunerd.c:74] info: S2API tuning support.
vtunerd: [1158 ../../vtuner-dmm-3.c:60] info: FE_GET_INFO dvb-type:1
vtuner-type:2
vtunerd: [1158 ../../vtunerd.c:84] info: adapter:0, frontend:0, demux,
0, dvr:0 is type:2
vtunerd: [1158 ../../vtunerd-service.c:35] debug: autodiscover socket
bound
vtunerd: [1158 ../../vtunerd-service.c:261] info: waiting for
autodiscover packet ...
vtunerd: [1158 ../../vtunerd-service.c:265] debug: request received
vtunerd: [1158 ../../vtunerd.c:99] info: received discover request,
vtuner_type:2
vtunerd: [1158 ../../vtunerd.c:103] debug: session status:0 session
type:2 tuner_type:2 match:1
vtunerd: [1158 ../../vtunerd-service.c:261] info: waiting for
autodiscover packet ...
vtunerd: [1158 ../../vtuner-dmm-3.c:60] info: FE_GET_INFO dvb-type:1
vtuner-type:2
vtunerd: [1158 ../../vtunerd-service.c:67] info: anon stream socket
prepared 6
vtunerd: [1158 ../../vtunerd-service.c:302] info: control socket bound
to 3790
vtunerd: [1158 ../../vtunerd-service.c:67] info: anon stream socket
prepared 7
vtunerd: [1158 ../../vtunerd-service.c:315] info: session prepared
control:3790 data:4047
vtunerd: [1158 ../../vtunerd-service.c:318] debug: Answered discover
request
vtunerd: [1158 ../../vtunerd-service.c:133] debug: tsdata_worker
thread started.
vtunerd: [1158 ../../vtunerd-service.c:82] debug: setsockopt
TCP_NODELAY 1 successful
vtunerd: [1158 ../../vtunerd-service.c:88] debug: setsockopt
SO_KEEPALIVE 1 successful
vtunerd: [1158 ../../vtunerd-service.c:95] debug: setsockopt
TCP_KEEPIDLE 15 successful
vtunerd: [1158 ../../vtunerd-service.c:102] debug: setsockopt
TCP_KEEPCNT 2 successful
vtunerd: [1158 ../../vtunerd-service.c:109] debug: setsockopt
TCP_KEEPINTVL 2 successful
vtunerd: [1158 ../../vtunerd-service.c:345] info: session running
vtunerd: [1158 ../../vtunerd-service.c:350] debug: control message
received
vtunerd: [1158 ../../vtunerd-service.c:350] debug: control message
received
vtunerd: [1158 ../../vtuner-dmm-3.c:234] warn: FE_SET_VOLTAGE failed
vtunerd: [1158 ../../vtunerd-service.c:399] debug: MSG_SET_VOLTAGE:
0x2
vtunerd: [1158 ../../vtunerd-service.c:438] warn: vtuner call failed,
type:9 reason:-1
vtunerd: [1158 ../../vtunerd-service.c:82] debug: setsockopt
TCP_NODELAY 1 successful
vtunerd: [1158 ../../vtunerd-service.c:88] debug: setsockopt
SO_KEEPALIVE 1 successful
vtunerd: [1158 ../../vtunerd-service.c:95] debug: setsockopt
TCP_KEEPIDLE 15 successful
vtunerd: [1158 ../../vtunerd-service.c:102] debug: setsockopt
TCP_KEEPCNT 2 successful
vtunerd: [1158 ../../vtunerd-service.c:109] debug: setsockopt
TCP_KEEPINTVL 2 successful
vtunerd: [1158 ../../vtunerd-service.c:350] debug: control message
received
vtunerd: [1158 ../../vtuner-dmm-3.c:149] info: FE_SET_FRONTEND
parameters: freq:370000000 inversion:1 SR:6875000 FEC:9 MOD:3
vtunerd: [1158 ../../vtunerd-service.c:365] debug: MSG_SET_FRONTEND 0
vtunerd: [1158 ../../vtunerd-service.c:265] debug: request received
vtunerd: [1158 ../../vtunerd.c:99] info: received discover request,
vtuner_type:2
vtunerd: [1158 ../../vtunerd.c:103] debug: session status:1 session
type:2 tuner_type:2 match:1
vtunerd: [1158 ../../vtunerd.c:113] info: No idle device found
vtunerd: [1158 ../../vtunerd-service.c:261] info: waiting for
autodiscover packet ...

On 9 Dec, 15:50, Honza Petrouš <jpetr...@gmail.com> wrote:
> 2011/12/9 Emmi <emmice...@gmail.com>:

Honza Petrouš

unread,

Dec 9, 2011, 11:58:22 AM12/9/11

to vtuner-...@googlegroups.com

2011/12/9 Emmi <emmi...@gmail.com>:

> So the server that are connected to the satellite sendes det satellite signal over LAN to the other box(client), then acts like it physical connected to the satellite.. Right or?
>

Exactly. The main idea is that upper layer application (Enigma in case
of dreambox)
"thinks" the tuner is local and works with him same way like with local tuners.

Honza

Honza Petrouš

unread,

Dec 9, 2011, 12:00:21 PM12/9/11

to vtuner-...@googlegroups.com

2011/12/9 SnorreDK <axf...@gmail.com>:

> ok.
> The yellow front diod is on= connected, but no picture.
> After gemini5 have booted i put it in stanby and do as follow:
>
> init 3
> export VTUNERD_DEBUG_LEVEL=4; /usr/sbin/vtunerd.mipsel
>
> Output of DM800C (server)

Can you check with attached vtunerd binary? I did it from latest sources.

Honza

vtuner_mipsel-latest-111209.tar.gz

SnorreDK

unread,

Dec 9, 2011, 12:16:35 PM12/9/11

to vtuner-en-user

I got % signalsrength at client
The server responds when i chane channel, but still no picture:

vtunerd: [1276 ../../vtuner-network.c:334] debug: 65535
vtunerd: [1276 ../../vtuner-network.c:360] debug:
vtunerd: [1276 ../../vtuner-dmm-3.c:336] debug: hw_pidlist befor: 20
1131 1137 1130 [1276 ../../vtuner-dmm-3.c:338] debug:
vtunerd: [1276 ../../vtuner-dmm-3.c:339] debug: hw_pidlist sent: 1131
1137 1130 [1276 ../../vtuner-dmm-3.c:341] debug:
vtunerd: [1276 ../../vtuner-dmm-3.c:354] warn: DMX_REMOVE_PID 20
failed - Invalid argument
vtunerd: [1276 ../../vtunerd-service.c:361] debug: control message
received
vtunerd: [1276 ../../vtuner-network.c:269] debug: v2/b 768 50331648
vtunerd: [1276 ../../vtuner-network.c:275] debug: 3 3
vtunerd: [1276 ../../vtuner-network.c:312] debug: 31
vtunerd: [1276 ../../vtuner-network.c:360] debug:
vtunerd: [1276 ../../vtunerd-service.c:386] debug: MSG_READ_STATUS:
0x1f
vtunerd: [1276 ../../vtuner-network.c:168] debug: v2/b 3 0
vtunerd: [1276 ../../vtuner-network.c:205] debug: 520093696
vtunerd: [1276 ../../vtuner-network.c:259] debug: 300 0

> vtuner_mipsel-latest-111209.tar.gz
> 47KVisaHämta

SnorreDK

unread,

Dec 9, 2011, 12:25:24 PM12/9/11

to vtuner-en-user

here is all:

vtunerd: [871 ../../vtuner-dmm-3.c:336] debug: hw_pidlist befor: 20 17
1111 1117 1110 [871 ../../vtuner-dmm-3.c:338] debug:
vtunerd: [871 ../../vtuner-dmm-3.c:339] debug: hw_pidlist sent: 20
1111 1117 1110 [871 ../../vtuner-dmm-3.c:341] debug:
vtunerd: [871 ../../vtuner-dmm-3.c:354] warn: DMX_REMOVE_PID 17
failed - Invalid argument
vtunerd: [871 ../../vtunerd-service.c:361] debug: control message
received
vtunerd: [871 ../../vtuner-network.c:269] debug: v2/b 768 50331648
vtunerd: [871 ../../vtuner-network.c:275] debug: 3 3
vtunerd: [871 ../../vtuner-network.c:312] debug: 31
vtunerd: [871 ../../vtuner-network.c:360] debug:
vtunerd: [871 ../../vtunerd-service.c:386] debug: MSG_READ_STATUS:
0x1f
vtunerd: [871 ../../vtuner-network.c:168] debug: v2/b 3 0
vtunerd: [871 ../../vtuner-network.c:205] debug: 520093696
vtunerd: [871 ../../vtuner-network.c:259] debug: 300 0
vtunerd: [871 ../../vtunerd-service.c:361] debug: control message
received
vtunerd: [871 ../../vtuner-network.c:269] debug: v2/b 768 50331648
vtunerd: [871 ../../vtuner-network.c:275] debug: 3 3
vtunerd: [871 ../../vtuner-network.c:312] debug: 31
vtunerd: [871 ../../vtuner-network.c:360] debug:
vtunerd: [871 ../../vtunerd-service.c:386] debug: MSG_READ_STATUS:
0x1f
vtunerd: [871 ../../vtuner-network.c:168] debug: v2/b 3 0
vtunerd: [871 ../../vtuner-network.c:205] debug: 520093696
vtunerd: [871 ../../vtuner-network.c:259] debug: 300 0
vtunerd: [871 ../../vtunerd-service.c:361] debug: control message
received
vtunerd: [871 ../../vtuner-network.c:269] debug: v2/b 768 50331648
vtunerd: [871 ../../vtuner-network.c:275] debug: 3 3
vtunerd: [871 ../../vtuner-network.c:312] debug: 31
vtunerd: [871 ../../vtuner-network.c:360] debug:
vtunerd: [871 ../../vtunerd-service.c:386] debug: MSG_READ_STATUS:
0x1f
vtunerd: [871 ../../vtuner-network.c:168] debug: v2/b 3 0
vtunerd: [871 ../../vtuner-network.c:205] debug: 520093696
vtunerd: [871 ../../vtuner-network.c:259] debug: 300 0
vtunerd: [871 ../../vtunerd-service.c:361] debug: control message
received
vtunerd: [871 ../../vtuner-network.c:269] debug: v2/b 768 50331648
vtunerd: [871 ../../vtuner-network.c:275] debug: 3 3
vtunerd: [871 ../../vtuner-network.c:312] debug: 31
vtunerd: [871 ../../vtuner-network.c:360] debug:
vtunerd: [871 ../../vtunerd-service.c:386] debug: MSG_READ_STATUS:
0x1f
vtunerd: [871 ../../vtuner-network.c:168] debug: v2/b 3 0
vtunerd: [871 ../../vtuner-network.c:205] debug: 520093696
vtunerd: [871 ../../vtuner-network.c:259] debug: 300 0
vtunerd: [871 ../../vtunerd-service.c:361] debug: control message
received
vtunerd: [871 ../../vtuner-network.c:269] debug: v2/b 768 50331648
vtunerd: [871 ../../vtuner-network.c:275] debug: 3 3
vtunerd: [871 ../../vtuner-network.c:312] debug: 31
vtunerd: [871 ../../vtuner-network.c:360] debug:
vtunerd: [871 ../../vtunerd-service.c:386] debug: MSG_READ_STATUS:
0x1f
vtunerd: [871 ../../vtuner-network.c:168] debug: v2/b 3 0
vtunerd: [871 ../../vtuner-network.c:205] debug: 520093696
vtunerd: [871 ../../vtuner-network.c:259] debug: 300 0
vtunerd: [871 ../../vtunerd-service.c:361] debug: control message
received
vtunerd: [871 ../../vtuner-network.c:269] debug: v2/b 768 50331648
vtunerd: [871 ../../vtuner-network.c:275] debug: 3 3
vtunerd: [871 ../../vtuner-network.c:312] debug: 31
vtunerd: [871 ../../vtuner-network.c:360] debug:
vtunerd: [871 ../../vtunerd-service.c:386] debug: MSG_READ_STATUS:
0x1f
vtunerd: [871 ../../vtuner-network.c:168] debug: v2/b 3 0
vtunerd: [871 ../../vtuner-network.c:205] debug: 520093696
vtunerd: [871 ../../vtuner-network.c:259] debug: 300 0
vtunerd: [871 ../../vtunerd-service.c:361] debug: control message
received
vtunerd: [871 ../../vtuner-network.c:269] debug: v2/b 768 50331648
vtunerd: [871 ../../vtuner-network.c:275] debug: 3 3
vtunerd: [871 ../../vtuner-network.c:312] debug: 31
vtunerd: [871 ../../vtuner-network.c:360] debug:
vtunerd: [871 ../../vtunerd-service.c:386] debug: MSG_READ_STATUS:
0x1f
vtunerd: [871 ../../vtuner-network.c:168] debug: v2/b 3 0
vtunerd: [871 ../../vtuner-network.c:205] debug: 520093696
vtunerd: [871 ../../vtuner-network.c:259] debug: 300 0
vtunerd: [871 ../../vtunerd-service.c:361] debug: control message
received
vtunerd: [871 ../../vtuner-network.c:269] debug: v2/b 3584 234881024
vtunerd: [871 ../../vtuner-network.c:275] debug: 14 14
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 1111
vtunerd: [871 ../../vtuner-network.c:334] debug: 1117
vtunerd: [871 ../../vtuner-network.c:334] debug: 1110
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:334] debug: 65535
vtunerd: [871 ../../vtuner-network.c:360] debug:

emrullah celik

unread,

Dec 9, 2011, 1:38:47 PM12/9/11

to vtuner-...@googlegroups.com

Hey SnorreDK,

How did you install the server part..?

I was thinking if you could help me, bcs i dont know how or where to start..

2011/12/9 SnorreDK <axf...@gmail.com>

Emil Axfors

unread,

Dec 9, 2011, 5:12:49 PM12/9/11

to vtuner-...@googlegroups.com

I snorredk am still struggeling and whaiting for response from my last post.

emrullah celik

unread,

Dec 11, 2011, 3:06:50 PM12/11/11

to vtuner-...@googlegroups.com

Hey Sorredk,

did you get it to work,

could you guide me on how to install/setting the server part up? bcs i still dont know how to do it..

2011/12/9 Emil Axfors <em...@axfors.se>

Honza Petrouš

unread,

Dec 11, 2011, 3:12:59 PM12/11/11

to vtuner-...@googlegroups.com

> did you get it to work,
> could you guide me on how to install/setting the server part up? bcs i still
> dont know how to do it..

Server part has no need to be installed. The only 2 steps you have
to do are:

1, kill enigma somehow
Enigma has not to be running, otherwise vtunerd server is not able
to connect to the local tuner.

2, start vtunerd.mipsel from commandline
Vtunerd.mipsel can be started without any parameters, it should fit
well in dm800 environment.

Honza

Emil Axfors

unread,

Dec 11, 2011, 3:15:59 PM12/11/11

to vtuner-...@googlegroups.com

Have you read my output honza?

emrullah celik

unread,

Dec 11, 2011, 3:22:27 PM12/11/11

to vtuner-...@googlegroups.com

What port does it use if im gonna connect over wan

On 11 Dec 2011 21:13, "Honza Petrouš" <jpet...@gmail.com> wrote:

> did you get it to work,

> could you guide me on how to install/setting the server part up? bcs i s...

Honza Petrouš

unread,

Dec 11, 2011, 3:33:44 PM12/11/11

to vtuner-...@googlegroups.com

2011/12/11 Emil Axfors <em...@axfors.se>:

> Have you read my output honza?

Yeas, I did. You have got tuned to the frequency
correctly (MSG_READ_STATUS: 0x1f => 1F means
successfull LOCK) but then I see some PIDs there
= 1110, 1111, 1117 what should be audio/video pids,
but can't see there pid 0, which is necessary for
correct PMT parsing. It is strange.

Can you send me similar log, but most full? I mean
the log from vtunerd.mipsel startup till first "MSG_READ_STATUS:
0x1f".

Honza

emrullah celik

unread,

Dec 11, 2011, 3:48:14 PM12/11/11

to vtuner-...@googlegroups.com

hey Honzo,

is it possible to connect over wan.. if so what port does it use..

2011/12/11 Honza Petrouš <jpet...@gmail.com>

Honza Petrouš

unread,

Dec 11, 2011, 4:00:37 PM12/11/11

to vtuner-...@googlegroups.com

> hey Honzo,
>
> is it possible to connect over wan.. if so what port does it use..

The protocol, esspecially port assignement part, is not designed
for WAN usability because both two TCP ports are set
dynamically. But, in general, you can use direct IP/hostname
option (-n) on client side and if you are able to forward all TCP
connections from client to the internet, then it can work for you.

Of course there (in vtunerd part) can be added some option
which instruct vtunerd to use all time the same TCP pairs
(the connection between client and server consist of 2 TCP
connections - one for managemment connection and one
for transport stream data connection). But this is very low
on my TODO list. I don't think it can work smoothly on WAN.

Honza

emrullah celik

unread,

Dec 11, 2011, 4:10:26 PM12/11/11

to vtuner-...@googlegroups.com

but if i port forward all ports on my router ill then be open for attack..

port forward the client or the server..`?

2011/12/11 Honza Petrouš <jpet...@gmail.com>

emrullah celik

unread,

Dec 11, 2011, 4:18:52 PM12/11/11

to vtuner-...@googlegroups.com

is there a way to see what port that are assign for the program..?

2011/12/11 emrullah celik <emmi...@gmail.com>

SnorreDK

unread,

Dec 11, 2011, 4:39:39 PM12/11/11

to vtuner-en-user

try vpn..

On 11 Dec, 22:10, emrullah celik <emmice...@gmail.com> wrote:
> but if i port forward all ports on my router ill then be open for attack..
> port forward the client or the server..`?
>

> 2011/12/11 Honza Petrouš <jpetr...@gmail.com>

Emil Axfors

unread,

Dec 11, 2011, 4:43:09 PM12/11/11

to vtuner-...@googlegroups.com

**************************
*                        *
*   The Gemini Project   *
*                        *
**************************

OpenDreambox 5.0.0 dm800

dm800 login: root
root@dm800:~# init 3
root@dm800:~# init 4
root@dm800:~# export VTUNERD_DEBUG_LEVEL=4; /usr/sbin/vtunerd.mipsel
vtunerd: [856 ../../vtunerd.c:87] info: S2API tuning support.
vtunerd: [856 ../../vtuner-dmm-3.c:60] info: FE_GET_INFO dvb-type:1 vtuner-type:2
vtunerd: [856 ../../vtunerd.c:97] info: adapter:0, frontend:0, demux,0, dvr:0 is type:2
vtunerd: [856 ../../vtunerd-service.c:36] debug: autodiscover socket bound
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:0 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-dmm-3.c:60] info: FE_GET_INFO dvb-type:1 vtuner-type:2
vtunerd: [856 ../../vtunerd-service.c:68] info: anon stream socket prepared 6
vtunerd: [856 ../../vtunerd-service.c:313] info: control socket bound to 3090
vtunerd: [856 ../../vtunerd-service.c:68] info: anon stream socket prepared 7
vtunerd: [856 ../../vtunerd-service.c:326] info: session prepared control:3090 data:3478
vtunerd: [856 ../../vtuner-network.c:168] debug: v0/0 1025 0
vtunerd: [856 ../../vtuner-network.c:259] debug: 104 0
vtunerd: [856 ../../vtunerd-service.c:329] debug: Answered discover request
vtunerd: [856 ../../vtunerd-service.c:134] debug: tsdata_worker thread started.
vtunerd: [856 ../../vtunerd-service.c:83] debug: setsockopt TCP_NODELAY 1 successful
vtunerd: [856 ../../vtunerd-service.c:89] debug: setsockopt SO_KEEPALIVE 1 successful
vtunerd: [856 ../../vtunerd-service.c:96] debug: setsockopt TCP_KEEPIDLE 15 successful
vtunerd: [856 ../../vtunerd-service.c:103] debug: setsockopt TCP_KEEPCNT 2 successful
vtunerd: [856 ../../vtunerd-service.c:110] debug: setsockopt TCP_KEEPINTVL 2 successful
vtunerd: [856 ../../vtunerd-service.c:356] info: session running
vtunerd: [856 ../../vtunerd-service.c:361] debug: control message received
vtunerd: [856 ../../vtunerd-service.c:479] debug: wait for TS data copy thread to terminate
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v2/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0001)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received (group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115] debug: session status:1 session type:2 tuner_type:2 match:1
vtunerd: [856 ../../vtunerd.c:125] info: No idle device found
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for autodiscover packet (groups 0xFFFFFFFF) ...

2011/12/11 Honza Petrouš <jpet...@gmail.com>

--
Med Vänliga Hälsningar
Emil Axfors

E-post:
em...@axfors.se
Mobiltelefon: 070-4054199

SnorreDK

unread,

Dec 11, 2011, 4:44:51 PM12/11/11

to vtuner-en-user

**************************
* *
* The Gemini Project *
* *
**************************

OpenDreambox 5.0.0 dm800

dm800 login: root
root@dm800:~# init 3
root@dm800:~# init 4
root@dm800:~# export VTUNERD_DEBUG_LEVEL=4; /usr/sbin/vtunerd.mipsel

vtunerd: [856 ../../vtunerd.c:87] info: S2API tuning support.
vtunerd: [856 ../../vtuner-dmm-3.c:60] info: FE_GET_INFO dvb-type:1
vtuner-type:2
vtunerd: [856 ../../vtunerd.c:97] info: adapter:0, frontend:0, demux,

0, dvr:0 is type:2

vtunerd: [856 ../../vtunerd-service.c:36] debug: autodiscover socket
bound
vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for

autodiscover packet (groups 0xFFFFFFFF) ...
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received
(group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request
proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115]

debug: session status:0 session type:2 tuner_type:2 match:1

vtunerd: [856 ../../vtunerd-service.c:263] info: waiting for

autodiscover packet (groups 0xFFFFFFFF) ...

vtunerd: [856 ../../vtuner-dmm-3.c:60] info: FE_GET_INFO dvb-type:1
vtuner-type:2
vtunerd: [856 ../../vtunerd-service.c:68] info: anon stream socket
prepared 6
vtunerd: [856 ../../vtunerd-service.c:313] info: control socket bound
to 3090
vtunerd: [856 ../../vtunerd-service.c:68] info: anon stream socket
prepared 7

vtunerd: [856 ../../vtunerd-service.c:326] info: session prepared
control:3090 data:3478
vtunerd: [856 ../../vtuner-network.c:168] debug: v0/0 1025 0
vtunerd: [856 ../../vtuner-network.c:259] debug: 104 0

vtunerd: [856 ../../vtunerd-service.c:329] debug: Answered discover
request
vtunerd: [856 ../../vtunerd-service.c:134] debug: tsdata_worker thread
started.
vtunerd: [856 ../../vtunerd-service.c:83] debug: setsockopt
TCP_NODELAY 1 successful
vtunerd: [856 ../../vtunerd-service.c:89] debug: setsockopt
SO_KEEPALIVE 1 successful
vtunerd: [856 ../../vtunerd-service.c:96] debug: setsockopt
TCP_KEEPIDLE 15 successful
vtunerd: [856 ../../vtunerd-service.c:103] debug: setsockopt
TCP_KEEPCNT 2 successful
vtunerd: [856 ../../vtunerd-service.c:110] debug: setsockopt
TCP_KEEPINTVL 2 successful

vtunerd: [856 ../../vtunerd-service.c:356] info: session running

vtunerd: [856 ../../vtunerd-service.c:361] debug: control message
received

vtunerd: [856 ../../vtunerd-service.c:479] debug: wait for TS data
copy thread to terminate
vtunerd: [856 ../../vtuner-network.c:269] debug: v0/0 260 33554432
vtunerd: [856 ../../vtuner-network.c:275] debug: 1025 33554432
vtunerd: [856 ../../vtuner-network.c:360] debug:
vtunerd: [856 ../../vtunerd-service.c:277] debug: request received
(group 0x0000)
vtunerd: [856 ../../vtunerd.c:111] info: received discover request
proto2, vtuner_type:2 group:0xFFFFFFFF
vtunerd: [856 ../../vtunerd.c:115] debug: [856 ../../vtunerd.c:115]