=='''Intro'''==
Basically, if you want to share data in a computer network, there is a server and a client side or many clients. On de server side there needs to be a protocol that the client understands. Here you will have to choose between the NFS or CIFS (SMB/Samba) protocol to able to access the machine you want to connect to. If you want OpenPLi to access or store data on another machine in your network, you will need to add a new network mount point, this can be done in OpenPLi using the MountManager (see below). Here you will have to choose between the NFS or CIFS protocol to able to access the machine you want to connect to.

'''NOTE I:'''
When you create a new mount using mount manager as described below and save it, it is by default disabled!!

'''NOTE II:'''
As of OpenPLi 10 Samba (CIFS) is '''not''' installed by default If you want a Samba/CIFS connection to your receiver you will have to install it, using the software manager or using the command line. Also you have to set a password, this can be done from the menu or using the command line. The reason we did not install it by default anymore is because Samba has become rather large for most receiver NANDs (internal memory).

opkg install samba
reboot && exit

passwd

(when using passwd from the command line, PAM will sync it with the smb password database)

=='''Background on NFS and CIFS (Samba/SMB)'''==
NFS and CIFS are protocols to make a (data)connection between server and client.

===NFS===
----
NFS stands for ''Network File system'' and was created in 1984 by Sun Microsystems and (were) used for their Unix workstations.

===CIFS===
----
CIFS stands for ''Common Internet File System'' and was developed by Microsoft. It’s a kind of dialect of SMB (Samba) most people use these two SMB/CIFS together, but although they are different, they play well together. In comparison to NFS, CIFS tends to be a bit more "chatty" in its communication.

====Autodetection====
----
As of OpenPLi 7.2 CIFS config has SMB version and security protocol autodetection, so that you no longer have to start looking for whether options have to be given, they are now entered automatically, so practically it means that the suggestions below should not be needed anymore, the system will try all options until one setting works!!

====No more guest access without password====
----
As of OpenPLi 8.2 there is no more guest access without a password possible, this is because modern OS's are not allowing this any more.

If you have this in use, please change the mount definition, entering "guest" for username and/or password instead of leaving it blank, BEFORE you upgrade to OpenPLi 8.2 (or flash it and restoring old configuration).

If you don't, your box will hang after the start, until the mount attempt times out, which can take a long time (10 minutes or more).

===Which protocol to use===
----
Oversimplified you could say that you choose NFS between Unix/Linux machines and CIFS between Windows and Unix/Linux machines.

====Using CIFS to connect to a Linux machine====
----
Please note that if you are using CIFS to connect to a Linux machine, make sure you specify the correct "iocharset" in the mount options (iocharset=utf8), because CIFS makes the assumption that the other side is Windows.

===How to start===
----
When you want to use NFS to access an OpenPLi box you will have to install "NFS server" on the server side. From the plugins, it is in de "extensions" section. If you want to access this new NFS server receiver from another OpenPLi receiver (the Client) you will need to configure the client using "MountManager" as explained below under NFS.

When you want to use CIFS (SMB/Samba) to access and OpenPLi box, you don't have to do anything on the server side, as CIFS is already "working". If you want to access this CIFS server receiver from another OpenPLi receiver (the Client) you will need to configure the client using "MountManager" as explained below under CIFS.

==Server share and the difference between CIFS and NFS==
When you add the server share, so like the location on a NAS you want access, there is a difference in the notation. For example if you want to access a shared folder named video on your Synology NAS which has a volume1, then with

'''NFS the Server share is:'''
/volume1/video

'''CIFS the Server share is'''
/video

===When CIFS is not working===

===Old method (Only needed for versions of OpenPLi 7.1 and below)===
If you can't create a mount, than some security settings may be not up-to-date. Maybe you are still using Samba version 1.0. Although you can make it work, remember still running Samba using version 1 can be a security risk. Follow this [[Problems_and_Solutions#Older_vs_newer_SMB_Protocol | link]] if you are sure that still using Samba version 1.0 is not a security risk for you.

=='''NFS'''==
==='''OpenPLi to OpenPLi'''===
----

When you have OpenPLi installed on 2 boxes, you can make a NFS share, '''WARNING!!''' you will have to edit on the command line. If can't do this, then stay away from a NFS share between to OpenPLi machines and use a CIFS share instead!!

