SatEurope.net
Z2U.com - IPTV
CardShare.cc
Advertise Here
Advertise Here
Advertise Here
Advertise Here
Advertise Here
Page 1 of 2 122 LastLast
Results 1 to 10 of 19

Thread: besoin d aide urgent CCcam 2.1.2 block mon routeur après quelque heure

  1. #1
    Member
    Join Date
    01-11-2008
    Posts
    65
    Uploads
    0
    Likes
    0

    besoin d aide urgent CCcam 2.1.2 block mon routeur après quelque heure

    bonjours a tous

    j ai une carte bis tv et depuis juin probleme apres update les chaine action cine fx. etc ne fonctionne plus en Cccam 2.0.11

    solution fix cccam 2.1.2 oui mais depuis que je l est installer mon routeur n arrete plus de s emballer il block completement mon reseau seule solution demarrer le routeur et puis mon serveur mais ca ne durre que quelle heure puis ca revien de nouveau mais si je retourn en Cccam 2.0.11 pas de probleme
    mais mes chainne ne fonctionne pas non plus en 2.0.11

    pour info
    j ai un serveur debian version 5
    avec 2 smargo+ reader.

    si quelqu un a rencontrai ce probleme et a put le resoundre ca peut servir.
    merci d avance.

  2. SatEurope.net
  3. #2
    Member
    Join Date
    01-11-2008
    Posts
    65
    Uploads
    0
    Likes
    0

    Re: besoin d aide urgent CCcam 2.1.2 block mon routeur après quelque heure

    visiblement je suis le seule a avoirs des problème ?

  4. #3
    VIP Member agecanonixeg's Avatar
    Join Date
    16-12-2006
    Location
    France
    Posts
    305
    Uploads
    4
    Likes
    1

    Wink Re: besoin d aide urgent CCcam 2.1.2 block mon routeur après quelque heure

    Si tu lis ta carte directement, utilise newcs+cccam ou cardesrver+cccam
    pour faire un essai sans changer de version de cccam. Ou bien, change
    de routeur (perso linksys WRT54G avec firm dd-wrt).
    amicalement

  5. #4
    Justice For All Tunimax's Avatar
    Join Date
    11-07-2006
    Location
    In My Room
    Posts
    3,539
    Uploads
    1,611
    Likes
    59

    Re: besoin d aide urgent CCcam 2.1.2 block mon routeur après quelque heure

    j'ais eu un probleme l'autre jour avec quelque chaine . je sais pas sa peus marcher avec toi
    la qu'elle ??
    desinstalle ou desactive constant.cw===== /var/key
    parfois sa fais un confusion
    tien moi au courant *
    bye

  6. #5
    VIP Member agecanonixeg's Avatar
    Join Date
    16-12-2006
    Location
    France
    Posts
    305
    Uploads
    4
    Likes
    1

    Talking Re: besoin d aide urgent CCcam 2.1.2 block mon routeur après quelque heure

    Quote Originally Posted by ►Tunimax™♫♫♫ View Post
    j'ais eu un probleme l'autre jour avec quelque chaine . je sais pas sa peus marcher avec toi
    la qu'elle ??
    desinstalle ou desactive constant.cw===== /var/key
    parfois sa fais un confusion
    tien moi au courant *
    bye
    C'est exacte, il y a un bug avec la derniere version de CCcam 2.1.2
    et le fichier constant.cw. (ecran noir....), tu as raison Tunimax™♫♫♫ cela peut venir de la.
    amicalement

  7. #6
    Member
    Join Date
    01-11-2008
    Posts
    65
    Uploads
    0
    Likes
    0

    Re: besoin d aide urgent CCcam 2.1.2 block mon routeur après quelque heure

    merci les amis de votre aides,

    mais le fichier constant.cw n'est pas dans mon serveur je ne l'est pas installer, je vien juste de verifier.

    mon problème ce trouve plus au niveau de mon routeur je pensse,

    mais ca dois depandre aussi du CCCam2.1.2 qui dois surement faire d'autre chause et mon routeur me dans dans le firewall log block nat,

    meme en le désactivant le problème persiste, est ce que le lynksys suporte le VDSL 2 ??

  8. #7
    VIP Member noobox's Avatar
    Join Date
    12-03-2006
    Location
    Aghioul City
    Posts
    732
    Uploads
    11
    Likes
    1

    Re: besoin d aide urgent CCcam 2.1.2 block mon routeur après quelque heure

    Colle un log de ton router

  9. #8
    VIP Member agecanonixeg's Avatar
    Join Date
    16-12-2006
    Location
    France
    Posts
    305
    Uploads
    4
    Likes
    1

    Exclamation Re: besoin d aide urgent CCcam 2.1.2 block mon routeur après quelque heure

    Quote Originally Posted by asterix_V View Post

    meme en le désactivant le problème persiste, est ce que le lynksys suporte le VDSL 2 ??
    C'est un routeur wifi pur et dur (de marque cisco pour les puristes)
    il ne se connecte pas directement a une ligne telephonique...
    il doit etre raccordé au modem (routeur) adsl
    amicalement

  10. #9
    Member
    Join Date
    01-11-2008
    Posts
    65
    Uploads
    0
    Likes
    0

    Re: besoin d aide urgent CCcam 2.1.2 block mon routeur après quelque heure

    voici le log dans mon routeur visiblement il se met a tous bloquer

    Aug 8 18:47:22 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1942->80.252.110.146:4661 on ppp0
    Aug 8 18:47:22 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1946->66.199.250.170:8911 on ppp0
    Aug 8 18:47:21 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1942->80.252.110.146:4661 on ppp0
    Aug 8 18:47:21 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1940->60.28.197.35:28221 on ppp0
    Aug 8 18:47:21 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1941->72.51.37.237:8899 on ppp0
    Aug 8 18:47:21 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1942->80.252.110.146:4661 on ppp0
    Aug 8 18:47:20 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1940->60.28.197.35:28221 on ppp0
    Aug 8 18:47:20 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1941->72.51.37.237:8899 on ppp0 [repeated 2 times, last time on Aug 8 18:47:20 2009]
    Aug 8 18:47:20 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1940->60.28.197.35:28221 on ppp0
    Aug 8 18:47:19 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:57481->77.207.77.221:64646 on ppp0
    Aug 8 18:47:19 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:37381->85.56.192.37:12000 on ppp0
    Aug 8 18:47:19 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:39905->41.228.232.152:17500 on ppp0
    Aug 8 18:47:17 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1934->219.239.90.172:28221 on ppp0
    Aug 8 18:47:17 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1935->66.199.250.170:8911 on ppp0
    Aug 8 18:47:17 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1934->219.239.90.172:28221 on ppp0
    Aug 8 18:47:16 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1935->66.199.250.170:8911 on ppp0 [repeated 2 times, last time on Aug 8 18:47:17 2009]
    Aug 8 18:47:16 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1934->219.239.90.172:28221 on ppp0
    Aug 8 18:47:16 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1929->80.252.110.146:4661 on ppp0
    Aug 8 18:47:15 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:39072->80.200.201.178:6666 on ppp0
    Aug 8 18:47:15 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:47055->79.32.161.124:12000 on ppp0
    Aug 8 18:47:15 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1929->80.252.110.146:4661 on ppp0 [repeated 2 times, last time on Aug 8 18:47:15 2009]
    Aug 8 18:47:15 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1928->72.51.37.237:8899 on ppp0
    Aug 8 18:47:15 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1927->60.28.197.35:28221 on ppp0 [repeated 2 times, last time on Aug 8 18:47:15 2009]
    Aug 8 18:47:14 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1928->72.51.37.237:8899 on ppp0 [repeated 2 times, last time on Aug 8 18:47:15 2009]
    Aug 8 18:47:14 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1927->60.28.197.35:28221 on ppp0
    Aug 8 18:47:12 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:57476->77.207.77.221:64646 on ppp0
    Aug 8 18:47:12 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:37376->85.56.192.37:12000 on ppp0
    Aug 8 18:47:12 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:39900->41.228.232.152:17500 on ppp0
    Aug 8 18:47:11 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1926->66.199.250.170:8911 on ppp0
    Aug 8 18:47:11 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1925->219.239.90.172:28221 on ppp0
    Aug 8 18:47:11 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1926->66.199.250.170:8911 on ppp0
    Aug 8 18:47:11 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1925->219.239.90.172:28221 on ppp0
    Aug 8 18:47:10 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1926->66.199.250.170:8911 on ppp0
    Aug 8 18:47:10 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1925->219.239.90.172:28221 on ppp0
    Aug 8 18:47:09 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1924->80.252.110.146:4661 on ppp0 [repeated 3 times, last time on Aug 8 18:47:10 2009]
    Aug 8 18:47:09 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1922->60.28.197.35:28221 on ppp0
    Aug 8 18:47:09 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1923->72.51.37.237:8899 on ppp0
    Aug 8 18:47:08 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1922->60.28.197.35:28221 on ppp0
    Aug 8 18:47:08 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1923->72.51.37.237:8899 on ppp0
    Aug 8 18:47:08 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:39067->80.200.201.178:6666 on ppp0
    Aug 8 18:47:08 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:47050->79.32.161.124:12000 on ppp0
    Aug 8 18:47:08 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1923->72.51.37.237:8899 on ppp0
    Aug 8 18:47:08 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1922->60.28.197.35:28221 on ppp0
    Aug 8 18:47:06 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:57471->77.207.77.221:64646 on ppp0
    Aug 8 18:47:06 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:37371->85.56.192.37:12000 on ppp0
    Aug 8 18:47:06 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:39895->41.228.232.152:17500 on ppp0
    Aug 8 18:47:06 2009 Outbound Traffic Blocked - NAT out failed UDP 192.168.1.11:23441->80.239.200.109:3004 on ppp0
    Aug 8 18:47:05 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1921->219.239.90.172:28221 on ppp0 [repeated 2 times, last time on Aug 8 18:47:05 2009]
    Aug 8 18:47:05 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1920->66.199.250.170:8911 on ppp0
    Aug 8 18:47:04 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1919->80.252.110.146:4661 on ppp0
    Aug 8 18:47:04 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1921->219.239.90.172:28221 on ppp0
    Aug 8 18:47:04 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1920->66.199.250.170:8911 on ppp0
    Aug 8 18:47:04 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1919->80.252.110.146:4661 on ppp0
    Aug 8 18:47:03 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:39062->80.200.201.178:6666 on ppp0
    Aug 8 18:47:03 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:47045->79.32.161.124:12000 on ppp0
    Aug 8 18:47:03 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1920->66.199.250.170:8911 on ppp0
    Aug 8 18:47:03 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1919->80.252.110.146:4661 on ppp0
    Aug 8 18:47:03 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1918->72.51.37.237:8899 on ppp0
    Aug 8 18:47:03 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1917->60.28.197.35:28221 on ppp0
    Aug 8 18:47:03 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1918->72.51.37.237:8899 on ppp0
    Aug 8 18:47:03 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1917->60.28.197.35:28221 on ppp0
    Aug 8 18:47:02 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1918->72.51.37.237:8899 on ppp0
    Aug 8 18:47:02 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1917->60.28.197.35:28221 on ppp0
    Aug 8 18:47:00 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:57466->77.207.77.221:64646 on ppp0
    Aug 8 18:47:00 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:37366->85.56.192.37:12000 on ppp0
    Aug 8 18:47:00 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.20:39890->41.228.232.152:17500 on ppp0
    Aug 8 18:46:58 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1916->219.239.90.172:28221 on ppp0 [repeated 3 times, last time on Aug 8 18:46:59 2009]
    Aug 8 18:46:58 2009 Outbound Traffic Blocked - NAT out failed UDP 192.168.1.11:23441->222.186.190.39:4073 on ppp0
    Aug 8 18:46:58 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1915->66.199.250.170:8911 on ppp0
    Aug 8 18:46:58 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1914->80.252.110.146:4661 on ppp0
    Aug 8 18:46:58 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1915->66.199.250.170:8911 on ppp0
    Aug 8 18:46:58 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1914->80.252.110.146:4661 on ppp0
    Aug 8 18:46:57 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1915->66.199.250.170:8911 on ppp0
    Aug 8 18:46:57 2009 Outbound Traffic Blocked - NAT out failed TCP 192.168.1.11:1914->80.252.110.146:4661 on ppp0

    si sa peut aider est que quelqu'un sait comment seactiver complètement le firewall sur un bbox2 belgacom

  11. Z2U.com - IPTV
  12. #10
    Member
    Join Date
    10-10-2005
    Posts
    90
    Uploads
    0
    Likes
    0

    Re: besoin d aide urgent CCcam 2.1.2 block mon routeur après quelque heure

    salut
    pour ton touteur je te conseil de le reseter ( n oublie pas de prendre note de tes donnee port ouvert etc etc ) pour le reseter il y as un petit trous derriere avec un cure dent ou autre tu pousse dessus quelque segonde et il vas revenir a l etat d origine apres tu reinstale tes port et le reste et tu verras ce que sa donne si sa deconne encore faut le changee desoler
    pour la carte absat a mon avis tu as le meme probleme que moi
    depuis un mois cette salope de carte deconne hihihihihi
    apres plusieur teste voilas ce que sa dit chez moi
    en ccam2.1.2
    en restant sur les chaines absat ( ha oui relance ta ccam avant )tu vas voir que tout vas sans probleme ( absat ou bis comme tu veus ) si tu change et tu met une autre chaine exemple canal plus tu verras que tu as perdus la moitier des chaines bis ces bizard met j ai pas trouver la solution par contre si je la met dans un recepteur exemple humax tout vas sans souci ces nikel
    solution et je ne fait pas de la pub tu prend une telesat belge tu aurras tout les bis plus les petit belge pour 20 euro par mois
    n oublie pas de nous dire si sa fonctione

Page 1 of 2 122 LastLast

Similar Threads

  1. Replies: 1
    Last Post: 27-02-2008, 14:49:33
  2. AIDE : Configurer Gbox sans routeur avec 56k thx
    By Wesker in forum French / Français
    Replies: 2
    Last Post: 17-04-2007, 15:03:42
  3. Besoin d'aide après retour vacances
    By Sarenner in forum French / Français
    Replies: 1
    Last Post: 28-08-2006, 10:22:20
  4. code pin kaon 570 apres flashe urgent
    By versatis in forum French / Français
    Replies: 5
    Last Post: 08-01-2006, 18:18:31
  5. dreambox 7000 qui ne redemmarre plus après une heure
    By constant in forum French / Français
    Replies: 0
    Last Post: 06-11-2005, 14:51:30

Posting Permissions

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