ICCCam Server & OSCam Client Configuration Guide

by Jhon Lennon 49 views

Hey guys! Let's dive into setting up an ICCCam server and configuring an OSCam client. This guide will walk you through the process, step by step, ensuring you get everything up and running smoothly. We'll cover the essentials and sprinkle in some tips and tricks to optimize your setup. So, grab your favorite beverage, and let's get started!

Understanding ICCCam and OSCam

Before we jump into the configuration, let's quickly understand what ICCCam and OSCam are and why they're used together.

ICCCam, often refers to a type of server used for card sharing. It's essentially a system that allows multiple clients to access a single satellite TV subscription. This is achieved by sharing the control words needed to decrypt the channels. ICCCam servers are generally used in conjunction with software like OSCam.

OSCam (Open Source Conditional Access Module) is a softcam, a software-based conditional access module. It's designed to decode encrypted channels and manage card sharing. OSCam acts as a client that connects to the ICCCam server to receive the necessary decryption keys. It's highly configurable and supports various protocols, making it a versatile choice for card sharing.

Why use ICCCam with OSCam? The combination provides a robust and flexible solution for managing card sharing. OSCam's advanced features and configuration options, coupled with the server capabilities of ICCCam, ensure a stable and efficient setup. This setup allows multiple devices within a network, or even remotely, to access the same subscription, reducing the cost and complexity of managing multiple subscriptions.

To put it simply: the ICCCam server hosts the card and shares its decryption keys, while the OSCam client requests those keys to decrypt the channels on your device. This symbiotic relationship is the core of card sharing.

Prerequisites

Before we get started, make sure you have the following:

  1. ICCCam Server: You need access to an ICCCam server. This might involve subscribing to a service or setting up your own server if you have a valid subscription card.
  2. OSCam Software: Download and install OSCam on your device. OSCam is available for various platforms, including Linux, Windows, and some set-top boxes. Make sure you download the correct version for your operating system.
  3. Device with OSCam Support: This could be a Linux-based set-top box, a Raspberry Pi, or a computer. Ensure your device is connected to the internet.
  4. Network Connection: Both the ICCCam server and the OSCam client need a stable internet connection to communicate.
  5. Text Editor: You'll need a text editor to configure the OSCam files. Notepad++ (Windows), Sublime Text (cross-platform), or Nano (Linux) are all good options.
  6. FTP Client (Optional): If you're configuring OSCam on a remote device, you'll need an FTP client like FileZilla to transfer the configuration files.

Having these prerequisites in place will ensure a smooth configuration process. Now, let's move on to configuring the OSCam client!

Configuring the OSCam Client

Configuring the OSCam client involves editing several configuration files. These files tell OSCam how to connect to the ICCCam server and how to handle decryption. The main files you'll be working with are oscam.conf, oscam.server, oscam.user, and oscam.dvbapi.

Step 1: oscam.conf

The oscam.conf file contains global settings for OSCam. This includes settings like the log file location, web interface port, and other general parameters. Here's an example oscam.conf file:

[global]
logfile = /tmp/oscam.log
pidfile = /tmp/oscam.pid
webifport = 8888
denyidentical = 1
netprio = 1
preferlocal = 1
saveinithistory = 1
unlock_parental = 1

[cache]

[dvbapi]
enable = 1
au = 1
decodeforever = 1

[webif]
enable = 1
httpuser = admin
httppwd = password
httphelplang = de
httprefresh = 10
httpallowed = 127.0.0.1,192.168.1.0-192.168.1.255

Explanation of Key Parameters:

  • logfile: Specifies the location where OSCam logs will be saved. This is useful for troubleshooting.
  • pidfile: Specifies the location where the OSCam process ID (PID) will be saved.
  • webifport: Sets the port for the OSCam web interface. You can access the web interface by navigating to http://your-device-ip:8888 in your web browser. Change 8888 to your desired port.
  • denyidentical: Prevents multiple clients from using the same account simultaneously.
  • netprio: Sets the network priority for OSCam.
  • preferlocal: Prioritizes local cards over remote ones.
  • saveinithistory: Saves the initialization history.
  • unlock_parental: Unlocks parental control.
  • enable = 1 under [dvbapi] turns on the DVB API which allows OSCam to communicate with your set-top box.
  • au = 1 under [dvbapi] enables automatic updates for your card.
  • decodeforever = 1 under [dvbapi] keeps channels open indefinitely.
  • httpuser and httppwd: Sets the username and password for the web interface. Change these to secure credentials!
  • httpallowed: Specifies the IP addresses that are allowed to access the web interface. Adjust this to match your network. 127.0.0.1 is localhost, and 192.168.1.0-192.168.1.255 allows access from your local network. Be careful when opening this up too widely!

Customization:

  • Change the httpuser and httppwd to strong, unique credentials. Never use the default values! This is a crucial security measure.
  • Adjust the httpallowed to restrict access to the web interface to your local network or specific IP addresses. This prevents unauthorized access to your OSCam configuration.

Step 2: oscam.server

The oscam.server file defines the connections to your ICCCam server. This is where you specify the server address, port, username, and password. Here's an example oscam.server file:

