Posts by s3n0

    If you're using a Linux PC x64 platform, find out how to compile an Oscam (using svn) and always use the latest Oscam, or find all the fixes for "NDS Videoguard" and you can apply them to the Oscam code if necessary.


    I still don't know what you need or what doesn't work. You did not attach any LOG. You didn't explain the problem. I don't know how to advise you. You wrote that the ECM decodes correctly and that the image sometimes freezes.


    The error can really be anywhere.


    My previous post was just an explanation of the possible cause of the error, which I hope I understood correctly. It was not a way to fix a problem that you didn't describe properly.


    If you are not an experienced user, then explain what does not work and attach the LOG file.

    Recently, however, many users of these cards have been complaining about a similar problem, so I recommend that you first try searching for a similar topic in this discussion forum (or through Google search engine).


    If you are an experienced user and can accurately identify the BUG in your case, you can report it as BUG on the Streamboard website. However, only if you are 100% sure, as the BUG reporting site does not provide support either.


    Most users do not even try to set the NDS Videoguard fixes that are already present in Oscam and will immediately use Multics.

    http://www.streamboard.tv/wiki/OSCam/en/Config/oscam.server - Press CTRL + F (in a web browser) to search for: "guard"

    Why do you use Multics ? Or does classic Oscam not handle NDS crypto mode well ?


    Check out the classic Oscam. What ECM time responses will be there.


    Internet connection is OK ? Or are you writing about a LAN network at home and not an internet connection ?


    What is VPS ? Do you mean VPN network ? If so, is this network connected via the internet ? Try a simple "PING" command to test the time response if ICMP protocol is also allowed in this network.

    Sat000info:


    You are replying to an old post. However, once you have refreshed it, I will also try to answer :).


    Oskracer:


    ECM packets are predetermined by the specific channels (services) you watch on the receiver. EMMs are commands for controlling the firmware in the decoding card or for controlling the CAM module.


    Consequently, you can filter the ECM by disabling or enabling individual "services" that you define in the "oscam.services" file and use it under a specific reader ("oscam.server" - [reader]) as a filter or even as a specific user filter ("oscam.user"). Use an exclamation mark to tell the reader to make the filter inverse.

    http://www.streamboard.tv/wiki/OSCam/en

    http://www.streamboard.tv/wiki…/en/Config/oscam.services

    http://www.streamboard.tv/wiki…fig/oscam.server#services

    http://www.streamboard.tv/wiki…onfig/oscam.user#services


    And I will reply to the previous older post on "au = Locale". It's wrong ! Unfortunately, there is no "Locale" label reader in your configuration ! The correct universal configuration should be "au = 1" for sending EMMs for all available Oscam readers. It is also correct to use the "au = <reader_label>" configuration for a particular single reader. More info here: http://www.streamboard.tv/wiki/OSCam/en/Config/oscam.user#au

    Hello.


    Do you mean the file "oscam.server" at client side or at server side ? :) So is this configuration from an Oscam server or an Oscam client ?


    Well, I will assume that the "oscam.server" configuration file comes from the server side, that is, from the Oscam that shares the decoder card. Since you are writing about Raspberri, "dvbapi" as the internal user will not work - the internal "dvbapi" user would have to have EMM and ECM receive from some source (satellite / terrestrial / cable tuner).


    So the server side setup should be without the "dvbapi" internal user and the oscam installed in Raspberr should act as a server.


    Now it is finally clear to me.


    I don't know your provider, CanalDigital / Nordic ? I don't know which EMMs and whether they have to be blocked at all. Try using the configuration for Nordic CanalDigital, which is here:

    vu solo 4k oscam config for canaldigital norden + viasat

    There is no EMMs blocking, which can also include refresh orders for paid packages for your decoder card serial number. Of course, customize the configuration (sharing + protocol settings you need).


    People, if you don't start to write the details, nobody will ever help you.

    ECM packets in the case of NDS crypto arrive at short intervals, new packets always arrive very quickly. A good internet connection is required. This could also be the cause of the occasional "freezing" of the image if the ECMs are working properly.


    What is the network connection time and what is the ECM processing time in LiveLOG (in Oscam-Webif) ?


    You ask endless questions, but you did not give a single detail that would solve the problem. If you want to continue this way, you can also ask Google search engine. He'll tell you more than I do. Of course you have to study it instead of me. For example:

    https://www.google.com/search?q=oscam+nds+freezing+image

    What exactly does Oscam Webif - LiveLOG say ? Can't you see any problems there ? Otherwise, this NDS Videoguard has always been reporting the last few weeks - like a freezing image, and the decoding works OK.


    It would be helpful if all people wrote all the details. What set-top box manufacturer what model - or even the type of chipset / CPU architecture. Also, the exact svn version used by Oscam would be nice to indicate, also the type of build or the source of that particular Oscam.


    Or describe exactly how the problems started to show up - since when ?

    Unfortunately, E-Channelizer is a commercial product based on the GUI of the well-known DreamboxEdit. E-Channelizer in trial version has very poor functionality. So you can also use DreamboxEdit, which is free for everyone. DreamboxEdit should also be able to run on Linux - via the WINE emulator.

    Hello.


    The client does not know the reader named "Serial:Reader 43" but according to the client configuration (label=.......). In this case, under "au=......" the specified reader name must be used on the same Oscam client. The ideal setting is "au = 1", but it will try to send EMMs to all available readers (to all local readers + including all remote readers) from the Oscam client.


    kalliffen mentions the file "oscam.server" but forgot to write if this configuration file came from the oscam server or oscam client.


    Certainly, however, adding "au = 1" in the client configuration (in the "oscam.user" file on the softcam client side) should help. It is also useful to verify that "au" is not blocked ("audisabled = 1" inside the file "oscam.server" or blocked with other settings) on the oscam server side by some accident.


    Some providers send EMM refresh for entitlements via emm-g and emm-u. If you block them all, of course no EMMs will be sent to the decoder card. Ideally, it would be possible to find a configuration for a particular cryptography as well as for a particular provider, since each provider can use a different card-sharing protection or special principles of recording "entitlements". Conversely, if you enable EMMs that are "unwanted", they can in turn block the decoder card. It really is better if you find a configuration for your provider. I don't know whether blocking emm-u and emm-g will not cause problems when refreshing "entitlements".


    blockemm-unknown = 1

    blockemm-u = 1

    blockemm-g = 1


    More info here (I recommend to read it all):

    http://www.streamboard.tv/wiki/OSCam/en/AU

    Hello.


    In that case, I only find that the dude who invented or compiled the above Cccam deserves the punishment of shame :). I wonder what the reason was to cancel compatibility.


    Linux is getting worse than Windows. I understand dependency on kernel versions, but I don't understand dependency on library versions. Any scared developer can't program some of the code himself, so will he use the features of the 2.0.0 library? :) New libraries are suitable for use in full-featured Linux systems and can be used there for large projects (eg dvb headend). I do not understand when someone in such a small thing as Cccam has to use the latest libraries or a newer Linux kernel system. These developers are a shame to other developers because they absolutely do not think at all.


    This is the same as when we design new applications and games, basically only for the new Android 10 and not older versions. Only apps and drivers for Windows 10 and not for older versions of Windows. Apps and drivers and modules only for linux kernel 5.4 and no other - ie. without compatibility in older versions.


    In the textbook for beginners - developers for Android systems, at the beginning of the book reads:

    Try to keep the compatibility with the oldest version possible! Otherwise, no one will use your app.

    Verify that your links are created correctly:

    ls -al /usr/lib/libcrypt*


    This is what it looks like in OpenATV 6.3 Enigma:

    Code
    root@formuler3ip:~# ls -al /usr/lib/libcrypt*
    lrwxrwxrwx    1 root     root            17 Jun  9 20:28 /usr/lib/libcrypt.so.1 -> libcrypt.so.1.1.0
    -rwxr-xr-x    1 root     root        137664 Jun  9 20:28 /usr/lib/libcrypt.so.1.1.0
    lrwxrwxrwx    1 root     root            18 Jun 10 20:20 /usr/lib/libcrypto.so.0.9.7 -> libcrypto.so.1.0.2
    lrwxrwxrwx    1 root     root            18 Jun 10 20:20 /usr/lib/libcrypto.so.1.0.0 -> libcrypto.so.1.0.2
    -rwxr-xr-x    1 root     root       1774316 Jul 19 19:18 /usr/lib/libcrypto.so.1.0.2


    In order to achieve the above, creating links in the right way is as follows:

    Code
    cd /usr/lib
    ln -s libcrypt.so.1.1.0 /usr/lib/libcrypt.so.1
    
    # then check it again :
    ls -al libcrypt*


    Or try the following commands ... of course only for testing purposes ... create and then delete the "libscrypt.so.2" symbolic link:

    How about applying symbolic links to old-new versions of libraries ? :) Backward compatibility should almost always be maintained. Only new features are added and BUGs are being fixed. There will be little change in the output or use of functions in libraries.


    If it is a set-top-box and not some x86 machine with full Linux, so if there is no conflict of many other dependencies on the old library, then it is sufficient to use symbolic links.


    In the case of set-top boxes and Softcams, it is common practice to use symbolic links to older libraries that are already removed from the system, but sometimes cccam or oscam (or other softcam) still require them.

    Hello.


    How to activate the installed softcam in Enigma depends on the Enigma distribution you use (OpenATV, OpenVIX, OpenPLi, PureE2, BlackHole, etc.). Each Enigme may even have a different trigger procedure (provided you do not use the manual softcam installation method).


    Why do you actually use Cccam ? :-P Why not multi-protocol Oscam, which is very popular today ? :) Of course, oscam also handles the cccam protocol and of course it can act as both a softcam client and a softcam server.

    Hi.


    Probably the OpenPLi 6 version is dead. In the meantime, several newer versions of OpenPLi have been released. The latest is if I'm not mistaken ver.7.2. Unfortunately, OpenPLi no longer provides support for all Dreambox devices, as well as other developer teams for other Enigmas. More info at OpenPLi web-page, here:

    https://openpli.org/download/dreambox/


    If you want to use regular online updates, you have to start using another and especially the new Enigma2. You download it from the Internet and flash it into the set top box and then set it up (I recommend backing up the settings for possible softcam and channel lists first). For example, one of the Enigmas that older Dreambox devices support is OpenATV:

    http://images.mynonpublic.com/openatv/current/


    However, it also depends on whether you own a DM800 clone or a full-fledged DM800. Then it depends on which DM800 you own - HD PVR, HD SE, HD SE V2 or which exactly:

    https://en.wikipedia.org/wiki/Dreambox#Table


    The DM800 models are slightly different in terms of their CFE boot loader or their hardware.


    The Ferrari edition is probably a "clone". If there are newer versions of OpenPLi than Dreambox 4.0, this is probably an unofficial release. Because the v4.0 feed server officially still exists (for the needs of older devices with old OpenPLi 4.0). However, newer OpenPLi versions that officially no longer exist for DM800 (except the 4.0 version), for example, no longer have a feed server. I don't know.... sorry ... because I don't use either Dreambox or OpenPLi. I use OpenATV.


    Try reading this thread ... maybe it will help you:

    OpenPLI 7-RC for dm800se sim ferrari old

    Hey everyone.


    Please, who is the author of the "feed" script on the URL link - http://updates.mynonpublic.com/oea/feed ? :P


    Please change the original characters ! used in the "sed" tool, in regular expressions, to another common used character / due to possible incompatibility issues between scripting languages: bash / sh / python. This can cause a syntax problem (POSIX) in certain specific cases.


    When I copied this function directly to the PUTTY open SSH terminal and ran it in Shell, the exclamation mark was misunderstood in Shell and the function could not be executed. Of course, I admit that this is just my specific case of using the code from the "feed" script.


    However, I think it is preferable to use the usual separator characters in regular expressions (for the "sed" tool), such as: #, @, or /


    From:

    OEVER=$(echo $OEVER | sed "s!OE-Alliance !!")

    To:

    OEVER=$(echo $OEVER | sed "s/OE-Alliance //")


    Thanks.

    :)

    You would first have to write down what doesn't work.


    There is nothing in LiveLOG that you provided. I don't see received EMMs and ECMs in your oscam LOG, but I repeat what I wrote above. Your Oscam (as a client) does not receive any requests - there is no activity. On what platform are you running it ? PC x86 Windows ? or ARM / MIPSEL at Linux set-top-box ? If it is an Oscam used in client mode and you also have a satellite tuner on it, then you should try to enable the dvbapi server/client as follows:


    - add to "oscam.conf":

    Code
    [dvbapi]
    enabled     = 1
    au          = 1
    user        = internal_user


    - add to "oscam.user":

    Code
    [account]
    user        = internal_user
    pwd         =
    group       = 1

    First, you try to re-share from a foreign server, and second, you don't even have your own decoder card in the internet reader. Unfortunately, in this case, I can't advise you. You would need to have access to the primary softcam server that shares the cards. You would have to see its complete configuration as well as any problems in its LOG records. Then a problem could be solved.


    Contact the administrator of the softcam server for advice on the problem, as it may find an error very quickly.

    Hello.


    In your attached LOG, unfortunately I see no attempt to decode channels or any attempt to process EMM / ECM packets by Oscam.


    Probably there is some problem between:

    card reader <-> SoftwareCAM (OSCam) <-> conditional access card from your provider


    Where do your oscam configs come from ? :) Are they sure ? Are they downloaded from the Internet ? Has anyone recommended them ? Maybe there is a mistake in them somewhere. The configuration is based on the "oscam.server" file, "oscam.conf". Alternatively, the "oscam.user" and "oscam.dvbapi" files are also necessary in some cases. Why didn't you mention them ? Do you even include them in your Oscam configuration ?