How to set up a cheap card sharing server in 2026: a step-by-step guide

Card sharing allows one paid smart card to service multiple satellite receivers over the internet. With proper setup, monthly server costs can be kept within 5–10 euros without sacrificing reception stability. Below is a detailed guide from choosing equipment to final signal testing.

What is card sharing and how does it work

A smart card inserted into a receiver or a special reader decrypts the control word (Control Word, CW) — a short key that changes every few seconds. The card sharing server intercepts this word and distributes it to client receivers over the network. Each client uses the received CW to decode the signal in real time.

Protocols for transmitting CW:CCcam — the most common, supported by most budget receivers;Newcamd — older, but compatible with almost all devices;CS378x (Camd35) — used in some OpenATV and E2 firmware.

Minimum server requirements

Hardware

To service up to 10 clients, the most modest hardware is sufficient. Optimal options in 2026:

  • Raspberry Pi Zero 2W — costs about 15 euros, consumes 0.4–1 W, operates silently. Sufficient for 5–8 clients with stable internet.
  • Orange Pi Zero 3 — about 20 euros, quad-core Cortex-A53, 1 GB RAM. Confidently handles 15–20 simultaneous connections.
  • KVM-based VPS — from 3 euros per month with providers like Hetzner Cloud (CX11: 1 vCPU, 2 GB RAM). Does not require a separate card reader if the card is already with the partner.

To connect a physical card to a single-board computer or home PC, you will need aUSB smart card reader. Models like Omnikey 3121 (~12 euros) or ACS ACR38 (~10 euros) are suitable — both are supported by OSCam without additional drivers.

Software

Two main tools:

  • OSCam — open source, actively supported, supports CCcam, Newcamd, CS378x protocols simultaneously. Recommended as the primary solution.
  • CCcam — proprietary, has not been updated since 2012, but still works on outdated Dreambox receivers.

Installing OSCam on Raspberry Pi / Debian-compatible system

Step 1: Basic system setup

Write Raspberry Pi OS Lite to the memory card (minimum Class 10, 8 GB). After the first boot:

sudo apt update&& sudo apt upgrade -y

Check if the system sees the card reader:

pcsc_scan

If the name of your card appears in the output (for example,SAGEM F ST IP 2 for the Canal+ card), the reader is recognized correctly.

Step 2: Compiling OSCam

We compile OSCam from source with support for the required protocols:

git clone https://github.com/oscam-emu/oscam-emu.git

An alternative is to download a ready-made binary from oscam.to, selecting the build for your architecture (arm-linux-gnueabihf for RPi).

Step 3: Configuration files

OSCam uses several configuration files in/usr/local/etc/oscam/.

oscam.conf — global settings:

[global]

oscam.server — description of your reader:

[reader]

The valuecaid andident depends on your provider. For example, for Viasat/TV Vlaanderen:caid = 0604; for Sky Deutschland:caid = 09C4.

oscam.user — client accounts:

[account]

The parameteruniq = 2 prevents simultaneous login from one account — protection against unauthorized sharing of your server.

Step 4: Launch and autostart

sudo mkdir -p /var/log/oscam

To enable autostart, we create a systemd unit in/etc/systemd/system/oscam.service:

[Unit]
sudo systemctl enable oscam

The web interface will be available athttp://<server IP>:8888.

Setting up the client receiver

Enigma2 (OpenATV, OpenPLi, OpenVision)

On receivers with Enigma2 (Formuler F1, Vu+ Duo4K, GigaBlue Quad 4K), install the pluginCCcam or the client partOSCam through the built-in package manager:

  1. Menu → Plugins → Load plugins → Searching (searchoscam)
  2. After installation, edit/etc/oscam/oscam.server on the receiver:
[reader]

Receivers with CCcam firmware

For Dreambox DM800 or clones, open/var/etc/CCcam.cfg:

C: yourserver.example.com 12000 client01 pass123

Restart CCcam via the menu or with the commandkillall -HUP CCcam.

How to reduce server costs to a minimum

Choosing a cheap hosting

