Detecting/preventing clines being re-shared!

Hi guys,

I'm running a cs server with around 10 clients connected.

Was just wondering if there is a simple way to see if a cline is being re-shared, and what measures I can take to prevent this?

Basically I can see all my clients connected with the exception of one which has not been showing for a long time. I thought this was a bit odd, so I decided to # out the cline and see what response I got. Sure enough the guy started shouting the very same day!

All seems a bit fishy to me... so thought I would ask the experts for some advice! :-)

Any thoughts...?

Thanks in advance.

Spodge

Thank you both for the prompt replies! beer10

I do trust the people that I'm sharing with, however it would be nice to be 100% sure that I don't have any free loaders spoiling the service for everyone else! To be fair if people do start abusing my trust they are only really spoiling it for themselves in my view!

Anyway just to be clear on my setup:-

I use oscam to read my card which is then linked to cccam, which my clients connect to.

I have only ever used very basic C/F lines as never had the need to look into greater detail. An example of my current cccam config would be:-

F: user password 0 0 0 {0:0:1}
C: dyndns 12000 username password

My understanding of the above is that the client only has rights to my local card and cannot re-share. However from what you guys have mentioned above it would seem that I am being some what naive! Lol

One point worth mentioning is that I currently use CS Studio to monitor my client connections. As mentioned above I noticed that one of my clients had not been connected for some time, so I hashed out their F line and they instantly contacted me to see if there was a problem. My question I guess is can a client connect to my server without showing as connected in CCcam?

Thanks again for the advice so far. I will have a good read through the above, try some things out and post any findings here.

Spodge

How would I set my clients up in oscam?

I currently use an N line to connect oscam to cccam, would I need to generate additional N lines to allow clients to connect directly to oscam?

All my clients use various versions of cccam, I have done some research but still a little unlear on how to do this directly from oscam!

Thanks for the advice so far.

Spodge

Hi Banny,

Thanks for the post but I can't seem to find a download link on your thread!? :confuse:

Spodge

Hi guys,

Quick update:-

I have now (thanks to the helpful posts and my own research!) managed to convert my Oscam/CCcam setup to just an Oscam setup.

Not completely what I was after but at least I have a much better understanding of Oscam now! :-)

I am now certain that one of my so called TRUSTED clients has re-shared his cline without even bothering to ask me, which has really p**sed me off! :ah:

Ok few more questions for the experts....

Qestion 1 - I was hoping to continue allowing some of my clients to connect using CCcam (and use Oscam to restrict the so called smart arses!). Is it possible to use Oscam to read the card whilst having multiple clients connecting via CCcam and some clients connecting via Oscam? The reason I am asking this is because I lost all clients from CCcam as soon as I changed my Oscam config!

Question 2 - When monitoring CCcam info although I didn't see the troublesome client connected, I did see two/three remote client connections. Does this mean the client is proxying the supplied cline so I can't see him, and then sharing it on?

Question 3 - Now I have my Oscam setup and all clients running on it I can see the troublesome client connected under the 'Users' tab of the Oscam web gui. All my other clients are showing their own public IP addresses however, the troublesome client is showing MY public IP address listed and not his own! I am guessing that this is another clear indication that he is perhaps proxying/re-sharing the supplied cline!?

Ok rant over and any thoughts would be much appreciated!.....?

P.S. I realise the obvious solution is to cut him off! :-)

Cheers,

Spodge

Sorry for the late reply I have been away on hols!

Thanks for the update mrgmx I will take the advice on board and worst case say goodbye to the person in question!

Unless anyone has anything more to add or ask here then I think this thread can be closed...?

Spodge