Auteur Sujet: Plus de TV depuis 2 jours (Lu 8822 fois)

jewome62 · « **Réponse #12 le:** 03 mars 2015 à 19:19:24 »

Citation de: ashemta le 03 mars 2015 à 18:52:45

bonjour,

hum très étrange.

Tu l'a dis! par contre un élèment quand j'ai regarder les logs, j'ai fait une mise à jour impromtu du ubuntu quand j'ai voulu installer un logiciel ...
Mais depuis j'ai essayer en recompilant igmpproxy

Citation de: ashemta le 03 mars 2015 à 18:52:45

le décodeur ne c'est t-il pas mise a jour ? du coup une autre fonctionne qui bloque l'ouverture du flux ?
genre une api en plus.

J'en sais rien pour les mise à jour décodeur
Quand je regarde l'access log de apache, il ne demande pas d'autre page d'api

Citation de: ashemta le 03 mars 2015 à 18:52:45

fraudais voir le syslog de igmpproxy lorsque le décodeur s'allume jusqu’à une chaine . même ci il y a l'erreur. car le décodeur check le flux.

Sur mon précédent poste, cela commence à la ligne "Mar 2 21:59:36 homeServer dhcpd: DHCPOFFER on 192.168.0.23 to e0:a1:d7:c6:0e:10 via eth1"

192.168.0.23 c'est mon décodeur avec lequel je test, et je venais de le redémarrer, j'ai éteins la capture quand j'ai eu l'erreur SL12

Citation de: ashemta le 03 mars 2015 à 18:52:45

Est-ce que tu a essaie de rebranché ta sfr box ? ci oui, est-ce que l’image est de bonne qualité ?
si non, c'est due a l'erreur SL12.

si non, poursuivre pour faire :

Tout fonctionne bien avec la SFRBox donc cela viens du routeur linux et l'image était de bonne qualité

Citation de: ashemta le 03 mars 2015 à 18:52:45

est-ce que tu a reboot ton ONT ?
essaie de faire un reset de ton decodeur.

ci cela fonctionne bien avec la sfr box.

J'ai pas reset le décodeur, ni l'ONT

Citation de: ashemta le 03 mars 2015 à 18:52:45

reste plus qu'a reboot ton serveur ... car y doit y avoir un problème cache ou pile... et cela doit être un problème de flux --ont--pc--decodeur.
(backup tout la conf avant)

Le serveur a été rebooter plusieurs fois sans succès.
J'ai tout bien fait pour que les services redémarre seul au démarrage et que iptable soit sauvegardé et restauré (En cas de coupure de courant, un reboot et pas besoin de se remettre à de l'admin système)

Citation de: ashemta le 03 mars 2015 à 18:52:45

reboot t'es switch/routeur ci tu en a.

ps chez moi j'ai un matériel etherne qui me pixelise le flux, une fois débranché ca va beaucoup mieux ( pas d'autre système Ethernet qui tu a rajouter ? home ciné, tv, camera ...)

Tout fonctionne en Ethernet, j'ai une dizaine d'appareils sur le réseau, j'ai jamais eu de soucis avec.

Ce soir :

On éteins tout (ONT, routeur, switch, décodeur) et on reset ONT et décodeur

ashemta · « **Réponse #13 le:** 03 mars 2015 à 19:53:10 »

Citation de: jewome62 le 03 mars 2015 à 19:19:24

Ce soir :

On éteins tout (ONT, routeur, switch, décodeur) et on reset ONT et décodeur

oki ça marche j’espère que ça résoudra ton problème ...

jewome62 · « **Réponse #14 le:** 03 mars 2015 à 20:09:06 »

Alors, j'ai tout fais (sauf reset ONT, je ne l'ai que redémarrer) et aucune amélioration,

Voici un log igmpproxy en mode commande (pas en daemon) et verbose

J'ai fait la commande et j'ai rallumer électriquement le décodeur jusqu'à avoir l'erreur et j'ai zapper sur quelques chaine sans grand résultat

Code: [Sélectionner]

