Вход в биллинг - Billing entrance - www.CardsharingServer.com

English forum section

Последние сообщения

Страницы: [1] 2 3 4 5 6 ... 10
1
Canal Digital Finland / Re: Missing chanels on canal digital nordic
« Последний ответ от tomzza 24 Мая 2019, 20:16:09 »
Here log Eurosport 1 HD (F)

0.8°W Channelname: Eurosport 1 HD (F) 1_0_19_1B66_42_46_E080000_0_0_0 frequency:10778  symbolrate:25000 SID: 1B66 (7014d)

freezetime 19.59.33

May 24 19:59:16 192.168.1.3 000: 80 70 85 70 7e 63 30 4d c4 e0 52 c5 bd 2f cd a5  .p.p.c0M..R../..
May 24 19:59:16 192.168.1.3 010: 33 c5 30 52 a3 08 ce bc 8c f7 c9 be 49 a6 82 fc  3.0R........I...
May 24 19:59:16 192.168.1.3 020: f0 4a ee 88 10 95 63 2d 32 d0 3d 92 0f 3b 18 9f  .J....c-2.=..;..
May 24 19:59:16 192.168.1.3 030: 4f 7a 6b 2d d9 1a 1b 6a cb 0d 66 6d 8d a7 79 3a  Ozk-...j..fm..y:
May 24 19:59:16 192.168.1.3 040: 0a 51 6f 0a 5b 92 c7 4a 5e bc 4a 76 18 4b f6 57  .Qo.[..J^.Jv.K.W
May 24 19:59:16 192.168.1.3 050: 97 02 02 19 6a 51 d5 09 14 20 b7 26 3b 54 b9 0a  ....jQ... .&;T..
May 24 19:59:16 192.168.1.3 060: 47 fd 33 bd 02 75 76 86 82 5a e0 b9 21 6e f0 22  G.3..uv..Z..!n."
 
May 24 19:59:19 192.168.1.3 
May 24 19:59:19 192.168.1.3 [mg0] <- CW from newcamd server_74:xxxxx (3594ms)
May 24 19:59:19 192.168.1.3 [mg0] 3594 msec -- Fri May 24 19:59:22 2019
May 24 19:59:19 192.168.1.3 ===== Conax ECM on CaID 0x0B00, pid 0x1c40 ======
May 24 19:59:19 192.168.1.3 prov: 000000
May 24 19:59:19 192.168.1.3 cw0:0 B8 0A 61 23 A8 42 23 0D
May 24 19:59:19 192.168.1.3 cw1:0 84 FF 0F 92 38 BC F2 E6
May 24 19:59:26 192.168.1.3  ECM to newcamd server_74:xxxxx
May 24 19:59:26 192.168.1.3  Server: -- Fri May 24 19:59:29 2019
May 24 19:59:26 192.168.1.3 ----------------------------------------------------
May 24 19:59:26 192.168.1.3 000: 81 70 85 70 7e 63 30 71 2b 68 38 ee d9 a6 35 06  .p.p.c0q+h8...5.
May 24 19:59:26 192.168.1.3 010: 2b 77 58 a4 af 7d 3a d3 74 f3 b6 52 ed 96 5c 31  +wX...:.t..R..\1
May 24 19:59:26 192.168.1.3 020: d3 67 5e 9e 37 85 64 2e 95 5c 43 27 2e e1 85 91  .g^.7.d..\C'....
May 24 19:59:26 192.168.1.3 030: 46 64 4c 76 61 fc 48 cd 73 58 67 8d c4 12 75 97  FdLva.H.sXg...u.
May 24 19:59:26 192.168.1.3 040: d9 be 39 6f 73 83 7c 1b cb 89 db 67 eb 0a 49 f9  ..9os......g..I.
May 24 19:59:26 192.168.1.3 050: 48 71 e7 16 08 74 05 e4 9a 99 06 5a 7f bd a9 31  Hq...t.....Z...1
May 24 19:59:26 192.168.1.3 060: 8f 64 2d 78 1e 43 93 09 f1 a4 78 96 57 70 d6 15  .d-x.C....x.Wp..
May 24 19:59:26 192.168.1.3 070: 23 2c e6 29 37 94 ff 00 5e fb 28 2a 08 33 87 2e  #,.)7...^.(*.3..
May 24 19:59:26 192.168.1.3 080: 2b f1 bc 02 03 50 02 00                           +....P..
May 24 19:59:26 192.168.1.3 
May 24 19:59:33 192.168.1.3  ECM to newcamd server_74:xxxxx
May 24 19:59:33 192.168.1.3  Server: -- Fri May 24 19:59:36 2019
May 24 19:59:33 192.168.1.3 ----------------------------------------------------
May 24 19:59:33 192.168.1.3 000: 81 70 85 70 7e 63 30 71 2b 68 38 ee d9 a6 35 06  .p.p.c0q+h8...5.
May 24 19:59:33 192.168.1.3 010: 2b 77 58 a4 af 7d 3a d3 74 f3 b6 52 ed 96 5c 31  +wX...:.t..R..\1
May 24 19:59:33 192.168.1.3 020: d3 67 5e 9e 37 85 64 2e 95 5c 43 27 2e e1 85 91  .g^.7.d..\C'....
May 24 19:59:33 192.168.1.3 030: 46 64 4c 76 61 fc 48 cd 73 58 67 8d c4 12 75 97  FdLva.H.sXg...u.
May 24 19:59:33 192.168.1.3 040: d9 be 39 6f 73 83 7c 1b cb 89 db 67 eb 0a 49 f9  ..9os......g..I.
May 24 19:59:33 192.168.1.3 050: 48 71 e7 16 08 74 05 e4 9a 99 06 5a 7f bd a9 31  Hq...t.....Z...1
May 24 19:59:33 192.168.1.3 060: 8f 64 2d 78 1e 43 93 09 f1 a4 78 96 57 70 d6 15  .d-x.C....x.Wp..
May 24 19:59:33 192.168.1.3 070: 23 2c e6 29 37 94 ff 00 5e fb 28 2a 08 33 87 2e  #,.)7...^.(*.3..
May 24 19:59:33 192.168.1.3 080: 2b f1 bc 02 03 50 02 00                           +....P..
May 24 19:59:33 192.168.1.3 
May 24 19:59:35 192.168.1.3 Client <- Server: -- Fri May 24 19:59:38 2019
May 24 19:59:35 192.168.1.3 ----------------------------------------------------
May 24 19:59:35 192.168.1.3 000: 81 00 00                                          ...
May 24 19:59:35 192.168.1.3 
May 24 19:59:35 192.168.1.3 [mg0] newcamd route server_74:xxxxx cant decode (1576ms)
May 24 19:59:35 192.168.1.3 [mg0] network can't decode
May 24 19:59:35 192.168.1.3 [mg0] pid 0x1C40 failed to decode.
May 24 19:59:35 192.168.1.3 Client <- Server: -- Fri May 24 19:59:38 2019
May 24 19:59:35 192.168.1.3 ----------------------------------------------------
May 24 19:59:35 192.168.1.3 000: 81 00 00                                          ...
May 24 19:59:35 192.168.1.3 
May 24 19:59:35 192.168.1.3 [mg0] newcamd route server_74:xxxxx cant decode (1576ms)
May 24 19:59:36 192.168.1.3  ECM to newcamd server_74:xxxxx
May 24 19:59:36 192.168.1.3  Server: -- Fri May 24 19:59:39 2019
May 24 19:59:36 192.168.1.3 ----------------------------------------------------
May 24 19:59:36 192.168.1.3 000: 81 70 85 70 7e 63 30 71 2b 68 38 ee d9 a6 35 06  .p.p.c0q+h8...5.
May 24 19:59:36 192.168.1.3 010: 2b 77 58 a4 af 7d 3a d3 74 f3 b6 52 ed 96 5c 31  +wX...:.t..R..\1
May 24 19:59:36 192.168.1.3 020: d3 67 5e 9e 37 85 64 2e 95 5c 43 27 2e e1 85 91  .g^.7.d..\C'....
May 24 19:59:36 192.168.1.3 030: 46 64 4c 76 61 fc 48 cd 73 58 67 8d c4 12 75 97  FdLva.H.sXg...u.
May 24 19:59:36 192.168.1.3 040: d9 be 39 6f 73 83 7c 1b cb 89 db 67 eb 0a 49 f9  ..9os......g..I.
May 24 19:59:36 192.168.1.3 050: 48 71 e7 16 08 74 05 e4 9a 99 06 5a 7f bd a9 31  Hq...t.....Z...1
May 24 19:59:36 192.168.1.3 060: 8f 64 2d 78 1e 43 93 09 f1 a4 78 96 57 70 d6 15  .d-x.C....x.Wp..
May 24 19:59:36 192.168.1.3 070: 23 2c e6 29 37 94 ff 00 5e fb 28 2a 08 33 87 2e  #,.)7...^.(*.3..
May 24 19:59:36 192.168.1.3 080: 2b f1 bc 02 03 50 02 00                           +....P..
May 24 19:59:36 192.168.1.3 
May 24 19:59:36 192.168.1.3 Client <- Server: -- Fri May 24 19:59:39 2019
May 24 19:59:36 192.168.1.3 ----------------------------------------------------
May 24 19:59:36 192.168.1.3 000: 81 00 00                                          ...
May 24 19:59:36 192.168.1.3 
May 24 19:59:36 192.168.1.3 [mg0] newcamd route server_74:xxxxx cant decode (51ms)
May 24 19:59:37 192.168.1.3  ECM to newcamd server_74:xxxxx
May 24 19:59:37 192.168.1.3  Server: -- Fri May 24 19:59:40 2019
May 24 19:59:37 192.168.1.3 ----------------------------------------------------
May 24 19:59:37 192.168.1.3 000: 80 70 85 70 7e 63 30 15 43 3d 5e b5 b8 b3 a8 e6  .p.p.c0.C=^.....
May 24 19:59:37 192.168.1.3 010: d7 60 90 ab 55 ed 8e e9 9f 04 46 65 f3 49 fd 45  .`..U.....Fe.I.E
May 24 19:59:37 192.168.1.3 020: 7b af f5 03 9d 78 c8 77 64 99 74 d5 d4 3f e6 42  {....x.wd.t..?.B
May 24 19:59:37 192.168.1.3 030: 75 19 0a a2 0d 56 57 02 ac 96 69 a9 1e 13 57 71  u....VW...i...Wq
May 24 19:59:37 192.168.1.3 040: fb cd 00 83 3c 63 7e 08 0e 8b 93 56 8f af d0 c8  ....<c.....V....
May 24 19:59:37 192.168.1.3 050: 05 43 f1 a5 d2 86 ff ca 7a 2c 74 da 75 30 09 32  .C......z,t.u0.2
May 24 19:59:37 192.168.1.3 060: cd de e0 b1 50 82 d7 37 be 41 ca cb dd dc 3c 28  ....P..7.A....<(
May 24 19:59:37 192.168.1.3 070: a1 fd 25 5a da 48 50 80 c1 74 75 f6 f8 67 82 81  ..%Z.HP..tu..g..
May 24 19:59:37 192.168.1.3 080: 0d 89 32 02 03 50 02 00                           ..2..P..
May 24 19:59:37 192.168.1.3 
May 24 19:59:39 192.168.1.3 Client <- Server: -- Fri May 24 19:59:42 2019
May 24 19:59:39 192.168.1.3 ----------------------------------------------------
May 24 19:59:39 192.168.1.3 ..._...2.5vw
May 24 19:59:39 192.168.1.3 010: c1 29 61                                          .)a
May 24 19:59:39 192.168.1.3 
May 24 19:59:39 192.168.1.3 [mg0] <- CW from newcamd server_74:xxxxx (2618ms)
May 24 19:59:39 192.168.1.3  [mg0] WARNING, both cws changed !
May 24 19:59:39 192.168.1.3 [mg0] 2618 msec -- Fri May 24 19:59:42 2019
May 24 19:59:39 192.168.1.3 ===== Conax ECM on CaID 0x0B00, pid 0x1c40 ======
May 24 19:59:39 192.168.1.3 prov: 000000
May 24 19:59:39 192.168.1.3 cw0:0 3E D3 9B AC 5F 9F 07 05
May 24 19:59:39 192.168.1.3 cw1:0 32 0F 35 76 77 C1 29 61
May 24 19:59:46 192.168.1.3  ECM to newcamd server_74:xxxxx
May 24 19:59:46 192.168.1.3  Server: -- Fri May 24 19:59:49 2019
May 24 19:59:46 192.168.1.3 ----------------------------------------------------
May 24 19:59:46 192.168.1.3 000: 81 70 85 70 7e 63 30 4e 88 f5 aa 07 e6 c0 5d f0  .p.p.c0N......].
May 24 19:59:46 192.168.1.3 010: 62 b8 a8 04 84 47 f4 e0 db 29 50 43 26 0b 8e 7d  b....G...)PC&...
May 24 19:59:46 192.168.1.3 020: 79 e7 f5 d1 1e a8 fc 47 2f ec 70 15 d3 76 cf b7  y......G/.p..v..
May 24 19:59:46 192.168.1.3 030: d1 dd 61 84 23 52 f6 88 4f 4d 4e ab cf b5 9b 62  ..a.#R..OMN....b
May 24 19:59:46 192.168.1.3 040: 53 f8 f9 42 a8 7b 0c b1 61 13 f2 94 e8 12 b2 bf  S..B.{..a.......
May 24 19:59:46 192.168.1.3 050: b6 d8 c2 58 df 8f 71 1b c0 25 f4 8d 80 77 cf bf  ...X..q..%...w..
May 24 19:59:46 192.168.1.3 060: 4c 6b 01 0d f6 34 ff 61 31 88 4f 63 00 a9 11 ff  Lk...4.a1.Oc....
May 24 19:59:46 192.168.1.3 070: f8 f4 6e e4 2c 44 01 dd 41 0c d1 58 d7 e0 b7 5f  ..n.,D..A..X..._
May 24 19:59:46 192.168.1.3 080: a8 16 0c 02 03 50 02 00                           .....P..



others channels works fine decode time n 450ms.
2
OSCam / Re: Violations: Number of requests above the limit
« Последний ответ от Jogi 23 Мая 2019, 18:27:20 »
I am using Neutrino on a ARM-based receiver: no CCcam-version available for this box type
3
OSCam / Re: Violations: Number of requests above the limit
« Последний ответ от suma 23 Мая 2019, 07:31:05 »
As Moderator suggests, try cccam 2.3.2_ de (available on the forum). As he thinks, Oscam is not ideal solution and also has bugs.
4
OSCam / Re: Violations: Number of requests above the limit
« Последний ответ от Jogi 21 Мая 2019, 17:38:51 »
Hello suma,

thanks for the reply. Starting with the easiest question:
NO, the STB is connected via LAN cable
I use a cable internet connection. Of course also this reconnects from time to time, but... perhaps once a month. Other "delays" of my provider (with still established connection, no renew of ip or anything) are at least not noticed by me and typical internet usage.

I have no idea why my receiver might send 3-4 requests on the same SID. As it sounds to be "usual 2-3 times a week": might this happen at night, 2:00am when the server is restarting (I believe, its usual that a 2:00am every day the picture freeze for about 1-2 minutes and its always 2:00am so something happening on purpose for sure and a reader restart during the night... not necessary for the user but if it helps to run stable of course accepted. During the week I do not watch TV at 2:00am CET (or might have felt asleep with running receiver)  but Friday and Saturday that's normal *g*. My Oscam might store unsuccessful requests and send them again.
Especially on the same SID: even if using PiP or recording the same channel, Oscam should not request the same codeword if it is already delivered once by the server. "Pause" function (timeshift) would do nothing else - the picture freeze using "Pause" and got recorded on the HDD so ECMs should be send as usually. My STB does not record scrambled streams and try to decode afterwords, so delayed decoding should not appear. If a picture is not decoded my recever records a file with 0 bytes regardless how long the record time was set.

DW lifetime means decoding-word lifetime ?
In my oscam.conf I have configured
[cache]
max_time = 20
this should be the time Oscam holds a received codeword (not sure if "usual"/default (at least its written in the file so most likely no default value) but in this case it is sure that recording or PiP might send the same request again and as we are talking about bytes on the RAM of my receiver... but I will reduce this value (as we know: after 7 seconds the decrypted codeword is useless anyway).

But at least I can say, that PiP or recordings are not really typical and I don't think I have used either once of it while the problem occur. At least ot the last time, when I decoded to create a thread for this behavior and not be able to fix it with rate-limit configuration.

Basically I am taking, that I do not have to worry at the moment.
Perhaps you can continue to have an eye on this during the next days, otherwise I will contact you via this thread again if I get additional warnings.
5
OSCam / Re: Violations: Number of requests above the limit
« Последний ответ от suma 21 Мая 2019, 07:22:06 »
In the log, we see that 2-3 times a week, 10-15 requests filtered for SkyDE come to the server. It's not so terrific. Server does not ban for this.
The question is - why 3-4 different requests come to the same SID over 7 seconds (DW lifetime)?   
Either he is using "pause" from his remote, or... we don't know.   
Briefly speaking, CW for SkyDe comes from the satellite strictly every 7 seconds. He managed to send different requests... 
It looks like some delay. Maybe, there is no internet connection for some time (on a regular basis), requests are "held" somewhere pending. Later on, when internet connection appears again, a "batch" of requests comes to the server at a time.  It's one of the versions we have. 
Maybe, he is using WiFi..., it's another reason.
6
Canal Digital Finland / Re: Missing chanels on canal digital nordic
« Последний ответ от suma 20 Мая 2019, 06:27:44 »
Problem Eurosport 1 HD (F)

Log-file is required and full parameters of the channel (satellite, frequency, etc)


C more Sport 2 HD finnish Channels.

C More is not shared regardless of provider. Forget
7
Canal Digital Finland / Re: Missing chanels on canal digital nordic
« Последний ответ от tomzza 19 Мая 2019, 14:26:58 »
Hi Suma!
Problem Eurosport 1 HD (F) and C more Sport 2 HD finnish Channels.

Small correction only C more live 1hd - 5 hd channels they are Sweden ppv channels  protected from sharing, overcrypt. not work.  (Sport Channels]

And C more Stars HD, C more First HD, C more Hits HD, C more Series are Nordic  Channels, (Finnish + Swedish + Norwegian. Danish) Movies and series channel. Still working perfect.

C More Max HD, C More Sport  1 HD, C More Sport 2 HD are Finnish package and working well, But C More Sport 2 HD It is longer than normal ecm time n. 2-3  seconds then  over 5 seconds ecm picture  freeze for a moment then continue, can work for a long time before freeze again over 10 min. Other channels: C More Max HD and C More Sport 1 HD  ecm time under 0.5 sec they work perfect.

Maybe C More Sport 2 Hd ( 1:0:19:1C12:1:46:E080000:0:0:0: 11247mhz V 24500 ) use Danish  card because, A few weeks ago when switching from SD to HD channel sd channel work perfect and Now hd channel are old Danish on the frequency C more Sport 2 work but normal longer ecm Sometimes it freezes. Can try FiX???

And. Eurosport 1
Eurosport 1 HD  change frequency 5.12.2019 Now, divided into 4 channel
Eurosport 1 HD (N) 10809, H 25000  (Norway Works perfect low ecm under 0.5 sec )
Eurosport 1 HD (S) 10809, H 25000 (Sweden Works perfect low ecm under 0.5 sec )
Eurosport 1 HD (D) 10778, H 25000 (Danish1:0:19:1C45:42:46:E080000:0:0:0:  normal longer ecm over2.5 sec,Freeze random picture) 
Eurosport 1 HD (F)  10778, H 25000 (Finland) 1:0:19:1B66:42:46:E080000:0:0:0: behavior when same ecm Danish.

Eurosport 1 HD (F)  before that name Eurosport 1 (D)  (Danish channel) old channel same frequency.
I'm pretty sure that the new Eurosport 1 HD (F) Use  Danish card not Finnish card ecm times are identical. (over 2.5sec) Probably only need change Channel Finland card
Can try Fixit?

And..
Eurosport 2 HD 5.12.2019 Now, divided into 2 channel:
Eurosport 2 HD (D), Danish work 2.5sec ecm freezen (i know not fully guaranteed)
Eurosport 2 HD (S/F) sweden and finland low ecm time works perfect.

But if you need mgcamd 1.35A log Suma, i can try to put it.
Thank you, keep up the good work!
Sorry for the long text and not good English :D
8
OSCam / Violations: Number of requests above the limit
« Последний ответ от Jogi 18 Мая 2019, 10:48:50 »
several times like this morning I recognized information in my connection history that shows a box on the right site "Violations: Number of requests above the limit per 10 18 seconds" (the 2nd number, here 18, varies - I do not really understand what it says/how this is calculated, but the values stays for the day or might rise if another decoding problem appear).
In addition in the box "Requests" I can see (today)   Requests rejected  21  + Delayed decoding 18

OK, on the top it said in the green banner "No violations of server rules detected!" - that's a dispute to the listed violation and that's why I come up with it (before my account might get closed). And if there are several deoding-problems a day I already saw the red line with serious rule violation.

From what I noticed, the problem comes up if there is a server problem, if cs-server has problems to decode for some time (not the short 1-2 ecm timeouts). Usually this happens for about 1-3 minutes. No reason to complain, only a rare problem but if the server/the reader on the server get stuck it seems to automatically restart itself - fine with me, I am only worried about the Violation it creates. In this case Oscam seems to send the unsuccessful requests again and again and I don't know how to avoid this behavior.
I already added the lines:
ratelimitecm = 2
ratelimittime = 8000  to oscam.server proxy-entries (every proxy-reader)
in addition to oscam.conf settings (that should be the lines refering to cs-server connection):
clienttimeout = 7200
fallbacktimeout = 7000  (as I have dual-login fallbacktimeout should not matter, cause there is no fallback-server available)
readerrestartseconds = 10

The ratelimit-settings makes switching channels already slower (about 1 second in addition to usual switching time) and because the codeword change-rate is usually 7 seconds (you should know) on all used packages, a time-limit 8000ms should be enough, using 10 seconds it makes switching channels especially while recording very slow, need several seconds. ECM-limit of course set to 2 because otherwise it also makes problems with recording channels or using Picture-in-Picture on the same PayTV provider/cs-reader - and thats why I ordered dual login.
I am using AX-HD51 STB with 2 tuners and the only available emulator is Oscam.
As I remember I was only watching one channel up to the problem and I am not really aware when the problem occur (I felt asleep while watching *g*). But I bet there was a server-problem while receiver was running, as I already noticed this connection between rule-violation and decoding-problem before, thats why I add the ratelimit-settings.
I was only watching this channel, no recording in addition, no PiP in use.

Any suggestion to avoid this violations ?
BTW: username = JayOswalt
9
Oscam / Re: Настраиваем OsCam
« Последний ответ от suma 18 Мая 2019, 07:03:58 »

Подскажите Spark 3 также нужно Oscam Настраивать?

Это универсальные настройки практически для любого ресивера, который поддерживает Oscam по протоколу Newcamd. Если через фид вашего ресивера невозможно установить Oscam, вручную это сделать лучше не пытайтесь и сначала изучите свой ресивер, почитайте форумы техподдержки
10
Oscam / Re: Настраиваем OsCam
« Последний ответ от Delp 17 Мая 2019, 17:33:15 »

Подскажите Spark 3 также нужно Oscam Настраивать?
Страницы: [1] 2 3 4 5 6 ... 10