Cardsharing server: principle of operation, selection and connection

Cardsharing is a technology for sharing a smart card for satellite television over a network. One physical subscription allows multiple users connected to a common server to access encrypted channels. For the owner of a satellite receiver, this means the ability to watch packages from Viasat, NTV-Plus, Tricolor, or Canal+ without purchasing a separate subscription for each device.

What is a cardsharing server and why is it needed

A cardsharing server is a software-hardware node that receives a control word (Control Word, CW) from a real smart card and distributes it to clients over the network. The control word is a short key of 8 bytes that changes every 10 seconds and is used to decrypt the video stream. Without the current CW, the picture on the screen turns into colored noise.

In practice, the scheme looks like this: the server owner has a subscribed smart card inserted into a reader connected to a computer or specialized device. The program (for example, OSCam or CCcam) reads incoming ECM requests from client receivers, sends them to the card, receives a response, and sends the CW back to the clients. The entire cycle takes 50–150 milliseconds — with a good connection, the user does not notice any delay.

How cardsharing works: the technical side

Protocols CCcam and Newcam

The two most common protocols for cardsharing — CCcam and Newcam (N2) — operate on a similar principle but have different implementation features.

CCcam was developed by a team of German programmers and for a long time remained the de facto standard. The protocol uses a TCP connection and supports cascading — one server can receive cards from another server and pass them on. Version CCcam 2.3.0 supports traffic encryption, making data interception more difficult. A typical configuration file CCcam.cfg contains lines likeC: server.domain.com 12000 login password, where 12000 is the standard port for the protocol.

Newcam (NewCS/N2): a newer protocol with improved encryption based on AES. It is used less frequently but is considered more stable under high load. The default port is 15000. The OSCam software supports both protocols simultaneously, making it the preferred choice for the server side.

The role of OSCam in the cardsharing ecosystem

OSCam (Open Source Conditional Access Module) is an open-source emulator that works on both the server and client sides. On the server, it manages cards and processes incoming requests. On the client receiver (for example, Dreambox, Vu+, Enigma2), it acts as a software decoder, requesting CW from a remote server.

Key configuration parameters for the OSCam client in the oscam.server file:

• protocol = cccam — protocol selection
• device = server, port — server address and port
• user / password — credentials
• reconnecttimeout = 30 — waiting time before reconnecting
• cccversion = 2.3.0 — CCcam protocol version

Types of cardsharing servers

Paid servers with guaranteed stability

Paid servers provide services on a commercial basis. For a monthly subscription fee (usually from 3 to 15 USD), the user gains access to a pool of cards from specific satellite operators. Among the characteristics to pay attention to when choosing:

• Server uptime — reliable providers publish availability statistics, usually from 99% and above. A server with uptime below 95% will cause regular image freezes.
• Ping to the server — for comfortable viewing, values up to 100 ms are sufficient. Servers located in Western Europe provide a ping of 30–60 ms for users from Eastern Europe.
• Number of lines — one line allows watching one channel simultaneously. For a family with two televisions, at least 2 lines are needed.
• Supported packages — before payment, make sure the server works with the required operator: Viasat Ukraine, Sky DE, Canal+ PL, NTV-Plus, etc.

Free test servers: capabilities and limitations

Many providers offer a trial period from 24 hours to 7 days. Free public servers, which are often posted on forums, are usually overloaded: 200–500 clients per card lead to delays of 300–500 ms and frequent freezes. They are not suitable for full viewing, but are good for an initial check of equipment compatibility.

Permanent free servers exist in the form of private pools, where participants contribute their own cards and gain access to the cards of other participants. This is a P2P card sharing model — it requires having your own smart card and a stable connection.

How to choose a card sharing server: step-by-step analysis

Checking the provider's reputation

Before payment, study reviews on independent forums: Satforum, Digitalworld, Sat-brothers. Pay attention to the provider's registration date and the dynamics of reviews — a new account with exclusively positive comments should raise suspicion. Reliable providers have been operating for at least 3 years and respond to complaints publicly.

Technical parameters for comparison

When choosing a server, compare the following indicators:

