Posts by s3n0

    Hi.


    So first of all ... by the term "oscam server" you mean a file called "oscam.server" or directly Softcam Oscam as a server ?


    Secondly ... how did you find out there was a problem with access rights ?


    The location of the directory with the Oscam configuration files can be found here:

    OscamWebif -> Files -> oscam.version ------- search the line "ConfigDir"


    You have to place your configuration files there. Of course, you should also assign the appropriate access rights to them, with the chmod command.


    If you place there some new configuration files, don't forget to restart Oscam to load them again. Then direct file editing via the "Files" MENU should work in OscamWebif, but also via the standard GUI configuration MENU items (WebGUI items).

    Hi.


    However, you need to show the initialization of an external USB reader from your OscamWebif > LiveLog. Restart Oscam and show how the external reader is initialized in Oscam.


    The "Rejected group" error can have many causes. Are you sure there is an error initializing the external USB reader? There may also be an error in the incorrect configuration of your 0B00 CAID (I assume from the CAID number that this is some kind of Conax encoding).


    Are the saved configuration files in correct folder? According to the content of your file "oscam.server" and according to your screenshot, the data for the set reader do not match. I mean the name of the reader and also the set protocol.


    Try to verify that your configuration files are in the correct folder. Go to: Oscam Webif > Files > oscam.version ....... then, find and check "ConfigDir" here.

    Hi.


    https://wiki.streamboard.tv/wi…onfig/oscam.conf#httpport


    The WebIf port parameter is optional, but I don't think there should be an empty (whitespace) value. You have to put zero or some port value there. Or delete this configuration entry for the WebIf port completely. In my opinion, this is the mistake. The default port is 8888. So delete the item, comment out (character # at the beginning of the line) or set this default port 8888 there:

    Code
    [webif]
    httpport                = 8888
    httpallowed             = 127.0.0.1,192.168.0.0-192.168.255.255,10.0.0.0-10.255.255.255

    I don't even know that how you got there... everything and each other... connected to all others - between all devices there. So I probably won't advise you very much.


    I don't even know what the problem is, so...

    Didn't you just mean EMMs writing to the decoder card ? These are very important for some coding systems. These are control packets, which, however, also write the so-called "entitlements" (table with prepaid channel packages). AU (AutoUpdate) configuration is used in Oscam for these purposes. However, in my basic oscam config-files for you, AU is already enabled.


    If you also use remote Cccam set up as a softcam server, then of course you have to enable the writing of EMMs (AutoUpdate).


    Problems can still arise with versions of the cccam protocol. I recommend removing the entry from the "oscam.server" file to determine the cccam version (https://wiki.streamboard.tv/wi…g/oscam.server#cccversion). Maybe it will help.


    Also, Oscam softcam usually doesn't work very well with Cccam softcam. Personally, I have a good experience only with Cccam softcam in version 2.3.0 (mipsel architecture). Other versions of Cccam softcam unfortunately in my case of IRDETO coding, never worked properly. Therefore, I am forced to use only Cccam softcam in version 2.3.0. I use Oscam softcam as a server (including writing and decoding the card also on the local port - in the set-top box). I always use Cccam softcam 2.3.0 exclusively as a softcam client.

    What does "Live Log" show in Oscam-Webif ?


    Is group = 1 added also for an external reader connected by the cccam protocol ? I mean in the oscam.server file.


    What does sending requests with ECM packets on both sides look like ?

    That has nothing to do with it. You enter there an IP address. The IP address must be visible and an open port must also be available to connect.

    How to convert "C-Lines" to "oscam.server" configuration file:


    How to setup Oscam.server on H 7 C box


    Of course, don't forget to add group = 1 there, because you definitely use these groups in the configuration as well. So you have to add an external reader (external Cccam server) also to this group of yours (or set up the groups as you need - according to your Oscam configuration).

    Hi.


    You need three basic files:

    oscam.conf

    oscam.server

    oscam.user


    Next you need to set up some CA source where the packets will be decoded :) in this your Oscam server. This "decoding source" is usually set in the oscam.server file. There you set up an internal card reader or also a connection to an external reader.


    If your Oscam server is running on a set-top box, where you also want to use packet decoding (ie the server will also be a client), then a "dvbapi" interface is used for this purpose. In the example config (see appendix) this dvbapi is already set up. It must be set to both oscam.conf and oscam.user files.


    Attached is the basic configuration of Oscam - just as an example.


    Here you will find a description of the configuration files for Oscam:

    https://wiki.streamboard.tv/wiki/OSCam/en

    Hi.


    There are several options.


    On the softcam server, if it is Oscam, you can specify one CAID or several CAIDs for each user, which they are allowed to use. You can do this in the file "oscam.user" (https://wiki.streamboard.tv/wi…en/Config/oscam.user#caid) or directly via Oscam Webif (WebGUI), directly in the settings of a specific user.

    Code
    [account]
    user        = user1
    pwd         = password1
    caid        = 0624,0D96
    group       = 1


    You can also specify directly on your server that you use only a specific CAID or multiple CAIDs. First, directly in the "oscam.reader" file, by writing a parameter (https://wiki.streamboard.tv/wi…/Config/oscam.server#caid).


    Furthermore, if it is a newcamd protocol and not a cccam protocol, you can also specify the CAIDs used on the softcam / Oscam server (https://wiki.streamboard.tv/wi…/Config/oscam.conf#port_6), for a specific port, such as:

    Code
    [newcamd]
    key     = 0102030405060708091011121314
    port    = 14000@0624:000000;14001@0D96:000004


    Finally, it is advisable to set priorities and ignore CAIDs on the device (configuration file: "oscam.dvbapi"), where you have your Oscam server, i.e. where you have your shared cards / CAIDs (https://wiki.streamboard.tv/wi…am/en/Config/oscam.dvbapi). For example, as follows:

    Code
    #### Setting priority rules for CAIDs (user_dvbapi):
    P: 0624     # Skylink SK (Irdeto)
    P: 0D96     # Skylink SK (CryptoWorks)
    
    #### Ignore every CAID that was not handled before:
    I: 0


    Or you can also set the CAID(s) directly in the softcam client connection:


    However, it depends on which softcam client you use. Cccam softcam or Oscam softcam - are set differently (there is a different configuration file). For example, in Oscam softcam, under the file "oscam.server", where you create a connection to a remote reader (to a external softcam), you can also add a CAID parameter there - as if it were a physical card reader (I mentioned the URL above).


    Oscam configuration files and their description:

    https://wiki.streamboard.tv/wiki/OSCam/en

    Guys... I didn't write that the bug is in the OpenATV python code. That was just a possible cause... one of many causes.


    As for the problem described, with starting and stopping a softcam via python code - it's better and faster verification, if you dont use Enigma2 to handle your Softcam, but simply use the Linux Shell. First stop the Softcam via the Linux Shell (killall -9 <softcam-process-name>) and then start it manually, as it should be, for example according to the command-line obtained from the "/etc/init.d/softcam" script.


    Your problem guys may not be caused at all by an error directly in the OpenATV / Enigma2 / python code.


    This problem could be, for example, the use of some newer versions of system libraries, in this newer version of OpenATV firmware. There may be a minor incompatibility in the Linux libraries used by Softcams. But even that is just another possible cause - one of many causes. I didn't test this because I don't have this problem.

    SpartacusTed


    This is difficult to judge because I don't know your softcams. It depends on many things: the decoding system used by your sat-provider, the compatibility of the used Oscam for your chipset set-top box as well as for your Linux kernel and its system libraries (Enigma), the configuration of Oscam itself, connected clients, etc. .


    For example, I recently discovered a small BUG in Oscam server while encoding IRDETO. If the client (CCcam 2.3.0) is connected before the dvbapi interface, it takes too long to create "entitlements" on the decoder card (required after each restart of Oscam) because Oscam considers the softcam, not the dvbapi interface, to be the primary connection of the external client. As a result, the Oscam server uses the external softcam client as the primary connected and, unfortunately the dvbapi user, connects via the cache (ECM cache). Thus, since I allowed EMMs to be written only through the internal user's dvbapi, there is a problem with writing "entitlements" (which are important for the functionality of the Irdeto decoder card). Well, if the clients are disconnected and if I restart Oscam and if only the dvbapi interface / client is running, then the "entitlements" will be written / created fine.

    Hi.


    For more info see also here:


    -file "oscam.services" : https://wiki.streamboard.tv/wi…/en/Config/oscam.services

    -file "oscam.server" / cfg-item "services" : https://wiki.streamboard.tv/wi…fig/oscam.server#services


    BTW, empty namespaces can probably be used, but I don't use them personally - just to be sure to prevent some random problems in Linux with names that don't understand the empty space. I am replacing empty spaces with a bracket :). So, rather to use the label "Bad_sids2" - instead of label "Bad sids2". However, it should also work with empty space - in this particular case (Oscam configuration).

    You're welcome :).


    BTW, Oscam configuration files can also be edited directly in Oscam Webif (Oscam WebGUI) - via the "Files" MENU (at the top of Oscam-Webif). So, you don't have to use an FTP client to access these files.


    Only set up additional configuration files if you really need them, following the instructions on the internet or if someone has advised or instructed you to do so. However, the basic 3 mentioned configuration files are.


    However, main files are only these two: "oscam.conf" + "oscam.server".


    Alternatively, the third file can also be very important "oscam.user". When you need to use the so-called "dvbapi" interface, for the purpose of connecting Oscam to yourself - i.e. when your Oscam serves both as a server but also as a client. And if you need to connect Oscam internally to yourself. Or this file is also used if your Oscam also works as a softcam server. Of course, you then add new users to this "oscam.user" file to allow access to your softcam server.

    Hi.


    For client needs, here is How-To converting C-Line to Oscam configuration:

    How to setup Oscam.server on H 7 C box


    A simple description of all configuration files and especially all their items can be found here (but this is not a manual, just a description):

    https://wiki.streamboard.tv/wiki/OSCam/en


    The most important are the files:

    oscam.conf

    oscam.server

    oscam.user

    ...while other configuration files are not so important.


    Of course, you can also use Oscam Web-GUI (Web-If / Web-Interface), but it then modifies these configuration files according to your own needs, by itself.

    sky23 :


    Hi.


    The problem could also be in starting and stopping the Softcam (Oscam) process. OpenATV works a little differently in the new versions - there is a different time limit. The process first stops (/etc/init.d/softcam stop) and then starts (/etc/init.d/softcam start) again. OpenATV waits 100 + 1000 milisecs during the Softcam "stop + start" process: https://github.com/openatv/eni…n/Screens/SoftcamSetup.py (/lib/python/Screens/SoftcamSetup.py). Unfortunately, OpenATV does not use the "init.d" script argument as the "restart", but "stop" + "start".


    So you need the correct "init.d" script that takes everything into account. Ideally, use Softcam from a "secret" feed for OpenATV.


    Did you use this correct Softcam / Oscam, which is tuned to work under OpenATV ?


    Unfortunately, these are the details that can disable Softcam in Enigma2. It is best to use your own system method of booting / starting processes, which the user adds to the system himself, so Softcam always starts correctly.


    The problem is that basic administrator knowledge of a Unix / Linux system is required. You must also own the correct / appropriate binary file of the appropriate Softcam, which is intended for a specific Linux (necessary modules and libraries must not be missing) and also for a specific Enigma2 distribution (if the user wants to control or even set up his Softcam via GUI / SKIN).

    Hi.


    You have to contact chocholousek , because he designs and takes care of all the picons. I'm just an Enigma2 plugin developer.


    So, please, try to contact him, here:


    https://picon.cz

    -- or --

    chocholousek

    -- or, as the best, here: --

    Picons by Chocholoušek


    However, if these are remote satellite positions and therefore less support for picons... then it will be a problem. Most picons are designed and maintained primarily for Europe. And that's a lot of work - keeping this up to date at all times.

    5.0.211019

    Added a simple function:

    - the 7-zip error "Can't allocate required memory!" may occur on some devices with 256MB or less of RAM installed

    - from now, free RAM is checked before downloading packages from the internet, then if possible, if necessary, some RAM (buffer / cache in Linux) will be freed - for the purpose of decompressing 7z packages

    Separated one user Oscam configuration:


    Value for user being idle before disconnect:

    Code
    umaxidle = -1        # the value clientmaxidle in [global]-section will used here
    umaxidle =  0        # idle disconnect disabled (default)
    umaxidle = seconds   # defined exact number of seconds for user idle time

    https://wiki.streamboard.tv/wiki/OSCam/en/Config/oscam.user

    - or -

    https://wiki.streamboard.tv/wi…onfig/oscam.user#umaxidle


    File: "oscam.user"

    Value: umaxidle=10800


    You can also use the global Oscam settings:


    Value for client process being idle before disconnect in seconds:

    Code
    clientmaxidle = 200   # Disconnect after 200 seconds
                  = 0     # idle disconnect disabled
    
    Default:
    
    clientmaxidle = 120   # Disconnect after 120 seconds


    https://wiki.streamboard.tv/wiki/OSCam/en/Config/oscam.conf

    - or -

    https://wiki.streamboard.tv/wi…/oscam.conf#clientmaxidle


    File: "oscam.conf"

    Value: clientmaxidle=10800 (under [global]-section)


    The problem can also occur if the softcam client is set up to maintain a continuous connection,

    even if it is IDLE. This is a setting option, for many protocols.

    For example: ccckeepalive = 1 - https://wiki.streamboard.tv/wi…oscam.server#ccckeepalive