Go to the OpenPLi machine (the server) where the data is you want to share and do as following:
# To configure the OpenPLi server machine, first install the plugin NFSserver from the Extensions section in the [[Plugin_Wiki|Plugin Manager]]
# Now go to
#: /etc
# Edit the file "exports" and make it look something like
#: /media/hdd 192.168.5.0/24(rw,no_root_squash,sync)
#:or
#: /media/usb 192.168.5.0/24(rw,no_root_squash,sync)
#: 
#:The line /media/usb is the location you want to share (can of course be any location on this machine) and 192.168.5.0/24 means that the whole range 192.168.5.0-255 has/can access (to) that share.
# Save the file and make it effective with the command
exportfs -r

Then on the client box go to '''Menu > Setup > System > Expert settings > Network > MountManager''' and choose ''Add new network mount point''. Here you will have to adjust 7 settings in order to make the connection a success.

[[File:MountManager-005.jpg|frameles|left|600px]]
[[File:MountManager-006.jpg|frameles|centre|600px]]

#'''Active''' set it to Enable
#'''Local share name''' set it to any name you like (here I leave it as Sharename). It's the name you will see in OpenPLi when the share is a success.
#'''Mount type''' set it to NFS
#'''Server IP''' here you enter the IP Address of the machine you want to connect to, remember it should be a static or reserved one (meaning it does not change when this machine goes on or off)
#'''Server share''' if you haven't anything regarding the recording location then leave it at default so /media/hdd or /media/usb.
#'''Use as HDD replacement''' if you want this choose, yes else no
#'''Mount options''' leave it as it is.
Now save these settings by pressing ''OK'' on your remote. When this done go to '''Menu > Setup > System > Expert settings > Network > MountManager''' and then choose ''Mountpoints management''. You should see something like this and you can access the data in this shared.

==='''OpenPLi to NAS'''===
----
[[File:MountManager-001.jpg|frameles|left|600px]]
[[File:MountManager-002.jpg|frameles|centre|600px]]

I assume the NAS uses a Linux distribution. Which is in most cases true, as Linux is free and that's favorable to manufacturer's business model. First you’ll have to set things right on the server side (NAS), check if NFS is active and grant the ip address of your OpenPLi box access to the NAS in the NFS settings of the NAS.
When this is done In OpenPLi go to '''Menu > Setup > System > Expert settings > Network > MountManager''' and then choose ''Add new network mount point''. Here you will have to adjust 7 settings in order to make the connection a success.

#'''Active''' set it to Enable
#'''Local share name''' set it to any name you like (here I leave it as Sharename). It's the name you will see in OpenPLi when the share is a success.
#'''Mount type''' set it to NFS
#'''Server IP''' here you enter the IP Address of the machine you want to connect to, remember it should be a static or reserved one (meaning it does not change when this machine goes on or off)
#'''Server share''' here you will have to enter the '''exact''' name of the path to the folder/directory on the machine you want to access. Notice and take look at the pictures NFS has a different path that CIFS, although NFS and CIFS where setup to the same machine!
#'''Use as HDD replacement''' if you want this, choose yes else no
#'''Mount options''' mostly you can leave this as it is.

Now save these settings by pressing ''OK'' on your remote. When this done go to '''Menu > Setup > System > Expert settings > Network > MountManager''' and then choose ''Mountpoints management''. You should see something like this and you can access the data.

=='''CIFS'''==
==='''OpenPLi to OpenPLi'''===
----
[[File:MountManager-007.jpg|frameles|left|600px]]
[[File:MountManager-006.jpg|frameles|centre|600px]]
Go to the OpenPLi box that will be the client, meaning the box that wants to have access to another OpenPLi receiver, then go to '''Menu > Setup > System > Expert settings > Network > MountManager''' and then choose ''Add new network mount point''. Here you will have to adjust 9 settings in order to make the connection a success.

