Posts by s3n0

    Hi.


    Maybe you missed the "maxlogsize" item there. However, its auto-default value is 10 (kB). So it should be OK.


    I used 500 kB in my case. These are the values in units of kB for the max. LOG-file size.


    However, the maxlogsize limitation wrong (bugged) settings may then overload the available RAM-disk (because you use the "/tmp" folder for logging file). But... by default, if you don't set anything... there should be automatically set the value of 10 kB.


    I'm just guessing at a possible cause. I don't know if that's the case.

    You have to log into the file, because after the crashing of the Oscam process, it also logically kills the OscamWebif - Live Log.


    oscam.conf:

    Code
    [global]
    disablelog                    = 0
    logfile                       = /tmp/oscam.log
    maxlogsize                    = 500
    logduplicatelines             = 1

    Hi.


    In my opinion it is best to use the original online installer - intended for OpenATV. What is IPK good for ? That is useless.


    Here is the online installer (shell script), which is also included in the IPKs:

    wget -qO- --no-check-certificate "http://updates.mynonpublic.com/oea/feed" | bash


    Or using it, with debugging to a temporary file (for diagnosing possible problems and errors during installation):

    wget -qO- --no-check-certificate "http://updates.mynonpublic.com/oea/feed" | bash -xv > /tmp/feed.log 2>&1


    To unistall the softcam feed source:

    rm -f /etc/opkg/*3rdparty-secret-feed.conf

    reboot

    If the Oscam process freezes, it is probably a bad / incompatible binary file or there is some bad compatibility with the system libraries in your Enigma2. Try another Oscam binary file. You can also download binary files here on this discussion forum. According to the type of your set top box, download the correct binary (mipsel, arm, sh4, aarch64, ...).


    As first, stop your Oscam process. Then rename the binary file, according to the current binary, in your device - in the "/usr/bin" folder. And upload it to the set-top box (overwrite it). Check if the binary attributes are set correctly to 755.

    Run-level-3 symbolic link is probably broken. Check the "/etc/rc3.d" directory. There should be a sym-link to this "/etc/init.d/softcam.*" script file. That is, a symbolic-link, for example, like this:

    /etc/rc3.d/S90softcam.OSCam_11714-r798

    How do I run this code?

    This code is activated automatically in Open-Webif, in case hidden files generated by OSCam have been discovered. However, this does not apply to every OSCam. Some OSCam builds can be modified or configured so that they don't have to generate this file and then even OpenWebif can't identify this OSCam on the system.


    First try Oscam Webif and not Open Webif:

    http://IP_address_of_your_set_top_box:PORT

    PORT is usually 8888 or 83. If a different port is used, you will find it in the "oscam.conf" file (which you already found in Linux terminals, as you wrote above).

    Looks like oscam has disappeared....


    I have just run following which I thought should install oscam but it didn't work....

    Nope... the OSCam binary file name can also be called something else. It doesn't have to be exactly "oscam".


    Even some Enigma2 distributions place the softcam binary file in some folder other than "/usr/bin" (than other, standard, all current Enigma2 distributions).


    Try looking through the top or top -c command at the running processes and find the one that could belong to Oscam (for example, look for the startup parameters belonging to the Oscam process).


    Or if you have the opportunity, install and use the htop tool / command. This one is more beautiful (more clear) tool.


    Look in the contents of the "/etc/init.d" folder to see if there is a shell script (by name) that is intended for starting a SoftCAM.


    If you're going to try anything else with the IPK softcam-installers, back up the oscam configuration files you found in your set-top box ! The IPK softcam-installer could delete your current configuration files.

    Hi.


    Here is the OpenWebif source code. Specifically, an algorithm that looks for an available Oscam in the system and if it finds it... takes the necessary steps:


    e2openplugin-OpenWebif/base.py at 6733eae4bed5a1399901f5d63222c03dee21c2cb · E2OpenPlugins/e2openplugin-OpenWebif
    GPL Web Interface for e2stabs. Contribute to E2OpenPlugins/e2openplugin-OpenWebif development by creating an account on GitHub.
    github.com


    According to this code, the presence of Oscam is detected through auxiliary temporary files. However, not every single Oscam that was compiled by some expert will also create these temporary files (by the way, they are hidden, you have to enable their visibility in FTP connection if you want to see them via FTP connection).


    Although I'm not sure exactly what you're looking for in Open-Webif (Enigma2-Webif). Don't you mean Oscam-Webif ? Or do you really mean Open-Webif (Enigma2-Webif) ?

    Hi.


    On most Enigma2 distributions, the "init.d" methos is usually used. Examine the "/etc/init.d" folder in your set-top box. There should be a file like "softcam" or "oscam" or with the extension ".sh". These are shell scripts for automatic execution (at boot time). With their help, you too can restart / stop / start this softcam service.


    For example:

    /etc/init.d/softcam restart


    You can also examine the contents of the "softcam" script. These "init.d" scripts also have some rules and they must be followed in the system.


    Please note that some Enigma2 distributions only use the symbolic link "/etc/init.d/softcam", which points to the real shell script file (in the same folder). This is because of possible switching between multiple softcams, via Enigma2 GUI / SKIN.


    Here is my universal shell script for softcams, also with instructions at the beginning of the code:

    GitHub - s3n0/e2scripts: some helpful scripts (Python or Shell) for Enigma2
    some helpful scripts (Python or Shell) for Enigma2 - GitHub - s3n0/e2scripts: some helpful scripts (Python or Shell) for Enigma2
    github.com

    https://github.com/s3n0/e2scripts/raw/master/softcam

    Hi johnvucz


    And do you even know what IPTV is ?


    Do you know how many stations or providers or broadcasters of various IPTVs there are in the world ? There are thousands of them all over the world. That would be a bit complicated :).


    I personally solve IPTV in my set-top box, by creating reference links myself to existing picons, for all channels that are also distributed via IPTV (one of many X.Y. different providers / distributors of IP-TV broadcasting - based on TS MPEG).

    litek


    I don't understand exactly what you are writing about.


    If you mean a SAT-provider or specifically one missing picon, then you have to write in the thread with picones to the creator Chocholousek (Picons by Chocholoušek). Chocholousek is the picon designer and he takes care of all the picons. It is his merit. I'm just a developer of the plugin as such, designed to update with these picons.


    However, the 0.8W satellite is probably already solved. Chocholousek does his work for free and maybe sometimes he doesn't have free time. This is not paid work. Maybe an occasional donation won't hurt for Chocholousek :-P to have more free time for updating picons :-). So it's a good idea to wait at least a few days for the update.

    I don't understand the question.


    You are probably asking about a public or private IP address ? And you also need to know whether the IP address from your Internet provider is assigned as dynamic or static.


    Then according to these findings, you can use the DynDNS paid service for your WiFi router - but a public + dynamic IP address is required there.


    Or then, if you have a fixed IP address from the provider - that means static and at the same time public (which can be seen from anywhere on the Internet), then you only set the redirection on the WiFi-router to your machine on which Oscam is running.


    The third option is to pay for a VPN server service somewhere on the Internet. Through an online server, a virtual (like a local) network is then created between computers - which can be anywhere on the Internet.

    The "device=" configuration item in the "oscam.server" file means the IP address (or HOST name), followed by a comma followed by the PORT number. It is the address and port of the CCCAM server.


    And that's why there are "X" characters, because the user is not allowed to share his private data in the discussion.

    Hello.


    You must first edit the "softcam" shell-script. Change the variable

    BINFILENAME="oscam"

    - to :

    BINFILENAME="ncam"

    ... and also rename the binary file in the "/usr/bin" folder to "ncam" if it is not there.


    Also, one of the default configuration files for Ncam is different than in the Oscam case, for example here:

    /etc/tuxbox/config/ncam


    You also have to change the names of the configuration files from:

    oscam.*

    - to :

    ncam.*


    Everything else is described inside the "softcam" shell-script.

    Hi.


    If you're a more experienced user, which you probably aren't, use the manual Oscam installation procedure:


    But... if you are less experienced, then use the IPK package designed for almost all Enigma2 distributions, mentioned in the post above.

    Hi.


    These automated converters are not very reliable. It is better to use your own algorithm in the human brain than a numerical algorithm from an unreliable programmer :). Convert it yourself.


    However, you also need basic Oscam configuration files. Download them for example from here:

    https://www.linuxsat-support.com/cms/attachment/193620-universal-basic-oscam-cfg-files-zip/


    Then just add your CCCAM readers to the OSCAM configuration - they are inserted into the "oscam.server" file, as in the conversion instructions, here:

    s3n0


    Alternatively, you can insert your current Oscam configuration files here, after deleting your passwords and IP addresses or server names (replace them with some letters such as: XXXXXX).