No announcement yet.

Cardsharing CCcam How To

  • Filter
  • Time
  • Show
Clear All
new posts

  • Cardsharing CCcam How To

    Cardsharing CCcam HowTo

    General concepts and explanations

    * Card Sharing (CS) = share of ticket (s)
    * Home Sharing (HS) = share of ticket (s) on the local network at home
    Internet connection is not necessary.
    * Internet Sharing (IS ) = share of ticket (s) over the Internet

    * Port Forwarding for IS
    For the client also reached the server, a port on the router
    are routed to the IP of the server on.

    * CAID = Conditional Access Identification indicates
    what encryption provider to encrypt
    one channel is used.
    * Provider ID = Provider ID
    is used to separate data from different vendors.
    e.g. 0100 0080 0100 0065 Cyfra + and Canal
    Both with caid 0100 but the first with PID 0080 and the second with PID 0065

    * Server = distributed signals
    * Client = receives signals
    * NodeID = a unique, automatically generated identification number.
    * emu = emulator

    * Rap = distance to the next box
    Boxing * x downhops = signals that are x hops away, pass
    * Z = uphops signals from the boxing z hop away, receive

    * DDNS = Dynamic Domain Name System
    Maps a hostname to its IP address

    1st General information for mapping

    * The central point is the red box, which is represented as server .
    * This server has 3 custom maps with the CAID's 0100, 0622, 0500
    and is in HS with Box A Box B connected .
    * Also distributes its cards through the Internet to "Friends"
    and receives signals from, and Server Hop 1 .
    * The Server Hop 2 spread his cards with "Hop Server 1".
    * The boxes Friend 1 + Friend 2 received over the Internet
    Signals from the "server".

    1.1. Hops and NewCS special case

    NewCS has a box installed, increasing the number of hops by +1
    NewCS is considered as an additional server in the chain of boxes.
    see in the picture, the connection between "Friend 2" and box "+ NewCS"
    This applies to both HS and IS.

    2 Home Sharing

    Server in the living room, "Box A" in the bedroom, "Box B" in the hobby room.

    2.1. HS without restrictions

    2.1.A. Server configuration
    The server has only one client for each of its CCcam.cfg Q: Setting up line.

    * Q: user_BoxA pw_BoxA
    * Q: user_BoxB pw_BoxB

    For HS, the router no port forwarding needed.

    2.1.b client configuration

    Each client needs a single C: line in his CCcam.cfg:
    C: <server_ip> <port> <user> <password> <want_ to_receive_emus_from_server>
    Box A
    C: 12 000 user_BoxA pw_BoxA no
    Box B
    C: 12 000 user_BoxB pw_BoxB no

    2.2. HS with restrictions

    The constraints are entered in the configuration of the server.
    The Config of clients remains unchanged.

    2.2.a. A box will not receive signals from the red card (0100:0080)
    Q: user_BoxA pw_BoxA {0100:000080, 0622:000000:1, 0500:000000:1}

    The last number after the Provider ID: 1, defines the number of downhops.
    The server can determine how far the signals are distributed his card (s).
    In this case: 1 = one time, up to the box A

    2.2.b. Box B should a station (15df) of the red card (0100:0080), see is not
    Q: user_BoxA pw_BoxA {0100:000080:1, 0622:000000:1, 0500:000000:1 0100:000080:15} {df}

    2.2.c. Box B is allowed to see everything but only between 16:00-20:00 clock
    Q: user_BoxB pw_BoxB {0:0:1} {} {} 16:00 to 20:00
    {0:0:1} means to see everything, but not share.

    2.3. Expanded HS

    <uphops> <shareemus> <allowemm> in the F: line

    This receives signals from the server box and 2 other servers (uphops)
    and allowed them to "Box A" and "Box B" route.

    2.3.a. A box may no signals of "server Hop 1" received
    uphops = 0
    Q: user_BoxA pw_BoxA 0 x x .........

    2.3.b. Box B signals may be of "one server hop" received

    uphops = 1
    Q: user_BoxB pw_BoxB 1 x ......... x

    2.3.c. Box B signals may be of "one server hop" + "server Hop 2" received
    uphops = 2
    Q: user_BoxB pw_BoxB 2 x x. ........

    2.3.d. A key box may receive from the server keyfile
    shareemus = 1
    Q: user_BoxA pw_BoxA x 1 x .........

    This requires the C: line of the clients are amended as follows:
    C: 12 000 user_BoxA pw_BoxA yes

    2.3.f. Box A must for any server updates for our cards (EMM) send
    allowemm = 0
    Q: user_BoxA pw_BoxA x x 0 .........

    Q: user_BoxB pw_BoxB 2 1 0

    * Box B may receive signals from "Hop Server 1" + "server Hop 2"
    * May receive emus
    * Key must not send updates

    If no values are entered for <uphops> <shareemus> <allowemm>,
    assumes the default settings CCcam
    > = 5 uphops
    > Shareemus = 1
    > Allowemm = 1

    3 I-sharing

    The red box server + 2 and 2 more servers Friends

    3.1. Prepare and set

    So that a client can receive signals from the server,
    access line: on this server using the C.
    C: <server_ip> <server_port> <user> <password>

    3.1.a. <server_ip>
    Most DSL users get a fixed IP address.
    The providers have eigerichtet a forced separation, all
    24 hours to the user assigns a new IP.
    To work around these IP-renewal, the services
    DDNS server used.
    As a host name set of causes that our server box,
    can always be reached via the same name.
    Well-known free DDNS providers are:

    * DynDNS
    * NOIP

    3.1.B. <server_port>
    For the client also reached the server, the port in the router
    are routed to the IP of the server (port forwarding).
    As is the default TCP port 12000 and must be used in the router
    the server box to be opened.
    The same port must of course be in the configuration of the server.

    Alternative ports:

    * 5948
    * 33 334
    * 28 274

    3.1.c. <user> and <password>
    The server defined in the F: line the user name and password
    Q: <username> <password> ........

    3.1.d. Last step - "call me"

    Are the o.g. Steps done, the client will be notified.
    The fits his C: to line and>> happy sharing!

    IS-sharing example between server + Friend 1:
    Q: myFriend1 pw_myFriend1

    Friend 1:
    C: 12 000 myFriend1 pw_myFriend1 no

    3.1.e. Helpful Links and Info
    Port Forwarding, router setup and live settings: here
    Set a static IP: here
    And other tools to check open port: here

    For editing the config files or other
    use a Unix-compatible editor and
    pay attention to the permissions of the file.

    3.2. A box as a server and client

    Take for example the red box server

    1st Server for "Friend 1" and "Friend 2"
    2nd Server + client for "server hop 1"
    3rd Indirect client "server Hop 2"

    3.2.1. Server for "Friend 1" and "Friend 2"

    CCcam.cfg the server:
    Q: myFriend1 passFriend1 .....
    Q: myFriend2 passFriend2 .....

    CCcam.cfg of clients "Friend 1":
    C: 12 000 myFriend1 passFriend1

    CCcam.cfg of clients "Friend 2":
    C: 12 000 myFriend2 passFriend2

    3.2.2. Server + client for "server Hop 1"

    Two lines of red in the CCcam.cfg server box:
    Q: myServerHop1 passServerHop1 .....
    C: 5948 name_for_ServerHop1 pw_for_ServerHop1

    The "server Hop 1" must also w.o. described an F: and C: Line
    Enter into his CCcam.cfg.

    3.2.3. Indirect client "server Hop 2"
    As can be seen in the drawing, there is no direct connection
    between "server Hop 2" and the red server box.

    can receive the red box signals from this server?

    The "server Hop 2" can determine the number of downhops his cards.
    Its direct share partners is the "server Hop 1".
    Q: Line of "server Hop 2":
    Q: 0:0:3} {user_ServerHop1 pw_ServerHop1
    The number 3 means:

    * You must receive my signals = 1 downhop
    * You must twice pass on this for 2 = downhops

    Well sure that the "one server hop" these signals for the red box server release.
    Granted a full release of this {0:0:2}, can also
    pass the red box one last time.

    This can receive signals from remote servers
    and forwarded.

    3.3. IS-settings for server and client
    A simple IS is set in steps:

    More details and options, as described in HS 2.1 - described in 2.3.

    3.4. Client - quality not quantity

    Clients in large sharing networks, up to 2000 or
    even more cards received.
    The removal and poor lines can cause image-Freezer.
    CCCam always tries to choose the shortest distance but these
    Selection costs and time.
    Possible workarounds:

    1st Card overclock
    2nd Prio & Ignore Lists
    3rd C: Line

    The subjects' card overclock "and" prio / ignore "are extensive and
    In the C: Line up the client can quickly and easily create your own locks.

    C: myserver 12 000 ..... { 0:0:3 }

    means everything to max. 3 uphops of "myserver" is received

    C: myserver 12 000 ..... { 0:0:3, 0d22: 000000:2 }
    means everything to max. 3 uphops of "myserver" is received
    removed but only uphops 0d22 cards to 2.

    C: myserver 12 000 ..... { 0:0:2, 1801:000000 }
    means everything to max. 2 uphops of "myserver" is received
    but ignore 1801.

    Maximum for relatively fast sharing. 4 uphops set.

    * From the CCcam version 2.1 can use IGNORE NODE
    certain cards, regardless of the uphops be ignored completely.
    This is the NodeID needed, either from the WebIf or from the file can be read.
    IGNORE NODE: ccddeeff11223344

    3.5. Client access and security
    CCcam server recognizes each of the logged user
    and a second access is blocked at the same time
    the same access.

    The server can also end up Q: Line set an IP for the client
    and thus determine from which host accepts the connection
    should be.

    Q: userFriend1 passFriend1 ....... {0:0: x} {} {}
    Register in this case, the "Friend 1" the host.
    see also 3.1.a. server_ip
    Pay attention to the brace!
    These must be present, whether empty or filled is secondary,
    otherwise the host of CCcam not read.

    ***** Not my work but thanks to Reppo ******