#'''Active''' set it to Enable
#'''Local share name''' set it to any name you like (here I leave it as Sharename). It's the name you will see in OpenPLi when the share is a success.
#'''Mount type''' set it to CIFS
#'''Server IP''' here you enter the IP Address of the machine you want to connect to, remember it should be a static or reserved one (meaning it does not change when this machine goes on or off)
#'''Server share''' here you will have to enter the '''exact''' name of the path to the folder/directory on the machine you want to access.
#'''Use as HDD replacement''' if you want this, choose yes else no
#'''Mount options''' mostly you can leave this as it is.
#'''User name''' default is guest, leave it at that, CIFS guest mounts without username/password no longer work as of OpenPLi 8.2, see [[Data_sharing#No_more_guest_access_without_password | here]] for more information
#'''Password''' default is *, leave it at that, CIFS guest mounts without username/password no longer work as of OpenPLi 8.2, see [[Data_sharing#No_more_guest_access_without_password | here]] for more information

Now save these settings by pressing ''OK'' on your remote. When this done go to '''Menu > Setup > System > Expert settings > Network > MountManager''' and then choose ''Mountpoints management''. You should see something like this and you can access the data.

==='''OpenPLi to NAS'''===
----
[[File:MountManager-007.jpg|frameles|left|600px]]
[[File:MountManager-006.jpg|frameles|centre|600px]]

On the NAS check if SMB/CIFS is active and give access to a username and password or give guest access.
Next go to the OpenPLi box and go to '''Menu > Setup > System > Expert settings > Network > MountManager''' and then choose ''Add new network mount point''. Here you will have to adjust 9 settings in order to make the connection a success.

#'''Active''' set it to Enable
#'''Local share name''' set it to any name you like (here I leave it as Sharename). It's the name you will see in OpenPLi when the share is a success.
#'''Mount type''' set it to CIFS
#'''Server IP''' here you enter the IP Address of the machine you want to connect to, remember it should be a static or reserved one (meaning it does not change when this machine goes on or off)
#'''Server share''' here you will have to enter the '''exact''' name of the path to the folder/directory on the machine you want to access. Notice and take look at the pictures CIFS has a different path than NFS, although NFS and CIFS where setup to the same machine!
#'''Use as HDD replacement''' if you want this, choose yes else no
#'''Mount options''' mostly you can leave this as it is.
#'''User name''' default is guest, leave it at that
#'''Password''' default is *, leave it at that

Now save these settings by pressing ''OK'' on your remote. When this done go to '''Menu > Setup > System > Expert settings > Network > MountManager''' and then choose ''Mountpoints management''. You should see something like this and you can access the data.

==='''OpenPLi to a Windows computer'''===
Here is explained how to access/add a shared folder that's on a Windows PC

===='''On the Windows machine'''====
In Windows you need to create a shared folder, you can do that for guest or everyone and choose to have passwords or not. After you created the shared folder with or without username or password, you will have to enter these in OpenPLi, you will also need the IP address of the Windows machine and the folder that you shared, so write these down.

===='''On the OpenPLi receiver'''====

1.Use your remote control and go to Main menu > Setup > System > Expert settings > Network > MountManager

2.Add new network mount point
[[File:MountManager-010.jpg|frameles|centre|850px]]

3. Active: change the slider to green
[[File:MountManager-011.jpg|frameles|centre|850px]]

[[File:MountManager-012.jpg|frameles|centre|850px]]

4.Local mountpoint: Leave this as it is (you can change this later if you want)

5.Mount type: Change it from NFS to CIFS (arrow to the left)
[[File:MountManager-013.jpg|frameles|centre|850px]]

6.Server IP: Enter the ip address of your Windows computer
[[File:MountManager-014.jpg|frameles|centre|850px]]

7.Hostname: Leave this as it is, so empty

8.Server share: this is the name of the folder you shared on your Windows PC. Keep in mind that when the shared folder is in

/folder/shared folder

you only have to enter

shared folder

so not the complete path (This is a Windows thingy ;))
[[File:MountManager-015.jpg|frameles|centre|850px]]

9.Username: When you have created a windows share with a username enter this, when you have set windows share without a username then leave this as it is, so guest

10.Password: When you have created a windows share with a password enter this, when you have set windows share without a password then leave this as it is, so *

11.Now press Ok on your remote control and if you entered everything correct then the share to your Windows PC should be active, the little world icon should now be green [[File:MountManager-016.jpg|frameles|centre|850px]]

12.Exit the mount manager and press the PVR or the Playlist on your remote (will be different per receiver or remote) and now you should be able to see the files on the Windows PC, please remember that not all files types can be displayed, as your receiver is a Linux machine accessing a Windows machine, but most movie file types should be recognized.
[[File:MountManager-017.jpg|frameles|centre|850px]]

