On Tue, 12 Feb 2013, Grant Ridder wrote: Hello,
Can you provide the traceroute?
Yes. Please see below. We were already told they drop icmp packets making the traceroute useless beyond 62.38.94.98 I strongly suspect there is an issue only on the return path, but i would need a traceroute originated at the other end so i can be sure and understand where the packets (tcp & udp) are exactly being dropped. Regards, Carlos Friaças # traceroute 194.63.247.20 traceroute to 194.63.247.20 (194.63.247.20), 30 hops max, 60 byte packets 1 193.136.2.29 (193.136.2.29) 0.278 ms 0.256 ms 0.241 ms 2 ROUTER4.10GE.Lisboa.fccn.pt (193.137.0.20) 0.294 ms 0.282 ms 0.269 ms 3 fccn.mx2.lis.pt.geant.net (62.40.124.97) 0.332 ms 0.320 ms 0.337 ms 4 xe-2-3-0.rt1.mad.es.geant.net (62.40.98.107) 12.650 ms 12.725 ms 12.641 ms 5 as2.rt1.gen.ch.geant2.net (62.40.112.25) 34.808 ms 34.791 ms 34.863 ms 6 ae3.rt1.fra.de.geant2.net (62.40.112.161) 43.062 ms 43.022 ms 43.010 ms 7 te0-7-0-5.ccr22.fra03.atlas.cogentco.com (149.6.42.73) 43.724 ms 43.808 ms 43.889 ms 8 te0-0-0-2.ccr22.ams03.atlas.cogentco.com (130.117.3.89) 50.106 ms te0-2-0-2.ccr22.ams03.atlas.cogentco.com (130.117.1.65) 50.240 ms te0-0-0-2.ccr22.ams03.atlas.cogentco.com (130.117.3.89) 50.114 ms 9 te0-2-0-0.ccr22.lon13.atlas.cogentco.com (130.117.1.170) 55.518 ms te0-0-0-0.ccr22.lon13.atlas.cogentco.com (130.117.1.225) 55.453 ms te0-5-0-0.ccr22.lon13.atlas.cogentco.com (154.54.61.154) 55.689 ms 10 te0-1-0-0.ccr22.lon01.atlas.cogentco.com (154.54.57.178) 55.570 ms te0-4-0-0.ccr22.lon01.atlas.cogentco.com (130.117.0.205) 55.452 ms te0-2-0-0.ccr22.lon01.atlas.cogentco.com (154.54.57.174) 55.481 ms 11 te2-1.mag02.lon01.atlas.cogentco.com (154.54.74.114) 55.439 ms 55.356 ms 55.342 ms 12 149.6.187.234 (149.6.187.234) 55.370 ms 55.451 ms 55.493 ms 13 POS00-07-00-03.med00.brd.hol.gr (62.38.36.13) 127.954 ms * 127.106 ms 14 tengigaeth00-01-00-02.med00.ccr.hol.gr (62.38.97.29) 136.321 ms * * 15 tengigaeth00-07-00-00.med00.csr.hol.gr (62.38.94.98) 125.525 ms 125.519 ms 125.584 ms 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *
-Grant
On Tue, Feb 12, 2013 at 6:01 AM, Carlos Friacas <cfriacas@fccn.pt> wrote:
Hello,
Does anyone has reachability issues with AS8388?
It seems i'm unable to get packets back from 194.63.246.0/23, but only if the source is my 193.136.0.0/15 block, at AS1930. It works well from my other netblocks. I'm basically performing a (non-recursive) DNS query to DNS servers within 194.63.246.0/23.
I've been trying to involve upstream providers to take a deeper look at this problem, but i haven't had any luck so far. I can't even get a traceroute back to my network from anyone at AS8388.
Any suggestions?
Best Regards, Carlos Friaças