If the physical card is already connected with a reliable partner, the server-retransmitter can be set up on a minimal VPS. Current prices as of July 2026:

  • Hetzner CX11 (Germany/Finland) — 3.29 €/month, 1 vCPU, 2 GB RAM, 20 GB SSD. Perfect for 10–15 clients.
  • Netcup RS 1000 G10 (Germany) — 2.69 €/month when paid annually. 2 vCPU, 2 GB RAM.
  • Contabo VPS S — 4.50 €/month, 4 vCPU, 8 GB RAM — excessive for card sharing, but sufficient for other tasks.

For European channels (Astra 19.2E, Hotbird 13E), servers in Germany, the Netherlands, or Austria are preferable — minimal latency to the satellite beam.

Traffic and resource optimization

One client watching an HD channel generates about 2–4 KB/s of CW traffic. A hundred clients — no more than 400 KB/s of outgoing traffic. Even the cheapest VPS with 1 TB of included traffic will not exhaust the limit in a year of operation.

To reduce CPU load, enable CW caching inoscam.conf:

[cache]

Security and stability of operation

Protection of the server from unauthorized access

The standard CCcam port is 12000. It is better to change it to a non-standard one (for example, 34521) so that automatic scanners do not find the service:

[cccam]

Additionally, restrict access through UFW:

sudo ufw allow from 192.168.1.0/24 to any port 34521

For remote clients with dynamic IPs, use a CAID whitelist instead of IP addresses.

Monitoring and automatic recovery

OSCam can automatically restart a hung reader. Inoscam.server:

resetcycle = 10

This parameter causes OSCam to reset the reader after 10 consecutive card read errors. For additional safety, set up an external watchdog via cron:

*/5 * * * * systemctl is-active oscam || systemctl restart oscam

Typical problems and their solutions

The card is not recognized by the system

Make sure the pcscd service is running (sudo systemctl status pcscd). If the reader is recognized throughpcsc_scan, but OSCam does not see the card, check the correctness ofcaid inoscam.server. For diagnostics, enable detailed logging:

[global]

The client connects, but the channel is not decoded

The most common reason is a CAID mismatch between the server and the client. Open the OSCam web interface (:8888), go to theUser Info section and check theLast found column — it shows the last successfully decoded CAID. Compare it with what the receiver requests in the log.

High CW delay (>400 ms)

A delay above 350–400 ms leads to brief image freezes. Check the ping to the server (ping yourserver.example.com). If the ping is normal (<80 ms), the problem is with the reader — replace the USB hub or try another port. Inoscam.server add:

mhz = 600

Increasing the card's operating frequency reduces the reader's response time by about 15–20%.

Legal aspect of using card sharing

Legislation in EU countries interprets card sharing differently. In Germany and Austria, transmitting CW to third parties without the rights holder's permission is classified as a copyright infringement and may lead to a civil lawsuit. In the Netherlands and Belgium, case law is less clear-cut, but major providers actively sue operators of commercial sharing servers. Using card sharing exclusively within one's own household (one subscriber, multiple receivers) is not prosecuted in most countries.

Alternatives to physical card sharing in 2026

If setting up your own server seems excessive, consider ready-made solutions. Legal IPTV services likeUtgard.tv provide access to European satellite packages via the internet without the need to buy a smart card, reader, and rent a server. The cost is comparable to renting space on a sharing server, but without the technical hassle and legal risks.

Another option —official provider applications: Canal+ App, Sky Go, Viaplay. They support simultaneous viewing on 2–4 devices with one subscription, which effectively solves the card sharing issue through legal means.

Final list of costs for a minimal server

  • Raspberry Pi Zero 2W — one-time purchase ~15 €
  • USB reader ACS ACR38 — one-time purchase ~10 €
  • MicroSD card 16 GB — one-time purchase ~5 €
  • Internet channel with static IP or DDNS — from 0 € (if already available at home)

In total, the initial investment will be about 30 euros. If using a VPS instead of a home single-board computer, add 3–5 euros per month for hosting. Against this background, ready-made legal IPTV packages for 8–12 €/month often turn out to be more cost-effective considering the time spent on setting up and maintaining 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.