2026-03-07T16:01:07Z

40H3X:

==New features or improved features:==
*Fixed Multibox remote buttons RECALL and VOD
*Add support for External subtitles - When playing a media file, srt/ass/ssa subtitle files (in this order) will be used when present
*Fixed opkg issue installing new dependencies in the wrong location if you have picons on HDD or USB
*SimpleChannelSelection - added epg button for select channel too
*Tryfix Gigablue Bluetooth remote authentication error

==New hardware support:==
*Added support for the Gigablue Quad 4K PRO
*Added support for the Gigablue Trio 4K PRO
*Added support for the GT-S2dCSS24 unicable switch (Poland)

==New or improved Plugins and Settings:==
*Added the DarkOS skin to the feed (will become the default skin in OpenPLi 10)
*Improved software update:
**Uses HTTP instead of HTTPS, so you can update the box without having the correct time set
**Check first if http://downloads.openpli.org is reachable
**Check next if the "trafficlight" is set to red for possible update issues (allows us to remotely block updating)
*[AutoDiseqc] update dectection of the Astra 23.5E position
*Change default values in cablescanplugin due changes done by a cable provider in the NL
*Added option in the system menu to set or change the root password (needed for Windows 11 connections)
*New repository for the infobarweather plugin (original author passed away)
*Enable SMB signing to support Windows 24H2 and newer
*Youtube plugin updates
*Update Streamlink server to v7.4.0
*Added pluto TV plugin
*Backupsuite: Add runtime dependencies for dm8000
*Epgimport: Update sources
*Epgimport: Add azman poland sources
*OSCam: add pcsc-lite as a build dependency, to support PCSC USB card readers

==Look and feel changes:==
'''As always many translation/language improvements, thanks to all the translators!!!'''
*Add picon to the display skin of the VU+ Duo 4K/Solo 4K
*Increased clock size on the VU+ Uno 4K SE display
*Fixed PiP when viewing encrypted channels via StreamRelay
*Re-add DVB-S NIM(45208 FBC) as valid FBC tuner (Lunix3 4K / Galaxy 4K)
*Added Single EPG filtering by timespan to the EPG settings
*Added NumberZap and Seek buttons to the help screens
*Improved skin compatibility with other images
*Add MENU key to the audio selection screen, to access the Language selection setup
*Reinstated the LEFT and RIGHT keys in the audio selection screen
*Fixed channel list key functionality when opening the channel list from EPG screens

==Driver updates: ==
All vendor zip and tar files are now served from our own download servers, to reduce dependencies on third-party infrastructure.
*all: Fixed blindscan-dvbs and transcoding support features
*gigablue: Added support for the Quad 4K PRO and Trio 4K PRO
*gigablue: Update BSP - Update Python3 patch Chromium
*gigablue: added wifi driver support feature for the Quad 4K and UE 4K
*gigablue: removed old bluetooth support plugin, no longer compatible with current python C bindings, and we don't have the source to fix it
*gigablue: add bootloader update package for gigablue UE and Quad; update Quad 4K PRO bootloader
*xtrend: Reinstated DVB-C support for the ET9x00, fixed it for ET7X00
*xtrend: Remove remove blindscan-dvbc feature for the ET9X00, no binary is available
*xtrend: Remove Full HD skin feature from the ET4x00 and ET5X00
*xtrend: Fixed SoC identification for several models
*vuplus: Improved Bluetooth plugin to reduce remote disconnects
*vuplus: Implement kexec multiboot detection for kernel updates
*vuplus: Fixed SoC identification for several models
*zgemma: Add missing blindscan-dvbs and blindscan-dvbc to the H11
*zgemma: Added emmc and recovery support feature to the H11
*Add support for wifi kernel drivers mt7601usta and rt5572sta for kernels versions 4.10.

==Samba (Windows file sharing) changes:==
With the introduction of Windows 11 update pack 24H2, Windows has disabled SMBv1, which allows for NETBIOS browsing, anonymous enumeration of shares, and anonymous logins, has enabled SMB packet signing, and made this signing compulsary. The Samba configuration on the box has been changed to accomodate these new requirements.

