CCcam and NewCs fixed Result!!

Liam1611

Inactive User
Joined
Jul 23, 2009
Messages
497
Reaction score
40
Location
Manchester
Having spent the past few days messing around with the above and a white card, I can safely say that they are happily working together and it looks like a local card in CCcam with a bit of cheating. Download CCcam 2.1.4 & NewCs 1.67 from the Blue panel, and download the attached file, edit the NewCs and CCcam configs with your own details and send them across to the receiver. CCcam config is located in /var/etc, NewCs.xml is located in /var/tuxbox/config and CCcam bin file is located in /var/bin. I used CCcam 2.1.3 bin file and simply renamed it CCcam 2.1.4 copied it across rebooted the box and its all sweet, clients see the card as a local and everything runs. I know its cheating but at least your peers see your card as a local rather than a Hop 1. If you are concerned about tricking your peers then just use the CCcam and NewCs configs only and show the card as a Hop 1.
Don't forget to put your boxkey in NewCs.

Regards

Liam
 
Last edited:
Having spent the past few days messing around with the above and a white card, I can safely say that they are happily working together and it looks like a local card in CCcam with a bit of cheating. Download CCcam 2.1.4 & NewCs 1.67 from the Blue panel, and download the attached file, edit the NewCs and CCcam configs with your own details and send them across to the receiver. CCcam config is located in /var/etc, NewCs.xml is located in /var/tuxbox/config and CCcam bin file is located in /var/bin. I used CCcam 2.1.3 bin file and simply renamed it CCcam 2.1.4 copied it across rebooted the box and its all sweet, clients see the card as a local and everything runs. I know its cheating but at least your peers see your card as a local rather than a Hop 1. If you are concerned about tricking your peers then just use the CCcam and NewCs configs only and show the card as a Hop 1.
Don't forget to put your boxkey in NewCs.



Regards

Liam

Hi, Winrar says this file is corrupt, unable to open it.

Finearrow
 
What about card updates, do they work in this setup or is it still back in the official box?
 
Having spent the past few days messing around with the above and a white card, I can safely say that they are happily working together and it looks like a local card in CCcam with a bit of cheating. Download CCcam 2.1.4 & NewCs 1.67 from the Blue panel, and download the attached file, edit the NewCs and CCcam configs with your own details and send them across to the receiver. CCcam config is located in /var/etc, NewCs.xml is located in /var/tuxbox/config and CCcam bin file is located in /var/bin. I used CCcam 2.1.3 bin file and simply renamed it CCcam 2.1.4 copied it across rebooted the box and its all sweet, clients see the card as a local and everything runs. I know its cheating but at least your peers see your card as a local rather than a Hop 1. If you are concerned about tricking your peers then just use the CCcam and NewCs configs only and show the card as a Hop 1.
Don't forget to put your boxkey in NewCs.

Regards

Liam
many thanks for this one mate......i am having a few problems with my debian server at the moment and need to use my TM600 with newcs on it so i can send my local card over to my server......Bloody smargo has gone faulty, and my omnikey refuses to work as well......What a past 24 hours i have been having......I messed about for 10 minutes this morning trying to get it working........waste of time i have to say that was...
 
What about this solution 3rd post down made by Digidude.

Regards

Liam
 
Last edited by a moderator:
Sorry to drag up an old thread, I am in the process of setting up my system again after a long lay off, how is this set up working out for you?

Still happy using newcs as server and cccam as client? I am still trying to fully understand all this :)

Looking at the config files you posted I see that the n: line points to the internal IP of the box and you need to state the deskey with the addition of 256 at the end?

I am assuming if you wanted to let an external client connect then they would have to add an N: line similer to the one you posted with the addition of dyndns details etc.

I am just thinking is it better to use newcs or just go with cccam

Frenchman
 
theres diffrent reasons to use the combi or on there own, but for the tm500 you must use the combi, as cccam wont read card on its own like it would say on dreambox. So newcs must read the card and serve it to cccam which will then serve your clients.

from all accounts cccam 2.1.1 + newcs 1.67 works a treat, using 2.1.1 you can accomodate the fussy spierboxs no problems.


thanks agin to liam / digi for the configs.
 
......... sorry posted in wrong section please delete
 
Last edited:
I know this is an old thread but I saved it in my favourites to when I eventually got round to using my TM as a server.

Thanks to Liam for post and files much appreciated.

Apologies in advance for what is probably a basic question but for a "noob" like me! How do you find out what the entitlements are on your card - just trying to find when the next update is?

Thanks in advance.
 
Cheers Scouser. Tried that and logged in to the newcs page but all I got was a page full of what seems to be html code.

If my understanding is correct you should got a list of options and you click on "entitlements".

Any ideas welcome.
 
internet explorer works for me and when i use rockmelt browser i get what you are seeing all html so try internet explorer see if that works m8
 
I have a feeling you are going to have to use oscam very soon and drop newcs.
 
skygod suspect you are correct.

Just trying to get this up and running first - sorted now. Oscam does seem to be the most likely next choice.
 
I have a 5402 but cannot get the premium channels to work. If I want to see them myself - ie not shared, how do I get the 5402 to see the premium channels? Thanks,.
 
Back
Top