The other users/accounts are, in my case, Newcamd protocol clients of mine, i.e. "user" has to be in both groups 1 and 2, to hook both onto your own server/reader, as well as your colleague's readers/servers.So, this first user must hook onto both your internal reader/server, as well as external readers. You can divide the and into groups.įor instance, your own internal server is in group 1. 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 nf file, which we will discuss a little bit later, in the P.P.S. a user will use your server/services, whether internally or externally.Įxternally speaking: partially, you allow your peers access to your server right here, by setting up their username and password. Each "user" in your file has an "account" with the server. user because in it you are setting various "users" or "clients" to your "server". If you have many C lines you can sub-divide them further, to make it all better optimised/efficient. Those are necessary to be able to hook onto their servers.Īs a client in CCcam protocol one does not need to open various ports, Only servers need to do that.įor 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. The details marked xxxxxx in those you get from your colleagues/peers, like username, password, port and dyndns domain name. Hence all are simply "readers", whether local or remote. their readers read their cards, not just for themselves, but for you, too. They are also servers but they are the servers of your peers, to which you hook onto, as a client. (.plus as many servers of your colleagues as you have, like the second example above.)Ī note, to explain the name of the file: the first is your reader, the "server" primarily for yourself, to which the OSCam client part hooks onto, internally, to open the channels.Īll the following ones are external. "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. You will need to forward the ports here defined, in your modem/router. ergo xxxxxx = whatever you desire or whatever the CAID of your smartcard. Note: xxxxxx = this you choose, whatever it is. # nf generated automatically by Streamboard OSCAM 1.00-unstable_svn build #4859 So, here are the four main configuration files - thanx primarily to also hperez, gianni, subnixonfire, Siri, belami etc. If it is named differently -> right click on it -> rename it to oscam and hit Enter on your keyboard. All except oscam module itself, which you get from the net, as mentioned and then give CHMOD to 755, as above. On your PC you can create various files, using a freeware application Notepad++, which you will FTP to oscamCAS folder. But I will attach it in this thread, if I can!įTP to AZbug HD and go to PLUGINS folder, then OpenXCAS and create a folder oscamCAS, then give it CHMOD to 755. The version of OSCam I am using, fairly successfully, with all the stops, bumps, reboots and so on, is 4859, with dvbapii!!! You can find it on OSCam forum, in AZbox HD section, the "sticky" thread with bin files. OK, this works - tested with my Conax CD card CAS5!!! - 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.Īfter plenty of testing, many different configurations on a couple of OSs and a couple of original FWs, as well as a couple of E2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |