Register

Welcome to the RDI-Board Community.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed.


Donate Now Goal amount for this month: 100 EUR, Received: 100 EUR (100%)
Donate to support this site...

Results 1 to 13 of 13
  1. #1
    TBD Teacher
    RDI - Board Default Avatar

    Join Date
    Jul 2008
    Location
    Pe ici pe colea...
    Posts
    254
    Posts Thanks / Likes

    Exclamation Tips and tricks about CCcam sharing

    Consider ca toti care fac CCcam sharing ar trebui sa respecte urmatoarele, sa le spunem recomandari, sau macar sa incerce sa le urmeze pentru un sharing CCcam corect si sigur. E in engleza, l-am postat pe un site care acum e down, dar cine vrea sa faca sharing trebuie sa stie engleza, limba de circulatie internationala.

    In plus:

    1. Inchideti portul 80 si/sau webif pe router. Daca nu stiti despre ce e vorba, studiati. Eu am fost hackerit, deci stiu despre ce e vorba. In plus am si scriptul. Deja ii sterg din server pe toti peersii naivi sau stupizi.
    2. Pentru remote monitoring folositi open vpn sau ssh. Nu lasati porturi deschise (21, 23 sau 80) pe router. Eu folosesc openvpn cu certificate generate local, privat. Deci 100% secure.
    3. Daca ati pus imaginea cu flashwizard, adica din network, nu cu seriala, schimbat parola cu passwd de 2 ori ori! Daca nu, riscati sa fiti "spart" cu parola implicita root / dreambox...
    4. Din cand in cand (asta e pt cei experimentati) lansati in telnet din directorul bin unde e CCcam comanda CCcam - d > logfile.txt. Veti vedea daca sunt probleme.
    Cele mai grave sunt IP-uri duplicat care incearca sa se logheze pe ac account, bad response si read -1.

    Am postat asta cu dedicatie pt giolgau care efectiv m-a scos din minti. I-am spus sa inchida portul 80. Nu l-a inchis, in plus am descoperit si un alt IP care incerca sa se logheze pe accountul lui. Deleted fara remuscari.
    De asemenea e dedicat lui alsta, serverul de skyuk.

    De asemenea m-am gandit la un moment dat sa fac public scriptul poate s-or lumina multi. Dar nu cred ca e o solutie. Nu citesc toti forumurile.

    Asa ca cititi si incercati sa faceti cam asa. O sa fie mai bine pentru toti.

    Cel putin o sa ii indrum pe incepatori sa inceapa de aici.

    Some tips regarding sharing


    You might know, but I think is fine to share with you the following tips and tricks regarding card sharing.
    CCcam card sharing
    - change your default password on DM if you didn't do it yet. root / dreambox are well know even by noobies... Telnet to your DM and type passwd. You will be asked to change the password. You know what to do next, isn't it? Change it!
    - change all your default user name and password for CCcam
    - change your CCcam default ports (in any case, try to avoid 12000) Everybody knows that 12000 UDP is for CCcam sharing. Easy to block. Choose a port greater, much greater. For example 52525...
    - open TCP port for CCcam sharing in your router. It is recommended to have a dedicated router. This will block all ports and will keep open only ports you set up.
    - always put dyndns at the end of each F line in your CCcam.config. This will prevent logging to your server from unauthorized or unwanted IP. The line will look like:
    F: user_name password 2 0 0 { 0:0:3 } { } { } peer_dyndns
    - When you put a C line from a peer in your config, start with hop 1 (locals). Use for beginning lines like this:
    C: peer_dyndns peer_port peer_name peer_password no { 0:0:1 }
    - When you give line C to your peer give line like this:
    C: your_dyndns your_port peer_name peer_password no { 0:0:3 }
    This will indicate to your peer the max downhop you give to him
    - ask for e-mail or messanger id for all peers you add
    - Always test your peer line. Announce on messanger your peers regarding offline period (something like "testing last added lines...") and leave only your peer line in config. First with local only { 0:0:1 }. Check if he has a full card or only some packages... Check how many CAID:ID his local(s) have. If there are only 1, there must do more checks. Which CCcam version he use, ECM time, ping time. After that test what providers he has (comment with # { 0:0:1 }). If there are some interesting ones, add to your C line to him.
    - never make public on open forums your messanger id, e-mail, dyndns or your IP. Even when you want to show something from your status or your config. Use pm, msn id or e-mail. You know why... It is for your safety...
    - if you have too many cards per provider, try to filter it more. Generally 5 cards per provider is enough... All these cards will make a huge traffic on net and you will get freezes because the variable delay... So usimg filters is a must. Always try to filter in your C line. Leave F line to be filtered by your peer. This is a sign of respect for your peer. Of course if you see too much traffic on a F line, you must block it using filters in F line as well.
    - when adding new lines, there is no need to restart the box! Just add the lines! Restart the box only once per day or if you are sure that this is mandatory for your box to work properly. CCcam is not gbox. CCcam EMU doesn't need to be restarted all the day!
    - regarding tools you have to use... I can recommend only what I am using and it does the job perfectly for me, I hope for you, also: CCcamInfoPHP v0.9, WinSCP and Notepad++.
    - to be continued (end of part 1)


    Fine tuning of CCcam


    After you install CCcam info php you know which is the status of your server. All the time. So looking in his screens, you may detect which is the amount of cards you get, which are the providers and how many cards for each provider, which are the clients most actve, who is online or offline.

    - Try to keep a maximum of 400-500 cards in your server.
    - If you have too many cards (I meet a bad example of a peer that had over 10100 cards in share) you have to eliminate cards, hops up till you get only a reasonable number of cards. I am talking about CCcam runing on receivers, not on linux servers where the limits might be much higher.
    - First of all peers with a low ping: if the peer have some good cards in hop 2, just add that CAID:ID to your C line as CAID:ID:2. But generally peers with ping above 150 ms may not give good ECM's from hop 2 or 3. Exception might be nagra3 cards that still go well in hop 2 or 3. If the ECM is under 700-800 ms. So peers with ping above 150 ms can be limited to hop 1 if there is no reason to do something else.
    C: dyn_dns peer_port username_given password_given no { 0:0:1 }
    - For peers with a good ping (same country, or ping bellow 100 ms), you have to select all interesting providers they may have in hop 2 and 3.
    C: dyn_dns peer_port username_given password_given no { 0:0:1, CAID1:ID1:2, CAID2:ID2:2, CAID3:ID3:3, CAID4:ID4:3 }
    - As I said no need to restart the CCcam. When you change a configuration and you put it on receiver with the ftp program, all the time your card will be available at least for you.
    - Try to organise your CCcam.cfg in order. Keep all examples that comes with the kit for later refference. Put F line and C line for the same peer together. Make all needed comments there. Don'y forget to put the # sign before any comments. For example I put there the forum from where I take that user, date, if I tested him or not, if I tested the ECM time for the local, some info regarding other providers that he has in shares.
    - From my experience it seams that is better to put first the peers that you are using most. This will limit the time till you open a channel and overall bad ECM's. Anyway, group the peers by local cards they have.
    - Make all needed comments in CCcam info php (server window) in order to know which card or package the peeer has
    - Try to communicate with all peers. Everybody may have some needs, as we do. Try to help them. If you don't know something just ask peers with more experience. Generally they will help in order to keep the sharing clean. Also communicating each other you can succesfully manage to get other peers with good cards in your shares... Don't be shy. Just ask them.
    - Never give the messanger id of a peer to somebody else, without your peer confirmation. This is a basic rule. I never take such of peers if they are not recommended by an another peer from my shares.
    - Looking into CCcam info statistics, try to understand what is going wrong. For example if there are a lot of bad ECM's, contact that peers and ask them about this issue. Also if there is a lot of traffic gererated by a peer, limit it. And let him know. Try to solve this issue together. Maybe he needs a card you have in share. Arrange an exchange for him. This will make him happy and of course will make your server more stable. A lot of traffic means over 700 ECM's per hour. Limiting the peer means to put in your F line, your card only with reshare rights, all other just for the peer:
    F: username password 1 0 0 { CAIDmine:IDmine:0:2, 0:0:1 } { } { } dyndns
    - If you have some channels that for sure can't be opened in sharing (for ex there are some XX channels that are protected by PIN code) put that CAID:ID:SID in the F line.
    F: username password 1 0 0 { CAIDmine:IDmine:0:2, 0:0:1 } { 092F:000000:00BD, 092F:000000:008F, 092F:000000:00BB, 092F:000000:00BC } { } dyndns
    This is an ex for all XXX channels that will be never opened by my card or from my shares for ex.
    - End of part 2 -
    Last edited by xyzzyx; 13th November 2008 at 13:00.

  2. #2
    Membrana Expert
    Join Date
    Aug 2005
    Location
    Tomis Nord
    Posts
    1,602
    Posts Thanks / Likes

    Default

    Quote Originally Posted by xyzzyx View Post
    ...
    1. Inchideti portul 80 si/sau webif pe router. Daca nu stiti despre ce e vorba, studiati. Eu am fost hackerit, deci stiu despre ce e vorba. In plus am si scriptul. Deja ii sterg din server pe toti peersii naivi sau stupizi.
    .....
    Uite ceva util pentru verificarea porturilor deschise http://dreambox.it/port_scanner.htm
    spersanutiiamulttimpsacitesticanuamsemnatura

  3. #3
    TBD Teacher
    RDI - Board Default Avatar

    Join Date
    Jul 2008
    Location
    Pe ici pe colea...
    Posts
    254
    Posts Thanks / Likes

    Default

    Da e bun... Dar parca mai bine in engleza:
    http://canyouseeme.org/

  4. #4
    TBD Teacher
    RDI - Board Default Avatar

    Join Date
    Jul 2008
    Location
    Pe ici pe colea...
    Posts
    254
    Posts Thanks / Likes

    Default Deconectarea clientilor

    Daca observati in CCcam info php ca va puteti conecta la peers, dar peersii nu se pot conecta la voi, dupa ce ati verificat ca portul de sharing e corect forwardat in router, mai trebuie sa verificati ca nu aveti probleme cu dns-ul (domain name server).
    Pentru a vedea ce se intampla, opriti CCcam-ul (din telecomanda sau din telnet cu comanda "killall CCcam" (CCcam sau cum se numeste la voi). Verificati cu comanda "ps" ca s-a oprit CCcam-ul.
    Apoi mutati-va in directorul cu CCcam cu
    cd /var/bin/
    si lansati de acolo comanda
    /var/bin/CCcam -d >logfile.txt
    Cu ftp, verificati din cand in cand dimensiunea fisierului logfile. Cand a crescut suficient de mult, opriti din nou CCcam-ul
    killall CCcam
    Examinati logfile.txt
    Daca aveti loguri de genul not fount host name sau bad response atunci aveti probleme cu dns-ul.
    Din ce am vazut, probleme au fost si sunt si pe rds si pe rtc.
    In situatia aceasta, trebuie sa folositi un alt dns. Eu m-am inspirat de pe pagina
    http://theos.in/windows-xp/free-fast...s-server-list/
    si am pus pe receiver 4.2.2.4. Idea e sa puneti un IP de dns cu ping cat mai mic.
    Si gata ati rezolvat problemele.
    Pt verificare puteti rula din nou logarea sau pur si simplu sa porniti CCcam-ul (telecomanda sau telnet).
    Pun asta aici ca sa nu mai fiu intrebat.

  5. #5
    Member Mentor
    Join Date
    Jul 2003
    Location
    Germany
    Posts
    764
    Posts Thanks / Likes

    Default

    Quote Originally Posted by xyzzyx View Post
    Consider ca toti care fac CCcam sharing ar trebui sa respecte urmatoarele, sa le spunem recomandari, sau macar sa incerce sa le urmeze pentru un sharing CCcam corect si sigur. E in engleza, l-am postat pe un site care acum e down, dar cine vrea sa faca sharing trebuie sa stie engleza, limba de circulatie internationala.

    In plus:

    1. Inchideti portul 80 si/sau webif pe router. Daca nu stiti despre ce e vorba, studiati. Eu am fost hackerit, deci stiu despre ce e vorba. In plus am si scriptul. Deja ii sterg din server pe toti peersii naivi sau stupizi.
    2. Pentru remote monitoring folositi open vpn sau ssh. Nu lasati porturi deschise (21, 23 sau 80) pe router. Eu folosesc openvpn cu certificate generate local, privat. Deci 100% secure.
    3. Daca ati pus imaginea cu flashwizard, adica din network, nu cu seriala, schimbat parola cu passwd de 2 ori ori! Daca nu, riscati sa fiti "spart" cu parola implicita root / dreambox...
    4. Din cand in cand (asta e pt cei experimentati) lansati in telnet din directorul bin unde e CCcam comanda CCcam - d > logfile.txt. Veti vedea daca sunt probleme.
    Cele mai grave sunt IP-uri duplicat care incearca sa se logheze pe ac account, bad response si read -1.

    Am postat asta cu dedicatie pt giolgau care efectiv m-a scos din minti. I-am spus sa inchida portul 80.
    Inainte cu 2 min de a citii aceasta postare, i-am trimis si eu lui Giolgau un MP, daca nu inchide pina mai deseara portul, sau nu schimba parola, vom avea multi dintre noi poate surprize.
    Cu parere de rau Giolgau, dar asa nu se poate, ori iei masuri, ori in scurt timp vei ramine fara peeri

    numai bine

  6. #6
    Senior Member Expert
    Join Date
    Feb 2007
    Location
    Prahova
    Posts
    1,162
    Posts Thanks / Likes

    Default

    giolgau chiar sta in curu gol ... cine vrea poate sa ne ia adresele din cccam.cfg lui lejer

    chiar acum cineva cu alt ip ( 81.242.188.11 ) se logheaza cu datele lui Giolgau la serverul meu
    Last edited by stargate99ro; 22nd December 2008 at 10:46.

  7. #7
    Senior Member Expert
    Join Date
    Feb 2007
    Location
    Prahova
    Posts
    1,162
    Posts Thanks / Likes

    Default

    Quote Originally Posted by skkip3r View Post
    @stargate99ro


    sincer, daca cineva s-a conectat la tine pe contul lui este strict greseala ta.
    daca puneai de la inceput in linia f sa se conecteze doar de la adresa lui o rezolvai lejer...
    pai este greseala mea ca servarul lui este fara protectie si cine vrea se conecteaza si ii ia cccam.cfg

    ps. am pus si la sfarsitul liniei {} {} ip lui si tot se conecteaza altul cu alt ip
    Last edited by stargate99ro; 22nd December 2008 at 11:02.

  8. #8
    Senior Member Expert
    Join Date
    Feb 2007
    Location
    Prahova
    Posts
    1,162
    Posts Thanks / Likes

    Default

    Quote Originally Posted by skkip3r View Post
    tu nu intelegi sau te faci ca nu intelegi

    "prezervativul" trebuia sa il folosesti tu nu el.. e mai putin problema ta ce face el...

    problema ar fi doar atacurile inutile care iti fac trafic inutil
    poate sunt eu mai greu de cap ... sa inteleg ca daca eu fac schimb cu tine si tu faci publice datele liniei este strict problema mea tu nu ai nicio vina ?

  9. #9
    Junior Member Teacher
    RDI - Board Default Avatar

    Join Date
    Jul 2006
    Posts
    129
    Posts Thanks / Likes

    Default

    exista vre-o metoda de a face ca de la un anumit peer sa vina doar anumite carduri ?

  10. #10
    Junior Member Teacher
    RDI - Board Default Avatar

    Join Date
    Mar 2008
    Location
    Constanta
    Posts
    189
    Posts Thanks / Likes

    Default

    Am verificat cu adresele astea:
    http://dreambox.it/port_scanner.htm
    http://canyouseeme.org/
    porturile 21,23 si 80 si imi spun ca am porturile deschise.
    Dar am pus pe un prieten bun sa verifice daca poate sa intre la mine in dream si nu poate.Deci sa trag congluzia ca sant de doi bani adresele?

  11. #11
    Senior Member Expert
    Join Date
    Jun 2006
    Location
    popescu bogdan PE FACEBOOK
    Posts
    1,096
    Posts Thanks / Likes

    Default la mine arata altfel

    Indirizzo esaminato:
    89.xx.xxx.x

    Porta 21 Chiusa
    Porta 23 Chiusa
    Porta 80 Chiusa

    Secondi impiegati per la ricerca: 30

    Deci cum e?
    Cei mai EXPERIMENTATI nu ne explica mai pe indelete?
    Deci le am inchise or WHAT?

  12. #12
    Senior Member Expert
    Join Date
    Oct 2005
    Posts
    1,388
    Posts Thanks / Likes

    Default

    Quote Originally Posted by rock5 View Post
    Indirizzo esaminato:
    89.xx.xxx.x

    Porta 21 Chiusa
    Porta 23 Chiusa
    Porta 80 Chiusa

    Secondi impiegati per la ricerca: 30

    Deci cum e?
    Cei mai EXPERIMENTATI nu ne explica mai pe indelete?
    Deci le am inchise or WHAT?
    Sigur le ai inchise. Chiusa= inchis
    aperta= deschis
    Nu stiti ce faceti in router?

  13. #13
    Member Mentor
    RDI - Board Default Avatar

    Join Date
    Oct 2008
    Location
    Romanica
    Posts
    535
    Posts Thanks / Likes

    Default

    nu sunt relevante portscanerele online. spre ex eu am un server web pe o masina cu linux pe langa 2 dreamuri... evidident ca portul 80 apare deschis insa e cel de la server.

 

 

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Back to Top