[tex-live] www.tug.org unreachable

[Zdenek Wagner]

2017-12-18 23:22 GMT+01:00 Reinhard Kotucha <reinhard.kotucha at web.de>:

> On 2017-12-18 at 22:10:45 +0100, Denis Bitouzé wrote:
>
>  > Le 18/12/17 à 21h44, Rick Graham a écrit :
>  >
>  > > ... I'm also curious to know if the TOR Browser
>  > > <https://www.torproject.org/projects/torbrowser.html.en> works for
> you,
>  > > since it will most assuredly take a different path, etc., to
>  > > www.tug.org.
>  >
>  > Bingo! That works :)
>
> Denis, the actual problem is not solved so far, sorry.
>
> When you start the Tor browswer, it says, for instance
>
>   Your IP address appears to be: 62.212.73.141
>
> But this IP address is not yours and you get another one when you
> start the browser again.
>
> What happens is that your browser connects to this remote machine and
> the remote machine sends your requests to www.tug.org and sends you
> the results.  This works, of course, because
>
>   http://downforeveryoneorjustme.com
>
> already told you that everbody except you can access www.tug.org .
>
> Using the Tor browser is probably a nice workaround for http(s) and
> ftp but it doesn't help if you need rsync, for example.
>

Exactly. Tor is primarily used to  hide your identity from the target
server so that you cannot be tracked and the cookies, if there are used,
cannot identify your computer.

>
>  > I guess we can conclude neither my router nor my configuration are
>  > the culprits...
>
> I can't imagine that there is something wrong at your site because you
> said that everything else works fine.
>
> BTW, tug.org and preining.info have completely different IP-numbers:
>
>   tug.org:         91.121.174.77
>   preining.info:   142.4.209.99
>
> Maybe one of the routers between Calais and Roubaix is
> screwed up.  Can anybody tell me what * * * means in the output of
> traceroute?
>
> Regards,
>   Reinhard
>
> Traceroute tries "ping" to the target with limited TTL (time to live). It
starts with one hop, tries 3 times and then increases the number of hops by
one and tries again until it either reaches the target or 30 hops. If set
initially to 1 hop, the packet expires at the very first router and its IP
address is returned. With 2 hops the IP packet gets on step further so this
way you can trace the whole way. * * * means that no reply packet was
received which may have one of two reasons:

1. The router is configured not to reply for ping packet
2. The router is unreachable

It is quite common to have * * * in the middle of a route but in any cas
you find the IP address of the furthest router that responded.


Zdeněk Wagner
http://ttsm.icpf.cas.cz/team/wagner.shtml
http://icebearsoft.euweb.cz



> --
> ------------------------------------------------------------------
> Reinhard Kotucha                            Phone: +49-511-3373112
> Marschnerstr. 25
> D-30167 Hannover                    mailto:reinhard.kotucha at web.de
> ------------------------------------------------------------------
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/tex-live/attachments/20171218/5a0f7943/attachment.html>