Posts by SpaceRat

I'll check asap.

whenever it's borked, just wait 1 day.

The feed gets built every night.

Quote from s3n0

SpaceRat:

Exactly. Not every linux set-top box has the same libraries, ...

No need to carry sand to the beach ... I know why I designed the feed in exactly the way it works, where every (open source) CAM gets compiled from scratch for each and every image version and box architecture.

I remember the request, but was extremely busy this year.

Lot's of stuff left on the to-do list, but I might have a look at it later.

Quote from s3n0

Melgas?

An interesting script ... and yes, "feed" was written by me.

Two suggestions:

• You can also wget "feed" to /tmp, then "source" it using ". /tmp/feed" and call the functions from it, rather than duplicating it inside your script.
• It is highly recommended NOT to replace any existing oscam-binary that could be from feed, because if it comes from the feed, it could get updated (= overwritten) from there as well.
  

  I.e. do not use /usr/bin/oscam-smod, /usr/bin/oscam-stable, /usr/bin/oscam-trunk, /usr/bin/oscam-emu as names for own or manually updated oscams. Use something genuine, like oscam-own, oscam-mine, oscam-s3n0 or whatever instead.

  Just "/usr/bin/oscam" (Without anything appended to it) is fine on OpenATV, there isn't and there will not be (in any foreseeable future) an oscam that has no appendix on OpenATV's feed, but I do not know about other images, like OpenPLi.

I'll have a look.

Can anyone else confirm this issue?

You are obviously using oscam-trunk, which was bugged in 11533 and 11534.

The only relevant change you made was adding "boxtype = dreambox", which avoided the bug.

And yes, of course you need to configure oscam yourself, whatever oscam you get, it can't know what cards or cardservers you have.

Even oscam-smod, which can operate totally configless as long as you only use the emulator and/or local cards, can only do so until proxies (cardservers) need to be added.

The following channels on Sat do not work using SoftCAMs:

Sky 1 HD

Sky Sport Bundesliga UHD

Sky Sport UHD

DAZN does work, but cards with it are rare, as it is only part of a special package for "Sky Sports Bars" with a hefty price tag (You can not offer this package regularily, only if you operate a Sky Sports Bar)!

Newer != better, as you noticed yourself.

All versions 11533 and 11534 are broken and that's what you get if you install oscam-trunk ...

.. while oscam-stable gives you 11518 which is known to work and exactly that is the difference: oscam-stable does not get updated until newer is better.

trunk 11533 and 11534 fail to read all available caid:provid for a given channel on multiple channels, e.g. Hustler TV on Astra 19.2°E.

It will only work if boxtype is set to "dreambox", which is ok if you happen to have a box that is compatible with boxtype "dreambox", but bad if you require using "duckbox", "ufs910", "sogno" or whatever.

Remember that on OpenATV, you can always chose to install oscam-stable instead of oscam-trunk to avoid such bad revisions.

Note that this error also exists in oscam-emu as they merged this change. It also errors on oscam-smod git2003, but a fixed version (git2006) is on its way (being built right now).

Most images have SoftCAMs on their feeds.

On some images the feeds for softcams need to be installed seperately before you can use them for the first time.

Most probably you will find oscam-emu there and that's the one source where you can be 99.9% sure that it will fit your image.

And for those "There is no svn17988-r983 on the feed" die-hards, here a short a explanation of git revisioning:

The origin for oscam-emu, where the source code is actually maintained, is https://github.com/oscam-emu/oscam-patched

If you look there, you will see that this repository had 1765 commits (since it exists) at the time I'm writing this:

fdce6642d79.png

Automated build processes will fetch the sources and check if this number has increased.

If it didn't, there is nothing new. If it did, there is something new and a new build is initiated.

These automated build processes also take this commit counter as package version number and it's not possible (at least not easily) to inject any other more or less random version information into the package version!

On the screenshot you can also see what the latest commit contained (what was changed in it):

The version number (for the emu part) was bumped to 797.

So an oscam-emu git1765 consequently is oscam-emu r797. Actually, even git1764 of oscam-emu would be oscam-emu r797, as the only thing changed in this one commit was to actually write this arbitrary number "797" into some file.

If you now compare what you get offered on the OpenATV feed (or got offered at the time of writing) ...

enigma2-plugin-softcams-oscam-emu - 1.20+git1765+253a2ee-r0 - OSCam-emu 1.20+git1765+253a2ee (IPv6/IPv4 Dual-Stack support)

... with the git repository of oscam-emu at that time, you will see that you really get the latest version:

git1765 with the latest commit hash being 253a2ee (You will find this information on the far right inside the orange marker).

The same applies to all other CAMs built from git repositories, e.g.

- NCam (https://github.com/OpenVisionE2/NCam) git99 remains the latest, no matter if the author put a 10.2, a 10.3 or a 99.9 before it

and

- oscam-smod (https://github.com/Schimmelreiter/oscam-smod).

The versioning scheme you might know better is svn11532, but it's actually the very same principle, just a different version administration software (subversion rather than git).

svn11532 means nothing else than that 11532 changes have been made to oscam on http://www.streamboard.tv/oscam/changeset/11532 since it was created.

Since subversion is a major PITA and the streamboard svn connectivity is also pretty unreliable, OpenPLi for example doesn't build from streamboard.tv's svn directly, but uses a git mirror of it: https://github.com/OpenVisionE2/oscam

For that reason plain oscam on OpenPLi's feed also has a git revision rather than a svn revision, but if you check out the URL for the git, you will notice that the code is even.

This just as a side-note in case I ever have to switch to using a git for plain oscam too :)

Feed news:

- New SoftCam.Key (2019-07-20) by enigma1969 and BIGMAN_58 in oscam-smod, oscam-emu and NCam

- dropped NCam version (e.g. 10.2, 10.3) from NCam package version, as it gets changed every other day, only relevant version information is the git revision anyways

You are welcome.

Actually the much easier handling of the CAM start/stop/restart from shell was one of the main reasons to switch.

That *.emu garbage required excessive parsing:

First you would have to parse /etc/enigma2/settings to check which cam was selected and then you would have to parse that CAM's .emu file in order to find out how to restart it.

Now it's always

/etc/init.d/softcam start
/etc/init.d/softcam stop
/etc/init.d/softcam restart

in order to start/stop/restart the current CAM (No matter which one that is).

So it's even with any other system service running on the box:

If you change /etc/auto.network to change mounts for autofs, you would also simply invoke

/etc/init.d/autofs restart

in order to apply the changes ...

And if you change options to the dropbear ssh server on the box, you invoke

/etc/init.d/dropbear restart

in order to apply them ...

BTW:

For oscam, there is no reason to fully restart it in order to make config changes apply!

Just send SIGHUP to oscam and it will reread it's config files:

killall -SIGHUP oscam-smod

(Replace oscam-smod with whatever oscam you use, e.g. oscam-emu)

Unless you changed the defaults, oscam will reload all relevant settings (except oscam.conf itself) on SIGHUP without having to exit and respawn.

That means, changes to oscam.user and oscam.server can be injected "hot".

os.system("/etc/init.d/softcam restart")

Something like that.

very low priority:

I've yet to see a decent cam suddenly stop working.

Currently there are still some useless cams left to be added to the feed, because some users demand them.

I've also stuff left to change in smod.

Feed news:

the start script for gbox has been fixed

libcrypto-compat is a package on oe-a images (OpenATV, OpenViX, ...) that provides support for binary blobs that still require older OpenSSL 0.9.8 or 0.9.7.

In fact, it's nothing but the links.

Which brings us back to the main problem:

SoftCAMs from image feeds usually have properly set dependencies that cause the image's package manager (opkg in most cases, apt-get on DreamOS) to automatically fulfill these dependencies by installing the required packages first.

SoftCAMs from generic "fits all images" packages usually only really fit one image (or none at all).

For all others, they just do "something" a packager who doesn't even use that image deemed fit.

If you know what a toolchain is and if you can tell what version of which library your image contains and if you can modify a toolchain and you can cross-compile, then you can consider building your own oscam, oscam-emu, ncam, .... from source.

If you don't, simply use the CAMs from the feed. Any external source can only be worse.

No idea then.

All I could do is to have a look using TeamViewer or AnyDesk

Do not make simultanous changes in the file itself, that is /etc/tuxbox/config/oscam-modern/oscam.server , and through the oscam-WebInterface at the same time.

The changes made in the oscam-Webinterface would overwrite the changes within the files directly.

Either change the files directly (The lesser comfortable way, but obviously the preferred one by most users)

or change the configs using the oscam-Webinterface (The more comfortable and more fail-safe way).

Try this way:

• Open the oscam Webinterface, either by opening http://ip_of_your_box:83 or by opening http://ip_of_your_box/ and clicking on OSCam Webinterface below "Extras" in the OpenWebif.
• Click on "Readers" in the top menu of OSCam's Webinterface and then click on the trashcan symbol on the far right in the line of every reader you do not want.
• Click on "Restart" in the top menu of OSCam's Webinterface and chose "Restart" below the appearing question "Do you really want to shutdown/restart OSCam?".
• After oscam has restarted, the useless readers should now be gone.

For adding your own readers, click on "Readers" again, then "Add Reader" and enjoy the guided tour.

- or -

Click on "Files", then "oscam.server" and edit oscam.servers just like you would inside any editor, but without the need to use ftp/network shares or shell access to locate them.

Note: If you use the second method, that is clicking "Files" and editing the oscam.server, you need to restart oscam again to make it read the changed file.