Opened 12 years ago

Closed 12 years ago

#2269 closed defect (invalid)

Clients stops online

Reported by: Tasiorsa Owned by:
Priority: critical Component: Protocol - CCCam
Severity: high Keywords:
Cc: Sensitive: yes

Description

Revision

6080 till latest (6145). 6078 works perfectly as CCcam Server/Client. On 6078 version peers can watch from my server all of the day and nothing wrong happend

Issue Description

DM 8000
Flash Release 3.2.1
On USB tested On Release 3.2.1@GP3 and latest Newnigma Image
Client watch one channel from my Oscam server on CCcam protocol. After 230-320 ecms hops to other CCcam server with same card as mine. Other server stay on original CCcam 2.2.1.
Client doesn't loose any ecms. Client suddenly jump to other server.

When the issue occurs

Always after 58-63 minutes ~230-320 ecms. Tested on Connax & Seca Card

In log nothing wrong happend. I see that peer stops online and doesn't catch ecms from my server. I don't see any errors or sth like this

Change History (16)

comment:1 by Tasiorsa, 12 years ago

Today i've made a test with latest experimental (10 Jan 2012) + GP3. All Oscams versions after #6078 kills active clients after 56-57 min "Time On Channel". I tried latest 6226/6221/6208/6087. Finally revert to #6078 and nothing wrong happened. I see "Time on Channel" 1h 41 min at this moment. Something is wrong after cccam fix in #6079. Could someone check where DM 8000 probably has a problem? It's very important because all versions after #6078 are completly unused for me.

comment:2 by Tasiorsa, 12 years ago

One more test. On DM 8000 my friend run Oscam server at CCcam protokol with Cyfra card (Id 0100:000068). After 56-57 min "Time On Channel" clients stops online and hop to other CCcam server with same card. I've made a test on DM 800. On DM 800 all works properly. So please review DM 8000 & Oscam problem.

comment:3 by raiuno, 12 years ago

I've got the same problem. I think it only concerns Dreamboxes 8000. My friend has a DM 800 and does not observe this problem. Regards.

comment:4 by Admin, 12 years ago

Well as r6080 just cleaned some compiler warnings, it must be r6079. From there it can only be either the change in module-cccam.c or the one in oscam.c. Can anyone with a dm8000 who can compile try which one of the both is the reason?

Are the really disconnected or do they just request another (faster?) cccam server? Is there a log from the client side? What happens if the client is an oscam client?

Normally, there should be no major difference between dm800 and dm8000...only the libraries in the images will probably differ.

comment:5 by raiuno, 12 years ago

I assumed that the problem begins with r6081 because on http://download.oscam.to/index.php?&direction=0&order=mod&directory=mips-tuxbox there was r6078 and then only r6081 (versions 6079-6080 were not compiled). On r6081 the problem occurs after 57 min. The log does not have any mention of the client being disconnected. The client simply makes use of another server. They don't lose any ecms. On the client's side, there's no info in the log about disconnection or anything. It looks as if the requests were switched to a faster server (but why after 56/57 minutes???) I think it may be the total online time of the client. For example, if a client watches one channel for 26 minutes and another channel for 30 minutes and then goes to another channel, they will be disconnected anyway because the total 56/57 minutes are used. When a client uses oscam as cccam, then the requests do not switch to another server after 56/57 minutes, but there is a stop in requests for a while (it can be seen in active clients) and then the client restarts sending requests. I have no idea whether the client experiences freezes then or not. I have no means to check it. This is what I observe.

comment:6 by Tasiorsa, 12 years ago

Oscam #6264 still no changes :(

comment:7 by Tasiorsa, 12 years ago

I've made one more test. On debian x64 oscam #6323 works perfectly. On DM 8000 still hops after 57 min :( Any idea? It's very disappointed :(

comment:8 by Tasiorsa, 12 years ago

Oscam #6445 still hops to other CCcam server after 59 minutes on DM 8000 :(

comment:9 by Deas, 12 years ago

Resolution: invalid
Status: newclosed

try another image on dm8000

comment:10 by Tasiorsa, 12 years ago

It happened on all image. I've tested Newnigma2, ICVS+GP3, OpenPli. Two my friends with DM 8000 has same problem as me. 57-61 min max and hops to other server. It happend without any info in debug file. Just stops online. We were tested with Seca 0100:0068 and 0b00 card

comment:11 by Tasiorsa, 12 years ago

Resolution: invalid
Status: closedreopened

I've tested with latest Oscam 7182 and still same problem. CCcam clients hops to CCcam server when Time On Channel >56 - 57 min. It happend always on DM 8000. I 've tried GP3 with latest Release 1.6 3.2.3 & with latest Newnigma. Same situation is with image on OE 2.0 (kernel 3.2.22). It works perfectly till 56-57 min. Latest version which doesn't hops still is #6078. It Happend on 3 dreambox 8000 with Seca card and Connax too. Please don't close this ticket and try to fix this. The cards are in internal reader. I've tested difrent Mhz & CardMhz and nothing changed. Always client online 56- 57 min

Last edited 12 years ago by Tasiorsa (previous) (diff)

comment:12 by ni hao, 12 years ago

no problems here (so peers do not stop and rcv ECMs) with original DMM image (OE2.0) and also ok with OoZooN image (OE2.0), using oscam build svn-7182. Try other clean images.

comment:13 by theparasol, 12 years ago

First of all: post your configs en logs, in the forum. There must be something wrong with it. If this was a common issue we would be getting much more tickets!

comment:14 by Tasiorsa, 12 years ago

Strange I've made one more test. With oscam 7184 again works properly - Doesen't hops after 56-57 min - I can watch 4h and all is ok - but strange show cards in hop. But In latest version 7187 again hops after 56-57 min. So this is not my fault! I haven't got any mistake in conf!

comment:15 by theparasol, 12 years ago

For sure misconfig, right configurated oscam systems have all problems with 7184.
No logs, no reader configs -> invalid and close!

comment:16 by theparasol, 12 years ago

Resolution: invalid
Status: reopenedclosed
Note: See TracTickets for help on using tickets.