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...

Page 1 of 4 123 ... LastLast
Results 1 to 15 of 49

Thread: cwshare.cfg

  1. #1
    Junior Member Teacher
    Join Date
    Sep 2006
    Location
    RO, EU
    Posts
    193
    Posts Thanks / Likes

    Default cwshare.cfg

    Salut!

    Am niste nedumeriri legate de acest fisier cwshare.cfg. In momentul cand schimbi o linie cu un peer, ii dai linia ta D, de forma:

    D: { nume.domeniu.com { PORT1 PORT2 { PASSWORD { AX AY }}}}

    Ma intereseaza acum AX si AY, adica reshare level-urile. Conform documentului How To Gbox de pe rdi-dreambox.com, AX inseamna cat de departe poate sa mearga cardul tau iar AY inseamna cat de departe pot sa mearga cardurile din reteaua ta (sa inteleg aici cat de departe poti sa retransmiti Virtual Card-urile, nu?).

    Prima intrebare (adica e a doua deja ). In How To Gbox, arata linia D de forma:

    D: { nume.domeniu.com { PORT1 PORT2 { PASSWORD { 5 5 }}}}


    De ce se pune de fapt A-ul acela in fata? De exemplu daca am, sa zicem, { A3 A3 }, care este reshare level-ul meu? 3 sau 163 ? (hexazecimalul A3 in baza 10 este egal cu 163).

    Ar fi recomandat sa se puna { 3 3 } si nu { A3 A3 } daca vrei ca reshare level-ul sa fie de 3?

    Urmatoarea intrebare: Eu primesc o linie D de la peer, linie in care el imi da un anumit reshare level. Sa zicem acum ca e { A1 A1 }. A cui e reshare level-ul asta? Al lui sau al meu?

    Adica... sa zicem ca peerul nu vrea sa i se transmita cartea decat la 1 Dreambox departare. In a cui linie va veni scris { A1 A1 }? In linia lui ce mi-o da (prin urmare in cwshare-ul meu)? Sau el va scrie in linia ce i-o dau eu { A1 A1 } (deci in cwshare-ul lui) (chit ca eu i-am scris linia mea D: cu { A3 A3 }?

    Ultima intrebare: (doar in cazul in care la Urmatoarea intrebare raspunsul este ca reshare level-ul din cwshare-ul meu sunt ale mele ). Sa zicem ca eu pana in momentul asta am vrut sa transmit cardul meu local la 3 Dreamboxuri departare. Acum m-am hotarat ca vreau numai la doua departare. Pot edita cwshare-ul meu punand { A2 A2 } la toate liniile mele D fara sa creez probleme?


    Multumesc,

    BAV

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

    Default

    1. Functiuneaza la fel cu A3 A3 sau 3 3, reshare level = 3
    2. Daca un peer iti da A1 inseamna ca ai reshare level 1. el trece linia ta cu A1 si nu prea ai ce face.
    3. Sigur poti pune A2 A2 la toate liniile din cwhare, indiferent cum pune partenerul de cs linia ta
    este chiar recomandat pentru reducerea traficului.
    A5? cine isi doreste carduri de la dist 5 ? 2<frezze...nds.

  3. #3
    Moderator Expert
    Join Date
    Jul 2006
    Location
    blowfish me....
    Posts
    2,472
    Posts Thanks / Likes

    Default

    mai simplu , pe o scara de la 1-5
    A1-A1 - esti/este bou cel care da asa ceva , te-a limitat sa vezi numai tu fara reshare
    A3-A3-ok pt ambele parti
    A5-A5 sau chiar 6 dai numai la corelarile care le faci tu , gen gbox +cs2gbox sau mgcamd , linia ta d mgcamd in cwshare are A5-A5
    intr-o retea de cativa peersi , poti pune A3 A3 la toti daca esti domn
    daca ai peste suta , reduci la toata lumea la A2 A2 pt trafic sa nu moara gboxul extenuat
    sper ca gresesc sa ma corecteze cineva pls:P)

  4. #4
    Junior Member Teacher
    Join Date
    Sep 2006
    Location
    RO, EU
    Posts
    193
    Posts Thanks / Likes

    Smile

    Multumesc mult de tot pt. raspunsuri Ma intrebam eu ca ar fi fost prea... nustiucum, sa fie in linia ta ce o primesti reshare level-ul peerului respectiv. Adica daca un peer imi dadea { A2 A2 } eu daca eram "smecher" ii puteam pune { A5 A5 } acolo fara sa stie el, si i-as fi dat poate boxul peste cap. Dar acuma e clara problema asta Asa e OK

    Mai vreau acum o intrebare: daca pui la o linie { A0 A0 }, asta inseamna ca peerul respectiv nu mai primeste share la localcard-ul tau? Sau setarea de { A0 A0 } nu exista?

    Acuma de la reshare level trec la liniile X si I. Numerele dintre acolade, se pun in DEC sau HEX? Adica, sa zicem daca avem:

    X: { 14 } (14 = 20 in baza 16),

    asta e totuna cu:

    X: { 20 },

    sau daca as pune X: { 20 } ar insemna ca primesc 32 de carti pentru un Provider?

    Mai mult, la linia I, daca vreau ca I sa fie 3 (deci sa primesc carti de la maxim 3 Dreamboxuri departare), pot pune oricare dintre variantele:

    I: { 3 } sau I: { 03 } ?

    (deci diferenta e ca scriu "3" sau "03")


    BAV

  5. #5
    Digitally Remastered Expert
    Join Date
    Feb 2005
    Location
    root
    Posts
    1,527
    Posts Thanks / Likes

    Default

    Acele cifre sunt în hexa.
    Recomand folosirea I: { 2 } sau I: { 3 } (distanţa 2, maxim 3; ce e peste e nefolositor) şi X: { 5 }, maxim X: { A } (adică între 5 şi 10 carduri de fiecare provider), totul depinzând de reţea.
    [LEFT]Signature not found... Try again!

  6. #6
    Junior Member Master
    RDI - Board Default Avatar

    Join Date
    Jan 1970
    Posts
    89
    Posts Thanks / Likes

    Default

    A-ul e pentru nds share. cu A in fata primesti sau dai sky si fara nu.

  7. #7
    Târnacopist Expert
    Join Date
    Dec 2005
    Location
    /home/satwien/
    Posts
    6,001
    Posts Thanks / Likes

    Default

    Eu am alta filizofie:
    Aproape toata lumea primeste numai A2 A3, pentru a mentine sanatatea retelei! . Adica pentru a incuraja aparitia cardurilor locale!
    Merg cu I=2 iar X ajustat astfel incat sa nu depaseasca 400 carduri pe DM500 (inclusiv clone ) sau 600 de carduri pe sistemele mai musculoase. Este arhisuficient, iar gboxul merge cu saptamanile fara reboot.
    Desigur, totul trebuie corelat un ignore.list actualizat, userii care au carduri fake banati fara niciun preaviz, celor care au trafic foarte mare le cer explicatii etc.
    Si inca o observatie la care eu tin mult: reduceti atacurile asupra gboxului, nu il incarcati aiurea. Daca aveti firewall in router sau imagine, blocati IP-urile de unde apar atacurile. O sa observati ca gboxul merge mai bine, e mai stabil si mai rapid.

    PS
    In scurt timp o sa incerc din nou CCcam pe unul din dreamurile mele, astfel incat una din locale va fi mutata de pe Gbox pe CCcam.

  8. #8
    Moderator Expert
    Join Date
    Jul 2006
    Location
    blowfish me....
    Posts
    2,472
    Posts Thanks / Likes

    Default

    sa nu gresesc sau sa ma tzin de @Satwien dar are dreptate si pe zii ce trece ma gandesc la firewallu din pli iolite:P) sau mai bine zis nu mai gandesc ca l-am si instalat

  9. #9
    Junior Member Teacher
    Join Date
    Sep 2006
    Location
    RO, EU
    Posts
    193
    Posts Thanks / Likes

    Default

    Salut!

    Chiar... cum poti vedea ce trafic are un anumit user? Si odata ce vezi ce trafic are... de unde sti daca e prea mare sau nu? Adica... care ar fi traficul normal ca sa spun asa, cam in ce interval ar trebui sa se incadreze?

    Si am vazut ca se mentioneaza de nenumarate ori ca se "testeaza cardul". Cum poti testa un localcard al unui user pe care il adaugi in cwshare.cfg? Adica... daca chiar se deschide imaginea canalului ce ar trebui sa se deschida cu cardul noului peer, de unde stii ca s-a deschis cu localcardul acelui peer?



    BAV

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

    Default

    Cea mai sigura metoda recomandata este alegi un cwshare nou numai cu linia lui, si pui
    I: { 01} dai pe providerul care zice ca il are si verifici ce deschide. Dupa care bagi vechiul cwshare la loc si daca iti convine ce are peerul respectic mai faci si linia G.
    Traficul a unui peer il verifici cu programul gbox share control/netstatepeer. Vezi aici:
    http://www.rdi-board.com/showthread.php?t=65994

  11. #11
    Member Mentor
    Join Date
    Mar 2003
    Location
    Romania
    Posts
    857
    Posts Thanks / Likes

    Default

    Quote Originally Posted by SatWien View Post
    ...
    Si inca o observatie la care eu tin mult: reduceti atacurile asupra gboxului, nu il incarcati aiurea. Daca aveti firewall in router sau imagine, blocati IP-urile de unde apar atacurile. O sa observati ca gboxul merge mai bine, e mai stabil si mai rapid.
    ....
    Asta cred ca se poate trece la categoria "urban legends".
    Am vrut sa verific efectul atacurilor asupra gbox si am facut urmatorul experiment:
    Am trimis de pe PC, cu un program facut de mine, serii de cate 10000 atacuri catre un DM500, deci in retea locala, intarzieri minime, frecventa atacurilor fiind foarte mare.
    Concluzia: in afara de cresterea fisierului atack.txt (in cateva minute fisierul a ajuns la 1MB), nu am constatat nici un efect negativ, dreamul nu s-a miscat mai greu, freezuri nu am avut.
    Redau mai jos o parte din fisierul de loguri (aprox. 3secunde), se poate vedea ca s-au inregistrat cam 60 atacuri pe secunda si chiar si asa au venit chei de NDS in 260 si 397 ms.

    11:51:12 <-CW (<-2) received from xxxxxxxxxxxxxxxxxxxx (0110) (260 ms)
    ...
    11:51:12 <-CW (<-2) received from xxxxxxxxxxxxxxxxxxxxx (0110) (397 ms)

    In mod normal un atac de la un peer vine la zeci de secunde ... cateva minute, dupa acest experiment imi vine greu de crezut ca poate avea vreun efect negativ.

    Code:
    11:51:09 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 <>ECM (3->1) from xxxxxxxxxxbox.co.uk forwarded to 192.168.1.3 (
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 <>ECM (3->1) from xxxxxxxxxxxxx.co.uk forwarded to 192.168.1.3 (
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 <>ECM (1->1) from xxxxxxxxxxxxxxxxxth.cx forwarded to 192.168.1.3 (
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 CW1:  0C B5 93 54 5D 78 31 06
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:10 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
     11:51:11 *ECM: CA ID: 0x0919  11:51:11 Videoguard (NDS)               
    11:51:11 ->ECM send to xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    11:51:11 ->ECM send to xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    11:51:11 ->ECM send to xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    11:51:11 ->ECM send to xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    11:51:11 ->ECM send to xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    11:51:11 ->ECM send to xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
     11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:11 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
     11:51:12 <-CW  (<-2) received from xxxxxxxxxxxxxxxxxxxx (0110) (260 ms)
    11:51:12 Videoguard (NDS)               11:51:12 CW0:  E2 53 CF 04 00 D7 B9 90
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
     11:51:12 <-CW  (<-2) received from xxxxxxxxxxxxxxxxxxxxx (0110) (397 ms)
    11:51:12 CW1:  0C B5 93 54 5D 78 31 06
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 <>ECM (2->1) from xxxxxxxxxxxxx.tv forwarded to 192.168.1.3 (
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG
    11:51:12 ATACK ALERT: from IP 192.168.001.002 port 5566 PASSWORD IS WRONG

  12. #12
    Junior Member Teacher
    Join Date
    Sep 2006
    Location
    RO, EU
    Posts
    193
    Posts Thanks / Likes

    Default

    Salut!

    Am avut Gbox Share Control-ul de mult timp, l-am si updatat cand a iesit noua versiune... dar nici sa imi fi dat in cap nu ma gandeam ca la Netstat peer gasesc statisticile cu traficul facut de peeri Deci am vazut comanda aia, dar nu miam pus problema ce ar face ea

    Am facut Netstat Peer la cativa peeri, dar nu stiu cum sa interpretez rezultatele... adica... nu stiu care ar fi valori "normale"... Am ales un peer la intamplare si am asa:

    __________________________________________________ ___________________________
    |_____________________|_Local Up_|_Local Down_|_Internet Up_|_Internet Down_|
    |___Last 5 minutes____|____0_____|_____0______|_____522_____|____4.3 98_____|
    |_Since Start/Restart_|____0_____|_____0______|___718.441___|___403.608_ ___|


    _______________________________________________
    |_________ECM_________|_IN__|_OUT_|_Forwarded_|
    |_Last 5 minutes______|__28_|__0__|_____2_____|
    |_
    Since Start/restart_|_661_|_15__|___1554____|

    ________________________________________________
    |__________CW_________|__IN__|_OUT_|_Forwarded_|
    |_Last 5 minutes______|___0__|__1__|_____0_____|
    |
    _Since Start/restart_|_1286_|_41__|____29_____|

    ____________________________________
    |_________Hello_______|__IN__|_OUT_|
    |_Last 5 minutes______|___0__|__0__|
    |_Since Start/restart_|___0__|_164_|


    Valorile se incadreaza in normal? Nu stiu daca conteaza asta dar ultimul restart l-am dat acum 3 zile, 21 de ore si 41 minute.

    Si ce masoara ele de fapt? Primul tabel banuiesc ca masoara traficul total [in bytes] facut de peerul respectiv, nu?



    Multumesc,

    BAV

  13. #13
    Junior Member Friend
    RDI - Board Default Avatar

    Join Date
    Apr 2008
    Location
    internet
    Posts
    14
    Posts Thanks / Likes

    Default

    Salut all,
    vin si eu cu o intrebare:

    cwshare.cfg se poate scrie si pentru mgcamd1.28 sau merge la CCCam doar?

    ce asemanator se poate scrie pentru mgcamd?

    tnx in advance,
    schumix

  14. #14
    Târnacopist Expert
    Join Date
    Dec 2005
    Location
    /home/satwien/
    Posts
    6,001
    Posts Thanks / Likes

    Default

    Quote Originally Posted by BAV View Post
    Salut!

    Am avut Gbox Share Control-ul de mult timp, l-am si updatat cand a iesit noua versiune... dar nici sa imi fi dat in cap nu ma gandeam ca la Netstat peer gasesc statisticile cu traficul facut de peeri Deci am vazut comanda aia, dar nu miam pus problema ce ar face ea

    Am facut Netstat Peer la cativa peeri, dar nu stiu cum sa interpretez rezultatele... adica... nu stiu care ar fi valori "normale"... Am ales un peer la intamplare si am asa:

    __________________________________________________ ___________________________
    |_____________________|_Local Up_|_Local Down_|_Internet Up_|_Internet Down_|
    |___Last 5 minutes____|____0_____|_____0______|_____522_____|____4.3 98_____|
    |_Since Start/Restart_|____0_____|_____0______|___718.441___|___403.608_ ___|

    _______________________________________________
    |_________ECM_________|_IN__|_OUT_|_Forwarded_|
    |_Last 5 minutes______|__28_|__0__|_____2_____|
    |_Since Start/restart_|_661_|_15__|___1554____|

    ________________________________________________
    |__________CW_________|__IN__|_OUT_|_Forwarded_|
    |_Last 5 minutes______|___0__|__1__|_____0_____|
    |_Since Start/restart_|_1286_|_41__|____29_____|

    ____________________________________
    |_________Hello_______|__IN__|_OUT_|
    |_Last 5 minutes______|___0__|__0__|
    |_Since Start/restart_|___0__|_164_|


    Valorile se incadreaza in normal? Nu stiu daca conteaza asta dar ultimul restart l-am dat acum 3 zile, 21 de ore si 41 minute.

    Si ce masoara ele de fapt? Primul tabel banuiesc ca masoara traficul total [in bytes] facut de peerul respectiv, nu?



    Multumesc,

    BAV
    Valorile sunt normale, poti sa incepi sa te ingrijorezi in momentul in care valorile cresc cu un ordin de marime.

  15. #15
    Târnacopist Expert
    Join Date
    Dec 2005
    Location
    /home/satwien/
    Posts
    6,001
    Posts Thanks / Likes

    Default

    Quote Originally Posted by schumix View Post
    Salut all,
    vin si eu cu o intrebare:

    cwshare.cfg se poate scrie si pentru mgcamd1.28 sau merge la CCCam doar?

    ce asemanator se poate scrie pentru mgcamd?

    tnx in advance,
    schumix
    Care e de fapt intrebarea? Sa legi CCcam, respectiv MGCamd, cu Gbox?

 

 

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