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

English forum section

Автор Тема: 3CSyslog (how to make log-file of linux receivers)  (Прочитано 14000 раз)

suma

  • Модератор
  • Ветеран
  • *****
  • Сообщений: 9487
  • Keep trying!
3CSyslog (how to make log-file of linux receivers)
« : 20 Февраля 2011, 19:51:48 »
You have downloaded and installed the software on you PC (see attached file below).
Before running it, make appropriate settings in your mg_cfg file.
Specify IP address of your PC in the L parameter line leaving 514 port as it is. It is used for connecting PC to the receiver. Warning! Check if 514 port is allowed by your firewall, otherwise you will wait for the log-file forever!



After editing, save and close. Restart emulator.
Run 3CSyslog. You will see the following window:



File--> Configure
Select Security settings sub-folder and add IP of your receiver.



Then, open Log-file destination sub-folder and appoint the route to the folder where your log-file is to be saved.



Finally, you will get the following:




In your C:\Program Files\3Com Corp folder, after the first run of the software, you will see syslog.log file which can be opened and edited using notepad or any text editor.



Log-file shall look like this:

Feb 19 08:58:08 192.168.1.35 ----------------------------------------------------
Feb 19 08:58:08 192.168.1.35 000: 80 00 3f 56 0e 02 56 00 00 4d 5f 31 ad a5 25 00  ..?V..V..M_1..%.
Feb 19 08:58:08 192.168.1.35 010: c4 8a 71 94 60 1b 4b a8 ee 78 eb a6 01 42 60 8f  ..q.`.K..x...B`.
Feb 19 08:58:08 192.168.1.35 020: b4 1a 73 97 72 fe fe fe 3a 4b 02 fe fe fe fe fe  ..s.r...:K......
Feb 19 08:58:08 192.168.1.35 030: fe fe fe fe fe fe fe fe fe fe fe fe fe fe 90 18  ................
Feb 19 08:58:08 192.168.1.35 040: f0 c5                                             ..
Feb 19 08:58:08 192.168.1.35 
Feb 19 08:58:09 192.168.1.35 Client <- Server: -- Sat Feb 19 02:57:59 2011
Feb 19 08:58:09 192.168.1.35 ----------------------------------------------------
Feb 19 08:58:09 192.168.1.35 000: 80 10 10 38 2c fe 62 4d 80 7a 47 6f a7 2e 44 d9  ...8,.bM.zGo..D.
Feb 19 08:58:09 192.168.1.35 010: 1b d9 cd                                          ...
Feb 19 08:58:09 192.168.1.35 
Feb 19 08:58:09 192.168.1.35 [mg0] <- CW from newcamd XX.XXX.XXX.X (server IP):port (702ms)
Feb 19 08:58:09 192.168.1.35 [mg0] 702 msec -- Sat Feb 19 02:57:59 2011
Feb 19 08:58:09 192.168.1.35 ===== @Sky ECM on CaID 0x4AE1, pid 0x0078 ======
Feb 19 08:58:09 192.168.1.35 prov: 000000
Feb 19 08:58:09 192.168.1.35 cw0:0 38 2C FE 62 4D 80 7A 47
Feb 19 08:58:09 192.168.1.35 cw1:0 6F A7 2E 44 D9 1B D9 CD


The lines highlighted are the main lines from where is it seen that the keys from the server are received by your receiver. You see CAID (0x4AE1) and IDENT (prov: 000000) of the provider.
P.S. Be sure that connection is allowed by your firewall.

That's all!


P.S. Please be noted that it is prohibited to openly show server name and port No.!!!

Your log-file must be just as provided above:

Feb 19 08:58:09 192.168.1.35 [mg0] <- CW from newcamd servX(server name):XXXXX (port) (702ms)
Feb 19 08:58:09 192.168.1.35 [mg0] 702 msec -- Sat Feb 19 02:57:59 2011
Feb 19 08:58:09 192.168.1.35 ===== @Sky ECM on CaID 0x4AE1, pid 0x0078 ======
Feb 19 08:58:09 192.168.1.35 prov: 000000
Feb 19 08:58:09 192.168.1.35 cw0:0 38 2C FE 62 4D 80 7A 47
Feb 19 08:58:09 192.168.1.35 cw1:0 6F A7 2E 44 D9 1B D9 CD



If the channel cannot be encoded, your log-file looks like this:

