OK, this works - tested with my Conax CD card CAS5!!! - both as a [Newcamd] card reader/server, as well as a [CCcam] client, so no need for any other Emus, thanx to various people for sharing info, like I am trying to do now...
After plenty of testing, many different configurations on a couple of OSs [original FW and E2] and a couple of original FWs [4890, 5303, 5305 and 5306], as well as a few E2s [RC4, RC7, RTi 1 Fix and SPAZE Fix]...
The version of OSCam I am using, fairly successfully, with all the stops, bumps, reboots and so on, is OSCAM 1.10rc-svn build #5755, with dvbapii!!! You can find it on OSCam forum, in AZbox HD section, the "sticky" thread with bin files... But I will attach it in this thread, if I can!
FTP to AZbug HD [use the freeware FileZilla Client] and go to PLUGINS folder, then OpenXCAS and create a folder oscamCAS, then give it CHMOD to 755 [right click on the file -> File permissions -> 755 -> OK].
On your PC you can create various files, using a freeware application Notepad++, which you will FTP to oscamCAS folder. All except oscam module itself, which you get from the net, as mentioned and then give CHMOD to 755, as above. If it is named differently -> right click on it -> rename it to oscam and hit Enter on your keyboard.
So, here are the four main configuration files [do not deviate from them, for starters... later, try different ones...] - thanx primarily to [email protected] but also hperez, gianni, subnixonfire, Siri, belami etc. etc.:
openxcas.conf
Note: the "-d 255" line is worth its weight in gold, so to speak...
Now AZbug HD reads the card consistently and fairly efficiently! Thanx to Siri! :thum:
oscam.conf
Note: xxxxxx = this you choose, whatever it is... ergo xxxxxx = whatever you desire or whatever the CAID of your smartcard...
You will need to forward the ports here defined, in your modem/router. "Forwarding ports" means to open those ports up to your AZbug HD, so when your peers try to get to you the traffic will not be blocked and it will automatically be directed to AZbox HD, instead of any other device you have hooked onto your home network, via the same modem/router.
oscam.server
A note, to explain the name of the file: the first [reader] is your [internal or embedded card] reader, the "server" primarily for yourself, to which the OSCam client part hooks onto, internally, to open the channels.
All the following ones are external [readers]. They are also servers but they are the servers of your peers, to which you hook onto, as a client. I.e. their readers read their cards, not just for themselves, but for you, too.
Hence all are simply "readers", whether local [yours] or remote [virtual, via internet].
The details marked xxxxxx in those you get from your colleagues/peers, like username, password, port and dyndns domain name. Those are necessary to be able to hook onto their servers.
As a client in CCcam protocol one does not need to open various ports, Only servers [your colleagues/"peers" giving you access to their cards] need to do that.
For now, let's just say that your embedded cardreader/internal reader/server should be in Group 1, whereas your CCcam peers should be in Group 2. If you have many C lines you can sub-divide them further, to make it all better optimised/efficient. Or you can add Newcamd ones in Group 3, GBox ones in Group 4 etc. etc. We shall come to that later.
Here's an example:
Many Original smartcards' details are here:
oscam.user
Note: the file is called oscam.user because in it you are setting various "users" or "clients" to your "server". Each "user" in your file has an "account" with the server. I.e. a user will use your server/services, whether internally [the first one is you and you will hook onto your own card reader/server] or externally.
Externally speaking: partially, you allow your peers access to your server right here, by setting up their username and password. The other parts to allow them access to your server, with which you create C (for your CCcam clients) or N (for your Newcamd clients) lines for your peers/colleagues, are from oscam.conf file, which we will discuss a little bit later, in the P.P.S.
You can divide the [readers] and [accounts] into groups.
For instance, your own internal server [the first "reader"] is in group 1.
All the other "readers" of a certain protocol are in group 2. The next protocol goes to group 3, next one to Group 4 etc.
The very first "account", i.e. "user" has to be in all the groups [for instance, 1,2,3,4], in order to hook both onto your own [internal] server/reader, as well as your colleague's [external] readers/servers. So, this first user [which is yourself] must hook onto both your internal reader/server [group 1], as well as external readers [groups 2, 3, 4 etc.].
The other users/accounts are, in my case, Newcamd protocol clients of mine [me being a server, in this case, passing my smartcard to them], i.e. they are getting access solely to my smartcard [internal] reader/server by being placed in Group 1. That way they will not draw from anything but my smartcard/reader.
Apparently, Newcamd server is meant for this purpose, so this is how it is supposed to be used. The N-lines you [partially] create from this file [oscam.user] and [partially] from Newcamd part of oscam.conf file, are to be given to your colleagues, people you trust. With those lines you pass only your card and nothing else and this is how it is done. These [users] are connected to my internal reader/server via Group 1 and thereby not connected to the CCcam protocol, which busy traffic is placed in Group 2.
This is enough for you to be both a [Newcamd protocol] server, as well as [mainly CCcam] client. You give your card in return for other people's cards. No need to pay for "CS services", run by our little CS entrepreneurs, spoiling the fun for us!!!
I will attach the rest of the files here, including the module itself, so you don't have to search for it too much...
A must info is here:
Btw, don't be afraid to keep checking out the new versions...
Cheers!
P.S. More details, as to how to work with FileZilla Client and so on - in my "Alternative guide for AZ..."
P.P.S. Thanx to [email protected], how you create your N and C lines [my translation]:
After plenty of testing, many different configurations on a couple of OSs [original FW and E2] and a couple of original FWs [4890, 5303, 5305 and 5306], as well as a few E2s [RC4, RC7, RTi 1 Fix and SPAZE Fix]...
The version of OSCam I am using, fairly successfully, with all the stops, bumps, reboots and so on, is OSCAM 1.10rc-svn build #5755, with dvbapii!!! You can find it on OSCam forum, in AZbox HD section, the "sticky" thread with bin files... But I will attach it in this thread, if I can!
FTP to AZbug HD [use the freeware FileZilla Client] and go to PLUGINS folder, then OpenXCAS and create a folder oscamCAS, then give it CHMOD to 755 [right click on the file -> File permissions -> 755 -> OK].
On your PC you can create various files, using a freeware application Notepad++, which you will FTP to oscamCAS folder. All except oscam module itself, which you get from the net, as mentioned and then give CHMOD to 755, as above. If it is named differently -> right click on it -> rename it to oscam and hit Enter on your keyboard.
So, here are the four main configuration files [do not deviate from them, for starters... later, try different ones...] - thanx primarily to [email protected] but also hperez, gianni, subnixonfire, Siri, belami etc. etc.:
openxcas.conf
Code:
[module]
name = oscamCAS
daemon = oscam -d 255
argument = c /PLUGINS/OpenXCAS/oscamCAS/
version = 1.00
api=Yes
wait =5sec
INFO = /tmp/ecm.info
REFRESH = 2oscam.conf
Code:
# oscam.conf generated automatically by Streamboard [COLOR=#FF0000][B]OSCAM 1.10rc-svn build #5755[/B][/COLOR]
# Read more: http://streamboard.gmc.to/oscam/browser/trunk/Distribution/doc/txt/oscam.conf.txt
[global]
logfile = /tmp/oscam.log
clientmaxidle = 9000
cachedelay = 120
unlockparental = 1
nice = 4
maxlogsize = 100
preferlocalcards = 1
saveinithistory = 1
lb_mode = 100
[monitor]
port = 988
nocrypt = 127.0.0.1,192.168.1.1-192.168.1.253
aulow = 120
hideclient_to = 0
monlevel = 4
appendchaninfo = 1
[newcamd]
port = [B]xxxxxx[/B]@[B]xxxx:xxxxxx[/B]
key = 0102030405060708091011121314
allowed =
keepalive = 1
mgclient = 0
[cccam]
port = [B]xxxxxx[/B]
reshare = 2
ignorereshare = 0
forward_origin_card = 0
version = 2.2.1
updateinterval = 240
minimizecards = 0
keepconnected = 1
stealth = 1
reshare_mode = 0
[dvbapi]
enabled = 1
au = 1
boxtype = none
user = azbox
pmt_mode = 0
request_mode = 0
[webif]
httpport = 80
httphelplang = en
httpuser = [B]xxxxxx[/B]
httppwd = [B]xxxxxx[/B]
httprefresh = 7
httpallowed = 127.0.0.1,192.168.0.1-192.168.255.255
httphideidleclients = 0
httpreadonly = 0
httpsavefullcfg = 0Note: xxxxxx = this you choose, whatever it is... ergo xxxxxx = whatever you desire or whatever the CAID of your smartcard...
You will need to forward the ports here defined, in your modem/router. "Forwarding ports" means to open those ports up to your AZbug HD, so when your peers try to get to you the traffic will not be blocked and it will automatically be directed to AZbox HD, instead of any other device you have hooked onto your home network, via the same modem/router.
oscam.server
Code:
[reader]
label = azbox-internal
enable = 1
protocol = internal
device = 0
services = [B]whichever_card_you_have[/B]
caid = [B]xxxx[/B]
ident = [B]xxxx:xxxxxx[/B]
detect = cd
mhz = 357
cardmhz = 357
group = 1
emmcache = 1,1,2
lb_weight = 500
[reader]
label = [B]xxxxxx[/B].dyndns.biz
enable = 1
protocol = cccam
device = [B]xxxxxx[/B].dyndns.biz,17000
user = [B]xxxxxx[/B]
password = [B]xxxxxx[/B]
lb_weight = 100
#inactivitytimeout = 1
reconnecttimeout = 30
#audisabled = 1
group = 2
cccversion = 2.2.1
cccmaxhops = 1
ccckeepalive = 1
#emmcache = 1,2,2
#fallback = 1
(...plus as many servers of your colleagues as you have, like the second example above...)A note, to explain the name of the file: the first [reader] is your [internal or embedded card] reader, the "server" primarily for yourself, to which the OSCam client part hooks onto, internally, to open the channels.
All the following ones are external [readers]. They are also servers but they are the servers of your peers, to which you hook onto, as a client. I.e. their readers read their cards, not just for themselves, but for you, too.
Hence all are simply "readers", whether local [yours] or remote [virtual, via internet].
The details marked xxxxxx in those you get from your colleagues/peers, like username, password, port and dyndns domain name. Those are necessary to be able to hook onto their servers.
As a client in CCcam protocol one does not need to open various ports, Only servers [your colleagues/"peers" giving you access to their cards] need to do that.
For now, let's just say that your embedded cardreader/internal reader/server should be in Group 1, whereas your CCcam peers should be in Group 2. If you have many C lines you can sub-divide them further, to make it all better optimised/efficient. Or you can add Newcamd ones in Group 3, GBox ones in Group 4 etc. etc. We shall come to that later.
Here's an example:
Code:
http://streamboard.gmc.to/wiki/index.php/OSCam/en/examples/Sky_HD_and_MTV-Unlimited
Code:
http://streamboard.gmc.to:8001/wiki/CardsList
Code:
[account]
user = azbox
group = 1,2
au = azbox-internal
monlevel = 4
uniq = 0
services = all
betatunnel = 1833.FFFF:1702
keepalive = 1
[account]
user = [B]xxxxxx[/B]
pwd = [B]xxxxxx[/B]
monlevel = 2
uniq = 1
group = 1
au = 1
(...and so on, as many as you have...)Externally speaking: partially, you allow your peers access to your server right here, by setting up their username and password. The other parts to allow them access to your server, with which you create C (for your CCcam clients) or N (for your Newcamd clients) lines for your peers/colleagues, are from oscam.conf file, which we will discuss a little bit later, in the P.P.S.
You can divide the [readers] and [accounts] into groups.
For instance, your own internal server [the first "reader"] is in group 1.
All the other "readers" of a certain protocol are in group 2. The next protocol goes to group 3, next one to Group 4 etc.
The very first "account", i.e. "user" has to be in all the groups [for instance, 1,2,3,4], in order to hook both onto your own [internal] server/reader, as well as your colleague's [external] readers/servers. So, this first user [which is yourself] must hook onto both your internal reader/server [group 1], as well as external readers [groups 2, 3, 4 etc.].
The other users/accounts are, in my case, Newcamd protocol clients of mine [me being a server, in this case, passing my smartcard to them], i.e. they are getting access solely to my smartcard [internal] reader/server by being placed in Group 1. That way they will not draw from anything but my smartcard/reader.
Apparently, Newcamd server is meant for this purpose, so this is how it is supposed to be used. The N-lines you [partially] create from this file [oscam.user] and [partially] from Newcamd part of oscam.conf file, are to be given to your colleagues, people you trust. With those lines you pass only your card and nothing else and this is how it is done. These [users] are connected to my internal reader/server via Group 1 and thereby not connected to the CCcam protocol, which busy traffic is placed in Group 2.
This is enough for you to be both a [Newcamd protocol] server, as well as [mainly CCcam] client. You give your card
I will attach the rest of the files here, including the module itself, so you don't have to search for it too much...
A must info is here:
Code:
http://streamboard.gmc.to/wiki/index.php/OSCam/enCheers!
P.S. More details, as to how to work with FileZilla Client and so on - in my "Alternative guide for AZ..."
P.P.S. Thanx to [email protected], how you create your N and C lines [my translation]:
Last edited: