Time to try some testing tools. Here the domains resolve
okay ( slashdot.org at 66.35.250.150 and www.slashdot.org
at 66.35.250.151. Right now at 1455 EDT Saturday I am
not reaching the site. A traceroute gets through 4 hops
in the rr net, 4 hops in atdn's net and 6 hops in cw net,
as far as Santa Clara, then to 66.35.210.202, then times
out after that. So it looks as if the site is actually
unreachable now due to availability and not routing. But
i was there Thursday night.
Despite that, the idea of site filtering was the first thing I
had thought of. In that part of the world I'd think it
is more than just "unlikely". Why not traceroute those
IP's and see how far it goes?
Remember the story of Panama's national telecomms
authority port filtering all the ports that VoIP etc runs on because
of complaints from their national telephone provider? And this
is stuff that TRANSITS as well as ORIGINATES there.
Noting is "unlikely" IMO. -Bob Foxworth
----- Original Message -----
From: "steve" <steve@itcom.net>
To: <slug@nks.net>
Sent: Saturday, April 19, 2003 12:30
Subject: Re: [SLUG] Slashdot
> On Saturday 19 April 2003 03:40, Neil Kittipalo wrote:
> > Here I am in Bangkok and I can find no report of what has
> > happened to slashdot.org and some other sites which went AWOL
> > some days ago. Does anyone know if this is a temporary situation
> > or whether they have been killed deliberately?
> > Neil
>
> An unlikely why could be that you somehow are on a connection going
> through the mainland where they are blocking a lot of western
> access.
>
> --
>
> Steve
> ______________________________________________________
> (This sig has been left open for your imagination.)
>
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:15:39 EDT