Opa Posted October 3, 2017 Report Share Posted October 3, 2017 Bonjour, Depuis mon travail je n'arrive pas à me connecter à ma freebox et tout ce qui est host chez moi. Un petit traceroute vers mon IP montre qu'il y a une boucle de routing entre 2 NRO, duh69 et cha69: traceroute to 82.255.131.243 (82.255.131.243), 64 hops max, 52 byte packets 1 172.29.2.1 (172.29.2.1) 3.260 ms 3.080 ms 2.701 ms 2 172.29.2.250 (172.29.2.250) 1.758 ms 1.011 ms 0.858 ms 3 192.168.98.254 (192.168.98.254) 1.094 ms 1.589 ms 1.457 ms 4 78.193.183.254 (78.193.183.254) 1.726 ms 2.997 ms 1.804 ms 5 78.255.68.126 (78.255.68.126) 1.666 ms 1.404 ms 2.094 ms 6 ber69-49m-1-v900.intf.nro.proxad.net (78.254.243.133) 1.464 ms 1.699 ms 1.619 ms 7 sal69-49m-2-v902.intf.nro.proxad.net (78.254.248.97) 1.613 ms 1.787 ms 1.564 ms 8 gui69-49m-1-v902.intf.nro.proxad.net (78.254.248.134) 1.854 ms 1.691 ms 1.913 ms 9 bel69-49m-1-v902.intf.nro.proxad.net (78.254.248.142) 1.549 ms 1.576 ms 2.027 ms 10 bel69-49m-1-v902.intf.nro.proxad.net (78.254.242.166) 3.638 ms 2.314 ms 2.778 ms 11 cat69-49m-1-v902.intf.nro.proxad.net (78.254.248.150) 1.987 ms 1.845 ms 1.830 ms 12 spv69-49m-1-v902.intf.nro.proxad.net (78.254.248.158) 1.691 ms 1.976 ms 1.682 ms 13 eis69-49m-1-v902.intf.nro.proxad.net (78.254.248.166) 2.127 ms 1.736 ms 1.712 ms 14 cha69-49m-1-v902.intf.nro.proxad.net (78.254.248.174) 2.464 ms 2.118 ms 1.795 ms 15 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 3.278 ms 2.673 ms 2.682 ms 16 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 1.822 ms 1.840 ms 1.794 ms 17 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 2.563 ms 2.599 ms 2.604 ms 18 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.142 ms 1.817 ms 1.838 ms 19 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 6.139 ms 3.676 ms 3.917 ms 20 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.618 ms 1.962 ms 1.960 ms 21 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 3.766 ms 2.778 ms 2.595 ms 22 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 10.205 ms 7.951 ms 7.372 ms 23 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 2.788 ms 2.664 ms 2.544 ms 24 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.791 ms 2.058 ms 2.045 ms 25 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 3.046 ms 2.729 ms 2.698 ms 26 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.334 ms 2.072 ms 2.011 ms 27 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 2.748 ms 2.831 ms 2.904 ms 28 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.092 ms 2.023 ms 2.312 ms 29 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 3.764 ms 3.072 ms 2.894 ms 30 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.197 ms 2.237 ms 2.358 ms 31 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 2.980 ms 3.205 ms 2.757 ms 32 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.690 ms 2.201 ms 4.342 ms 33 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 2.841 ms 2.749 ms 2.807 ms 34 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.353 ms 2.240 ms 2.199 ms 35 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 2.949 ms 2.754 ms 2.856 ms 36 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.250 ms 2.267 ms 2.247 ms 37 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 3.098 ms 2.805 ms 2.780 ms 38 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.612 ms 2.520 ms 2.213 ms 39 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 2.889 ms 2.732 ms 2.670 ms 40 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.319 ms 2.345 ms 2.641 ms 41 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 2.853 ms 2.957 ms 2.950 ms 42 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.722 ms 2.736 ms 2.372 ms 43 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 2.909 ms 3.028 ms 3.083 ms 44 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.676 ms 4.008 ms 2.340 ms 45 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 3.040 ms 3.277 ms 3.765 ms 46 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.612 ms 2.459 ms 2.442 ms 47 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 2.974 ms 3.271 ms 2.985 ms 48 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.477 ms 2.893 ms 2.631 ms 49 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 3.524 ms 3.134 ms 3.282 ms 50 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.465 ms 2.497 ms 2.514 ms 51 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 3.278 ms 3.119 ms 3.011 ms 52 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 3.087 ms 2.582 ms 2.697 ms 53 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 3.095 ms 3.181 ms 4.037 ms 54 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.744 ms 2.669 ms 4.264 ms 55 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 3.276 ms 3.194 ms 3.312 ms 56 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.858 ms 2.701 ms 2.632 ms 57 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 5.349 ms 3.238 ms 3.177 ms 58 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.740 ms 2.970 ms 2.879 ms 59 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 3.199 ms 3.208 ms 3.329 ms 60 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.698 ms 3.274 ms 2.895 ms 61 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 3.586 ms 3.386 ms 3.309 ms 62 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.769 ms 2.992 ms 2.779 ms 63 duh69-49m-1-v902.intf.nro.proxad.net (78.254.242.106) 3.407 ms 3.531 ms 3.403 ms 64 cha69-49m-2-v902.intf.nro.proxad.net (78.254.242.105) 2.840 ms 4.961 ms 2.844 ms Et un tracert sous Windows me sort qu'il essai de se connecter vers lns-bzn-55-82-255-131-243.adsl.proxad.net alors que je suis en FTTH. TRACERT.EXE 82.255.131.243 Détermination de l’itinéraire vers lns-bzn-55-82-255-131-243.adsl.proxad.net [82.255.131.243] avec un maximum de 30 sauts : 1 2 ms 2 ms 1 ms 172.29.2.1 2 <1 ms <1 ms <1 ms 172.29.2.250 3 <1 ms <1 ms <1 ms 192.168.98.254 4 <1 ms <1 ms <1 ms 78.193.183.254 5 <1 ms 1 ms <1 ms 78.255.68.126 6 <1 ms <1 ms 1 ms ber69-49m-1-v900.intf.nro.proxad.net [78.254.243.133] 7 1 ms <1 ms <1 ms sal69-49m-2-v902.intf.nro.proxad.net [78.254.248.97] 8 1 ms 1 ms <1 ms gui69-49m-1-v902.intf.nro.proxad.net [78.254.248.134] 9 8 ms 3 ms 4 ms bel69-49m-1-v902.intf.nro.proxad.net [78.254.248.142] 10 1 ms 2 ms 2 ms bel69-49m-1-v902.intf.nro.proxad.net [78.254.242.166] 11 1 ms 2 ms 1 ms cat69-49m-1-v902.intf.nro.proxad.net [78.254.248.150] 12 1 ms 1 ms 1 ms spv69-49m-1-v902.intf.nro.proxad.net [78.254.248.158] 13 1 ms 1 ms 1 ms eis69-49m-1-v902.intf.nro.proxad.net [78.254.248.166] 14 1 ms 3 ms 1 ms cha69-49m-1-v902.intf.nro.proxad.net [78.254.248.174] 15 2 ms 2 ms 2 ms duh69-49m-1-v902.intf.nro.proxad.net [78.254.242.106] 16 10 ms 5 ms 1 ms cha69-49m-2-v902.intf.nro.proxad.net [78.254.242.105] 17 2 ms 2 ms 1 ms duh69-49m-1-v902.intf.nro.proxad.net [78.254.242.106] 18 1 ms 1 ms 1 ms cha69-49m-2-v902.intf.nro.proxad.net [78.254.242.105] 19 2 ms 2 ms 2 ms duh69-49m-1-v902.intf.nro.proxad.net [78.254.242.106] 20 1 ms 1 ms 1 ms cha69-49m-2-v902.intf.nro.proxad.net [78.254.242.105] 21 2 ms 2 ms 2 ms duh69-49m-1-v902.intf.nro.proxad.net [78.254.242.106] 22 2 ms 1 ms 1 ms cha69-49m-2-v902.intf.nro.proxad.net [78.254.242.105] 23 2 ms 2 ms 2 ms duh69-49m-1-v902.intf.nro.proxad.net [78.254.242.106] 24 1 ms 1 ms 1 ms cha69-49m-2-v902.intf.nro.proxad.net [78.254.242.105] 25 2 ms 2 ms 3 ms duh69-49m-1-v902.intf.nro.proxad.net [78.254.242.106] 26 1 ms 2 ms 1 ms cha69-49m-2-v902.intf.nro.proxad.net [78.254.242.105] 27 2 ms 2 ms 2 ms duh69-49m-1-v902.intf.nro.proxad.net [78.254.242.106] 28 2 ms 1 ms 1 ms cha69-49m-2-v902.intf.nro.proxad.net [78.254.242.105] 29 2 ms 2 ms 2 ms duh69-49m-1-v902.intf.nro.proxad.net [78.254.242.106] 30 1 ms 1 ms 1 ms cha69-49m-2-v902.intf.nro.proxad.net [78.254.242.105] Itinéraire déterminé. Savez vous si il y une personne a contacter plutôt que de passer par le service client qui ne va pas savoir de quoi je parle ?.. Merci Quote Link to comment Share on other sites More sharing options...
nicobz25 Posted January 16, 2018 Report Share Posted January 16, 2018 Bonjour, Avez-vous essayé de faire un traceroute depuis votre freebox sur l'ip de votre travail ? Quote Link to comment Share on other sites More sharing options...
Opa Posted January 16, 2018 Author Report Share Posted January 16, 2018 Bonjour, Le soucis a été réglé depuis Je ne sais pas si mon appel au service client a fait bouger les choses où si ils ont vu le problème d'eux même Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.