Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: icmp rpf

  • From: virendra rode //
  • Date: Sun Sep 24 19:28:34 2006

Hash: SHA1

Mark Kent wrote:
> A smaller North American network provider, with a modest North
> American backbone, numbers their internal routers on public IP space
> that they do not announce to the world.
> One of the largest North American network providers filters/drops
> ICMP messages so that they only pass those with a source IP
> address that appears in their routing table.
> As a result, traceroutes from into have numerous
> hops that time out.
> Traceroutes from elsewhere that go into but return on
> also have numerous hops that time out.
> We do all still think that traceroute is important, don't we?
> If so, which of these two nets is unreasonable in their actions/policies?
> Please note that we're not talking about RFC1918 space, or reserved IP
> space of any kind.   Also, think about the scenario where some failure
> happens leaving with an incomplete routing table, thus breaking
> traceroute when it is perhaps most needed.
> Thanks,
> -mark
- --------------------------
This is yet another reason one shouldn't rely on pings & traceroutes to
perform reachability analysis.

Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla -


Discussion Communities

About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home

Merit Network, Inc.