Welcome to LIGHT Forum.......The place to be.......Enjoy your stay and have fun ....

Announcement

Collapse
No announcement yet.

OSCam in AZbug HD with original FW 5303: both server and client at once!

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • OSCam in AZbug HD with original FW 5303: both server and client at once!

    OK, this works - tested with my Conax CD card CAS5!!! - both as a [Newcamd] card reader/server, as well as a [CCcam] client, so no need for any other Emus, thanx to various people for sharing info, like I am trying to do now...

    After plenty of testing, many different configurations on a couple of OSs [original FW and E2] and a couple of original FWs [4890 and 5303], as well as a couple of E2 [RC4 and RC7]...

    The version of OSCam I am using, fairly successfully, with all the stops, bumps, reboots and so on, is 4859, with dvbapii!!! You can find it on OSCam forum, in AZbox HD section, the "sticky" thread with bin files... But I will attach it in this thread, if I can!

    FTP to AZbox HD [use the freeware FileZilla Client] and go to PLUGINS folder, then OpenXCAS and create a folder oscamCAS, then give it CHMOD to 755 [right click on the file -> File permissions -> 755 -> OK].

    On your PC you can create various files, using a freeware application Notepad++, which you will FTP to oscamCAS folder. All except oscam module itself, which you get from the net, as mentioned and then give CHMOD to 755, as above. If it is named differently -> right click on it -> rename it to oscam and hit Enter on your keyboard.

    So, here are the four main configuration files [do not deviate from them, for starters... later, try different ones...] - thanx primarily to B@mbi but also hperez, gianni, subnixonfire, Siri, belami etc. etc.:

    openxcas.conf

    Code:
    [module]
     name = oscamCAS
     daemon = oscam -d 255
     argument = c /PLUGINS/OpenXCAS/oscamCAS/
     version = 1.00
     api=Yes
     wait =5sec
     INFO = /tmp/ecm.info
     REFRESH = 2
    Note: the "-d 255" line is worth its weight in gold, so to speak... Now AZbug HD reads the card consistently and fairly efficiently! Thanx to Siri!

    oscam.conf

    Code:
    # oscam.conf generated automatically by Streamboard OSCAM 1.00-unstable_svn build #48259
     # Read more: http://streamboard.gmc.to/oscam/browser/trunk/Distribution/doc/txt/oscam.conf.txt
     
     [global]
     logfile                       = /tmp/oscam.log
     clientmaxidle                 = 9000
     cachedelay                    = 120
     unlockparental                = 1
     nice                          = 4
     maxlogsize                    = 100
     preferlocalcards              = 1
     saveinithistory               = 1
     lb_mode                       = 100
     
     [monitor]
     port                          = 988
     nocrypt                       = 127.0.0.1,192.168.1.1-192.168.1.253
     aulow                         = 120
     hideclient_to                 = 0
     monlevel                      = 4
     appendchaninfo                = 1
     
     [newcamd]
     port                          = xxxxxx@xxxx:xxxxxx
     key                           = 0102030405060708091011121314
     allowed                       = 
     keepalive                     = 1
     mgclient                      = 0
     
     [cccam]
     port                          = xxxxxx
     reshare                       = 2
     ignorereshare                 = 0
     forward_origin_card           = 0
     version                       = 2.2.1
     updateinterval                = 240
     minimizecards                 = 0
     keepconnected                 = 1
     stealth                       = 1
     reshare_mode                  = 0
     
     [dvbapi]
     enabled                       = 1
     au                            = 1
     boxtype                       = none
     user                          = azbox
     pmt_mode                      = 0
     request_mode                  = 0
     
     [webif]
     httpport                      = 80
     httphelplang                  = en
     httpuser                      = xxxxxx
     httppwd                       = xxxxxx
     httprefresh                   = 7
     httpallowed                   = 127.0.0.1,192.168.0.1-192.168.255.255
     httphideidleclients           = 0
     httpreadonly                  = 0
     httpsavefullcfg               = 0
    Note: xxxxxx = this you choose, whatever it is... ergo xxxxxx = whatever you desire or whatever the CAID of your smartcard...

    You will need to forward the ports here defined, in your modem/router. "Forwarding ports" means to open those ports up to your AZbug HD, so when your peers try to get to you the traffic will not be blocked and it will automatically be directed to AZbox HD, instead of any other device you have hooked onto your home network, via the same modem/router.

    oscam.server

    Code:
    [reader]
     label = azbox-internal
     enable = 1
     protocol = internal
     device = 0
     services = whichever_card_you_have
     caid = xxxx
     ident = xxxx:xxxxxx
     detect = cd
     mhz = 357
     cardmhz = 357
     group = 1
     emmcache = 1,1,2
     lb_weight = 500
     
     
     [reader]
     label = xxxxxx.dyndns.biz
     enable = 1
     protocol = cccam
     device = xxxxxx.dyndns.biz,17000
     user = xxxxxx
     password = xxxxxx
     lb_weight = 100
     #inactivitytimeout = 1
     reconnecttimeout = 30
     #audisabled = 1
     group = 2
     cccversion       = 2.2.1
     cccmaxhops       = 1
     ccckeepalive     = 1
     #emmcache = 1,2,2
     #fallback = 1
     
     
     (...plus as many servers of your colleagues as you have, like  the  second   example above...)
    A note, to explain the name of the file: the first [reader] is your [internal or embedded card] reader, the "server" primarily for yourself, to which the OSCam client part hooks onto, internally, to open the channels.

    All the following ones are external [readers]. They are also servers but they are the servers of your peers, to which you hook onto, as a client. I.e. their readers read their cards, not just for themselves, but for you, too.

    Hence all are simply "readers", whether local [yours] or remote [virtual, via internet].

    The details marked xxxxxx in those you get from your colleagues/peers, like username, password, port and dyndns domain name. Those are necessary to be able to hook onto their servers.

    As a client in CCcam protocol one does not need to open various ports, Only servers [your colleagues/"peers" giving you access to their cards] need to do that.

    For now, let's just say that your embedded cardreader/internal reader/server should be in Group 1, whereas your CCcam peers should be in Group 2. If you have many C lines you can sub-divide them further, to make it all better optimised/efficient. Or you can add Newcamd ones in Group 3, GBox ones in Group 4 etc. etc. We shall come to that later.

    Here's an example:

    Code:
    http://streamboard.gmc.to/wiki/index.php/OSCam/en/examples/Sky_HD_and_MTV-UnlimitedMany
    Original smartcards' details are here:

    Code:
    http://streamboard.gmc.to:8001/wiki/CardsList
    oscam.user

    Code:
    [account]
     user       = azbox
     group      = 1,2
     au         = azbox-internal
     monlevel   = 4
     uniq       = 0
     services   = all
     betatunnel = 1833.FFFF:1702
     keepalive  = 1
     
     [account]
     user       = xxxxxx
     pwd        = xxxxxx
     monlevel   = 2
     uniq       = 1
     group      = 1
     au         = 1
     
     (...and so on, as many as you have...)
    Note: the file is called oscam.user because in it you are setting various "users" or "clients" to your "server". Each "user" in your file has an "account" with the server. I.e. a user will use your server/services, whether internally [the first one is you and you will hook onto your own card reader/server] or externally.

    Externally speaking: partially, you allow your peers access to your server right here, by setting up their username and password. The other parts to allow them access to your server, with which you create C (for your CCcam clients) or N (for your Newcamd clients) lines for your peers/colleagues, are from oscam.conf file, which we will discuss a little bit later, in the P.P.S.

    You can divide the [readers] and [accounts] into groups.

    For instance, your own internal server [the first "reader"] is in group 1.

    All the other "readers" of a certain protocol are in group 2. The next protocol goes to group 3, next one to Group 4 etc.

    The very first "account", i.e. "user" has to be in all the groups [for instance, 1,2,3,4], in order to hook both onto your own [internal] server/reader, as well as your colleague's [external] readers/servers. So, this first user [which is yourself] must hook onto both your internal reader/server [group 1], as well as external readers [groups 2, 3, 4 etc.].

    The other users/accounts are, in my case, Newcamd protocol clients of mine [me being a server, in this case, passing my smartcard to them], i.e. they are getting access solely to my smartcard [internal] reader/server by being placed in Group 1. That way they will not draw from anything but my smartcard/reader.

    Apparently, Newcamd server is meant for this purpose, so this is how it is supposed to be used. The N-lines you [partially] create from this file [oscam.user] and [partially] from Newcamd part of oscam.conf file, are to be given to your colleagues, people you trust. With those lines you pass only your card and nothing else and this is how it is done. These [users] are connected to my internal reader/server via Group 1 and thereby not connected to the CCcam protocol, which busy traffic is placed in Group 2.

    This is enough for you to be both a [Newcamd protocol] server, as well as [mainly CCcam] client. You give your card[s] in return for other people's cards. No need to pay for "CS services", run by our little CS entrepreneurs, spoiling the fun for us!!!

    I will attach the rest of the files here, including the module itself, so you don't have to search for it too much...

    A must info is here:

    Code:
    http://streamboard.gmc.to/wiki/index.php/OSCam/en
    Btw, don't be afraid to keep checking out the new versions...

    Cheers!

    P.S. More details, as to how to work with FileZilla Client and so on - in my "Alternative guide for AZ..."

    P.P.S. Thanx to B@mbi, how you create your N and C lines [my translation]:

    N-lines

    In relation to the parameters from oscam.conf file, one forms an N-line, for a user who uses a CS-server, capable of working with N-lines (like CCcam server, OSCam server…):

    [newcamd]
    port = AAAAA@xxxx:000000
    key = xxxxxxxxxxxxxxxxxxxx


    Ergo, N-lines, if you want to give those to anyone, are made like so:

    Code:
    N: your.dyndns.org AAAAA username1 password1      xxxxxxxxxxxxxxxxxxxx
    You must add a user with those details to your oscam.user configuration file, using the specified username1 and password 1.

    AAAAA is the port for your NewCamd server in OSCam and it must be opened/directed/forwarded in your router, towards AZbug HD's IP address.

    C-lines:

    Using the parameters from your oscam.conf file one forms a C-line for a user on CCcam or OSCam servers, using the C-line as a connection with remote cardreaders:

    [cccam]
    port = BBBBB


    Code:
    C: your.dyndns.org BBBBB username2 password2 no
    In your oscam.user file add a user with username2 & password2.

    So, BBBBB is a port for your CCcam server in OSCam and it has to be opened/directed/forwarded in your modem/router towards the AZbug HD's IP-address.
    Last edited by gorski; 21-06-2011, 15:14.

  • #2
    Just to let you know...

    I am testing this version now:

    oscam-1.00-trunk-svn4854-azbox-mips_dvba pi-fix.tar.gz (350.21 KB, 24 downloads)

    I find it to be much more stable than any other I have tested lately [and I did test a few...]

    Btw, I moved all to my "Group 1"!

    Working fine!

    oscam-4854 AZbug HD.zip http://light-files.site50.net/php_up...oxHD/Emulator&

    Comment


    • #3
      Top post amended, as I keep learning...

      Comment


      • #4
        Thank you to the guys from OSCam forum is in order!

        Newcamd client part working now! I learnt a few new things, plus I saw a few little corners in documentation which I haven't seen before and bookmarked them...

        But!

        I must notice that, at least in my setup [AZbug HD Elite with FW 5303] with this version of OSCam [4859], plus the configuration that will follow below - Newcamd client is much slower than CCcam client. Gets beaten to it every time. Response times are very high. From well over a second to "timed out" and no images...

        Here is my configuration. Can it be improved, please?

        oscam.conf

        [global]
        disablelog = 1
        disableuserfile = 1
        clientmaxidle = 9000
        cachedelay = 120
        unlockparental = 1
        nice = -1
        preferlocalcards = 1
        saveinithistory = 1
        lb_mode = 100

        [monitor]
        port = xxxx
        nocrypt = 127.0.0.1,192.168.1.1-192.168.1.254
        aulow = 120
        hideclient_to = 0
        monlevel = 4
        appendchaninfo = 1

        [newcamd]
        port = xxxx@0B00:000000
        key = xxxxxxxxxxxxxxxxxxxxxxxxxxxx
        allowed =
        keepalive = 1
        mgclient = 0

        #[cccam]
        #port = xxxxxx
        #reshare = 2
        #ignorereshare = 0
        #forward_origin_card = 0
        #version = 2.2.1
        #updateinterval = 240
        #minimizecards = 0
        #keepconnected = 1
        #stealth = 1
        #reshare_mode = 0

        [dvbapi]
        enabled = 1
        au = 1
        boxtype = none
        user = azbox

        [webif]
        httpport = 80
        httphelplang = en
        httpuser = xxxxxxxx
        httppwd = xxxxxxxx
        httprefresh = 7
        httpallowed = 127.0.0.1,192.168.0.1-192.168.255.255
        httphideidleclients = 0
        httpreadonly = 0
        httpsavefullcfg = 0

        oscam.server

        [reader]
        label = azbox-internal
        enable = 1
        protocol = internal
        device = 0
        services = canal digital
        caid = 0B00
        ident = 0B00:000000
        detect = cd
        mhz = 357
        cardmhz = 357
        group = 1
        emmcache = 1,3,2
        lb_weight = 500

        [All CCcam ones are in group 2 and disabled, in order to test Newcamd client part, which looks as shown below!]

        [reader]
        label = XXXXXXXX
        enable = 1
        protocol = newcamd
        device = xxxxxx.ath.cx,xxxxxx
        user = xxxxxx
        password = xxxxxx
        key = xxxxxxxxxxxxxxxxxxxxxxxxxxxx
        reconnecttimeout = 30
        group = 3
        emmcache = 1,3,2

        [reader]
        label = xxxxxxxx
        protocol = newcamd
        device = xxxxxxxx.biz,xxxxxx
        user = xxxxxxxx
        password = xxxxxxxx
        key = xxxxxxxxxxxxxxxxxxxxxxxxxxxx
        reconnecttimeout = 30
        group = 3
        emmcache = 1,3,2
        etc. etc.

        oscam.user

        [account]
        user = azbox
        group = 1,2,3
        au = 1
        monlevel = 4
        #uniq = 0
        services = all
        betatunnel = 1833.FFFF:1702
        keepalive = 1

        [account]
        user = xxxxxx
        pwd = xxxxxx
        monlevel = 2
        #uniq = 1
        group = 1
        au = 1
        CAID = 0B00
        etc. etc.

        Cheers!

        Comment


        • #5
          Code:
          Oscam-svnX-mips-azbox---------->AZBOXHD
          
          ------------------------------------------------------------------------
          r5443 | schlocke | 2011-06-20 21:15:30 +0200 (Mon, 20 Jun 2011) | 2 lines
          cccam: added extra logdata for finding card problems
          
          ------------------------------------------------------------------------
          r5442 | alno | 2011-06-20 20:34:46 +0200 (Mon, 20 Jun 2011) | 6 lines
          
          XMLApi: add user(account) config to XMLApi
          Call:
          1) read: /oscamapi.html?part=userconfig&user=<username>
          2) write: /oscamapi.html?part=userconfig&user=<username>&<par ametername>=<parametervalue>[&<parametername>=<parametervalue>]&action=Save
          
          If WebIf is in readonly mode the write Apicall returns a readable XML formated Errormessage
          http://www.megaupload.com/?d=1MV39N5R

          http://www.megaupload.com/?d=O6FGH83L

          Comment


          • #6
            Top post updated...

            But I must learn more about the new parameters in new versions of OSCam and see then...

            Comment

            Working...
            X