Default OSCam in AZbug HD with original FW 5303: both server and client at once!
OSCam in AZbug HD with original FW 5303: both server and client at once!
OK, this works - tested!!! - both as a card reader/server, as well as a 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 and 5303], as well as a couple of E2 [RC4 and RC7]...
The version of OSCam I am using, fairly successfully, with all the stops, bumps, reboots and so on, is 4682, with dvbapi, thanx to belami and giannii!!! You can find it on OSCam forum, in AZbox HD section, the "sticky" thread with bin files... But I will attach it to this message, also!
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 B@mbi:
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 = 2
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!
oscam.conf
Code:
# oscam.conf generated automatically by Streamboard OSCAM 1.00-unstable_svn build #4826
# Read more:
http://streamboard.gmc.to/oscam/browser ... m.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 = xxxxxx@xxxx:xxxxxx
key = 0102030405060708091011121314
allowed =
keepalive = 1
mgclient = 0
[cccam]
port = xxxxxx
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 = xxxxxx
httppwd = xxxxxx
httprefresh = 7
httpallowed = 127.0.0.1,192.168.0.1-192.168.255.255
httphideidleclients = 0
httpreadonly = 0
httpsavefullcfg = 0
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
Code:
# internal reader
[reader]
label = azbox-internal
enable = 1
protocol = internal
device = 0
services = whichever_card_you_have
caid = xxxx
ident = xxxx:xxxxxx
detect = cd
mhz = 357
cardmhz = 357
group = 1
emmcache = 1,1,2
lb_weight = 500
[reader]
label = xxxxxx.dyndns.biz
enable = 1
protocol = cccam
device = xxxxxx.dyndns.biz,17000
user = xxxxxx
password = xxxxxx
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
Note, to explain the name of the file: the first [reader] is your [internal or embedded] 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 [reader]s. 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.
oscam.user
Code:
account]
user = azbox
group = 1,2
au = azbox-internal
monlevel = 4
uniq = 0
services = all
betatunnel = 1833.FFFF:1702
keepalive = 1
[account]
user = xxxxxx
pwd = xxxxxx
monlevel = 2
uniq = 1
group = 2
au = 1
(...and so on, as many as you have, as described above, for the previous file...)
Note: the file is called oscam.user because in it you are setting various "users" or "clients" to various "servers". Each "user" in your file has an "account" with a server. I.e. a user will use various servers/services, whether internally [the first one will hook onto your own card reader/server] or externally [onto your peer's servers].
Here, in this file, you determine/configure how you hook onto various servers, whether your own, internally or external servers, i.e. those of your peers, via internet...
You can divide them into groups. For instance, your own server is in group 1 and all the others in group 2. So, this first user [which is yourself] must hook onto both your internal server [group 1], as well as external ones [group 2].
This is enough for you to be both a [Newcamd protocol] server, as well as [mainly CCcam] client. You give your card[s] 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...
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 B@mbi, how you create your N and C lines [my translation]:
Quote:
N-lines
In relation to the parameters from oscam.conf file, one forms an N-line, for a user who uses a CS-server, capable of working with N-lines (like CCcam server, OSCam server
):
[newcamd]
port = AAAAA@xxxx:000000
key = xxxxxxxxxxxxxxxxxxxx
Ergo, N-lines, if you want to give those to anyone, are made like so:
Code:
N: your.dyndns.org AAAAA username1 password1 xxxxxxxxxxxxxxxxxxxx
You must add a user with those details to your oscam.user configuration file, using the specified username1 and password 1.
AAAAA is the port for your NewCamd server in OSCam and it must be opened/directed/forwarded in your router, towards AZbug HD's IP address.
C-lines:
Using the parameters from your oscam.conf file one forms a C-line for a user on CCcam or OSCam servers, using the C-line as a connection with remote cardreaders:
[cccam]
port = BBBBB
Code:
C: your.dyndns.org BBBBB username2 password2 no
In your oscam.user file add a user with username2 & password2.
So, BBBBB is a port for your CCcam server in OSCam and it has to be opened/directed/forwarded in your modem/router towards the AZbug HD's IP-address.
big tanks to gorski
Attached Files
File Type: zip oscam-4682 dvbapi azbox hd.zip (364.8 KB, 22 views)
http://www.sat-universe.com/showthread.php?t=204723
