OScam Setup on Enigma2 & Dreambox

Enigma2 is the most widely used operating system for Linux-based satellite receivers, powering popular brands like Dreambox, VU+, GigaBlue, Formuler, Mutant, and many others. Installing OScam on these receivers is a straightforward process that can be accomplished through the built-in software manager or via manual installation over FTP or SSH. This guide covers both methods and walks you through the complete configuration process to get OScam running on your Enigma2 device.

Compatible Receivers and Requirements

OScam runs on virtually all Enigma2-based receivers, regardless of the chipset manufacturer. Whether your receiver uses a Broadcom, HiSilicon, or ARM-based processor, there is an OScam build available for it. The key requirement is that your receiver runs an Enigma2 firmware image, which is the standard for most Linux satellite receivers. Common compatible firmware distributions include OpenATV, OpenPLi, OpenViX, Pure2, and VTi among others.

Before installing, verify that your receiver has network connectivity, as OScam needs an active internet connection to communicate with remote cardsharing servers. You will also need either FTP or SSH access to the receiver for transferring configuration files. Most Enigma2 images come with both services enabled by default. The default login is typically root with no password or the password set during initial setup.

Installing OScam via Software Manager

The easiest installation method is through the Enigma2 software manager, also known as the plugin browser. Navigate to your receiver's main menu, then go to Setup, Software Management, and finally Plugin Browser or Install Extensions. From there, look for the softcam section, which typically contains OScam packages. Select the appropriate OScam package for your receiver and confirm the installation. The system will download and install OScam automatically.

Some firmware images include a dedicated softcam manager plugin that makes it even easier to switch between different softcams. After installing OScam through the package manager, you may need to install a softcam manager if one is not already present. This allows you to start, stop, and switch between softcams directly from the receiver's menu without needing command-line access. Popular softcam managers include SoftcamManager, CamManager, and the built-in softcam control panel found in images like OpenATV.

Manual Installation via FTP or SSH

If OScam is not available in your receiver's package manager, or you need a specific version, manual installation is the alternative. First, download the correct OScam binary for your receiver's architecture from a trusted source. The binary must match your receiver's processor architecture, which is usually MIPSEL for older Dreambox models or ARM for newer receivers.

Connect to your receiver via FTP using a client like FileZilla or WinSCP. Upload the OScam binary to /usr/bin/ and set the file permissions to executable (chmod 755). If you prefer SSH, connect to the receiver's terminal and use wget to download the binary directly. After placing the binary, you need to make it executable and create a startup script so that OScam launches automatically when the receiver boots. The configuration files should be placed in /etc/tuxbox/config/ which is the default configuration directory on most Enigma2 systems.

Creating the Configuration Files

OScam requires three primary configuration files to operate. The first is oscam.conf, which handles global settings including the web interface, protocol listeners, and logging. For a basic Enigma2 setup, your oscam.conf should include a global section, a webif section for the web interface, and protocol sections for whichever protocols your servers use. Enable the DVB API module, which is essential for communicating with the receiver's tuner hardware to descramble channels.

The second file is oscam.server, which contains your reader definitions. If you are migrating from CCcam, each C-line becomes a reader block with protocol = cccam. You can use our online converter to generate these reader blocks automatically from your C-lines. The third file is oscam.user, which defines user accounts for local access and any downstream sharing.

DVB API Configuration for Enigma2

The DVB API is what connects OScam to the Enigma2 tuner system. It must be enabled in oscam.conf for descrambling to work on the receiver itself. The DVB API section should be configured with the appropriate parameters for your specific receiver model. Most modern Enigma2 receivers work well with the default DVB API settings, but some older models may require specific adjustments to the user, AU, and boxtype parameters.

If you are using OScam solely as a client on the receiver without sharing to other devices, the DVB API user should match the username defined in your oscam.user file. This user must have access to the reader groups that contain your server connections. Getting this mapping right is essential; if the DVB API user does not have the correct group assignments, the receiver will not be able to access any readers and channels will remain scrambled.

Starting OScam and Verifying Operation

After placing all configuration files in the correct directory, start OScam using the softcam manager or via SSH command. Open a web browser on your computer or phone and navigate to your receiver's IP address followed by the web interface port (default is 8888) to access the OScam status page. Check that all your readers show as connected with green indicators. If any readers show errors, check the log section of the web interface for detailed error messages.

Tune to an encrypted channel on your receiver and observe the OScam web interface. You should see ECM requests being processed by one of your readers. The channel should descramble within a few seconds if everything is configured correctly. If you encounter issues, common causes include incorrect file permissions on the OScam binary, wrong configuration file path, or network connectivity problems. For detailed troubleshooting, refer to our OScam error codes guide.