Getting Started - Flines & Clines For Beginners

Ten Below

Inactive User
Joined
Aug 16, 2009
Messages
28
Reaction score
58
I wrote this myself a few months ago, hope somebody new to the hobby finds it helpfull.

This is probably the most confusing thing for beginners so i will try and keep this as simple as possible.
The first thing you need to to is create yourself a dns address and download the updater software to go with it.I recommend using one of the following,both are equally good.


Dyndns- Register Here - DynDNS.com - Free Domain Name, Managed DNS, Email Services
Updater Software here - DynDNS.com - Support -- Update Clients -- Windows Update Client


No-ip - Register Here - No-IP - Dynamic DNS, Static DNS for Your Dynamic IP
Updater Software here - Download a Free Dynamic DNS Update client for your dynamic IP


The dns address you choose will form the first part of all clines you send to your peers like this.

C: anyone.dyndns.org

The next part of the cline is the server listen port, by default this is 12000.
If you want to change it look in your cccam.cfg for the following line.

SERVER LISTEN PORT : 12000

you can change it to whatever you want as long as you open the corresponding port in your router.

So the cline so far reads.

C: anyone.dyndns.org 12000

This is how every cline you send will start,now you need to create a user name and password in your cccam.cfg that will allow a peer to connect to your server.This is where the fline comes in.

Remember this
F: = Friend, for others to connect to you.
C: = Connect, for you to connect to others.

To make the fline using your ftp programme connect to your box and go to Var/ect you will then see a file named cccam.cfg, right click on this and choose edit.

Everything you see with # in front of it is not read by cccam and can safely be deleted or if you wish to leave it there it will make no difference.These are the only lines that need to be there for it to work.If you find it easier delete it all then copy and paste this in its place.

SERVER LISTEN PORT : 12000
ALLOW TELNETINFO: yes
ALLOW WEBINFO: yes
WEBINFO USERNAME : yourchoice
WEBINFO PASSWORD : yourchoice
TELNETINFO USERNAME : yourchoice
TELNETINFO PASSWORD : yourchoice
TELNETINFO LISTEN PORT : 16000
WEBINFO LISTEN PORT : 16001
ZAP OSD TIME : 3
#OSD USERNAME : yourchoice
#OSD PASSWORD : yourchoice
OSD PORT : 80
SHOW TIMING : yes
DEBUG : no
NEWCAMD CONF : no
DISABLE EMM : no
EXTRA EMM LEVEL : no
MINI OSD : yes
SOFTKEY FILE : /var/keys/SoftCam.Key
AUTOROLL FILE : /var/keys/AutoRoll.Key
STATIC CW FILE : /var/keys/constant.cw
CAID PRIO FILE : /var/etc/CCcam.prio
PROVIDERINFO FILE : /var/etc/CCcam.providers
CHANNELINFO FILE : /var/etc/CCcam.channelinfo
EMM THREADS : 1
#MINIMUM DOWNHOPS: 1
#LOG WARNINGS : /tmp/warnings.txt

You can disable/enable any of these by adding/removing #


A simple Fline looks like this.

F: digiworldz jspass


This is all you need fo your peer to connect to you and means we can complete the cline using the user name and password from the fline.

Completed cline ready to send to your peer looks like this.

C: anyone.dyndns.org 12000 digiworldz jspass


Other Settings


To optimize your servers performance and security there are some other settings to add to both the c & f lines,I recommend you start with the following on your flines



F: digiworldz jspass 2 0 0 { 0:0:2 } { } { } yorpeersdnsaddress


This will give you the best performance i will now try and explain what these numbers mean

The 2 0 0

The 2 means that the peer will get all cards at a maximum of 2 hops away from you.

The first 0 means that the peer gets no emus from you. Change to 1 to get peer’s emu.

The other 0 means that the peer is not allowed to send us emm. Change to 1 to take peer’s emu. Please note that there has to be a corresponding entry in the in the server you are sharing with.Cccam is capable of its own emu these are the optimal settings.

The { 0:0:2 }

The 2 means that the peer can reshare your card once.Change to 1 for no reahsare,3 for 2 reshare ect,ect.

The IP or DNS address at the end of the F line

The IP Address at the end of the F:line makes sure that only the specified peer connects to your server. This is known as locking the fline and is very important against hackers.

Cccam is capable of its own emu work so there is no point using your peers or vice versa.
The safest way to share is receive emm from only the person you trust most - YOURSELF



Extra cline settings

You should resrtict the amount of hops you receive from your peers as anything above hop 3 is virtually unwatchable,ideally you want to using hop1 and 2 only this is done by adding the following after the cline you recieve from your peer.

No { 0:0:2 }
This means you recieve your peers local and hop 1
if you are sharing without a local make this No { 0:0:3 }


Later on
Once you have most of the cards you want in hop1 and there are still some hop2 cards you use it is possible to take only the cards you want from hop2 to further improve the speed of your server.To do this add the caid of the provider like this

C: anyone.dyndns.org 12000 anyuser anypass no { 0:0:1, 0963:0:2, 093b:0:2 }

This takes the peers local plus sky uk & sky italia from hop 2

There is loads more on this but follow this guide and you should be off to a good start.Please ask as may questions as you want i will try and write a complete guide once i get some feedback on my attempts so far.

Best Regards

js940
 
Excellent post mate. Enjoyed and learned reading from it. I made it a sticky for you and others.
 
You really need to change the server port from the default one at 12000 most people don't actually change it and its quite easy for an Isp to monitor your ports and as 12000 is the default one it could be quite easy for you to get caught due to the traffic that is being sent from that port.

Regards

Liam
 
You really need to change the server port from the default one at 12000 most people don't actually change it and its quite easy for an Isp to monitor your ports and as 12000 is the default one it could be quite easy for you to get caught due to the traffic that is being sent from that port.

Regards

Liam
Good point mate, i did and all should but the point of this tut was to help people understand the basics.
 
Could someone confirm which is the correct format for this version as I have seen two brackets and three brackets in various tutorials?

F: digiworldz jspass 2 0 0 { 0:0:2 } { } { } yorpeersdnsaddress

F: digiworldz jspass 2 0 0 { 0:0:2 } { } { } { } yorpeersdnsaddress
 
Could someone confirm which is the correct format for this version as I have seen two brackets and three brackets in various tutorials?

F: digiworldz jspass 2 0 0 { 0:0:2 } { } { } yorpeersdnsaddress

F: digiworldz jspass 2 0 0 { 0:0:2 } { } { } { } yorpeersdnsaddress


Top one m8 :)
 
Top one m8 :)

I configured my flines as the top one and I was expecting a couple of clients to drop off but none did so was getting worried that my config was not correct. Thanks for the confirmation.
 
correct me if i'm wrong, but if theres nothing you want put in the brackets, then you dont need them at all.
 
correct me if i'm wrong, but if theres nothing you want put in the brackets, then you dont need them at all.

You can put info in there to resrtict certain channels or only allow access at certain times, handy if you wanted to resrict your kids viewing for example.
 
correct me if i'm wrong, but if theres nothing you want put in the brackets, then you dont need them at all.

Ok your corrected :)

You need those empty brackets there otherwise it wont work.
 
ahem ahem,
sorry, just clearing my throat.

Yeah, i dont have those empty brackets and mine works fine :)
 
ahem ahem,
sorry, just clearing my throat.

Yeah, i dont have those empty brackets and mine works fine :)

But how do you know its working? What I mean is unless you ask someone other then the genuine sharer to connect to test it how can you be sure its doing its job and stopping your cline from being used by others?
 
ahem ahem,
sorry, just clearing my throat.

Yeah, i dont have those empty brackets and mine works fine :)

Yes your server will work fine but your lines will not be locked to the peers dns meaning they could be used by anyone.
 
I see,
thanks for the info guys.

my question is,
i havent inputted my peers' dns into my cccam config.
so how can my cccam 'lock on to' anybody in the first place.
is it a case of it just latches onto the first ip that the box connects to?

Cheers,
Crazzzy.
 
I see,
thanks for the info guys.

my question is,
i havent inputted my peers' dns into my cccam config.
so how can my cccam 'lock on to' anybody in the first place.
is it a case of it just latches onto the first ip that the box connects to?

Cheers,
Crazzzy.

On my original post if you look at the format you get the 'yourpeeraddress' from the cline supplied to you by your sharer and you copy that into the fline. The DNS address will then lock your sharer with your fline.

F: digiworldz jspass 2 0 0 { 0:0:2 } { } { } yorpeersdnsaddress
 
ahem ahem,
sorry, just clearing my throat.

Yeah, i dont have those empty brackets and mine works fine :)

I accept your apology ;)

I see,
thanks for the info guys.

my question is,
i havent inputted my peers' dns into my cccam config.
so how can my cccam 'lock on to' anybody in the first place.
is it a case of it just latches onto the first ip that the box connects to?

Cheers,
Crazzzy.

Your CCcam doesnt lock on to anybody,
it allows connections based on matching clines and flines i.e it will compare usernames and passwords and then allow or disallow based on the comparison,

putting your clients dns address just adds an extra level of sercurity :)
 
thanks for that buddy, :)
well half of my clients are idiots
*cough cough*

damn, just cant shake this wretched cough.
so yeah.
i'll be giving the client DNS thing a miss.

Regards,
Crazzy.
 
thanks for that buddy, :)
well half of my clients are idiots
*cough cough*

damn, just cant shake this wretched cough.
so yeah.
i'll be giving the client DNS thing a miss.

Regards,
Crazzy.

If your client are idiots then your clines could be all over internet so I would actually install the 'DNS thing'.
 
Back
Top