Posts by s3n0

Do you also use a VPN network ? If so, try temporarily shutting down.

The configuration of the WiFi router (LAN switch in your network) is OK ? Try disconnecting the LAN cable between the set-top box and the WiFi router. Then switch off the set-top box and the WiFi router (completely disconnected from the mains). Then turn on the first WiFi router again and wait for it to boot for a few minutes. Then reconnect the LAN cable between the WiFi router and the set-top box and turn on the set-top box. Test if FTP connection is already working.

If the netstat command works in PurE2 image, try this in Linux Shell:

netstat -tulpn | grep LISTEN | grep 21

Is the FTP service (server / daemon) running ? It should be possible to verify this in the Enigma2 GUI, it will normally find it somewhere in the MENU... probably under the "network" or "network connections" setting.

I don't know. But some PurE2 expert should answer here :). I don't remember his exact nick-name, but he's also here on this discussion forum (PurE2 development team).

Does the Telnet connection work ? Did you set a password via Telnet ? For most Enigma2 distributions, it is necessary to connect first via the Telnet protocol (terminal connection using the PuTTY application, for example) and change the password there with the command:

passwd

Or try to check if the FTP / Telnet / SSH services are running at all. However, these services do not have to be enabled and started on every Enigma2 distribution by default. For higher security reasons, they can be stopped by default. They should also be able to be enabled (started) using the RCU, in the Enigma2 GUI.

Hi.

Check the LAN configuration in the Enigma2-GUI (SKIN) - using the RCU.

What do you see there ? Do you have IP, MASK and DNS assigned ?

Mastering the Linux process, for installing any new service (binary file) is unprecedented :).

The Linux installation-way will work anytime and anywhere... and under any circumstances.

During the installation via the Linux Shell, if something does not work, you will immediately find out what does not work and why.

IPKs are packages made up of different (random) people, often people without a good knowledge of Linux.

IPK is just an installation package and nothing more. The IPK should ensure that everything is "done automatically per user".

There are already a lot of IPK packages on the internet today, but almost half of them may not work (fit) in your Enigma2 distribution unless they come from a feed-server designed specifically for your Enigma2 distribution.

Very often, users use these IPK packages downloaded from the internet. But these IPK packages are not always universal (so-called "_ALL"). Even if it is an IPK package that is designed for "all" ("_ALL") Enigma2 distributions and for all CPU/chipset architectures, there may still be a problem. And there can be many of these problems ! For example: The IPK package will include an Oscam binary file that was compiled without USB external reader support or without SSL support. But what then, if the user needs these modules in Oscam ? He must then look for another IPK package ? :) It's really complicated. Unfortunately, Linux is not Windows :). Although Linux appears to be a universal OS, the opposite is true.

The manual installation method using a binary file is quick and easy. You don't even need a feed server. BTW, many Enigma2 distributions, even on the feed server do not even have Softcams packages. Even then, you must use the manual Softcam installation procedure.

Running the right Softcam in a set-top box is often accompanied by many problems.

You may also update your Enigma2 distribution and Softcam will immediately stop working. Even then, you have to use the Linux Shell again to find out why your Softcam doesn't start. If you have your init.d script ready and you know where the binary is, then you can easily find out why it doesn't start.

Some IPK packages may have forced directory settings for softcam configuration files. Then, when you reinstall Softcam or use a different IPK package, the default directories for configuration files can be used there. But the newly-launched Softcam will not find your previous / alternate configuration directory.

It could take a long time ... there are really many causes and problems with Softcam startup.

The average user will usually not encounter problems. If a problem also arises, it will be solved, for example, through a discussion forum and then it will definitely forget about its troubles.

I have personally dealt with X cases of a malfunctioning Softcam start on set-top boxes. Thanks to the Linux Shell, I have always solved everything. Even less experienced users can then write a question to the discussion, with the error message in the Linux Shell.

////// EDIT :

I would like to add, that some users (although in my view it is nonsense) also requires running multiple Softcams at the same time, on one Linux set-top box. And in this case, again, the knowledge of manual installation of the service (its auto-start) will serve best. Many IPK packages do not address these ideas at all.

If you want to install 2 x OSCam, it will simply overwrite the original, including the default configuration + without backing up the original configuration... because most IPK packages are really primitive (without an intelligent algorithm in the installation script).

However, this also applies to the installation of two different Softcams (for example Oscam + Ncam). Many "Softcam-Panels" for managing Softcams in GUI / SKIN do not allow to start, several Softcams at the same time.

Since I also mentioned the lost Softcam configuration, this is also a common problem for users if they use IPK. Users reinstall the IPK package, but often forget to back up their own Softcam configuration. This configuration is usually silently overwritten, the default configuration, after a new IPK package is installed. Therefore, again, the advantage is to stop the Softcam service, swap the binary in Linux, and restart this Softcam service.

As you can see ... the method of manual installation of the Softcam service ultimately has a lot of benefits.

You're welcome.

BTW ... in the case of OpenATV Enigma2, you can also use a boot shell-script: "/usr/bin/enigma2_pre_start.sh". However, not all Enigma2 distributions use this shell-script. You also need to keep in mind that this shell-script runs every time Enigma2 starts.

While the "init.d" scripts run through the Linux system directly - i.e. during boot of the set-top box (regardless of the Enigma2 GUI) - during the boot into Run-Level-3.

Note 1:

If you create a new shell-script (if does not exist) then you must to assign the execution attributes - with the command chmod a+x /path-to-file, or set the value of the file attributes to 755 using the FTP client.

Note 2:

Also, keep in mind that for all shell-scripts, you must always use with the Unix/Linux line ending (LF). Not the Windows (CR + LF) line ending.

Hi.

This should be set via Anti-Cascading:

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

But I think that's difficult.

You need to activate the Anti-Cascading function first and set it:

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

It is also possible to limit the number of requests to your card reader. But you have to know exactly what you're doing. You need to know your decoding system. This will limit the number of ECM requests beyond a certain time limit. Also, it is not applicable to any decoding system.

I mean something like this:

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

Or... simply... I mean the follwing entries, in the "oscam.server" file:

(values are fictitious !!! it was just an attempt for Irdeto's coding system !!!)

ratelimitecm                  = 4
ratelimittime                 = 9000
ecmunique                     = 1
srvidholdtime                 = 2000
cooldown                      = 30,600

With different decoding systems, it is possible to use different (another) methods to limit TV channel switching.

Hi.

It's not complicated. This is a system of "init.d" control shell-scripts (start / stop / restasrt), depending on the current Linux run-level.

I recommend you take a look at my "init.d" script, designed to run Softcams: https://github.com/s3n0/e2scripts/blob/master/softcam

You will find all general information there at the beginning of this shell-script. You can, of course, delete the contents of the script and use your own code.

The important parameters (arguments) used for the $1 "init.d" script are: start, stop and restart. The original "init.d system", which you can find on the internet, uses more input arguments, not just these 3 arguments (start | stop | restart). Also the output exit code from the "init.d" script has its meaning. Therefore, if no error has occurred, it is recommended to exit the init.d script with a zero error return code, i.e.: exit 0.

In the case of Linux Enigma2 set-top boxes, the very common rules and standards do not apply to these init.d scripts ... but many of them also apply to Linux set-top boxes, where a bit truncated Linux is used.

Once you have created your init.d script and placed it in the "/etc/init.d" folder, then a sym-link must be created to the appropriate Run-Level. Most Enigma2 set-top boxes use the main Run-Level number 3. Therefore, you need to create a sym-link from your "init.d" script as a file, just to the "/etc/rc3.d" folder. However, this sym-link in the "/etc/rc?.d" folders must have the prescribed form. This information can also be googleed on the internet :) - for example: https://man.cx/init.d - I mean the shape and meaning of numbers and letters, in a sym-link, created for a specific "init.d" script.

Of course, your "init.d" script must have an execution attribute assigned to it. For example, using with the Linux-Shell:

chmod a+x /etc/init.d/your_script

And that's about it.

You can test the auto-start of your "init.d" script, for example, by restarting the set-top box:

reboot

If something doesn't work for you, feel free to write and ask.

"How-to init.d scripts" can also be Googleed ;-).

///// EDIT:

One more note:

All "init.d" scripts should also be terminated regularly ! For example, with the command exit 0, or in the event of an error, the corresponding other error code according to the "init.d" standard. Otherwise, booting may remain stuck on this init.d script if it did not complete successfully. If you need to run something "in the background", so this can also be done, with the help of appropriate tools / commands, directly in your init.d script.

Uhm...

As far as I know, these problems are with Dreambox and Qviart Lunix. These vendors give very little support for their hardware in terms of open-source Enigma2 distributions (firmware).

Not in the case of Vu+, which does not update the HW drivers for open-source set-top boxes (for Linux) too often, but still updates them.

After all, according to what you write, then there will be no current HW drivers also for the Enigma2 distribution - VTi. And that's hard to believe.

But I dont know. Maybe I'm wrong. I'm not at all involved in Enigma2 compilations or creating Enigma2 distributions.

Vu+ ? Really ? Didn't you get it wrong with the Dreambox manufacturer? :)

Vu+ is a team of developers who escaped from Dreambox development and founded their own company Vu+. Also so that open-source code can continue. But maybe I'm wrong. Sorry if I'm wrong. I just "heard" that.

Hi.

As master G wrote, it depends on how much your budget is.

If you want more expensive quality set-top boxes, then definitely buy Dreambox (closed firmware / system with limited options if you want to make adjustments in the system or plugins).

Or also good, expensive, quality set-top box is Vu+ (open system with the possibility of installing any Enigma2 open-source distribution).

If you want cheap and good set-top boxes, try to look for brands such as:

Octagon, Qviart Lunix, Zgemma, Formuler, Gigablue

Init.d has its prescribed standard on Linux systems. If you restart or shut down the Linux, there is sent the "stop" argument, to the "init.d" scripts, at the appropriate Linux run-level. But you don't have this argument, treated inside the init.d script. So, your "script" is not a clear init.d - script.

It's like booting a Linux router with a 21st century chipset, using a Floppy 3.5" magnetic disk drive (1.44 MB capacity disk) instead of using internal flash memory. It can be done. The question is whether it matters at all.

Keep at least the minimum init.d standard please !

In a full-fledged Linux op. system (for example, Ubuntu Linux on a desktop / workstation PC), of course, there are a many other features, that do not exist in Linux set-top boxes. But the start and stop argument is used and exists also in older Linux set-top box.

The start / stop / restart arguments may not be handled inside the scripts... in some special cases... but not in the case of the Softcam. If you run Softcam twice in a row, you will create unnecessary problems (because the same configuration directory and the same card reader will be used). It can end up with many different and unforeseen crashes.

Do it the way what you think, it's your business. :)

Good Luck.

Hi.

Script files in the "/etc/init.d/" folder are also called when Enigma2 is stopping and not only when Enigma2 is starting. It's not good if there is only one command in the "init.d" script - to run Oscam. Or do you want another Oscam to run again and again during the shutdown (stopping) of Enigma2 ? :)

You should have the arguments there for the start and stop services... for example:

#!/bin/sh

case "$1" in
      start) /var/bin/oscam-svn11704-sh4-webif-dvbapi -b -r 2 ;;
       stop) killall -9 oscam-svn11704-sh4-webif-dvbapi ;;
    restart) $0 stop; sleep 1; $0 start ;;
          *) echo "Usage: $0 {start|stop|restart}"; exit 1 ;;
esac

exit 0

Or you can download and use my softcam script, directly from my github (https://github.com/s3n0/e2scripts/blob/master/softcam), as described in the article for manually installing the Softcam :-P. However, the binary file must then be renamed:

mv /var/bin/oscam-svn11704-sh4-webif-dvbapi /var/bin/oscam
chmod a+x /var/bin/oscam /etc/init.d/softcam

It is also very important to remember that the created script file must contain UNIX / LINUX (LF only) line endings and not WINDOWS (CR + LF) :).

The ___how_to_manual_installing_Oscam.txt file now contains some info about installing on the "systemd" method ... and not only "init.d" method.

The "systemd" method is used in Enigma2 distributions, which are based on the new Enigma2 core - close to the original Dreambox. Or on Enigma2 distributions that come from Dreambox. But, of course, open-source Enigma2 distributions usually use the "init.d" method.

Hi.

There are several methods.

You should also write down which Enigma2 distribution you use (OpenPLi, OpenATV, OpenHDF, Pure2, DreamOS, etc ...). The method of installation may depend on the Enigma2 used.

Anyway, if you get a binary oscam file for your Enigma2 (DM7020HD V2 includes a mipsel chipset), then the manual installation procedure should work. However, it is intended for advanced users only:

Article

Tutorial : How to install softcam (OSCam/CCCam) manually, if you hate ipk packages

OMG ... don't use IPK packages. Don't be lazy to learn something. Use the manual installation method to install SoftCams like OSCam or CCcam.

s3n0

May 1st 2019

Another method could be to use an IPK installation package. You copy this IPK file with Oscam to the "/ tmp" folder via an FTP connection on your LAN (using for example the FTP client in TotalCommander). You then start the IPK package via a terminal connection (Linux Shell) or directly via the GUI MENU in Enigma2 with the help of RCU (not every Enigma2 allows you to install IPK from an external source).

Hi.

Of course, a "connecting error" represents 90% of a network communication error.

So you could look for a mistake at the beginning, right there ;-).

Hi.

"Oscam go to error" - is a primitive error description. Please paste the copied error directly from OscamWebif -> LiveLOG (copy+paste text from LiveLog here - into the CODE TAG).

What kind of CAID do you actually use ? Or at least write the name of the provider and the country of the provider.

The error can be anywhere, uhm.

atari uses very versatile configuration oscam files, which are far too customized for a specific Oscam situation. So they may not always be 100% usable and reliable. A universal and clean configuration for Oscam, for example, is this: RE: Rai1 HD freezing box (download the zip-attachment).

Delete the original configuration files from the folder (back them up !). Then upload new and clean configuration files from the ZIP archive there. Edit the required remote card reader (CCCAM protocol) in them - in the "oscam.server" file, as you need. Finally, restart Oscam. And try it, that Oscam will work this way.

If the errors persist, insert a OscamWebif -> LiveLog entry here (use the CODE TAG in the discussion forum).

Of course, Linux (Enigma2) set-top boxes can also be managed (configured) remotely.

If you have a VPN server, you can connect all your Linux (Enigma2) set-top boxes to it. Then you don't need to set up a router or have a public Internet IP address to connect. If you do not have a VPN created, then you must have a public Internet IP and set up port forwarding on the router.

It is possible to use interactive video via OpenWebif (as LIVE screenshots from the screen output on the set-top box) + at the same time use the graphic RCU in OpenWebif. Best of all, it's probably using this OpenWebif (port 80, IP address of the set-top box, HTTP protocol, via any web browser). Of course, the end user will see what you are doing on the TV / LCD if you use this set-top box configuration method.

There are really many possibilities. After connecting via Telnet / SSH (terminal connection - at ports 22 and 23), you can use the console. Through the console, you can install various packages through the OPKG - package manager.

In many cases, you can also change the configuration of plugins and Enigma2 by editing the "/etc/enigma2/settings" file. However, when Enigma2 is stopped (with the command "init 4" you stop Enigma2 and use "init 3" to restart Enigma2).

It's all a bit complicated. I'm sorry, but if you have to ask these basic things and if you don't control the Linux Shell or you can't connect to the set-top box via the terminal, you probably won't be able to do your goal - remote control / configuration of the set-top boxes.