[69549] in North American Network Operators' Group
Re: Routing issues
daemon@ATHENA.MIT.EDU (Iljitsch van Beijnum)
Wed Apr 14 09:55:01 2004
In-Reply-To: <00d801c42220$29579500$7c00000a@SimonPC>
Cc: <nanog@merit.edu>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 14 Apr 2004 15:53:15 +0200
To: "Simon Brilus" <sbrilus@cableinet.net>
Errors-To: owner-nanog-outgoing@merit.edu
On 14-apr-04, at 14:58, Simon Brilus wrote:
> Are there any other Service Providers who have been allocated blocks
> out of
> the 83/8 network that are experiencing connectivity issues? We have
> been
> allocated 83.146.0.0/18 and customers on this network have difficulty
> getting to sites like www.mercer.com, hk.yahoo.com etc..etc..
I'm seeing the same thing: works from 80.*, doesn't work from 83.*.
Note that www.mercer.com seems to suffer from a bad case of paranoia,
they filter traceroute and ping, so probably a misconfigured firewall
there. hk.yahoo.com traceroutes just fine from a 212.* address:
13 sl-gw10-hk-15-3.sprintlink.net (203.222.38.54) [AS 1239] 292 msec
292 msec 292 msec
14 sla-yahoo2-1-0.sprintlink.net (203.222.39.74) [AS 1239] 292 msec
292 msec 292 msec
15 alteon1.hkg.yahoo.com (202.1.233.118) [AS 18293] 296 msec 292 msec
292 msec
but hits a wall after the last sprintlink hop when coming from 83.*, so
it's probably the router in that case:
13 sl-bb20-hk-3-0.sprintlink.net (144.232.20.28) 293.716 ms 293.990
ms 294.028 ms
14 sl-gw10-hk-15-3.sprintlink.net (203.222.38.54) 292.629 ms 292.934
ms 292.710 ms
15 * * *