They do however have some side-effects you need to be aware of:
* anonymous logins are no longer possible, logins with invalid passwords (which would also cause an anonymous login) will now also fail
* you have to assign the root user of your box with a password. There is a menu option added that allows you to do so
* you have to make sure you haven't added /etc/samba to your auto backup fileset, to avoid restoring old and now invalid config
* a linux password and a samba password are two different things, and may get out of sync, reset it if a login fails with the correct password to resync

==Other improvements:==
*Fallback import now retries for 2 minutes instead of 15 seconds, to allow for possible AVAHI name resolving issues.
*Add possibility to indent configs in setup.xml file

==Known issue's==
===No Oscam after upgrade===
The Oscam version in 9.2 release has added support for PCSC card readers. To enable this, the pcsc support package must be installed as part of new dependencies.

Due to a bug in the OPKG installer in 9.1 release, this support package is installed in the wrong location, if you have installed picons on USB or HDD. The result is that after the update, oscam refuses to start.

The quickest way to fix this is to go to the plugins menu, remove oscam, and reinstall it again. Alternatively, you can execute these commands on the commandline:
* opkg update
* opkg install libpcsclite1
* /etc/init.d/softcam restart

===No DNS after upgrade===
In 9.2 release, the static DNS configuration has been moved from /etc/resolv.conf to /etc/network/interfaces.