root@homeServer:/# /usr/local/sbin/igmpproxy -v -d /usr/local/etc/igmpproxy.conf
adding VIF, Ix 0 Fl 0x0 IP 0xc5dd186d eth0, Threshold: 1, Ratelimit: 0
adding VIF, Ix 1 Fl 0x0 IP 0x0100a8c0 eth1, Threshold: 1, Ratelimit: 0
joinMcGroup: 224.0.0.2 on eth1
RECV Membership query   from 192.168.0.1     to 224.0.0.1
RECV V2 member report   from 192.168.0.1     to 224.0.0.2
Mebership report was recieved on the upstream interface. Ignoring.
RECV Membership query   from 0.0.0.1         to 224.0.0.1
RECV V2 member report   from 192.168.0.1     to 224.0.0.251
Mebership report was recieved on the upstream interface. Ignoring.
RECV V2 member report   from 192.168.0.1     to 239.255.255.250
Mebership report was recieved on the upstream interface. Ignoring.
Inserted route table entry for 239.255.255.250 on VIF #-1
RECV V2 member report   from 109.24.221.197  to 224.0.0.251
The IGMP message was from myself. Ignoring.
RECV V2 member report   from 109.24.221.197  to 239.255.255.250
The IGMP message was from myself. Ignoring.
Route activation request from 109.24.221.197 for 239.255.255.250 is from myself. Ignoring.
RECV Membership query   from 192.168.0.1     to 224.0.0.1
RECV Membership query   from 0.0.0.1         to 224.0.0.1
RECV V2 member report   from 192.168.0.1     to 239.255.255.250
Mebership report was recieved on the upstream interface. Ignoring.
RECV V2 member report   from 192.168.0.1     to 224.0.0.2
Mebership report was recieved on the upstream interface. Ignoring.
RECV V2 member report   from 192.168.0.1     to 224.0.0.251
Mebership report was recieved on the upstream interface. Ignoring.
Removing MFC: 192.168.0.1 -> 239.255.255.250, InpVIf: 0
MRT_DEL_MFC; Errno(2): No such file or directory
RECV V2 member report   from 109.24.221.197  to 224.0.0.251
The IGMP message was from myself. Ignoring.
RECV V2 member report   from 109.24.221.197  to 239.255.255.250
The IGMP message was from myself. Ignoring.
Route activation request from 109.24.221.197 for 239.255.255.250 is from myself. Ignoring.
Inserted route table entry for 239.255.255.250 on VIF #-1
RECV Membership query   from 192.168.0.1     to 224.0.0.1
RECV V2 member report   from 192.168.0.1     to 239.255.255.250
Mebership report was recieved on the upstream interface. Ignoring.
The origin for route 239.255.255.250 changed from 192.168.0.23 to 192.168.0.1
RECV Membership query   from 0.0.0.1         to 224.0.0.1
RECV V2 member report   from 192.168.0.1     to 224.0.0.2
Mebership report was recieved on the upstream interface. Ignoring.
The origin for route 239.255.255.250 changed from 192.168.0.1 to 192.168.0.23
RECV V2 member report   from 109.24.221.197  to 224.0.0.251
The IGMP message was from myself. Ignoring.
RECV V2 member report   from 109.24.221.197  to 239.255.255.250
The IGMP message was from myself. Ignoring.
Route activation request from 109.24.221.197 for 239.255.255.250 is from myself. Ignoring.
RECV V2 member report   from 192.168.0.1     to 224.0.0.251
Mebership report was recieved on the upstream interface. Ignoring.
The origin for route 239.255.255.250 changed from 192.168.0.23 to 192.168.0.50
The origin for route 239.255.255.250 changed from 192.168.0.50 to 192.168.0.23
RECV Membership query   from 0.0.0.1         to 224.0.0.1
RECV V2 member report   from 109.24.221.197  to 224.0.0.251
The IGMP message was from myself. Ignoring.
RECV V2 member report   from 109.24.221.197  to 239.255.255.250
The IGMP message was from myself. Ignoring.
Route activation request from 109.24.221.197 for 239.255.255.250 is from myself. Ignoring.
RECV Membership query   from 0.0.0.1         to 224.0.0.1
RECV V2 member report   from 109.24.221.197  to 239.255.255.250
The IGMP message was from myself. Ignoring.
Route activation request from 109.24.221.197 for 239.255.255.250 is from myself. Ignoring.
RECV V2 member report   from 109.24.221.197  to 224.0.0.251
The IGMP message was from myself. Ignoring.
RECV Membership query   from 0.0.0.1         to 224.0.0.1
RECV V2 member report   from 109.24.221.197  to 239.255.255.250
The IGMP message was from myself. Ignoring.
Route activation request from 109.24.221.197 for 239.255.255.250 is from myself. Ignoring.
RECV V2 member report   from 109.24.221.197  to 224.0.0.251
The IGMP message was from myself. Ignoring.
The origin for route 239.255.255.250 changed from 192.168.0.23 to 192.168.0.60
The origin for route 239.255.255.250 changed from 192.168.0.60 to 192.168.0.23
RECV Membership query   from 0.0.0.1         to 224.0.0.1
RECV Membership query   from 192.168.0.1     to 224.0.0.1
RECV V2 member report   from 192.168.0.1     to 224.0.0.2
Mebership report was recieved on the upstream interface. Ignoring.
RECV V2 member report   from 109.24.221.197  to 239.255.255.250
The IGMP message was from myself. Ignoring.
Route activation request from 109.24.221.197 for 239.255.255.250 is from myself. Ignoring.
RECV V2 member report   from 192.168.0.1     to 224.0.0.251
Mebership report was recieved on the upstream interface. Ignoring.
RECV V2 member report   from 109.24.221.197  to 224.0.0.251
The IGMP message was from myself. Ignoring.
RECV V2 member report   from 192.168.0.1     to 239.255.255.250
Mebership report was recieved on the upstream interface. Ignoring.
The origin for route 239.255.255.250 changed from 192.168.0.23 to 192.168.0.1
Removing MFC: 192.168.0.1 -> 239.255.255.250, InpVIf: 0
MRT_DEL_MFC; Errno(2): No such file or directory
Inserted route table entry for 239.255.255.250 on VIF #-1
The origin for route 239.255.255.250 changed from 192.168.0.50 to 192.168.0.23
^Cselect() failure; Errno(4): Interrupted system call
Got a interupt signal. Exiting.
Removing MFC: 192.168.0.23 -> 239.255.255.250, InpVIf: 0
MRT_DEL_MFC; Errno(2): No such file or directory
All routes removed. Routing table is empty.
Shutdown complete....