Nov 01 20:25:46 192.168.1.34 [mg0] newcamd route serv3:XXXXX cant decode (128ms)
Nov 01 20:25:47 192.168.1.34 [newcamd] Ping to serv3:XXXXX...
Nov 01 20:25:47 192.168.1.34 [newcamd] Pong from serv3:XXXXX (126ms)
Nov 01 20:25:47 192.168.1.34  ECM to newcamd serv3:XXXXX
Nov 01 20:25:47 192.168.1.34  Server: -- Fri Nov  1 20:25:40 2013
Nov 01 20:25:47 192.168.1.34 ----------------------------------------------------
Nov 01 20:25:47 192.168.1.34 000: 81 70 b4 00 00 01 14 ca 01 73 2b 1f ac 00 00 81  .p.......s+.....
Nov 01 20:25:47 192.168.1.34 010: 21 84 01 00 01 01 02 0e 00 00 82 9b 7d 09 44 7f  !.............D.
Nov 01 20:25:47 192.168.1.34 020: ab 7d 20 4e 76 67 83 90 8e c0 02 97 b9 94 80 45  .. Nvg.........E
Nov 01 20:25:47 192.168.1.34 030: 5a 02 66 aa d6 48 6b 8f d5 00 d7 a7 d1 5f 86 3a  Z.f..Hk......_.:
Nov 01 20:25:48 192.168.1.34 040: f0 cc d7 29 6b 13 b0 20 f4 65 c6 78 5b 40 39 f6  ...)k.. .e.x[@9.
Nov 01 20:25:48 192.168.1.34 050: 54 ca b9 bc 09 6a 26 a1 4c 91 28 d4 dc 2a 28 4f  T....j&.L.(..*(O


https://www.cardsharing.cc/index.php?topic=32076.0
VU+Zero. 13E, 82.5E, 56E, Vip All, OpenPLI 6.0 image, OSCam: 1.20-unstable_svn. ALL POSTS WITHOUT SIGNATURE AND LOG-FILE will be ignored and deleted!1.mg_cfg here http://www.cardsharing.cc/index.php?topic=23717.msg58140#msg58140
2. ignore-priority.lists here http://www.cardsharing.cc/index.php?topic

insomniac

  • Пользователь
  • **
  • Сообщений: 30
Re: 3CSyslog (how to make log-file of linux receivers)
« Ответ #1 : 21 Февраля 2011, 02:03:11 »
Thank you very much for writing this tutorial as it is clear, concise and has pictures to help.... To be honest ive only just found out that you need to enable syslog in gemini settings as it is switched off by default, so I thought that was the reason it wasnt working but I was wrong. I have followed the tutorial exactly and still 3csyslog doesnt log anything at all. Just to clarify ive enabled syslog in gemini 4.20 and my PCs IP is 192,168.1.2 and my Dreamboxs IP is 192.168.1.5 so I edited the mg_cfg adding my PCs IP and leaving it as port 514. I then loaded 3csyslog and added my Dreambox IP to the list of IP addresses being logged. I then restarted mgcamd1.35a but still 3csyslog didnt log anything. I appreciate all your time and effort writing the tutorial and giving me advice but somehow it still doesnt work. Ive even spoke to someone on another forum and they assured me I had everything set up right and he was completely stumped as to why it still isnt working. I know there is no other help you can give me as this tutorial explains everything but I wanted to post anyway just to let you know that it is still not working for me. Thanks anyway though mate, Rob aka insomniac
Eagle Box 1000S (Dreambox DM500S clone), 28.2e, Gemini Enigma 4.20, Protocol NEWCAMD 5.25, MGCAMD 1.35 emulator,

suma

  • Модератор
  • Ветеран
  • *****
  • Сообщений: 9487
  • Keep trying!
Re: 3CSyslog (how to make log-file of linux receivers)
« Ответ #2 : 21 Февраля 2011, 04:53:14 »
Check your firewall. Maybe it stops the software, you must allow your firewall to listen to 514 port. Initially, the software was written for DM500, it was checked on DM800HD - OK, AzBox Elite HD- OK!
VU+Zero. 13E, 82.5E, 56E, Vip All, OpenPLI 6.0 image, OSCam: 1.20-unstable_svn. ALL POSTS WITHOUT SIGNATURE AND LOG-FILE will be ignored and deleted!1.mg_cfg here http://www.cardsharing.cc/index.php?topic=23717.msg58140#msg58140
2. ignore-priority.lists here http://www.cardsharing.cc/index.php?topic

insomniac

  • Пользователь
  • **
  • Сообщений: 30
Re: 3CSyslog (how to make log-file of linux receivers)
« Ответ #3 : 21 Февраля 2011, 05:45:18 »
Thanks for the advice my firewall was blocking the port so ive sorted that and it is now logging fine. Thanks again for all your help and patience, I will post a log if I have any freezing but TBH it hasnt froze since I installed gemini enigma 4.20 earlier tonight. Cheers, Rob aka insomniac
Eagle Box 1000S (Dreambox DM500S clone), 28.2e, Gemini Enigma 4.20, Protocol NEWCAMD 5.25, MGCAMD 1.35 emulator,