im looking to install oscam as standalone

Quote

my advice is use oscam to read the card & cccam to share. there are self install scripts in pc linux tutorials

your advice to someone else from a previous thread about a week ago:snicker:

To be perfectly honest, your advice on that day in my opinion was good advice, because Oscam as a standalone CCcam server has a fair few issues, and you might find yourself on the wrong side of your peers.

If you do want to set it up as a server, then this can still be done on an Oscam/CCcam install. I have an Oscam/CCcam install on my server and I have Oscam running but not being used because I haven't told it to do anything in the configs, and this would be the same the other way round.

the basics of an Oscam server - oscam.conf you need to enable the cccam protocol;

[cccam]
port = 12000
version = 2.1.3
stealth = 1

replace port with the one you have open on your router.

oscam.server would be where you set up your card reader. If you are already using oscam to read your card, then this might already be ok.
oscam.server is also where you place your virtual readers (clines)

consider the following cline

C: anydns.dyndns.com 12000 user pass

in oscam.server you enter this as follows;

[reader]
label = example
protocol = cccam
device = anydns.dyndns.com,12000
user = user
password = pass
group = 2
inactivitytimeout = 30
cccversion = 2.1.3
cccmaxhops = 2
ccckeepalive = 1

note how the 'cline' is broken down in the device, user and password flags.
you can use the above as a format, and change device, user, password and group for each virtual card (cline) you have

also you need to consider how groups work

your entry for your card might have 'group = 1' - and for every virtual reader (cline) you get, you should probably put this in its own group for best control

now there are flines - in oscam these are called user accounts. You might already see a user account set up to send your card to cccam in a cccam/oscam setup.

consider an fline

F: user pass 2 0 0 { 0:0:2 }

in oscam.user you enter this as follows;

[account]
user = user
pwd = pass
group = 1,2
cccmaxhops = 2
cccreshare = 1
keepalive = 1

to break down the above - user and pwd self explanatory - set your user's name and password.
group - this is where you set what real or virtual cards you want to share with your peer - this is why it is good to have a different group set for each entry in oscam.server
cccmaxhops - set this at 2 then you share cards up to two hops away from you
cccreshare - this sets the level of downhops you want to share to - so best leave this at 1 - as this is direct peer and a further share level.
keepalive - keeps alive!!

this is the basics - but if you have a good look around webif - you will pick up a lot more, with direct links to the oscam wiki.

Remember if you are not using CCcam, then you can get rid of the CCcam.cfg, (idea to back it up) - and you can also delete the account in oscam.user that sends the card to CCcam, also you can delete the [newcamd] entry in oscam.conf.

hehe - wish you metioned that earlier - would have saved me a bit of time on the writeup!!!

If you are sharing with your Vu+ (using the Vu+ as CCcam server) and using the PC Oscam server as just a card reader, then keep the newcamd protocol entry in oscam.conf - you don't need the CCcam protocol, unless you decide to try it out as a server. You might already have an entry in oscam.user to send the card to your CCcam server on your Vu+

You can copy and paste most of the CCcam.cfg to the Vu+ - and you can set the minimum downhops to 0 to benefit from having the server on the receiver, and instead of using 127.0.0.1 on the nline in CCcam.cfg, change this to the IP of your Oscam server. The Server listen port on CCcam.cfg on your receiver should be open on your router and forwarded to your receiver ip. No need to open any more ports