ashemta · « **Réponse #15 le:** 04 mars 2015 à 12:13:00 »

bonjour,

je c'est plus ou donnée de la tête....

ashemta · « **Réponse #16 le:** 05 mars 2015 à 19:31:28 »

bonsoir,

toujours pas de news ?

jewome62 · « **Réponse #17 le:** 05 mars 2015 à 20:02:49 »

Nop,

J'ai l'impression que il n'y a rien qui s'applique ...
Bref, j'ai refais une compilation igmpproxy pour voir si je n'aurai pas déinstaller un truc mais rien à l'horizon ...

Est-ce-qu'un qui aurait une machine (qui sert à rien) pourrais refaire la procédure sur un ubuntu frais (pour savoir si un mise à jour de bibliothèque aurait changer quelque chose)

jewome62 · « **Réponse #18 le:** 05 mars 2015 à 20:15:47 »

Petit log en mode very verbose

Code: [Sélectionner]

root@homeServer:~/igmpproxy-0.1/doc# /usr/local/sbin/igmpproxy -vv -d /usr/local/etc/igmpproxy.conf
Searching for config file at '/usr/local/etc/igmpproxy.conf'
Config: Got a phyint token.
Config: IF: Config for interface eth0.
Config: IF: Got upstream token.
Config: IF: Got ratelimit token '0'.
Config: IF: Got threshold token '1'.
Config: IF: Got altnet token 10.0.0.0/8.
Config: IF: Altnet: Parsed altnet to 10/8.
Config: IF: Got altnet token 192.168.0.0/24.
Config: IF: Altnet: Parsed altnet to 192.168.0/24.
Config: IF: Got altnet token 10.10.0.0/16.
Config: IF: Altnet: Parsed altnet to 10.10/16.
Config: IF: Got altnet token 10.200.0.0/16.
Config: IF: Altnet: Parsed altnet to 10.200/16.
Config: IF: Got altnet token 233.0.0.0/8.
Config: IF: Altnet: Parsed altnet to 233/8.
Config: IF: Got altnet token 224.0.0.0/8.
Config: IF: Altnet: Parsed altnet to 224/8.
Config: IF: Got altnet token 93.17.149.15.
Config: IF: Altnet: Parsed altnet to 93.17.149.15/32.
Config: IF: Got altnet token 93.17.149.158.
Config: IF: Altnet: Parsed altnet to 93.17.149.158/32.
Config: IF: Got altnet token 86.66.67.62.
Config: IF: Altnet: Parsed altnet to 86.66.67.62/32.
Config: IF: Got altnet token 86.66.67.58.
Config: IF: Altnet: Parsed altnet to 86.66.67.58/32.
Config: IF: Got altnet token 93.20.55.42.
Config: IF: Altnet: Parsed altnet to 93.20.55.42/32.
Config: IF: Got altnet token 86.65.232.0/24.
Config: IF: Altnet: Parsed altnet to 86.65.232/24.
Config: IF: Got altnet token 80.118.201.0/24.
Config: IF: Altnet: Parsed altnet to 80.118.201/24.
Config: IF: Got altnet token 84.96.146.0/24.
Config: IF: Altnet: Parsed altnet to 84.96.146/24.
Config: IF: Got altnet token 84.96.219.0/24.
Config: IF: Altnet: Parsed altnet to 84.96.219/24.
Config: IF: Got altnet token 80.118.192.0/24.
Config: IF: Altnet: Parsed altnet to 80.118.192/24.
Config: IF: Got altnet token 86.65.94.0/24.
Config: IF: Altnet: Parsed altnet to 86.65.94/24.
Config: IF: Got altnet token 86.65.95.0/24.
Config: IF: Altnet: Parsed altnet to 86.65.95/24.
Config: IF: Got altnet token 86.64.245.128/25.
Config: IF: Altnet: Parsed altnet to 86.64.245.128/25.
Config: IF: Got altnet token 86.64.159.201/32.
Config: IF: Altnet: Parsed altnet to 86.64.159.201/32.
Config: IF: Got altnet token 93.17.149.158/32.
Config: IF: Altnet: Parsed altnet to 93.17.149.158/32.
Config: IF: Got altnet token 109.203.65.49/32.
Config: IF: Altnet: Parsed altnet to 109.203.65.49/32.
IF name : eth0
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 1
Allowednet ptr : 1f274b0
Config: Got a phyint token.
Config: IF: Config for interface eth1.
Config: IF: Got downstream token.
Config: IF: Got ratelimit token '0'.
Config: IF: Got threshold token '1'.
IF name : eth1
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 2
Allowednet ptr : 0
buildIfVc: Interface lo Addr: 127.0.0.1, Flags: 0x0049, Network: 127/8
buildIfVc: Interface eth0 Addr: 109.24.221.197, Flags: 0x1043, Network: 109.24.221/24
buildIfVc: Interface eth1 Addr: 192.168.0.1, Flags: 0x1043, Network: 192.168.0/24
Found config for eth0
Found config for eth1
adding VIF, Ix 0 Fl 0x0 IP 0xc5dd186d eth0, Threshold: 1, Ratelimit: 0
        Network for [eth0] : 109.24.221/24
        Network for [eth0] : 10/8
        Network for [eth0] : 192.168.0/24
        Network for [eth0] : 10.10/16
        Network for [eth0] : 10.200/16
        Network for [eth0] : 233/8
        Network for [eth0] : 224/8
        Network for [eth0] : 93.17.149.15/32
        Network for [eth0] : 93.17.149.158/32
        Network for [eth0] : 86.66.67.62/32
        Network for [eth0] : 86.66.67.58/32
        Network for [eth0] : 93.20.55.42/32
        Network for [eth0] : 86.65.232/24
        Network for [eth0] : 80.118.201/24
        Network for [eth0] : 84.96.146/24
        Network for [eth0] : 84.96.219/24
        Network for [eth0] : 80.118.192/24
        Network for [eth0] : 86.65.94/24
        Network for [eth0] : 86.65.95/24
        Network for [eth0] : 86.64.245.128/25
        Network for [eth0] : 86.64.159.201/32
        Network for [eth0] : 93.17.149.158/32
        Network for [eth0] : 109.203.65.49/32
