Card sharing: setting up the receiver in 2026 — a detailed guide

Card sharing allows access to encrypted satellite channels without a physical smart card in the receiver. The server decrypts the signal and sends the keys over the internet to your receiver. In 2026, the scheme still works on most popular receivers with Enigma2, OpenATV, and TiViAmo firmware, however, the setup process has become slightly stricter due to updates in encryption protocols by several providers.

In this article — a step-by-step setup for the three main emulators: CCcam, MGcamd, and Oscam. Each section contains specific examples of configuration files, and at the end — an analysis of typical errors with explanations of the reasons.

What is card sharing and how does it work

Satellite television is encrypted by conditional access systems — Nagravision, Viaccess, Irdeto, Conax. A smart card with an active subscription is required for decryption. In card sharing, one card is inserted into a central server, which generates a Control Word (CW) every few seconds — a 16-byte key. This key is transmitted to client receivers over an encrypted channel, where the emulator inserts it into the decoder.

The delay in key transmission is critical: if the CW does not arrive on time, the screen freezes or shows artifacts for 1–2 seconds. A good server keeps the ping to the client within 50–150 ms and updates the key 100–200 ms before the previous one expires.

How CCcam differs from Newcamd and Oscam

CCcam — a proprietary protocol developed by the Dream Multimedia team. It is supported by almost all receivers based on Enigma2. The configuration is stored in one file/etc/CCcam.cfg. Disadvantage: the protocol is outdated, and several servers have switched only to Oscam.

MGcamd works on top of the Newcamd protocol. Less common, but on some servers provides a more stable connection with Irdeto and Conax cards. Config:/etc/newcamd.list.

Oscam (Open Source Conditional Access Module) — the most flexible emulator. It supports several protocols simultaneously, has a built-in web interface on port 8888, and maintains detailed statistics. In 2026, most major sharing servers operate on Oscam.

Which receiver is suitable for card sharing

Not every satellite receiver supports emulators. Below is the current list of equipment tested in 2025–2026.

Receivers on Enigma2

  • VU+ Uno 4K SE — one of the most popular options in 2026. Supports Oscam, CCcam, MGcamd out of the box via the plugin manager. OpenATV 7.4 firmware.
  • GigaBlue Quad 4K — a budget alternative to VU+. Works on OpenATV and Gemini Project. CCcam is installed via the pluginCCcam Info.
  • Dreambox DM900 UHD — the flagship of the series. Supports all three emulators, has a built-in CI slot for parallel use of the card.
  • Formuler F4 Turbo — a new product of 2025. Enigma2 firmware OoZooN, Oscam support confirmed by users of the Sat Universe forum.

Receivers with TiViAmo and OpenPLi firmware

OpenPLi 9.0 and TiViAmo 5.x firmware also support card sharing through the same emulators. The difference is in how plugins are installed: OpenPLi uses the package manageropkg, while TiViAmo has its own plugin store.

Installing Oscam in OpenPLi via SSH:

opkg update

Setting up CCcam on an Enigma2 receiver

CCcam — the easiest option to set up. The provider gives a username, password, server address, and port.

Step 1: Installing CCcam

Open the receiver, go to the menuPlugins → Load plugins → Softcam. SelectCCcam 2.3.2 (the current version for 2026). After installation, the plugin will appear in the sectionSoftcam Panel.

Step 2: Editing CCcam.cfg

Connect to the receiver via SSH (username: root, default password: dreambox or empty). Open the file:

nano /etc/CCcam.cfg

Add the server connection line in the format:

C: server.example.com 12000 mylogin mypassword

Where12000 — port,mylogin andmypassword — data received from the provider. One file can contain multiple linesC: for different servers — CCcam will cycle through them if the main one is unavailable.

Step 3: Restarting the emulator

Save the file (Ctrl+O, Enter, Ctrl+X) and restart CCcam:

init 4&& init 3

Or through the receiver menu:Softcam Panel → CCcam → Restart.

Configuring Oscam: detailed instructions

Oscam is more complex to configure but offers more control. The configuration is split into three files:oscam.conf,oscam.server,oscam.user.

Basic configuration of oscam.conf

The file is stored in/etc/oscam/ or/usr/keys/ — depends on the firmware. Minimum working config:

[global]

After starting Oscam, the web interface will be available athttp://192.168.1.XXX:8888, where XXX is the IP of your receiver in the local network.

Configuration of oscam.server for connecting to the card sharing server

This file describes the servers that Oscam connects to. For the Newcamd protocol:

[reader]

For the CCcam protocol through Oscam (cccam client):

[reader]

The parametercaid indicates the encryption system:0500 — Viaccess (NTV+, Tricolor),0D00 — Cryptoworks,1800 — Nagravision,0B00 — Conax.

Configuration of oscam.user for the local emulator

This file is needed if Enigma2 accesses Oscam as a local server (which happens when installing Oscam as a softcam):

[account]

Connecting Enigma2 to local Oscam

