Changed ISP now can't get to websites / traceroute

[Edmund Craske]

Argh! I'm always the last to put it down to the dreaded i word, but...
INCOMPETENCE!

That is all.
Ed

-----Original Message-----
From: freebsd-users-admin at uk.freebsd.org
[mailto:freebsd-users-admin at uk.freebsd.org] On Behalf Of Stacey Roberts
Sent: 07 July 2003 22:45
To: jfm at blueyonder.co.uk
Cc: freebsduk; FreeBSD Questions
Subject: Re: Changed ISP now can't get to websites / traceroute


Hello,

On Mon, 2003-07-07 at 21:20, John Murphy wrote:
> Stacey Roberts <stacey at vickiandstacey.com> wrote:
> 
> >Well., that's the story they're feeding me now. Something to do with
> >the fact that its a new range??????
> 
> Hmm.  Looking at the headers of your post you seem to have an address
> in the previously bogus 82/8 range.  These were only made available to

> RIPE circa November 2002 and some operators have been slow to update 
> their ACLs.  My ISP has acquired a whole range of these and forced one

> on me, so I know what problems they can cause.
> 
> >Really pisses me off this.., I'm quite fond of the FreeBSDforums
> >site, one of the best *bsd-related forum site I've come across.., 
> >too.
> 
> I can't get to http://www.freebsdforums.org/ either!
> 

Sorry but.., AT LAST!!!!!! I'm not going crazy.., and it might be that
there's some sanity to what Zen is telling me?

> The temporary fix for me is to use the ISP's web-cache :(
> 

No such option for me :-(

> Here's a traceroute from here (in case it helps):
> 
> traceroute to vail.edry.com (207.174.189.161), 64 hops max, 44 byte
> packets  1  10.48.128.1 (10.48.128.1)  11.499 ms  14.670 ms  9.454 ms

> 2  gsr01-tf.blueyonder.co.uk (62.31.176.161)  28.402 ms  9.319 ms  
> 9.155 ms  3  172.18.4.41 (172.18.4.41)  8.951 ms  18.224 ms  12.685 ms

> 4  kno-rab-wol-pos.telewest.net (194.117.136.49)  23.042 ms  24.131 ms

> 40.047 ms  5  tele2-kno-rab-pos.telewest.net (194.117.136.70)  18.752 
> ms  37.390 ms  28.197 ms  6  zcr1-so-5-0-0.Londonlnt.cw.net 
> (166.63.222.37)  50.513 ms  19.658 ms  19.770 ms  7  
> dcr2-loopback.Chicago.cw.net (208.172.2.100)  119.590 ms  111.810 ms  
> 116.965 ms  8  agr4-so-6-0-0.Chicago.cw.net (208.175.10.158)  128.898 
> ms  138.911 ms  113.668 ms  9  acr2.Denver.cw.net (208.172.162.62)  
> 152.239 ms  162.933 ms  145.562 ms 10  internap.Denver.cw.net 
> (208.172.161.178)  155.267 ms  155.384 ms  160.362 ms 11  
> border10.ge3-0-bbnet2.den.pnap.net (216.52.40.79)  155.735 ms  160.266

> ms  158.363 ms 12  coop-2.border10.den.pnap.net (216.52.42.118)  
> 133.003 ms  134.785 ms  134.697 ms 13  199.45.130.33 (199.45.130.33)  
> 138.747 ms  147.327 ms  135.144 ms 14  * 
> border-to-141-netrack.boulder.co.coop.net (207.174.144.178)  139.951 
> ms !X * 15  border-to-141-netrack.boulder.co.coop.net 
> (207.174.144.178)  136.281 ms !X * * 16  
> border-to-141-netrack.boulder.co.coop.net (207.174.144.178)  159.470 
> ms !X *  137.951 ms !X

Note here that you don't appear to actually *get* to freebsdforums' IP:
>From nslookup for freebsdforums.org :
Non-authoritative answer:
Name:    freebsdforums.org
Address:  207.174.189.161

I'm trying to force Zen to increase their efforts in doing whatever
they're able to do for me, but its a nightmare getting through to tech
support to even begin that process.., 

For now, I'm trying to google around for what I might need to do in
order that I can get traceroute to work for my *nix boxes here.., 

Thanks again for that..,

Regards,

Stacey

-- 
Stacey Roberts
B.Sc (HONS) Computer Science

Web: www.vickiandstacey.com



------ FreeBSD UK Users' Group  -  Mailing List ------
http://listserver.uk.freebsd.org/mailman/listinfo/freebsd-users