Posts by musogeek


    just highlighted a couple of things in red


    I have never used serverip flag - any reason why you are using it?
    the cs357x configs - is it needed as part of your setup?


    also in the CCcam config - I would delete the forward_origin_card = 1 completely - again unless there is a reason you have this - i found it slows everything down.


    Not sure if it will solve your issue but worth having a tweak

    are you trying to access oscam webif remotely or from the same PC you have oscam installed?


    If it is from the same PC then the httpallowed flag in oscam.conf should have localhost address added (127.0.0.1)


    so
    httpallowed = 192.168.0.1-192.168.255.255
    should becme
    httpallowed = 192.168.0.1-192.168.255.255,127.0.0.1

    so when you mean things are freezing are you talking about peers or your local receiver? If depending on how you have things set up, if you have gone from a receiver based server to PC server you may have lost a hop, which could be what is going on. Not enough info to go on though, you need to post your configs - read the rules first so you know what you should leave out.

    avast is free as far as i know but you might have to register every year - AVG free is common one - I use microsoft securicy essentials - which also comes as part of Windows 8

    something i may have missed - is oscam just a cardreader? Are you sharing to local CCcam and using this as a server? - are you sharing nlines rather than using CCcam protocol to share?


    also i noticed something in your configs


    Services =[SateliteBg]


    take away the[]


    so it would be services = SateliteBg


    If you are using Oscam as a cardreader and CCcam as a server then you can't really do anything about defining sids.

    Thank you musogeek!!


    Many of thinks you notice I know, but I havent all need it information...like puzle..I miss some off them.
    I will try right away if I can succeeded with your tips and feedback you.
    Thx again!


    Btw. Sorry for double post:lol:


    Problem with a lot of info out there is that it is in bits and you have to put it together, and your question gave me an excuse to present it as a mini tutorial on oscam.services!
    Didn't notice the double post but since you mentioned it I have deleted it - cheersbeer10

    Hi muso I have a separate server so unable to leave on a single channel?


    not sure what you mean - you leave your local client on a channel overnight - this isn't related to having a server - you are trying to update your card from your local receiver so just leave your receiver on sly 1 overnight.


    if you have peers you could update from them if you have their flines/user accounts set right.

    you need to use oscam.services - it doesn't work if you set services for a physical card but it will work on user accounts in oscam.user, so you can set this in each user account so clients connected to your server will not request the services you haven't got.


    you need to have a file in the same folder as oscam.conf called oscam.services. In this file you name a [service], add caid provid and srvid as below example for mtv unlimited card


    Code
    [mtv]
    caid                          = 0B00
    provid                        = 000000
    srvid                         = 6FEE,6FEF,6FF0,6FF1,6FF3,6FFA,6FFF


    now in each user account, you add


    Code
    services = mtv


    mtv is the name in [] - you can place multiple services in this file, for example



    and on the user accounts in oscam.user you add


    Code
    services = mtv, jsc


    so you are telling restricting each user to receive only the services defined under the [] headings in oscam.services.


    You can also define a whole caid, by leaving out provid and srvid flags in oscam.services definition


    Code
    [s*y]
    caid = 0963


    if above is defined by services = s*y - then it will restrict your user account to just 0963 channels, but all of them. As soon as you start defining provid and srvid, then it will restrict the card to the ones defined, and reject others. You can make multiple definitions to control each user account. This control is done best in oscam's web based GUI.


    It can be used in another way. If you want it to clear everything apart from certain services/channels, then you still create the definitions in oscam.services as above, but in the user accounts, you just put a '!' in front of the name of the definitions you have created. for example, I want my peer to get all channels apart from boxnation and premier sports, so in oscam.services I put this


    Code
    [boxnation]
    caid                          = 0963
    provid                        = 000000
    srvid                         = C5CB


    and on the user account in oscam.user you add


    Code
    services = !boxnation


    You can also use this to restrict what you get from peers, so if you have peers who give you fake or bad clearance on certain services or whole cards, you can block them out, or just set definitions for all the stuff you want, and set this on the accounts in oscam.server.


    Thanks for agreeing to the forum rules, but you just broke one and didn't post an intro!


    Introductions


    doesn't take long.....

    your card should have already updated tbh - you need to be patient though - I used to suffer from pre update anxiety for weeks before each update when I had a sly card but never missed an update in the end! - as I said though for some reason I remember that it seemingly worked better with CCcam protocol in oscam with cline in CCcam.cfg rather than nline - but I was one for tweaking alot when updates were due so I still am confident you will get it to update - be patient it might take a few days.

    your CCcam.cfg is disabling emm's


    delete or hash out the line in red


    N: 127.0.0.1 12000 **** **** 01 02 03 04 05 06 07 08 09 10 11 12 13 14 256



    SERVER LISTEN PORT : *****
    ALLOW TELNETINFO: yes
    ALLOW WEBINFO: yes
    WEBINFO USERNAME :****
    WEBINFO PASSWORD :****
    TELNETINFO USERNAME :****
    TELNETINFO PASSWORD :****
    TELNETINFO LISTEN PORT : *****
    WEBINFO LISTEN PORT : *****
    ZAP OSD TIME :0
    OSD USERNAME :****
    OSD PASSWORD :****
    OSD PORT :80
    SHOW TIMING : yes
    DEBUG : no
    NEWCAMD CONF : no
    DISABLE EMM : yes
    EXTRA EMM LEVEL : yes
    SHOW EXTENEDED CLIENT INFO : yes
    MINI OSD : no
    MINIMUM DOWNHOPS: 1
    CHANNELINFO FILE : /var/etc/CCcam.channelinfo
    PROVIDERINFO FILE : /var/etc/CCcam.providers
    CAID PRIO FILE : /var/etc/CCcam.prio
    LOG WARNINGS : /tmp/warnings.txt
    SOFTKEY FILE : /var/keys/SoftCam.Key
    AUTOROLL FILE : /var/keys/AutoRoll.Key
    STATIC CW FILE : /var/keys/constant.cw
    SMARTCARD CLOCK FREQUENCY: /dev/sci0 6800000

    no dvb api?


    [dvbapi]
    enabled =1
    boxtype = pc
    user = localuser
    au = 1


    dvbapi not used for standalone server.


    show your CCcam configs in the client to see if that is preventing sending them to Oscam.


    Are you using newcamd protocol (nline) or CCcam protocol (cline) to connect to your client receiver? I have found (although may be coincidence) that connecting with cline rather than nline has better results. Patience is key, as is leaving the receiver on a channel that your card clears (not a FTA channel) such as sly 1 every night for a few days.

    New versions may include bug fixes, new features, etc, so me being me would regularly update. If you are happy with what you have got and see no reason to update then that is fine. Considering 1.20 builds are considered unstable then you should always expect that along with bug fixes will be new bugs. It is very easy to update, it is pretty much just a case of getting the new binary and overwriting the old.

    To clear this up - as can see the confusion! - If you use ecmwhitelist, then it will only clear the services where the correct ecm length is defined. If you don't use it at all, then it will clear all lengths by default. So if you use it, then you have to bother with keeping it up to date, if you don't use it, then so long as you are not concerned about the alleged possibility of your card being killed, you can save yourself the trouble - so I agree with rossi2000.

    Defining CAID and Ident in your oscam.server will not do the trick in a lot of cases, for example, an MTV unlimited card has CAID 0B00 and ident 000000, which is also shared by other cards. MTV Unlimited only has a handful of services. Firstly, your peer should use SID assign or oscam.services on their side to help this. Also, once Oscam realises that a service isn't on your peer's card, it will flag it as a bad sid and stop requesting it. You can also set up oscam.services to define the particulars of your peer's card, so you are only requesting the services that clear on your peer's card


    http://linuxsat-support.com/os…uk-sid-assign-reject.html

    http://linuxsat-support.com/li…l-package-debian-6-a.html
    Follow this to a T.
    DON'T install it with a Graphical User Interface. You can access your server remotely, and with 256mb I cannot see a big install with a GUI working well at all. A flavour of debian on a 256MB Raspberry Pi is possible, so you might get away with it, but bear in mind the Raspberry Pi has a different architecture, so it is hard to draw a comparison, but I managed to get the above installed on a very old laptop with 512MB ram (intel celeron as well) and without a GUI was perfect, but as soon as you try using this with a GUI then it is very slow.