adding VIF, Ix 1 Fl 0x0 IP 0x0100a8c0 eth1, Threshold: 1, Ratelimit: 0
        Network for [eth1] : 192.168.0/24
Got 262144 byte buffer size in 0 iterations
Joining all-routers group 224.0.0.2 on vif 192.168.0.1
joinMcGroup: 224.0.0.2 on eth1
SENT Membership query   from 192.168.0.1     to 224.0.0.1
Sent membership query from 192.168.0.1 to 224.0.0.1. Delay: 10
Created timeout 1 (#0) - delay 10 secs
(Id:1, Time:10)
Created timeout 2 (#1) - delay 21 secs
(Id:1, Time:10)
(Id:2, Time:21)
RECV Membership query   from 192.168.0.1     to 224.0.0.1
RECV V2 member report   from 192.168.0.1     to 224.0.0.2
Mebership report was recieved on the upstream interface. Ignoring.
Route activate request from 192.168.0.22 to 239.255.255.250
No table entry for 239.255.255.250 [From: 192.168.0.22]. Inserting route.
No existing route for 239.255.255.250. Create new.
No routes in table. Insert at beginning.
Inserted route table entry for 239.255.255.250 on VIF #-1
No downstream listeners for group 239.255.255.250. No join sent.

Current routing table (Insert Route):
-----------------------------------------------------
#0: Src: 0.0.0.0, Dst: 239.255.255.250, Age:2, St: I, OutVifs: 0x00000000
-----------------------------------------------------

Current routing table (Activate Route):
-----------------------------------------------------
#0: Src: 192.168.0.22, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
-----------------------------------------------------
RECV V2 member report   from 192.168.0.1     to 239.255.255.250
Mebership report was recieved on the upstream interface. Ignoring.
Route activate request from 192.168.0.1 to 239.255.255.250
The origin for route 239.255.255.250 changed from 192.168.0.22 to 192.168.0.1

Current routing table (Activate Route):
-----------------------------------------------------
#0: Src: 192.168.0.1, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
-----------------------------------------------------
RECV V2 member report   from 192.168.0.1     to 224.0.0.251
Mebership report was recieved on the upstream interface. Ignoring.
About to call timeout 1 (#0)
Aging routes in table.

Current routing table (Age active routes):
-----------------------------------------------------
#0: Src: 192.168.0.1, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
-----------------------------------------------------
RECV Membership query   from 0.0.0.1         to 224.0.0.1
RECV V2 member report   from 109.24.221.197  to 239.255.255.250
The IGMP message was from myself. Ignoring.
Route activation request from 109.24.221.197 for 239.255.255.250 is from myself. Ignoring.
Route activate request from 192.168.0.23 to 239.255.255.250
The origin for route 239.255.255.250 changed from 192.168.0.1 to 192.168.0.23

Current routing table (Activate Route):
-----------------------------------------------------
#0: Src: 192.168.0.23, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
-----------------------------------------------------
Route activate request from 192.168.0.60 to 239.255.255.250
The origin for route 239.255.255.250 changed from 192.168.0.23 to 192.168.0.60

Current routing table (Activate Route):
-----------------------------------------------------
#0: Src: 192.168.0.60, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
-----------------------------------------------------
RECV V2 member report   from 109.24.221.197  to 224.0.0.251
The IGMP message was from myself. Ignoring.
About to call timeout 2 (#0)
SENT Membership query   from 192.168.0.1     to 224.0.0.1
Sent membership query from 192.168.0.1 to 224.0.0.1. Delay: 10
Created timeout 3 (#0) - delay 10 secs
(Id:3, Time:10)
Created timeout 4 (#1) - delay 21 secs
(Id:3, Time:10)
(Id:4, Time:21)
RECV Membership query   from 192.168.0.1     to 224.0.0.1
Route activate request from 192.168.0.22 to 239.255.255.250
The origin for route 239.255.255.250 changed from 192.168.0.60 to 192.168.0.22

Current routing table (Activate Route):
-----------------------------------------------------
#0: Src: 192.168.0.22, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
-----------------------------------------------------
RECV V2 member report   from 192.168.0.1     to 224.0.0.251
Mebership report was recieved on the upstream interface. Ignoring.
RECV V2 member report   from 192.168.0.1     to 239.255.255.250
Mebership report was recieved on the upstream interface. Ignoring.
Route activate request from 192.168.0.1 to 239.255.255.250
The origin for route 239.255.255.250 changed from 192.168.0.22 to 192.168.0.1

Current routing table (Activate Route):
-----------------------------------------------------
#0: Src: 192.168.0.1, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
-----------------------------------------------------
RECV V2 member report   from 192.168.0.1     to 224.0.0.2
Mebership report was recieved on the upstream interface. Ignoring.
About to call timeout 3 (#0)
Aging routes in table.
Removing group 239.255.255.250. Died of old age.
Removed route entry for 239.255.255.250 from table.
Vif bits : 0x00000000
Removing MFC: 192.168.0.1 -> 239.255.255.250, InpVIf: 0
MRT_DEL_MFC; Errno(2): No such file or directory

Current routing table (Remove route):
-----------------------------------------------------
No routes in table...
-----------------------------------------------------

Current routing table (Age active routes):
-----------------------------------------------------
No routes in table...
-----------------------------------------------------
RECV Membership query   from 0.0.0.1         to 224.0.0.1
RECV V2 member report   from 109.24.221.197  to 224.0.0.251
The IGMP message was from myself. Ignoring.
Route activate request from 192.168.0.23 to 239.255.255.250
No table entry for 239.255.255.250 [From: 192.168.0.23]. Inserting route.
No existing route for 239.255.255.250. Create new.
No routes in table. Insert at beginning.
Inserted route table entry for 239.255.255.250 on VIF #-1
No downstream listeners for group 239.255.255.250. No join sent.

Current routing table (Insert Route):
-----------------------------------------------------
#0: Src: 0.0.0.0, Dst: 239.255.255.250, Age:2, St: I, OutVifs: 0x00000000
-----------------------------------------------------

Current routing table (Activate Route):
-----------------------------------------------------
#0: Src: 192.168.0.23, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
-----------------------------------------------------
RECV V2 member report   from 109.24.221.197  to 239.255.255.250
The IGMP message was from myself. Ignoring.
Route activation request from 109.24.221.197 for 239.255.255.250 is from myself. Ignoring.
Route activate request from 192.168.0.22 to 239.255.255.250
The origin for route 239.255.255.250 changed from 192.168.0.23 to 192.168.0.22

Current routing table (Activate Route):
-----------------------------------------------------
#0: Src: 192.168.0.22, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
-----------------------------------------------------
^Cselect() failure; Errno(4): Interrupted system call
Got a interupt signal. Exiting.
clean handler called
Removing route entry for 239.255.255.250
Vif bits : 0x00000000
Removing MFC: 192.168.0.22 -> 239.255.255.250, InpVIf: 0
MRT_DEL_MFC; Errno(2): No such file or directory
All routes removed. Routing table is empty.
Shutdown complete....

Pour info, j'ai la même erreur que j'active igmpproxy ou pas ...

jewome62 · « **Réponse #19 le:** 15 mars 2015 à 20:40:25 »

Bon pas de solution en vue.

J'ai acheter un HDD externe de 2TO, je suis en train de faire une sauvegarde du raid et des fichiers système (/var, /etc, etc) et je vais tout reformater.

Auriez-vous une suggestion moins "Hard" ?

En sachant que le SSD avec les fichiers système n'utilise que 8.7Go sur les 55Go disponible. j'imagine que je peux réduire la seul partition pour en faire une seconde. et éviter de formater tout.
Après, comment j'exporte mes config raid pour bien tout remonté sans tout perdre (j'ai une sauvegarde mais j'aimerai faire au plus rapide et ne pas tout recopier à nouveau)

Thanks

jewome62 · « **Réponse #20 le:** 21 mars 2015 à 17:30:59 »

Pendez-moi par les pieds car il s'agit d'une connerie.

Je détaillerai cela ce soir, la je vais faire des courses

ashemta · « **Réponse #21 le:** 09 avril 2015 à 17:47:29 »

Citation de: jewome62 le 21 mars 2015 à 17:30:59

Pendez-moi par les pieds car il s'agit d'une connerie.

Je détaillerai cela ce soir, la je vais faire des courses

J'aimerais connaître ton erreur

jewome62 · « **Réponse #22 le:** 11 avril 2015 à 00:14:59 »

Erreur de syntaxe dans igmpproxy.conf

J'ai copié le tient et je n'ai plus eu de problème ...