[reader]
label = ICCCamServer
protocol = cccam
device = your-icccam-server.com,12000
user = your-username
password = your-password
inactivitytimeout = 30
group = 1
cccversion = 2.3.2
ccckeepalive = 1

Explanation of Key Parameters:

  • label: A unique name for this server connection. You can choose any name you like.
  • protocol: Specifies the protocol used to connect to the server. In this case, it's cccam.
  • device: The address and port of your ICCCam server, separated by a comma. Replace your-icccam-server.com and 12000 with the actual values.
  • user: Your username for the ICCCam server. Replace your-username with your actual username.
  • password: Your password for the ICCCam server. Replace your-password with your actual password.
  • inactivitytimeout: The timeout in seconds for inactivity. If no data is received within this time, the connection will be closed.
  • group: The group this server belongs to. You can use this to prioritize servers.
  • cccversion: The CCCam protocol version. Make sure this matches the version supported by your server.
  • ccckeepalive: Sends keep-alive packets to maintain the connection.

Important Notes:

  • Replace the placeholder values (your-icccam-server.com, 12000, your-username, your-password) with your actual ICCCam server details. Double-check these values for accuracy!
  • The cccversion parameter is crucial. Using the wrong version can prevent OSCam from connecting to the server. Consult your ICCCam provider for the correct version.

Step 3: oscam.user

The oscam.user file defines the users that can access OSCam. This is important if you have multiple devices connecting to the same OSCam instance. Here's an example oscam.user file:

[account]
user = localuser
pwd = localpassword
group = 1
au = 1
caid = 0100,0500,1801

Explanation of Key Parameters:

  • user: The username for the local user. Change localuser to a unique username.
  • pwd: The password for the local user. Change localpassword to a strong password.
  • group: The group this user belongs to. This should match the group defined in the oscam.server file.
  • au: Enables automatic updates for this user.
  • caid: Specifies the CAIDs (Conditional Access IDs) that this user is allowed to access. This limits the channels the user can decrypt.

Configuration Tips:

  • Create a separate user account for each device that connects to OSCam. This improves security and allows you to track usage.
  • Use strong, unique passwords for each user account.
  • Adjust the caid parameter to restrict access to specific channels. This can be useful if you want to limit what users can watch.

Step 4: oscam.dvbapi (Optional)

The oscam.dvbapi file is used to prioritize channels and providers. This can help optimize decryption and improve channel switching speed. Here's an example oscam.dvbapi file:

P: 0100:000068
I: 0

Explanation of Key Parameters:

  • P: Prioritizes a specific CAID and service ID. 0100:000068 is just an example; you'll need to find the appropriate CAID and service ID for your provider.
  • I: Ignores a specific CAID.

How to Use It:

  • Use P lines to prioritize the CAIDs and service IDs for the channels you watch most often.
  • Use I lines to ignore CAIDs that are not relevant to your subscription.

Uploading and Starting OSCam

Once you've configured the OSCam files, you need to upload them to your device and start OSCam.

  1. Upload the Files: Use an FTP client to upload the oscam.conf, oscam.server, oscam.user, and oscam.dvbapi files to the appropriate directory on your device. The directory varies depending on your operating system and setup. Common locations include /etc/tuxbox/config/oscam/, /usr/keys/, or /var/tuxbox/config/oscam/. Consult your device's documentation for the correct location.
  2. Start OSCam: Use the command line or your device's control panel to start OSCam. The command to start OSCam varies depending on your operating system. Common commands include oscam, oscam -b, or /usr/bin/oscam. Again, check your device's documentation.
  3. Access the Web Interface: Open your web browser and navigate to http://your-device-ip:8888 (replace your-device-ip with the IP address of your device and 8888 with the port you configured in oscam.conf). Log in using the username and password you set in oscam.conf.

Troubleshooting

If you're having trouble getting OSCam to work, here are some troubleshooting tips:

  • Check the Logs: The OSCam logs are your best friend when troubleshooting. Check the oscam.log file for error messages or warnings. This can help you identify the cause of the problem.
  • Verify the Configuration: Double-check your configuration files for errors. Make sure the server address, port, username, and password are correct. Also, verify that the cccversion parameter is correct.
  • Check the Network Connection: Make sure your device has a stable internet connection. OSCam needs to be able to connect to the ICCCam server to receive decryption keys.
  • Firewall Issues: Ensure that your firewall isn't blocking OSCam's access to the internet or local network.
  • Incorrect CAIDs: Double-check the CAIDs and service IDs in your oscam.dvbapi file. Incorrect values can prevent channels from decrypting.
  • Restart OSCam: Sometimes, simply restarting OSCam can fix the problem.

Conclusion

Configuring an ICCCam server with an OSCam client can seem daunting, but with this guide, you should be well on your way to a working setup. Remember to double-check your configuration files, pay attention to the logs, and don't be afraid to experiment. With a little patience and perseverance, you'll have a stable and efficient card sharing system. Good luck, and happy viewing! Remember to keep your setup secure by using strong passwords and restricting access to the web interface.

And hey, if you run into any snags, the OSCam community is super helpful, so don't hesitate to ask for help on forums or other online resources. Happy configuring!