Posts by s3n0

    This is a question of setting up the network interface correctly, in your WiFi router or in your set-top box system.


    It depends on what is used as the main gateway for internet access. It depends on the direction of network communication ... from the plugin (from your Linux set-top box), through various connection nodes, then via the internet and then it ends up in the picon server.


    However, the picon server does not allow proxy and VPN connections (through VPN gateways). These connections are often abused, for example as for DDoS. Unfortunately... reporting of these VPN accounts is also a lengthy process (in terms of jurisdiction).


    The solution would be to set up your Linux set-top box so that according to the network communication policy, the connection to the picon.cz server was routed only through your internet gateway (your internet provider directly) and not through the VPN network.

    wika


    But I don't know all the Enigma2 distributions in the world. Not at all Polish distributions Enigma2 :). I know only two of the most popular in Europe, namely: "OpenPLi" and "OpenATV".


    In addition, I also referenced the URL where the procedure for properly installing softcams is given, according to the query (i.e. the procedure for the Enigma2 distribution called "Hyperion 8").


    I do not instruct anyone to use the manual softcam installation method. However, it is a procedure written for Linux systems. This means that it must work in any set-top box that is based on the Linux system ! That is, regardless of the Enigma2 distribution used in the set-top box. The manual softcam installation method will work anytime, anywhere. In exceptional cases, users also need a GUI (SKIN) for Softcam. However, not every Enigma2 / GUI (SKIN) also has support for Softcam (for example, for restarting Softcam using the RCU, while watching TV).

    dan20701


    Hi.


    The file you downloaded is probably not a 7z archive, but a html code - if you also use a VPN in your Linux set-top box.


    In the plugin source code, the header of 7-zip files is detected as follows:

    Code
        def fileHeader7z(self, f_path):
            with open(f_path, 'rb') as f:
                f_header = f.read(4)
            if f_header == b'7z\xbc\xaf':         # check the 7-zip file header (the first 4 bytes from file)
                return True
            else:
                return False


    If you use a VPN in a set-top box, try disabling it temporarily. The same applies when using the PROXY server. If you are using PROXY to connect, try temporarily disabling it.


    The download of picon packages via another internet network (another internet provider) should also be tested. For example with a friend... without a tuner / antenna connection... all you have to do is connect the set-top box to a PC monitor or TV and download the icons there (via another internet provider).


    It would help to create a DEBUG / LOG file in your Enigma2 (I don't know which Enigma2 distribution you are using). There will be more information in the debug file when the error occurs. For example, send me this debug file in a private message.


    EDIT :


    You write that in the latest version of the plugin, this file download worked correctly. Write down which version worked correctly. It is also possible that there is a small BUG in the new version. In this case, it must be found and repaired. However, only with your help, as this latest plugin works correctly everywhere.


    Please also write which Enigma2 distribution (OpenPLi, OpenATV, ... etc.) you have installed in the set-top box.

    Oscam is always the same. They are only xxxx-MOD, xxxx-EMU are only modifications (EMU is, for example, an extension of Software Card Reader + Emulator with a virtual decoder card).


    If you want to convert CCcam configuration to Oscam, it's quite easy, just convert the data to "oscam.server":

    How to setup Oscam.server on H 7 C box


    Of course, for Oscam to work properly, basic settings are also needed and this is the "oscam.conf" and "oscam.user" files.

    Hi.


    This procedure - https://www.enigma2.net/tutori…nstall-oscam-on-hyperion/ does not work for you ?


    Or you can also install a separate Oscam binary. You download the binary for your chipset (mipsel, arm, aarch64, ...). It must be downloaded from a trusted source ! Oscam binaries and not IPK packages, you can also find it here on the discussion forum. Then just upload the Oscam binary file to the "/usr/bin/" folder and set the execute permissions (chmod 755 /path/to/file). Then upload my shell script https://github.com/s3n0/e2scripts/raw/master/softcam to the set-top box, the Linux startup "init.d" script, into the "/etc/init.d/" folder. You must also to set the execution rights, for this shell script. Everything else is described at the beginning of my shell script - in the comments.

    wafi villa :


    Instead of repeating the post, you'd better write what exactly doesn't work for you.


    /// EDIT :


    Improved previous script, no need to use curl (only wget will be used):



    Of course, this shell-script is not necessary at all if you use CRON - system scheduler. Just add a configuration line to CRON config-file:


    * * * * *       if [ $(/usr/bin/wget -qO- "http://USER:PASS@127.0.0.1:PORT/entitlements.html?label=YOUR_READER_LABEL" | grep -c "tier") -gt 0 ]; then /usr/bin/wget -qO- "http://USER:PASS@127.0.0.1:PORT/status.html?action=restart&label=YOUR_READER_LABEL" > /dev/null 2>&1; fi


    Don't forget to fill (to replace) the USER, PASS and PORT values for your Oscam-Webif !


    Or here is another example, a ready-made shell script that runs in the background and can run automatically with the set-top box via the init.d system in RunLevel3 (applies to Enigma2 set-top boxes):

    e2scripts/oscamrr at master · s3n0/e2scripts
    some helpful scripts (Python or Shell) for Enigma2 - e2scripts/oscamrr at master · s3n0/e2scripts
    github.com

    Hi.


    Disable SSL support and this is resolved. You don't need SSL after all... or do you ?

    88362193e46.png


    BTW, I'm not looking for an Oscam binary anymore and in my case the problem was more specific. I was looking for an Oscam binary for a specific router-firmware. Oscam binaries for OpenWRT also worked on this firmware, which I once used. But I needed a full package that already has everything compiled in it (stand-alone binary, without less dependence on Linux system libraries).


    But, I'm not looking for it anymore.


    If you use OpenWRT, just install the extension (Entware) and you can then download Oscam from the Entware feed. Although I admit that in some cases, it's complicated.

    fake ?? i dont understand .tryed again one channel opened but rest didnt for got to mention its sat 28.2 .unless every channel has gone dark then its understandable why wont get any cw

    Hi.


    Fake CWs can send softcam-servers intentionally, instead of the correct CWs. This is the case if the softcam server administrator has intentionally set it up. It is one of the forms of penalties for unauthorized (forbidden) way of accessing the softcam server.


    If you are the administrator and owner of the softcam server, then this is probably fine. However, if you are not the owner of the server yourself, try asking the server administrator what might be wrong.

    Directory path of the binary file ?


    The following path is used for most Enigma2 distributions:

    /usr/bin/your_Oscam_binary_filename


    However, in the case of BlackHole Enigma2, I am not quite sure. I think BH uses some special ingredient. I'm not sure.


    The location of the Oscam binary file can be determined in several ways. For example:


    1. finding the file name on root directory (as recursive):

    find / -iname "*oscam*"


    2. using HTOP tool (you may need to install it: opkg update; opkg install htop):

    htop

    ...and find in the list the running Oscam process


    3. using TOP tool:

    top -c | grep -i "oscam"

    ...to cancel, press the CTRL + C keyboard shortcut

    Hi.


    If you use different Softcam IPK-package that are not designed for your Enigma2 distribution (edition), so the installed Softcam may not be displayed correctly in the GUI (the type of SKIN used in Enigma2). So, you must use the IPK package designed for your Enigma2 distribution. Then it is enough to replace only the binary file, in your set-top box:


    1. stop the softcam service (enough via GUI)

    2. you overwrite the old Oscam binary file, with a new one (the new binary must have the same file name as the original one)

    - a note: Oscam binary file, must be designed for your processor (mipsel, arm v7, arm v8 - cortex, aarch64) and must support the system libraries (their correct version) that are installed in your Linux (set-top box)... this is sometimes also a problem, unfortunately, uhm :(

    3. set the file attributes again - for sure (command-line: chmod a+x /directory/file) or use an FTP client and set the bianry file attributes to value: 755

    4. you start the softcam service (it is enough via the GUI)

    Hi.


    This is nonsense :).


    Oscam is open source and is freely available on the internet. You may to download the source code. There are several options. You can use SVN on Linux, for example. Or you can download the Oscam source code from the website:


    WEB: https://trac.streamboard.tv/oscam/browser

    WEB - download trunk edition, as ZIP file: https://trac.streamboard.tv/os…runk?rev=11703&format=zip


    SVN: https://svn.streamboard.tv/oscam/trunk/


    Even if you use a disassembler, for a specific processor or some C-decompiler, a lot of information will be lost (for example, variable names). Compiled machine code looks different from compiled source code such as .pyo from .py (Python language). After compiling the C source code, the machine code (binary) is created. And to read this code, after its C-decompilation, a hard-to-read mish-mash is created. You can still decompile it with the disassembler. But then you don't read it at all (you get a tangle of instructions, depending on the type of processor - on millions of lines).


    After downloading the Oscam code from the internet, further edit what you need - just for your own use! Do not share the modified source code with anyone, as this corrupted code will begin to spread!


    After your modifications, simply compile this source code into a binary, according to your needs and settings, for your chipset / processor.


    If your modification is very important and if you are a developer of DVB systems, you can register on the Streamboard server and request a modification of the source code right there. The master can then approve it and appear in the standard Oscam building.

    Unfortunately, full-fledged Linux systems require the compilation of source code, directly for the appropriate processor, into a specific Linux kernel + to add the necessary libraries according to compatibility (library revisions). Therefore, it is used in full-fledged Linux, just the compilation of Oscam source code, on a specific PC.


    You need to download and compile the Oscam source code in your Linux. That's a pretty big problem - in terms of compatibility. Therefore, written shell scripts that do everything for you don't always work correctly.


    However, there are many instructions on the internet. Do not rely on the VPS, but on the version and name of the Linux distribution. So, search for a HowTo for your Linux, not for VPS. And it has to work. Alternatively, try more HowTo-s (procedures). It doesn't matter if you use the "svn" tool (https://trac.streamboard.tv/oscam/wiki/BuildingOscam) or if you download it manually to a folder and simply use the "make" tool. Only compatibility is important. You need to supplement the necessary libraries and tools designed to compile Oscam or to supplement the libraries for running compiled Oscam.

    What are you writing again, oh ...


    In the "init.d" folder of the system, there can only be control shell-scripts, for some processes. OScam process can also be one of them.


    Configuration files for Oscam, I have already explained to you 3 times - where is the directory, how to change it, how to find it and how it actually works with the path to the configuration directory. You can find the appropriate shell script and change or delete the "-c /directory" argument.


    The shell script can have any file name, but is usually called "softcam.oscam" or "softcam" or just "oscam". Find it yourself... for example with the command: grep -l "oscam" /etc/init.d/* or, for example, somethins as this: grep -l "cam" /etc/init.d/*. Then open and check the files found. So you find out which one starts your Oscam process. There may also be an "-c /directory" argument, which you can modify to change the directory/path where you have full access as a user, and where you want to upload Oscam configuration files.


    I recommend to read this :

    https://www.satsupreme.com/sho…SCam-on-Debian-and-Ubuntu

    Uhm...


    that's weird. According to Oscam's source code, configuration directories are searched in a certain order, ie if a directory has not already been specified directly in the startup command-line with the argument "-c /full/config/directory/path".


    https://trac.streamboard.tv/os…owser/trunk/oscam.c#L1662


    I don't know your Linux. There is probably a trigger of the Oscam process, just as script in the "/etc/init.d" folder. There should be a directory specification via the "-c /directory" argument. You can change it or delete it altogether + restart Oscam (with the help of this "init.d" script - for example: /etc/init.d/softcam restart). If you delete the argument "-c /directory", then Oscam will search the config dir, in the order you see in Oscam's source code. Or is it even better to change the directory, where you have access as a Linux-user, for example to the "home" folder ? Then move your Oscam configuration files there (to the "home" folder).


    BTW, you know I also hope that just one "oscam.server" file is not enough. Usually three files are always used:

    "oscam.conf"

    "oscam.server"

    "oscam.user"