1. Diese Seite verwendet Cookies. Wenn du dich weiterhin auf dieser Seite aufhältst, akzeptierst du unseren Einsatz von Cookies. Weitere Informationen

Problem GBox und OScam - Wie miteinander verbinden?

Dieses Thema im Forum "CS Gbox" wurde erstellt von ezflashback, 15. Dezember 2011.

  1. ezflashback
    Online

    ezflashback Ist oft hier

    Registriert:
    24. Dezember 2009
    Beiträge:
    182
    Zustimmungen:
    31
    Punkte für Erfolge:
    28
    Hi Leute,

    ich habe einen Debian Squeeze, wo ich Oscam am Laufen habe und ich möchte intern die Keys in OScam einspeisen.

    Ich hoffe, ihr könnt mir helfen!

    Ich finde den Fehler nicht ...

    Meine Config:

    cs2gbox
    Code:
    M: { 192.168.2.24 { ABCDE145 }}
    #M: { IP-Adresse des Clients { Password1 }}
    D: { 192.168.2.24 { 2401 2400 { ABCDEF45 { 5 5 }}}}
    #D: { IP-Adresse des Clients { TX-Port RX-Port { Password2 { 5 5 }}}}
    C: { 192.168.2.24 34000 cooli cooli  01 02 03 04 05 06 07 08 09 10 11 12 13 14 }
    #C: { IP-Adresse des Servers Port Benutzer Password 01 02 03 04 05 06 07 08 09 10 11 12 13 14 }
    cwshare
    Code:
    M: { 192.168.2.24 { ABCDEF45 }}
    #M: { IP-Adresse des Clients { Password2 }}
    D: { 192.168.2.24 { 2400 2401 { ABCDE145 { 5 5 }}}}
    #D: { IP-Adresse des Clients { RX-Port TX-Port { Password1 { 5 5 }}}}
    gbox_cfg
    Code:
    # gbox config file
    
    # Trace, Debug
    #xx yz ; xx=00 no konsole output
    #xx yz ; xx=01 konsole output
    #xx yz ; y=0 debug output (dont use)
    #xx yz ; y=1 no debug output
    #xx yz ; z=0 ouput to konsole
    #xx yz ; z=1 output to /var/tmp/debug.txt
    #xx yz ; z=2 Output to UDP (to capture with gboxt)
    Z: { 01 10 } 192.168.1.2 8024
    
    # gbox working mode
    #00 pure Emu
    #01 pure SoftCam (when card inside), Emu (when no card inside)
    #02 pure Net Client
    #03 Mixed mode !!!!! always use this !!!!!
    G: { 03 }
    
    # Display ECM messages on Konsole
    #00 dont show any ECMs
    #01 show only valid ECMs
    #02 show valid and bad ECMs with complete data display
    #1X show ca access
    #2X use nagra aladin 1801 in betacrypt mode (for UM-I02)
    C: { 02 }
    
    # Display EMM messages on Konsole
    #00 dont show any EMMs
    #01 show only valid EMMs
    #02 show valid and bad EMMs with complete data display
    #1* Log any tier change on PW-Nagra-17xx cards into /var/keys/pwupdate.log
    M: { 12 }
    
    # Auto Update
    #00 is ignored (default)
    #01 enable AU
    #02 Auto AU !!!!! always use this !!!!!
    A: { 01 }
    
    # Key Update
    #01 update only new keys, default setting
    #02 update all keys (used for valid PMK checking)
    U: { 01 }
    
    # Hash pids
    #00 hash all pids, DO NOT USE THIS OPTION, IT IS ONLY FOR TESTING STUFF
    #01 hash only pids with implemented algos and available keys !!!!! always use this
    H: { 01 }
    
    # Key files folder
    #00 keyfiles in /var/keys
    #01 keyfiles in /var/tmp
    T: { 00 }
    
    # On Screen Display for the Multysystemcam on com1/com2
    #00 No OSD (default)
    #01 display Smartcard messages in Neutrino
    #02 display Smartcard messages in Neutrino new nhttpd format
    #03 display Smartcard messages in Enigma
    #04 display Smartcard messages in Enigma2
    O: { 00 } 192.168.0.3 coolstream
    
    # Logger and NET-mode UDP port Init
    #00 do not init UDP port
    #01 Init UDP port for IP, port, UDP
    L: { 01 } 192.168.0.251 7025
    
    # demux, multicam/comport configuration
    # example: yz = 0x0A = 00001010 (use com2 with inverted CTS detection line)
    #*x ** ; x = device nummber to be used (0= default)
    #D* ** ; force use of /proc/bus/gtx for cw write operations
             (in the dbox2 the gbox writes directly the CWs, 00 is the
             recommended mode ! No drivers are required) use D* ** ONLY if
             you have Problems. 0* ** should be prefered !!!
    #F* ** ; write CWs in both devices (used for PVR in STB04xxx devices)
    #** y* ; y=0001b (0x1*) use slot1 as Multicam (only on STB04xxx)
    #** y* ; y=0010b (0x2*) use slot2 as Multicam (only on STB04xxx)
    #** y* ; y=0011b (0x3*) use slot1 and slot2 as Multicams (only on STB04xxx)
    #** *z ; z=0001b (0x*1) use com1 as Multicam
    #** *z ; z=0010b (0x*2) use com2 as Multicam
    #** *z ; z=0011b (0x*3) use com1 and com2 as Multicams
    #** yz ; yz=00110011b (0x33) use slot1+slot2+com1+com2 as Multicams
    #** *z ; z=0100b (0x*4) invert CTS detection on com1
    #** *z ; z=1000b (0x*8) invert CTS detection on com2
    V: { F0 30 }
    
    # RS232 SSSP mode
    #xdebug messages, 1=on, 0=off
    # y   com port to use (0=none, 1=com1, 2=com2)
    R: { 00 }
    
    # Task type
    #00 **  normal mode gbox mode (no season, use Multicam instead)
    #01 **  Season Emulation in a Irdeto allcam chid 0602 nonZ
    #10 **  Season Emulation in a Irdeto allcam chid 1702 nonZ
    #11 **  Season Emulation in a Irdeto allcam chid 1702 Z
    #12 **  Season Emulation in a Irdeto allcam chid 1722 Z
    #13 **  Season Emulation in a Irdeto allcam chid 1762 Z
    #** *1  Com port to use for season emulatiom (1 or 2)
    #** 0*  Use CTS for RST detection
    #** 1*  Use DCD for RST detection
    #** **   9600 = Baudrate to be used (working only on dbox2)
    W: { 00 00 } 9600
    
    # =============================================================================
    # extra options to override default seting in case you expirience Problems,
    # normaly these setings are not required.
    
    # GboxTwin mode
    # this options for the 2nd gbox ONLY
    # you must have an extra gbox, gbox_cfg and cwshare.cfg running on /tmp,
    # all other files can linked to the org. files
    #F: { A6 } 5
    
    # cpu, api, cw write method
    # 00 auto
    # 01 80X86
    # 02 MPC823
    # 03 IBM STB04xxx
    #    00 auto
    #    01 ibm
    #    02 api2
    #    03 api3
    #       00 cw write style = use internal routine (only dbox2)
    #       01 cw write style = CA_SET_DESCR type1 (dbox2, vdr)
    #       02 cw write style = CA_SET_DESCR type2
    #       03 cw write style = CA_SET_DESCR type3
    #       04 cw write style = 16 byte /proc/bus/gtx
    #       05 cw write style = 4096 byte /proc/bus/gtx, cw offset=0x04D0
    #          xx write cw in 1st device with index=xx
    #             yy write cw in 2nd device with index=yy
    #                01 means with .index=0 (default)
    #                02 means with .index=1
    #                03 means with .index=0 and .index=1
    #                .. any bitwise combination ...
    #                FF means with all 8 indexes (0-7)
    #J: { 00 03 01 00 00 }
    
    # Files, folders, devices
    #      folder/device         comment
    #F: { 01 } /var/tmp/pmt.gbx// pmt file
    #F: { 02 } /var/tmp/emm.info// key update log file
    #F: { 03 } /var/tmp/ecm.info// ecm info file
    #F: { 04 } /var/tmp/atack.txt// atack info file
    F: { 08 } 1// pmt mode (0 - pmt file mode, 1 - pmt socket mode)
    #F: { 11 } /var/keys// folder for config files
    #F: { 12 } /var/tmp// folder for temporary file
    #F: { 13 } /var/tmp// folder for keyfiles
    #F: { 21 } /dev/null// ca device
    #F: { 22 } /dev/null// dvr device
    #F: { 23 } /dev/null// demux device
    #F: { 31 } /dev/null// second ca device to write cw's (recording)
    #F: { 41 } /dev/sci0// STB04xxx slot1
    #F: { 42 } /dev/sci1// STB04xxx slot1
    #F: { 43 } /dev/tts/0// rs232 com1
    #F: { 44 } /dev/tts/1// rs232 com2
    
    # For overclocking freaks, Clocking internal STB04xxx slots with:
    # 1=7.80MHz 2=6.30MHz 3=5.25MHz 4=4.50MHz 5=3.94MHz 6=3.50MHz 7=3.15MHz
    # Irdeto works fine on 7.8MHz, all other fine on 6.30MHz or 5.25MHz
    # The Dream has not a clean clock signal, some cards that are sensitive will
    # refuse to work even on 3.5MHz, thats why 3.15MHz is the default value there.
    # On other STB04xxx recievers the same cards work with 6.30MHz
    #F: { 51 } 02                    // irdeto
    #F: { 52 } 03                    // seca
    #F: { 53 } 03                    // viaccess
    #F: { 54 } 03                    // nagra
    #F: { 55 } 03                    // crypto
    #F: { 57 } 03                    // conax
    #F: { 58 } 03                    // nds
    
    # force a name change of the season or sssp rs232 device
    #F: { 45 } /dev/ttyS1
    
    # set stay alive ping time in seconds (default is 300)
    #F: { A0 } 300
    
    # disable direct serial port I/O access on 80x86cpus (win and linux)
    # direct port i/o is used to set unusual Baudrates, if you want to
    # a 3.579MHz card in a 6.000MHz reader etc ...
    #
    # Enabled (A1=0) is the default setting, has always been !!!
    #
    # Disable (set to 1) it ONLY if you have problems with ioperm or you want
    # to use a usb-to-rs232 smartcard reader
    F: { A1 } 1
    
    #Visit: www.coolstream.to
    oscam.conf
    Code:
    [newcamd]
    port                      = 34001@0500:022610
    serverip                  = 192.168.2.24
    key                       = 0102030405060708091011121314
    mgclient                  = 1
    oscam.reader
    Code:
    [reader]
    label                     = gbox
    protocol                  = newcamd
    device                    = 192.168.2.24,34000
    key                       = 0102030405060708091011121314
    user                      = cooli
    password                  = cooli
    caid                      = 0500
    group                     = 2
    audisabled                = 1
    der gbox log
    Code:
    strange input data in Nagra keyfile filepos 566
    strange input data in Nagra keyfile filepos 613
    strange input data in Nagra keyfile filepos 695
    strange input data in Nagra keyfile filepos 742
    strange input data in Crypto keyfile C filepos 220
    strange input data in Crypto keyfile C filepos 284
    strange input data in Crypto keyfile C filepos 418
    strange input data in Crypto keyfile C filepos 648
    strange input data in Crypto keyfile C filepos 712
    strange input data in Crypto keyfile C filepos 776
    strange input data in Crypto keyfile C filepos 910
    Total 91 EMM keys read from nagra.txt
    ReRead gbox_cfg
    
    gbox 2.25/Linux@X86 ( May 21 2006, 18:56:23 )
    Checking/Logging PW tiers on every EMM
    OSD (dbox2) IP = 192.168.0.3
    direct serial port i/o disabled
    mode 03
    AU:01/update:01/KeyFile:00 Hash:01 DispECM:02/EMM:02 UDPInit:01 OSD:00
    strange input data in Seca keyfile filepos 191
    strange input data in Seca keyfile filepos 226
    strange input data in Seca keyfile filepos 261
    strange input data in Seca keyfile filepos 296
    strange input data in Seca keyfile filepos 331
    strange input data in Seca keyfile filepos 366
    strange input data in Seca keyfile filepos 401
    strange input data in Seca keyfile filepos 436
    strange input data in Seca keyfile filepos 471
    strange input data in Seca keyfile filepos 533
    strange input data in Seca keyfile filepos 568
    strange input data in Seca keyfile filepos 603
    strange input data in Nagra keyfile filepos 203
    strange input data in Nagra keyfile filepos 250
    strange input data in Nagra keyfile filepos 324
    strange input data in Nagra keyfile filepos 371
    strange input data in Nagra keyfile filepos 445
    strange input data in Nagra keyfile filepos 492
    strange input data in Nagra keyfile filepos 566
    strange input data in Nagra keyfile filepos 613
    strange input data in Nagra keyfile filepos 695
    strange input data in Nagra keyfile filepos 742
    strange input data in Crypto keyfile C filepos 220
    strange input data in Crypto keyfile C filepos 284
    strange input data in Crypto keyfile C filepos 418
    strange input data in Crypto keyfile C filepos 648
    strange input data in Crypto keyfile C filepos 712
    strange input data in Crypto keyfile C filepos 776
    strange input data in Crypto keyfile C filepos 910
    Total 136 EMM keys read from nagra.txt
    ->Here? to 192.168.2.24 (192.168.002.024)
    
    cs2gbox log
    Code:
    CS2Gbox support www.satkeynet.com/forum
    [11:37:18.887] config: reading file '/var/keys/cs2gbox.cfg'
    [11:37:18.893] My IP 192.168.2.24 ID 4A88 (192.168.2.24) pass ABCDE145, we are online
    [11:37:18.906] IP 192.168.2.24 Port 2401-2400 ID 4488 pass ABCDEF45 sharelevel 5/5 (192.168.2.24)
    [11:37:18.926] cardserver 192.168.2.24/34000 NOT responding !
    [11:37:18.928] Total 1 UDP ports to monitor:
    2401
    [11:37:18.928] Entering main loop...
        gbox: send message to 192.168.2.24:2400
          0000: 48 49 AB CD EF 45 AB CD E1 45 01 15 30 02 04 19
          0010: 19 66 00 1F 31 39 32 2E 31 36 38 2E 32 2E 32 34
          0020: 0C
    [11:37:18.939] -> Hello to 192.168.2.24:2400
        gbox: receive message from 192.168.2.24:49325
          0000: 41 C0 AB CD E1 45 AB CD EF 45 15 30 02 04 19 19
          0010: 66
    [11:37:20.372] comeONLINE (192.168.2.24:2400)
    [11:38:18.912] ! connection failed to cardserver 192.168.2.24/34000
    [11:39:18.921] ! connection failed to cardserver 192.168.2.24/34000
    
     
    #1
  2. phantom

    Nervigen User Advertisement

  3. ezflashback
    Online

    ezflashback Ist oft hier

    Registriert:
    24. Dezember 2009
    Beiträge:
    182
    Zustimmungen:
    31
    Punkte für Erfolge:
    28
    AW: GBox und OScam - Wie miteinander verbinden?

    ein erster schritt ...



    CardServer to Gbox v3.00 (compiled Jul 12 2011)
    CS2Gbox support

    Dieser Link ist nur für Mitglieder!!! Jetzt kostenlos Registrieren ?


    [12:21:22.563] config: reading file '/var/keys/cs2gbox.cfg'
    [12:21:22.581] My IP 192.168.2.24 ID 4A88 (192.168.2.24) pass ABCDE145, we are online
    [12:21:22.589] IP 192.168.2.24 Port 2401-2400 ID 4488 pass ABCDEF45 sharelevel 5/5 (192.168.2.24)
    newcamd: send message
    0000: E0 00 00 75 73 65 72 00 24 31 24 61 62 63 64 65
    0010: 66 67 68 24 31 73 30 62 76 37 2E 4F 6A 4E 69 7A
    0020: 6C 72 4D 41 4F 49 51 44 37 2E 00
    [12:21:25.208] login failed to cardserver (192.168.2.24:34011), wrong data length
    [12:21:25.211] Total 1 UDP ports to monitor:
    2401
    [12:21:25.211] Entering main loop...
    gbox: send message to 192.168.2.24:2400
    0000: 48 49 AB CD EF 45 AB CD E1 45 01 15 30 02 04 19
    0010: 19 66 00 1F 31 39 32 2E 31 36 38 2E 32 2E 32 34
    0020: 0C
    [12:21:25.222] -> Hello to 192.168.2.24:2400
    gbox: receive message from 192.168.2.24:34119
    0000: 41 C0 AB CD E1 45 AB CD EF 45 15 30 02 04 19 19
    0010: 66
    [12:21:26.121] comeONLINE (192.168.2.24:2400)

    cs2gbox
    M: { 192.168.2.24 { ABCDE145 }}
    #M: { IP-Adresse des Clients { Password1 }}
    D: { 192.168.2.24 { 2401 2400 { ABCDEF45 { 5 5 }}}}
    #D: { IP-Adresse des Clients { TX-Port RX-Port { Password2 { 5 5 }}}}
    C: { 192.168.2.24 34011 user pass 12055 01 02 03 04 05 06 07 08 09 10 11 12 13 14 }
    #C: { IP-Adresse des Servers Port Benutzer Password 01 02 03 04 05 06 07 08 09 10 11 12 13 14 }

    cwshare
    M: { 192.168.2.24 { ABCDEF45 }}
    #M: { IP-Adresse des Clients { Password2 }}
    D: { 192.168.2.24 { 2400 2401 { ABCDE145 { 5 5 }}}}
    #D: { IP-Adresse des Clients { RX-Port TX-Port { Password1 { 5 5 }}}}

    oscam.user

    [account]
    user = user
    pwd = pass
    group = 2
    cccignorereshare = 0


    ocsam.conf
    [newcamd]
    port = 34011@0500:022610
    serverip = 192.168.2.24
    key = 0102030405060708091011121314
    mgclient = 1

    oscam.reader
    [reader]
    label = gbox
    protocol = newcamd
    device = 192.168.2.24,12055
    key = 0102030405060708091011121314
    user = user
    password = pass
    caid = 0500
    group = 2
    audisabled = 1
     
    #2
  4. D_K
    Offline

    D_K Guest

    AW: GBox und OScam - Wie miteinander verbinden?

    ................................................
     
    Zuletzt von einem Moderator bearbeitet: 1. Dezember 2012
    #3
  5. ezflashback
    Online

    ezflashback Ist oft hier

    Registriert:
    24. Dezember 2009
    Beiträge:
    182
    Zustimmungen:
    31
    Punkte für Erfolge:
    28
    AW: GBox und OScam - Wie miteinander verbinden?

    ich will tnt und csat keys an oscam weitergeben ...

    das habe ich schon bei camd3 erfolgreich am laufen ... aber leider hab ich bisher keine möglichkeit gefunden, die csat und tnt keys in camd3 einzubinden .... daher der umweg über gbox ...

    also von gbox die keys zu oscam ...
     
    #4
  6. D_K
    Offline

    D_K Guest

    AW: GBox und OScam - Wie miteinander verbinden?

    .................................
     
    Zuletzt von einem Moderator bearbeitet: 1. Dezember 2012
    #5
  7. ezflashback
    Online

    ezflashback Ist oft hier

    Registriert:
    24. Dezember 2009
    Beiträge:
    182
    Zustimmungen:
    31
    Punkte für Erfolge:
    28
    AW: GBox und OScam - Wie miteinander verbinden?

    verstehe ... liest cccam denn auch die tnt & csat keys von viaaccess 3?

    könntest du mir vielleicht nen hinweis bzw. link zu nem richtigen aufbau einer cline in der cs2gbox geben?
     
    #6
  8. D_K
    Offline

    D_K Guest

    AW: GBox und OScam - Wie miteinander verbinden?

    ................................................
     
    Zuletzt von einem Moderator bearbeitet: 1. Dezember 2012
    #7
  9. ezflashback
    Online

    ezflashback Ist oft hier

    Registriert:
    24. Dezember 2009
    Beiträge:
    182
    Zustimmungen:
    31
    Punkte für Erfolge:
    28
    AW: GBox und OScam - Wie miteinander verbinden?

    via scemu scheint tnt via cccam zu gehen :) ... via newcamd "noch" nicht ;)



    CCcam mit Emu Freigabe - F: user pass 2 1 0 ... werden dann alle vorhanden keys als lokale angezeigt?

    ... dann reader eintragen im oscam eintragen

    Die Line ist von cs2gbox zu gbox ... das habe ich schonmal verstanden ^^
     
    #8
  10. D_K
    Offline

    D_K Guest

    AW: GBox und OScam - Wie miteinander verbinden?

    ................................................
     
    Zuletzt von einem Moderator bearbeitet: 1. Dezember 2012
    #9
  11. ezflashback
    Online

    ezflashback Ist oft hier

    Registriert:
    24. Dezember 2009
    Beiträge:
    182
    Zustimmungen:
    31
    Punkte für Erfolge:
    28
    AW: GBox und OScam - Wie miteinander verbinden?

    ocsam (newcamd) - cs2gbox - gbox zu gbox share ... keine keys ^^

    scemu - oscam cccam (0500 tnt wird erkannt und angezeigt) ...

    csat realisiere also ich dann von cccam 2.0.11 zu oscam (cccam)?

    sorry, bin etwas begriffsstutzig ^^
     
    #10
  12. D_K
    Offline

    D_K Guest

    AW: GBox und OScam - Wie miteinander verbinden?

    ................................................
     
    Zuletzt von einem Moderator bearbeitet: 1. Dezember 2012
    #11
  13. ezflashback
    Online

    ezflashback Ist oft hier

    Registriert:
    24. Dezember 2009
    Beiträge:
    182
    Zustimmungen:
    31
    Punkte für Erfolge:
    28
    AW: GBox und OScam - Wie miteinander verbinden?

    gebe dir morgen mal ne rückmeldung, obs geklappt hat ;)
     
    #12

Diese Seite empfehlen