This is because the resolv configuration is now volatile (it doesn't survive a reboot), and openresolv is now active by default to aid VPN users separate DNS servers per network connection.

If you had a static DNS configured before the upgrade, you need to reconfigure it after the upgrade, so it is stored in the correct location. You only need to do this once.

Since there is no way of knowing if the DNS information in /etc/resolv.conf was added statically or via DHCP, we can not convert this automatically when you restore a backup.

'''Do not touch the files resolv.conf or resolvconf, so '''only use the GUI to edit DNS or Gateway'''

===No IP after upgrade===
This is not so much an issue when using DHCP over a wired connection, but has been reported to happen when using a wifi connection.

The root cause of this problem is that the standard DHCP timeouts as defined by OE are very short, which means that if it takes longer for the connection to establish itself, the DHCP client may time out.

You can address this either by editing the interface configuration on the box, disable the interface, save it, then enable the interface again.

Alternatively, you can edit /etc/network/interfaces directory, and change the options from "udhcpc_opts -T1 -t9" to "udhcpc_opts -S -T6 -t10".

===Autobackup backward compatibility===
An Autobackup backup made with OpenPLi 9.2+ is no longer backwards compatible, which can cause problems if you want to downgrade an image to an older OpePLi version.

This is because in the Enigma configuration file, /etc/enigma2/settings, boolean values are now capitalized, and "True" is not seen as "true" by older images, but as "false".

If you need to restore a new backup on an older image, you need to do this (assumes your backup is on /media/usb):
* stop Enigma using the command:
** init 4
* extract the enigma settings from your backup using the commands:
** cd /tmp
** tar -zxvf /media/usb/backup/PLi-AutoBackup.tar.gz etc/enigma2/settings
** sed -i 's/=True$/=true/g' /tmp/etc/enigma2/settings
** sed -i 's/=False$/=false/g' /tmp/etc/enigma2/settings
* copy the settings file:
** cp /tmp/etc/enigma2/settings etc/enigma2/settings
* start Enigma using the command:
**init 3

2026-02-12T12:43:34Z

40H3X: /* Access OSCam webinterface through OpenWebif */

=='''What is OSCam'''==
OSCam is a softcam, software to be used to decrypt digital television channels on a settopbox (receiver), as an alternative for a conditional access module (CAM). OSCam is, compared with other softcams (Cccam, mgcamd, etc.), open source. Hence, the name ''Open Source Conditional Access Module'' (OSCam)). OSCam is based on the not so well known softcam MpCS. The main features of OSCam are next to its softcam capabilities, that it is able to function as a cardserver.

=='''OSCam install'''==
OSCam can be downloaded from the OpenPLi feeds (see also https://wiki.openpli.org/Plugin_Wiki:Information). To install OSCam use your remote control go to '''Menu -> Plugins -> Download plugins (green button) -> softcams then select OSCam to install.'''
Please note after installation you'll have to activate the softcam also in Menu -> Settings -> Softcam / CI -> Softcam settings.

=='''OSCam config'''==
You can access OSCam through the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> or edit the files using your favorite remote access program (telnet-SSH-SCP-FTP-etc.) for this you could have a look at our Wiki page [[Tips_and_Tweaks|Tips and Tweaks]]

[[File:OScam-000.jpg|frameless|Centre|1200px]]

===Access OSCam webinterface through OpenWebif===
Using [[Webif | OpenWebif]] you can also access OSCam webinterface

[[File:Webif-006.jpg|frameless|centre|800px]]
[[File:Webif-007.jpg|frameless|centre|800px]]

=='''Canal Digitaal or TV Vlaanderen'''==
If you have a TV Vlaanderen or Canal Digitaal card the OScam that we compile\make\build and is in the OpenPLi feed, is already pre-configured for you. After installation (see above) you login the webinterface <nowiki>"http://ipaddressofyourbox:8081"</nowiki> with your favorite browser (Firefox, Chrome, Safari, etc.) and go to the tab '''Readers''' and enable the card by mouse clicking the '''on/off''' button for your card (see picture below) and that should be all.

[[File:OScam-001.png|frameless|Centre|1200px]]

===Manually access your config file===
You can find/place the OScam configuration file into:
/etc/tuxbox/config/oscam/

=='''SoftCSA'''==

===What is SoftCSA===
SoftCSA is a software descrambling implementation directly inside Enigma2. For CSA-ALT encrypted channels (Algorithm 3), Enigma2 performs the descrambling itself instead of using OSCam StreamRelay as a detour.

===How and What concerning SoftCSA===
* No StreamRelay overhead: no more double HTTP connection
* Direct descrambling of the AV stream within the Enigma2 process
* Better performance for zapping and timeshift
* Fewer interruptions and more stable playback
* Full recording functionality – recordings are playable on a PC as well
* FCC support – Fast Channel Change works

===Using SoftCSA===
When you freshly install OpenPLi the config files will be setup right and CSA will be actif, but when you upgrade OSCam or restore a backup not, because an update will not overwrite your current config files and when a backup is restored, the default config files will be overwritten. So below you see how to setup the config files, so that CSA is activated and Stream Relay is deactivated, as it is no longer needed with CSA active. Don't forget to restart OSCam to use the new settings!!

[[File:CSA-001.png|frameless|Centre|1000px]]

[[File:CSA-002.png|frameless|Centre|1000px]]

If you go to a channel like Sky Krimi you will now see CSA in the left below corner, depending on whether you have a card you see a picture or not, as it is not FTA.

[[File:CSA-003.png|frameless|Centre|1000px]]

=='''OSCam removing config files'''==
By default OpenPLi has the OScam package in the feed configured with a few common readers like for Canal Digitaal (CD) and TV Vlaanderen (TVV) like in the picture above. When you don't see these, it is because every restore of a backup re-installs your previous readers. Removing your OScam using the plugin manager won't remove your configuration files, that's so made by design.

'''So what to do?'''
----
If you want to remove your current config files and have the OpenPLi configured OScam files and see the readers in the picture above? Well, you have to first remove the installed package using the menu, so go to the plugin manager and remove OScam. Second you have to manually remove a folder
/etc/tuxbox/config/oscam

There are a few ways to do this, manually using putty eg. telnet, or use a FTP program, like Filezilla. When these are not suited for you or your don't know how? Then try the solution below.

===In Windows===
*Be sure to have a OpenPLi [[Backup | Backup]]!
*Uninstall/remove OScam using the [[Plugin_Wiki | plugin manager]] and go to the softcam section.

#In Windows right click on Windows Start button
#Select Run or in Dutch Uitvoeren
#Enter the //the-ipaddress-of-your-box
##Example so like:
#: //192.168.100.10
#Choose the root folder
#Now go to
#: /etc/tuxbox/config
#Now you should see the oscam folder
#delete the folder oscam
#reboot/restart your receiver
#After a restart go to the plugin manager and install OScam
#After installation the readers created by OpenPLi should be there (like in the picture above)and select the one your need (see above)
#There is one thing to do!!
#Make a manual backup with [[Backup/AutoBackup | AutoBackup]] , so when you suddenly have to restore to replace the "old" config files in the last backup you made.

=='''Updates'''==
The OScam version will only be updated when there is a reason for it, so when you see you're not running the latest update, there is no reason for it. Of course you can always compile a new version yourself, see the developers site below.

=='''Internal cardshare'''==
In OpenPLi the softcam OScam is already set/configurated to do an internal cardshare between 2 boxes. By default OScam is configured to connect 2 boxes with "Mainreceiver" becoming the server and the “2nd_box” becoming the client (OSCam terminology calls this the reader).
As the developers of OpenPLi don’t know which box you want to be the Mainreceiver and which one becomes the 2nd_box, OScam is configured for both.
So you'll have to do 2 things on the one which becomes “2nd_box“ (OScam terminology calls this the reader).

===Preparations===
----
Both boxes have to be in the same network.
You have to know the IP address of the Mainreceiver.

===Mainreceiver===
----
This will be your server for the client “2nd_box”. On this one you don’t have to do anything, as there is already a user “2nd_box” which has access with the password “2nd_box”.

===2nd_box===
----
This box is the client and it will login on the Mainreceiver using a "reader", let’s say to read the data it needs. All you’ll have to do is to enter the IP address of the Mainreceiver and start the Reader.

Login into OScam on the box which will be the 2nd_box, by using your favorite browser, eg. Iceweasel-Firefox-Opera-Chrome-Internet Explorer or Microsoft Edge and enter <nowiki>http://ipadres_of_the_2nd_box:8081</nowiki> , so you can configure it properly.

#Go to the Readers TAB and click on the red pencil in the line of the Mainreceiver.
#A window will open , then you go to the line that says Device.
#On this line there is “ip_adress_mainreceiver,12005".
#Here you have to enter the IP address of the Mainreceiver instead of the text.
#Now go the bottom of the screen and click the save button.
#Now click on the Readers TAB on top of the screen.
#Then on the line Mainreceiver click on the On/Off button on the screen. By clicking it the button should go from grey to green.

It all should work like instant. Yet, to be on the safe side, you could restart the Mainreceiver and the 2nd_box.

=='''NL: Use with Ziggo Irdeto cards'''==
If you are using Ziggo Irdeto cards it will work after doing the following:
#Open in a editor the file \\ipofyourbox\root\etc\tuxbox\config\oscam\oscam.server (or add the keys in the reader section of the OScam webinterface using the pencil in the reader)
#Add the following rules in the section reader of the reader that contains the Ziggo card (or both): boxkey = please Google this generic key for Ziggo and rsakey = please Google this generic key for Ziggo
#Save the config and it should work
Note: Unfortunately this doesn't work with Ziggo Nagra cards as these cards are linked to the boxkey which is unique to the reciever you got from Ziggo. As long as you dont know this key the smartcard can't be used by OScam.

=='''OSCam Tuning (Mapping)'''==

'''Please, keep in mind use at own risk!'''

Edit all oscam.conf files with a simple text editor like kate/vim/notepad++, don't use wordpad or other windows badness

Restart the softcam after changing your config files by pressing '''Menu''' on remote control and navigate to: '''Setup > SoftCam/CI > Softcam setup... > Select softcam >''' (press left or right to select) '''oscam >''' press '''green button'''(ok).

'''Mapping'''

This mapping method will work for BE and NL seca cards.

Make sure you are using '''dvbapi request mode 1 (try all CAID simulataneously)'''

'''the dvbapi file is located in /etc/tuxbox/config/oscam/oscam.dvbapi'''

Add (or edit) two lines to the oscam.dvbapi file

M: 1817:00006A 0100:00006A
M: 1818:00006C 0100:00006C

'''oscam.server''' ratelimitecm and ratelimitseconds settings explained

This is setting crucial for performing home card sharing SECA cards of the M7 media group.
If this is setting is set wrong, the picture will result in frozen images, this is caused by bad decrypt keys (control words) from the smartcard also known as penalty mode.

Until now ratelimitecm have to be set to 4 (default setting if you use the oscam versions from the feeds), because you are not able to decode more than 4 channels continuously.

For ratelimitseconds it is known that values from 8 seconds and lower result in bad decode keys.
Further, it is also known that if ratelimitseconds is larger or equal to 11
seconds, you can zap you channels and keep a decoded tv image.
----

=='''There is a official website of the developers of OSCam'''==
To go to official developers board http://www.streamboard.tv/wbb2/portal.php

To go to official OSCam wiki. http://www.streamboard.tv/wiki/index.php/OSCam/en

To see an overview of the last changes. https://trac.streamboard.tv/oscam/timeline