Significance of the F: line in CCcam

The F: line is in the server box (CCcam.cfg) and controls the permissions for the Clientbox.

If you sharest online, you need a server box in the router a DynDNS and port (TCP) to the receiver.
Here you wearing a your friends that connects to you and / n gets from you card.
You need at several friends, each a separate name and password.

Introduction:

Q: [user] [passwd] 3 0 0 {[0:0:3], [caid]: [id]: [downhops]} {[caid]: [id]: [sid]} {[start time] - [End Time]} [Host Name / IP Address]

The F: line consists of three components

1 Login data with the client C: must match Line
2 Release of the card for the client
3 Restriction map for the client

Server box = Provides maps for the client available.
Clientbox = get cards from the server box.
Local Map / n = Is my card / s from the server box.
Virtual Card / n = Are the card / s, which gets the server box as a client of another server boxes.
Hops = If the distance to the map. Each connection from the server box to Clientbox is a hop.

LogIn

Q: [user] [passwd] ...

* The maximum length for the user is 20 characters.
* The length of the password is unlimited.
* Only the following characters are used: AZ, az, 0-9.
* With no user IP or Hostname / DynDNS is meant.

Release

Q: ... 3 0 0 ...

In the release, you decide what you will allow a share partners, what with the setting in the C: must match line.

If these options in the F: is disabled-line, do not get the share partners, these options also free, even if he has enabled this.

Hop

Q: ... 3 0 0 ...

Here you determine on how many hops the client is allowed maximum access.

* Hop is the distance to the map. Each connection from the server box to Clientbox is a hop.
* Card / s that are stuck in our box for us on Hop-0.
* Card over a card server (Newcs / MPCS) are arriving for us hop-1
* Tickets are stuck in the box of a friend directly connected to us for us to hop-1.
* Cards that this friend has on Hop-1, reach us on Hop-2. And so on.
* The closer the card is, the better and faster they can deliver the required CWs.
* So it makes no sense cards from Hop-4 or to use hop-5, as these already wandering through too many servers had until this gets through to us.

Share on Keyfile

Q: ... 3 0 0 ...

You can determine whether your client is allowed to access the file / var / keys / SoftCam.Key.

From the CCcam version 2.1.2 the Softcamfunktion is no longer active and therefore you can disable this option.

Received EMM

Q: ... 3 0 0 ...

EMM are responsible for updating the map and enables you to control whether you want to receive from the client EMM.

* EMMs are responsible for AutoUpdate of the local map.

Example, if you subscribe to a new package to your ABO, so your provider sends new data to your map. This data is then needed for the new station can be unlocked from the card.

Restriction

Q: ... {[0:0:3], [caid]: [id]: [downhops]} {[caid]: [id]: [sid]} {[start time] - [end]} [Host Name / IP address]

@ All DownHops

Q: ... {[0:0:3], [caid]: [id]: [downhops]} {[caid]: [id]: [sid]} {[start time] - [end]} [Host Name / IP address]

Here you can set how far all cards may be gesharet.

DownHops

Q: ... {[0:0:3], [caid]: [id]: [downhops]} {[caid]: [id]: [sid]} {[start time] - [end]} [Host Name / IP address]

[Caid]: [id]: [downhops] = Here you can set how far certain caid + ID may be weitergeshaeret.

* [Caid] = eg ORF => 0D05
* [Id] = ProviderID => 000400
* [Downhops] must be = weitergesharet how far.

Transmitter control

Q: ... {[0:0:3], [caid]: [id]: [downhops]} {[caid]: [id]: [sid]} {[start time] - [end]} [Host Name / IP address]

Here you can determine which individual channel their share partners do not get from you.

* [Caid] = eg ORF => 0D05
* [Id] = ProviderID => 000400
* [Sid] = The transmitter example of ORF1 of the SID in Hexial => 32C9

Timing

Q: ... {[0:0:3], [caid]: [id]: [downhops]} {[caid]: [id]: [sid]} {[start time] - [end]} [Host Name / IP address]

This allows you to determine which timeframe the Share Partners of Do not map / n gets.

* [Start time] - [end] = Time Format => 10:30 to 16:15

-> Note that the time does not overlap!

IP / DynDNS

Q: ... {[0:0:3], [caid]: [id]: [downhops]} {[caid]: [id]: [sid]} {[start time] - [end]} [Host Name / IP address]

Here you can define the client that can connect to you.

Thus, it is not possible that another client with the same login data logs with you.

Info

It is not possible nor desirable that two clients can login with the same login data simultaneously.

Port Sharing

You need the router when a DynDNS server box and an open port (TCP) to the receiver, if you sharest online.

* Eg Dbox2 with the IP = 192.168.2.110 and you want to port 9200 (from the F: line) release as a server,
* At IP address 192.168.2.110 =
* Protocol = TCP
* Port = 9200 -> to Port = blank (Public Port)
* On port = 9200 (Private Port)

NOTE: card sharing is illegal and excluded in the terms and conditions of the service provider.

Sharesave 171 16 in place of R: Line with CCcam

This entry was posted in EMU and tagged , , , tagged. Set Bookmark the permalink .

Leave a Reply

Your email address will not be published. Required fields are marked *

CAPTCHA-Bild
Refresh Image

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>