<div dir="ltr"><div><div>Hi all,<br><br></div>it seems to me that the problem is at the router at position 7 in the traceroute output sent by Denis. Yo can see that if responds only once, the next two attmpts fail, and when TTL is set to 11 hops, two different paths are attempted. I tried to access this router just now and it is inaccessible. Or probably the problem is even on router 6 that should have never tried the next one and use another path. It is definitely not a problem of DNS because my computer finds the same IP address. So DNS spoofing is not the problem. This is my trace:<br><br>$ traceroute <a href="http://www.tug.org">www.tug.org</a><br>traceroute to <a href="http://www.tug.org">www.tug.org</a> (91.121.174.77), 30 hops max, 60 byte packets<br> 1 gate.czw57 (192.168.1.1) 9.945 ms 9.936 ms 9.931 ms<br> 2 <a href="http://62-141-11-99.tmcz.cz">62-141-11-99.tmcz.cz</a> (62.141.11.99) 10.023 ms 10.235 ms 16.212 ms<br> 3 <a href="http://62-141-13-18.tmcz.cz">62-141-13-18.tmcz.cz</a> (62.141.13.18) 16.271 ms 19.412 ms 23.496 ms<br> 4 62.168.52.65 (62.168.52.65) 22.326 ms 24.754 ms 28.199 ms<br> 5 <a href="http://ae-2.fra2027-ex1.gtsce.net">ae-2.fra2027-ex1.gtsce.net</a> (193.85.195.94) 35.877 ms 39.003 ms 41.273 ms<br> 6 * * *<br> 7 <a href="http://be103.rbx-g1-nc5.fr.eu">be103.rbx-g1-nc5.fr.eu</a> (178.33.100.158) 60.547 ms 58.720 ms 62.512 ms<br> 8 * * *<br> 9 <a href="http://vl10.rbx-g3-a72.fr.eu">vl10.rbx-g3-a72.fr.eu</a> (94.23.122.73) 55.899 ms 54.242 ms 56.437 ms<br>10 * * *<br>11 <a href="http://tug.org">tug.org</a> (91.121.174.77) 37.863 ms !X 37.069 ms !X 39.435 ms !X<br><br></div>Now, comparing again my route with that found by Denis, I see that <a href="http://vl10.rbx-g3-a72.fr.eu">vl10.rbx-g3-a72.fr.eu</a> is on the right path but Denis is sometimes sent by router #7 to a wrong direction. Both http, https, and ftp are TCP services and establishing a connection requires sending several packets. If they do not go correctly to the server, connection will never be established.<br><br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature">Zdeněk Wagner<br><a href="http://ttsm.icpf.cas.cz/team/wagner.shtml" target="_blank">http://ttsm.icpf.cas.cz/team/wagner.shtml</a><br><a href="http://icebearsoft.euweb.cz" target="_blank">http://icebearsoft.euweb.cz</a></div></div>
<br><div class="gmail_quote">2017-12-18 23:33 GMT+01:00 Zdenek Wagner <span dir="ltr"><<a href="mailto:zdenek.wagner@gmail.com" target="_blank">zdenek.wagner@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class="">2017-12-18 23:27 GMT+01:00 Alan Litchfield <span dir="ltr"><<a href="mailto:alan@alphabyte.co.nz" target="_blank">alan@alphabyte.co.nz</a>></span>:<br></span><div class="gmail_extra"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Given that is the case, has you tried using OpenDNS?</div></blockquote><div><br></div></span><div>DNS is not the problem. The problem is that a router finds a way to the IP address through inaccessible routers. <br></div><span class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><br></div><div>Alan<br><div>
<div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="color:rgb(0,0,0);font-family:Helvetica;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div><div>--</div><div>Dr Alan Litchfield</div><div>AlphaByte</div><div>PO Box 1941</div><div>Auckland, New Zealand 1140</div></div></div></div></div></div></div></blockquote></span><div><br><br><span class=""><br clear="all"><div><div class="m_4308231231304729875gmail_signature">Zdeněk Wagner<br><a href="http://ttsm.icpf.cas.cz/team/wagner.shtml" target="_blank">http://ttsm.icpf.cas.cz/team/<wbr>wagner.shtml</a><br><a href="http://icebearsoft.euweb.cz" target="_blank">http://icebearsoft.euweb.cz</a></div></div>
<br> </span></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><div>
</div><div><div class="m_4308231231304729875gmail-h5">
<div><br><div><div class="h5"><blockquote type="cite"><div>On 19/12/2017, at 11:22, Reinhard Kotucha <<a href="mailto:reinhard.kotucha@web.de" target="_blank">reinhard.kotucha@web.de</a>> wrote:</div><br class="m_4308231231304729875gmail-m_-2814262103695231314Apple-interchange-newline"><div><div>On 2017-12-18 at 22:10:45 +0100, Denis Bitouzé wrote:<br><br><blockquote type="cite">Le 18/12/17 à 21h44, Rick Graham a écrit :<br><br><blockquote type="cite">... I'm also curious to know if the TOR Browser<br><<a href="https://www.torproject.org/projects/torbrowser.html.en" target="_blank">https://www.torproject.org/pr<wbr>ojects/torbrowser.html.en</a>> works for you,<br>since it will most assuredly take a different path, etc., to<br><a href="http://www.tug.org" target="_blank">www.tug.org</a>.<br></blockquote><br>Bingo! That works :)<br></blockquote><br>Denis, the actual problem is not solved so far, sorry.<br><br>When you start the Tor browswer, it says, for instance<br><br> Your IP address appears to be: 62.212.73.141<br><br>But this IP address is not yours and you get another one when you<br>start the browser again.<br><br>What happens is that your browser connects to this remote machine and<br>the remote machine sends your requests to <a href="http://www.tug.org" target="_blank">www.tug.org</a> and sends you<br>the results. This works, of course, because<br><br> <a href="http://downforeveryoneorjustme.com" target="_blank">http://downforeveryoneorjustm<wbr>e.com</a><br><br>already told you that everbody except you can access <a href="http://www.tug.org" target="_blank">www.tug.org</a> .<br><br>Using the Tor browser is probably a nice workaround for http(s) and<br>ftp but it doesn't help if you need rsync, for example.<br><br><blockquote type="cite">I guess we can conclude neither my router nor my configuration are<br>the culprits...<br></blockquote><br>I can't imagine that there is something wrong at your site because you<br>said that everything else works fine.<br><br>BTW, <a href="http://tug.org" target="_blank">tug.org</a> and <a href="http://preining.info" target="_blank">preining.info</a> have completely different IP-numbers:<br><br> <a href="http://tug.org" target="_blank">tug.org</a>: 91.121.174.77<br> <a href="http://preining.info" target="_blank">preining.info</a>: 142.4.209.99<br><br>Maybe one of the routers between Calais and Roubaix is<br>screwed up. Can anybody tell me what * * * means in the output of<br>traceroute? <br><br>Regards,<br> Reinhard<br><br>-- <br>------------------------------<wbr>------------------------------<wbr>------<br>Reinhard Kotucha Pho<wbr>ne: <a href="tel:+49%20511%203373112" value="+495113373112" target="_blank">+49-511-3373112</a><br><a href="https://maps.google.com/?q=Marschnerstr.+25+D-30167+Hannover&entry=gmail&source=g" target="_blank">Marschnerstr. 25</a><br><a href="https://maps.google.com/?q=Marschnerstr.+25+D-30167+Hannover&entry=gmail&source=g" target="_blank">D-30167 Hannover</a> <a href="mailto:reinhard.kotucha@web.de" target="_blank">mailto:rein<wbr>hard.kotucha@web.de</a><br>------------------------------<wbr>------------------------------<wbr>------<br></div></div></blockquote></div></div></div><br></div></div></div></div></blockquote></div><br></div></div>
</blockquote></div><br></div>