Differences between cccam-versions as server?

[Satphoenix]

Re: Differences between cccam-versions as server?

so, as a client of cccam.server...

Ähhm, aplok,
perhaps it's much more easy just to change the "overloaded" cline with another from the server (if you have the choice between more than one e.g. here from satlover)?!
OK, you have to change the cccam.cfg because of only one cline to use at the same time.

[aplok]

Re: Differences between cccam-versions as server?

so, as a client of cccam.server,

the smart way to handle this,

is
- monitor ecm time,
- keep stats,
- settle a ecm.time.fair (let's say 1.5 sec),

and roll on the consecutive available clines on ccam.server,
until a fair ecm-time meets ecm.time.fair, (ie ecm-time < ecm.time.fair )

if ecm-time > ecm.time.fair then goto roll on ..


*** and without double connections ***
thus, with a tempo
to ensure the tcp disconnect message

[BlueIsMyColor]

Re: Differences between cccam-versions as server?

So there are two problems: disconnects - reconnects and a "lot" of freezes...

regards

[Satphoenix]

Re: Differences between cccam-versions as server?

Yes, but you often will have disconnects - reconnects.

You can see the connection result in the cccam-webinterface how long the actual connection lasts. And if you are online for two hours, but the connection time only shows two minutes, you had a dis- and reconnect.

[BlueIsMyColor]

Re: Differences between cccam-versions as server?

@ Satphoenix

that answers a question that i am making myself a longtime: "what happens when 2, 3, 4, 5... persons connect to a server using the same line?"

So, below 2.1.0 cccam version (2.0.11) "everyone" is able to connect with the same line, right?

regards

[Satphoenix]

Re: Differences between cccam-versions as server?

OK, I've found the answer which I was looking for in post #24. It was written on a site which is a known traitor of satlovers clines, so I have no problem to just copy and paste the articel:

"CCcam: why good clines show 0 shares?

To understand why this happens, we need a little background on the matter. As we know, a cline has the following syntax:

C: <hostname> <port> <username> <password>

Basically, it tells our box to connect to hostname : port using username / password as credentials. On the other side, the box acting as a server is listening for new connections. In normal circumstances, when a new client connection is received, the server checks if the received username/password is found in the local config file as a fline, and grants the connection.
But what happens when a new client logins and there’s already a connection present for the given username?

This scenario is quite frequent with the free clines found on internet because eventually many clients will use the same cline.

In this situation, the older CCcam versions up to v2.0.11 used a strategy consisting in allowing only one connection per user, keeping the last login and closing the previous connection. Since multiple logins are assumed to happen due to network issues, for instance when a new ip is assigned by our isp, this behavior grants a fast reconnection.
What happens when two or more boxes use the same cline?

Let’s says we have a box labeled Client1 which connects to a box Server1. Since we are the first client, we can login without further problems. Now, if a new box Client2 establishes a connection using the very same cline, then Server1 will accept this new client and discard our connection. But then Client1 will reconnect to the server and, as you should have figured by now, Server1 will drop Client2. Of course Client2 won’t abandon but will reconnect after a short timeout and thus starting a cycle that prevents both clients from using the cline.

To mitigate this issue, starting from the version 2.1.0, the developers of CCcam opted for a different strategy. From now on, multiple logins are not allowed and therefore only the first client will be kept. Any further connection attempts using the same cline are ignored. This prevents the cycle discussed earlier but the downside happens when a legitimate client loose his connection and wants to reconnect. In this case, he will be rejected and will have to wait until the previous connection is marked as dead, which usually happens after a few minutes.

In conclusion, the 0 card issue happens when multiple clients try to connect to a cccam server v2.0.11 or below with the same cline. Luckily, the cccam version is always shown in the details of the [...] Edit: cccam-webinterface."

[gianni253]

Re: Differences between cccam-versions as server?

hi
if the server is on linux pc, you can monitor connections:
.....

Well said aplok !
I think people talking about backdoors don't know much of linux internals ... we have some powerful commands that show perfectly what's going on inside our receivers.

[pan1300]

Re: Differences between cccam-versions as server?

hi dizzymac

going out off topic here ...

take a look here (free): http://www.satlover.eu/forum/free-ca...art-again.html
and/or here (pay, but not open right now): http://www.satlover.eu/forum/satlove...m-servers.html

[dizzymac]

Re: Differences between cccam-versions as server?

Hi, Can you help me as i'm new to all this,i'm buying a skybox and dont't know much about setting it all up apart from looking on the net.I understand i have to get a cline from a server? but I am in the dark here?...where do i get these,do i have to pay?Hope you can help.Thanks.

[aplok]

Re: Differences between cccam-versions as server?

hi

if the server is on linux pc, you can monitor connections:

- to list established connections:

lsof -i |grep ESTABLISHED


- to list established connections on CCcam server, running the executable cccam, on port 31234 :

lsof -i |grep ESTABLISHED |grep cccam |grep 31234


- to list badguy ip with multiple connections to 31234 port, on cccam server:

lsof -i |
perl -ne 'print "$1\n" if/^cccam.*TCP .*->([^ ]*) .ESTABLISHED/' |
sort -u |
perl -ne 'BEGIN{$p=0}{/([^:]*)/; print "$1\n" if($p eq $1); $p=$1}'


- to ban those badguy :

# activate the iptables black list (badguy):
iptables -A INPUT -m recent --name badguy --rcheck -j DROP

# identify badguys, and add their ip into iptables black list:
lsof -i |
perl -ne 'print "$1\n" if/^cccam.*TCP .*->([^ ]*) .ESTABLISHED/' |
sort -u |
perl -ne 'BEGIN{$p=0}{/([^:]*)/; print "$1\n" if($p eq $1); $p=$1}' >> /proc/net/xt_recent/badguy


- to purge iptables black list:

echo > /proc/net/xt_recent/badguy



# --- this example shows connections ...
# on my CCcam server running the executable cccam, listening the port 31234 :
# on my ftp server, running the executable ftpd, listening the port 21 :


$ lsof -i
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

# --- client
telnet 6660 toto 3u IPv4 288707 0t0 TCP myip:38868->dboxip:telnet (ESTABLISHED)
telnet 7339 toto 3u IPv4 302048 0t0 TCP myip:53847->pcip:telnet (ESTABLISHED)
cccam 7095 titi 13u IPv4 317879 0t0 TCP myip:56885->cccam.org:1234 (ESTABLISHED)

# --- server
cccam 7095 titi 10u IPv4 291587 0t0 TCP *:12000 (LISTEN)
cccam 7095 titi 11u IPv4 291588 0t0 TCP *:16000 (LISTEN)
cccam 7095 titi 12u IPv4 291589 0t0 TCP *:16001 (LISTEN)


cccam 7516 titi 3r IPv4 320552 0t0 TCP myip:31234->badguyip:58047 (ESTABLISHED)
cccam 7517 titi 3u IPv4 320552 0t0 TCP myip:31234->badguyip:58047 (ESTABLISHED)

cccam 7596 titi 3r IPv4 320552 0t0 TCP myip:31234->badguyip:57892 (ESTABLISHED)
cccam 7597 titi 3u IPv4 320552 0t0 TCP myip:31234->badguyip:57892 (ESTABLISHED)


cccam 1236 titi 3r IPv4 320552 0t0 TCP myip:31234->goodguyip:57232 (ESTABLISHED)
cccam 1237 titi 3u IPv4 320552 0t0 TCP myip:31234->goodguyip:57232 (ESTABLISHED)


ftpd 7433 titi 4u IPv4 312142 0t0 TCP *:ftp (LISTEN)
ftpd 7433 titi 9u IPv6 312144 0t0 TCP *:ftp (LISTEN)
ftpd 7659 titi 0u IPv4 321955 0t0 TCP myip:ftp->badguyip:35134 (ESTABLISHED)
ftpd 7659 titi 1u IPv4 321955 0t0 TCP myip:ftp->badguyip:35134 (ESTABLISHED)

[Satphoenix]

Re: Differences between cccam-versions as server?

I've read somewhere (don't know exactly when or where) that there's a different behavior of the cccam versions as server when more than one user tries to connect with the same cline (like it often happens with bigger free-servers).
Does anyone know details about that?

[kalpikos]

Re: Differences between cccam-versions as server?

... a trick or an illusion ? :

even if the hop counter is reset to 0,

this does not stop the ecm time response ... and further freezing ...

...trick or an illusion , I think that the result is the same...
They used this in order to cheat and present as local cards , the cards that they were receiving as clients .
They don't care about ecm time response as they only want to show that have local cards and how to collect more and more.

[aplok]

Re: Differences between cccam-versions as server?

it was as a client

for further details, i have to dive into the post to remember more precisely ...

i'll tell you later ...

[Satphoenix]

Re: Differences between cccam-versions as server?

i compare cpu and mem % for cccam ...

OK, but did you compare as server or as client?
Or is there no difference when looking into your results?

[aplok]

Re: Differences between cccam-versions as server?

... are there other performance differences?

i compare cpu and mem % for cccam 2.0.10, 2.0.11, 2.1.4, 2.2.1 and 2.3.0
monitored by top (the gnu process monitoring tool)

i posted the facts here:
__http://www.satlover.eu/forum/cccam/50309-cccam-contest-2-0-10-2-0-11-2-1-4-2-2-1-and-2-3-0-a.html

interesting comments in the post ...