In the file/etc/CCcam.cfg or through the pluginSoftcam Panel specify Oscam as the active softcam. Oscam itself creates a compatible interface with Enigma2 via the camd.socket protocol.

Configuration of MGcamd via Newcamd

MGcamd uses the file/etc/newcamd.list. Connection string format:

CWS = server.example.com 15050 mylogin mypassword 01 02 03 04 05 06 07 08 09 10 11 12 13 14

The sequence of 14 bytes is a DES key provided by the provider along with the username and password. If the provider issues the key as a string0102030405060708091011121314, it needs to be split into pairs of characters with spaces.

After editing the file, restart MGcamd similarly to CCcam — via SSH or Softcam Panel.

Typical setup errors and their causes

The screen freezes every 10 seconds

This is a symptom of high latency or an unstable connection to the server. Check the ping to the server:

ping server.example.com

If the ping is above 300 ms — the problem lies in the route or server overload. Ask the provider for an alternative address. Also, check if you have double NAT — a receiver behind a router, which in turn is behind the provider's router.

Error "Wrong password" in CCcam logs

Check the encoding of the fileCCcam.cfg. If you edited the file in Windows Notepad, it may have been saved in UTF-8 with BOM or with Windows line endings (CRLF instead of LF). Use Notepad++ and set the formatUnix (LF), or convert it via SSH:

sed -i 's/ //' /etc/CCcam.cfg

Oscam starts, but channels are not decrypted

Go to the Oscam web interface (:8888) and open the tabReaders. If the reader status showsOFFLINE — there is a problem with the connection to the server. IfCONNECTED, but the channels still do not work — there is a CAID mismatch. Check what CAID your channel package uses and compare it with thecaid parameter inoscam.server.

After the firmware update, the emulator stopped working

Some firmware updates overwrite files in/etc/. It is recommended to keep a backup of configuration files on a USB drive or in the/media/usb/ directory, which is not affected during updates. For Oscam, it is especially important to keep the entire/etc/oscam/ folder.

Choosing a card sharing provider in 2026

When choosing a server, it is worth paying attention to several parameters.

Supported packages and encryption systems

Make sure the server supports the package you need. For example, Tricolor TV uses Viaccess 5.0 (CAID 0500), NTV+ also uses Viaccess, and some European packages use Nagravision 3 (CAID 1843). A good provider specifies the exact list of supported CAIDs in the tariff description.

Stability and uptime

Request uptime statistics from the provider for the last 30 days. A reliable server maintains uptime above 99%. Some providers publish a real-time status page — this is a good sign.

Trial period

Most servers offer trial access for 24–72 hours. Take advantage of it to check the quality of decryption specifically on your channels and with your equipment before paying for a subscription.

Additional settings for stable operation

Traffic priority on the router

If the internet channel is congested, packets from the sharing server may arrive with delays. Configure QoS (Quality of Service) on the router: set a high priority for traffic from the IP address of the card sharing server or for ports 12000–15100 (a typical range for CCcam and Newcamd).

Auto-start emulator after reboot

In firmware based on OpenATV, emulators start automatically if installed via the plugin manager. If you installed Oscam manually, add the line to/etc/rc.local:

sleep 10&& /usr/bin/oscam -b&

A 10-second delay is needed for the network interface to come up before starting Oscam.

Backup server

Configure a second reader inoscam.server with the parametercccmaxhops = 1 and the same group. Oscam will automatically switch to the backup server if the main one is unavailable for more than 30 seconds.

Properly configured card sharing works for years without intervention. The main task after the initial setup is to monitor firmware updates for the receiver and timely renew the subscription on the server.

Practical checklist for smooth viewing

Even the best CCCam or OSCam line needs two or three simple preparations. Update your receiver firmware, reset the ECM cache once a week and keep 15–20% free space on the USB stick or internal flash so that the reader can store keys without delays.

When tuning a dish, aim for MER/BER reserve: a two‑degree offset or a loose F‑connector often causes the “freezing” that users blame on cardsharing. Keep a short patch cord to test alternative routers, and save two profiles in OSCam — one for TCP, one for UDP — so you can switch instantly if your ISP starts filtering a protocol.

Utgard.tv monitors each hub 24/7, but you can speed up diagnostics by keeping a short log of your receiver actions. Note the time when you changed the channel, which CAID was active and whether you used Wi‑Fi or Ethernet. This tiny “journal” helps engineers reproduce your environment in the lab and return with a solution in minutes instead of hours.

  • Keep two line slots enabled: if the first server hits a maintenance window, the second one instantly takes over without re-entering credentials.
  • Run a monthly speed and latency test. Stable 1–2 Mbps with ping <80 ms is enough for SD/HD, but if jitter exceeds 20 ms, switch the router to wired mode.
  • Save the Utgard.tv status page and Telegram bot @utgard_sharing_bot to bookmarks — they publish maintenance notices before SEMrush or uptime monitors raise alerts.