Posts by s3n0

    Sorry, but you have to know which CAIDs you use and which you don't use in Oscam. Then add them to Oscam (according to the configuration manual of Oscam).


    Maybe that will help. I don't really know. I'm just thinking... that if you tell to Oscam, not to use and to completely ignore specific CAIDs, it might work.


    /// EDIT :


    Btw... you shouldn't have copied what I attached above because it was just an example. You can put the CAIDs you find in Oscam as available and through which Oscam searches... according to the Oscam LOG they should probably be the ones you see... but it's probably better to add the CAIDs you find in Readers > Info (Entitlements info). Here is an example for your use that might work:



    Btw, I see in the LOG that the user anonymous appears. This is usually when an unknown user connects to your Oscam using a local connection, usually a "dvbapi" user. You probably haven't set up "dvbapi", which is necessary.


    Here are the basic and convenient configuration 3 files for Oscam - download:

    oscam_config_for_megatron80.zip


    I also attached the file "oscam.dvbapi" there (the fourth file) - for you, which could work in your case SoftCAM vs HardCAM. If you use other CAIDs, edit them yourself (in all configuration files).

    OSCam/en/Config/oscam.server – Streamboard Wiki


    OSCam/en/Config/oscam.user – Streamboard Wiki


    OSCam/en/Config/oscam.dvbapi – Streamboard Wiki

    -example of oscam.dvbapi file:

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


    Simply tell Oscam to ignore the CAIDs you need in CI+. And tell Oscam to use only some CAIDs that belong to Oscam processing. It's a simple idea, but I don't know if it will work because I've never needed to do it.

    Hi. I don't know, I've never solved such a problem before. Maybe it would be enough to add the CAID, which is used in the hardware CAM (CI+ DIGI module with card), to the software CAM, so that it is ignored by the software CAM (Softcam - OSCam). I don't know if it will help, but theoretically yes. You use the file oscam.dvbapi and also set the CAID you need in oscam.server and oscam.user.

    Hi.


    Yes, it is possible. However, you must then supply the current data to chocholousek (creator and author of the picons) on a regular basis. Not just once a year :).


    Me... s3n0 ... I'm just a developer of this plugin - to support Chocholousek's great picons :).


    BTW, forum discussion thread for picons support, I already mentioned 3 posts above !!!

    OK, I understand.


    If there was a problem with updating one picon, intended for the SAT-channel called "TVP 4K", then in that case it would be appropriate to indicate the exact service reference code. If not, that's okay.


    However, this is a discussion about the plugin, not exactly about picones. Picons are solved at Picon.cz or here :) ->

    I have decided to stay on the older version since it updates my picons just as well as the newer version

    Of course. According to the "what's new" file, nothing important has been added.


    However, the problem when updating through the plugin configuration window and through updates in Enigma2 is clear.


    Something will have to be invented / perfected in the case of ChocholousekPicons BitBake recipe for OE-AllianceGroup, which is used by many Enigma2 teams included in this group. The idea of the existence of common plugins is nice, but unfortunately it is to neccessary to work on compatibility.

    Yes, but there is also a mistake in the BB-recipe. I know that for sure. I can try to fix it, but I don't know exactly how. Unfortunately, I don't have much experience with these BitBake recipes.


    Anyway, the mistake is, if the Enigma2 offers to user some constantly update, for newer plugins. Enigma2 is not a OS Windows, which needs to be updated every week :).

    Yes Warder , but not every Enigma2 distribution always behaves the same.


    Some Enigma2 distributions force the user to install a supposedly newer version from their own feed Enigma2 server.


    But if the BB recipe is bad, he thinks there is a newer version. But unfortunately there is no newer version on the feed server.

    I don't know if this is a bug, but you can help here, if possible.

    I installed the latest version 5.0.221117, after a few minutes, I got a message asking for update of this plugin.

    When I did this, it went ck to an old version as shown below

    Any explanations?

    Hi.


    This is likely to be a "feature" of the Enigma2 distribution you are using. I think so.


    Unfortunately, the BB recipe (OE Alliance Group) for the ChocholousekPlugin plugin has still not been modified to the necessary and final form.


    The plugin algorithm (source code) does not automatically update to a new version. And also new versions, the plugin does not automatically offer to install them.


    Only if the user uses the manual update of the plugin (yellow button in the ChocholousekPicons plugin), then only the update from the Github server will be started, ignoring the version on the feed-server (belonging to your installed Enigma2).


    So when you update from the feed server of your Enigma2 distribution, a different version gets there. You can find it, for example, via linux-shell:

    Code
    opkg update
    opkg list-installed | grep chocholousek-picons

    (a) if you see version 5.x.xxxxxx, it is from the feed server (created via BitBake recipe), from your Enigma2 (feed server)

    (b) if you see version 5.0.2.........., then that is the version installed directly from Github (from me)

    Hi.


    Thanks for the report and sorry for the mistakes. I fixed it !


    There was a small typo, after the last modification of this shell-script :). I forgot to comment out one "}" character in the case of a disabled function in the shell-script.


    My second mistake was the addition of the --proxy off parameter, which is different in the lightweight version from BusyBox (--proxy off) and in the full version (--no-proxy). I'm lazy to add wget --version testing :) and based on that also use parameter to disable proxy :).


    In my case, now everything works without a problem.


    If the problem persists, I can of course look into it. But for that I need remote access to your set-top box. If you believe me, for example, you can write to me on Skype and then I can look at it via TeamViewer or directly via a direct SSH/Telnet connection (SSH is a more secure connection with difficult sniffing of network packets).

    I don't know what exactly you want from me.


    After all, you wrote that you already have Oscam installed and functional. And that the problem is that you cannot connect to Oscam-Webif.


    But now you are asking for the overall process of installing Oscam.


    I don't know all the set-top boxes in the world and unfortunately I don't know all the Enigma2 distributions either.


    First of all, it depends on which Enigma2 distribution you have installed in the set-top box (developer team name and also version number).


    Secondly, I don't know if you used some kind of installation package or just a binary file. In the case of a binary file, the question is whether you followed it correctly (there is a slightly more complicated procedure).


    In the end, the problem may not be in Oscam functionality at all, but in you... maybe you configured Oscam incorrectly or there are several configuration files contained in your set-top box and they are crossed (after starting, Oscam looks for configuration files in several folders, but uses the first one found).

    It's hard to say what's wrong. There can be many reasons.


    Try writing http:// before the IP address. Try verifying the port again in the oscam.conf configuration file. Restart Oscam every time you change its configuration. Check the connection to Enigma2, also by trying to connect to FTP or SSH / Telnet services (if these services are active in your Enigma2).

    Hi.


    I think yes.


    But it also depends on the specific provider and their decoding satellite cards. They may contain some algorithms to protect sharing. I'm not an expert, so I don't know exactly.


    However, I know for sure that, for example, the ANTIKSAT provider with CAID=0B00 and CONAX encoding can be shared.


    However, I also know that some CONAX cards require pairing with a hardware access device. They don't answer otherwise. So you need some key for Oscam in that case.


    This may vary from case to case. So it's hard to advise you. Even a specific sat provider can after some time start producing newer decoding cards that have some protection included in them (SurfLock protection is known for example).

    In that case, it would be necessary to search for and debug the error.


    If there is a wget-error, try adding additional arguments, such as "--proxy off" ... or some others.


    It is also possible to use a different download link than the one I use ("raw" source).


    Online shell-script installer file, is located directly here (source code):

    e2plugins/online-setup at master · s3n0/e2plugins
    Enigma2 plugins. Contribute to s3n0/e2plugins development by creating an account on GitHub.
    github.com


    //////// EDIT (16.11.2022) :


    So I modified the mentioned installation online shell script a bit.


    I believe that the error arises from imperfect communication between the WGET tool and the GITHUB response.


    In some cases, GTIHUB will probably return only HTML code. It probably happens when it is an unknown file and GITHUB does not know how to provide (display) this file - in the case of RAW mode.


    For example, if it is a binary or an encoded or unknown type of file (.ipk), then GITHUB will not transfer it, but will (not always) first send only some HTML informative web page, without the possibility of a standard RAW button (for a direct link to download this file) - at the top right of the GITHUB website.


    In theory, it should now be solved by adding a parameter for GITHUB, which says that URL (WGET) directly requests the RAW format ( ?raw=true ). In the case of .ipk files, this should mean sending a real direct file, in RAW format (unknown to GITHUB - packaged .ipk file format).

    Hi.


    If you download the .ipk package using the wget tool, using the wrong arguments or if you do not add the appropriate arguments yourself, then it may happen that you download some HMTL page with an error message. Wget then saves it as an .ipk file :). And you then try to send this HTML page to the OPKG (installation package manager).


    I recommend using the online shell-script installer available on my Github: https://github.com/s3n0/e2plug…omatic-ipk--deb-selection This script can be run directly by downloading it and redirecting it via pipe directly to the shell-interpreter.

    Hello I don't know if I've posted this in the right place?

    I have a VU+ Duo 4k I have the plugin installed and working... But the only issue I have come across is with 7zip I have tried to install it as I'm a pretty technical person, but I can't seem to get it download and extract the picons do I have install 7z manually? I get Error! The downloaded file is not in 7-zip format!. I do run a vpn on router but that's never ever caused issues before.

    I hope someone can help thanks in advance


    VU+ Duo 4k Running open atv 6.4 armv7l

    Hi.


    There will probably be a problem in the computer network settings in your Linux set-top box.


    As Warder mentioned earlier, the problem will most likely be in the VPN network.


    A plugin or other application in Linux OS, don't know which gateway is in use (access to the internet network). The Linux system already knows that. However, connection via VPN is not allowed on the server from which all picon packages are downloaded. Often, unfortunately, the gateway in the VPN interface is used and not the gateway in the LAN / WiFi interface of the majority internet connection (the majority network interface in your Linux). There is a misconfigured network policy... I think.


    Unfortunately, the lightweight Linux OS in set-top boxes is not foolproof :). Large official distributions designed for desktop PCs are foolproof and there everything for amateurs is already treated and checked and possibly also very easily adjusted via the Linux GUI. However, this is often a problem in Linux set-top boxes - I don't know why... I haven't found out.


    Since VPN networks are misused for network attacks and malicious activity, the server with picons rejects these VPN connections. In that case, instead of a .7zip file, the plugin will simply receive a .html file. This html code contains some unknown and unidentifiable error. Some errors are treated, unfortunately not all and not one hundred percent, because it cannot be done so easily. Then... an error occurs when trying to extract the .html file as a 7zip archive.


    Btw... the 7zip archiver is already solved in the ChocholousekPicons plugin code. First, the plugin will try to install the 7zip package, directly from the Enigma feed. If it cannot be installed from the feed, a binary file, stand-alone archiver - 7za, intended for the appropriate architecture is downloaded and uploaded to the set-top box.

    Hi.


    For OpenATV it would be more convenient to use the additionally installed SoftCAMs package source:


    Then you simply install SoftCAM as a plugin.


    After installing it, of course you have to upload the appropriate configuration (configuration files for Oscam) via FTP connection.


    And then you just start Oscam using the GUI (blue button > Softcam Panel > and here you select the installed SoftCAM).