• ECM time — the time taken to process a single decryption request. Optimal value: up to 150 ms. Values above 400 ms lead to visible artifacts when changing scenes.
• Share ratio — the ratio of the number of cards to the number of active clients. A value of 1:5 or lower is considered comfortable.
• Protocol and version — make sure your receiver supports the server's protocol. Most modern receivers on Enigma2 work with CCcam 2.1.4 and above.
• Backup servers — professional providers offer 2–3 backup addresses in case of technical work on the main one.

Trial period and refund

Always request a trial before payment. During the trial period, check performance during prime time (7:00 PM–11:00 PM Moscow time) — this is when the load on the servers is maximum and stability issues become apparent. If the provider does not offer a trial — this is a warning sign.

How to connect to a card sharing server

Connection on Dreambox and Enigma2 receivers

Receivers on the Enigma2 platform (Dreambox DM900, Vu+ Duo4K, GigaBlue UHD) support OSCam natively. Setup order:

1. Connect to the receiver via SSH (standard port 22, login root).
2. Open the file/etc/oscam/oscam.server and add the client section:

[reader]

3. Restart OSCam with the command/etc/init.d/oscam restart.
4. Check the connection status through the OSCam web interface on port 8888: in the Readers section, your reader's green status should appear.

Configuration on receivers with native CCcam

Receivers that work with the original CCcam software (for example, some models of Openbox, Formuler) require editing the CCcam.cfg file on a USB drive:

C: server.example.com 12000 mylogin mypassword

The file is saved in UTF-8 encoding without BOM, then inserted into the root of the USB drive and read by the receiver at boot. Some models support up to 5 servers simultaneously — CCcam automatically switches to the next one if the first is unavailable.

Common connection errors

The three most common problems after setup:

• Freezing every 10 seconds — a sign that the CW does not arrive in time for the next key update. Reasons: high ping, overloaded server, or incorrectly specified port.
• Channels are not decrypted (No ECM) — the server does not support this SID (Service ID) of the channel. Check with the provider whether the required channel is included in the package.
• Frequent reconnections — are usually related to port blocking at the router or internet provider level. Try an alternative port (for example, 443 or 80) if the server supports it.

Comparison of popular card sharing platforms

Satellite operators and supported encryption systems

Different satellite operators use different conditional access systems (CAS). Understanding this helps to correctly choose a server:

• Viasat (Irdeto 2) — cards are changed regularly, servers require constant updates. Irdeto is considered one of the most secure systems.
• NTV-Plus (Viaccess 3.0) — the Viaccess system is widely supported by OSCam and CCcam. Stable operation with most Russian servers.
• Sky Deutschland, Sky Italia (Nagravision 3) — Nagravision 3 (Nagra3) is one of the most complex systems for card sharing due to frequent card firmware updates.
• Canal+ (Mediaguard/SECA) — the SECA system is well supported by OSCam, Canal+ Poland and Canal+ France servers are common on European platforms.

Security and anonymity when using card sharing

Card sharing traffic is easily identifiable by characteristic patterns — regular small TCP packets every 10 seconds. Internet providers and the satellite operators themselves can use this for blocking or tracking. To reduce risks, the following practices are used:

• Connecting via VPN with servers in the same country as the card sharing server — reduces latency and hides the type of traffic.
• Using non-standard ports (443, 8080) — masks traffic as HTTPS or HTTP, which is filtered less frequently.
• Tunneling via SSH — complete encryption of traffic between the client and the server.

Frequently asked questions

How many clients can one server handle?

Performance depends on hardware and the number of cards. On a typical VPS with 2 CPUs and 2 GB RAM running OSCam, it is comfortable to serve 50–100 clients with 5–10 smart cards. Exceeding this threshold causes ECM time to start rising above acceptable values.

Does card sharing work with 4K channels?

Yes, the conditional access system does not depend on the resolution of the video stream. Card sharing works with HD and 4K UHD channels just as it does with standard resolution, provided the receiver supports the corresponding codec (HEVC/H.265 for 4K).

What is better — card sharing or IPTV?

These are fundamentally different technologies. Card sharing works with satellite signals through a dish and receiver — image quality is determined by the satellite stream (without losses during transcoding). IPTV delivers already encoded video streams over the internet and may suffer from buffering with an unstable connection. For maximum picture quality, card sharing via DVB-S2 remains the preferred option.