Opened 7 years ago

Closed 7 years ago

#344 closed request (duplicate)

Re: can't reach AS2518

Reported by: s-kawamura@… Owned by: jim@…
Priority: tbd Milestone: IETF Week
Component: incoming Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

Hi Jim

Sorry for this mess.
Here's more info.
This is the traceroute result from the IETF network.

  1     1 ms     1 ms     1 ms  130.129.80.2
  2     2 ms     1 ms     1 ms  130.129.4.3
  3     1 ms     1 ms     1 ms  217.31.202.1
  4     4 ms     2 ms     1 ms  gw-g-01-v103.nic.cz [217.31.205.210]
  5     *        *

I logged into a BSD machine inside my network through a relay.
Here's the ping results the other way around.
(From AS2518 to the IETF network)
The source address is from the prefix 220.144.0.0/16

217.31.205.210 ping ok
217.31.202.1 ping ok
130.129.4.3 ping NG

hmm. so nic.cz seems to know how to get back to my network.
It may be a specific router problem inside nic.cz.

Regards,
Seiichi

(2011/03/26 17:46), Seiichi Kawamura wrote:
> Hi Jim
> 
> The network I am not able to reach
> is AS2518. I operate this network.
> Here are the prefixes that I route as origin.
> 
> 61.193.0.0/17 218.42.0.0/17 61.203.0.0/17 133.205.0.0/16 202.225.0.0/16
> 202.247.0.0/17 203.136.0.0/16 210.147.0.0/16 210.151.128.0/17
> 211.13.0.0/17 211.135.128.0/17 218.227.0.0/16 219.107.0.0/16
> 220.144.0.0/16 221.170.0.0/15 220.102.0.0/16 60.236.0.0/14
> 125.192.0.0/13 122.130.0.0/15 122.132.0.0/14 118.108.0.0/14
> 119.238.0.0/15 119.240.0.0/14 119.244.0.0/16 110.233.0.0/16
> 111.168.0.0/15 27.127.0.0/17 49.129.0.0/16 27.127.0.0/17 49.129.0.0/16
> 60.236.0.0/14 202.225.0.0/16 202.247.0.0/17 122.130.0.0/15
> 221.170.0.0/15 122.132.0.0/14 119.244.0.0/16 220.102.0.0/16
> 61.203.0.0/17 111.168.0.0/15 203.136.0.0/16 211.135.128.0/17
> 218.227.0.0/16 220.144.0.0/16 210.147.0.0/16 211.13.0.0/17
> 110.233.0.0/16 119.238.0.0/15 210.151.128.0/17 125.192.0.0/13
> 218.42.0.0/17 133.205.0.0/16 119.240.0.0/14 118.108.0.0/14
> 219.107.0.0/16 61.193.0.0/17
> 
> Here are my customer ases
> AS18082 AS2515 AS45674 AS7500
> 
> Thanks so much for helping out.
> 
> Regards,
> Seiichi
> 
> 
> (2011/03/26 17:11), Seiichi Kawamura wrote:
>> I cannot reach my AS2518 (ipv4) from the
>> IETF network right now. IPv6 works fine. Its just IPv4.
>> Traceroute as follows.
>>
>>   1     1 ms    <1 ms     1 ms  130.129.80.2
>>   2     1 ms     1 ms     1 ms  130.129.4.3
>>   3     1 ms     1 ms     1 ms  217.31.202.1
>>   4     2 ms     1 ms     1 ms  gw-g-01-v103.nic.cz [217.31.205.210]
>>   5     *        *
>>
>> Now a traceroute to IIJ
>>
>>   1     1 ms     1 ms     1 ms  130.129.80.2
>>   2     1 ms     1 ms     1 ms  82.113.59.4
>>   3     1 ms     1 ms     1 ms  xe-4-0-0.prg11.ip4.tinet.net [213.200.74.93]
>>   4    97 ms    97 ms    97 ms  xe-2-1-0.was12.ip4.tinet.net [89.149.182.97]
>>
>> I've tried a few other ASes in Japan and none
>> go to nic.cz except for my AS.
>>
>> Please excuse the reply-to header since I'm using a server
>> I usually don't use.
>>
>> Regards,
>> Seiichi

Change history (2)

comment:1 Changed 7 years ago by jim@…

Owner: changed from llynch@… to jim@…
Status: newassigned

comment:2 Changed 7 years ago by jim@…

Resolution: duplicate
Status: assignedclosed
Note: See TracTickets for help on using tickets.