For some more information, this previous document and presentation make
good resources:
Document:
http://www.nanog.org/meetings/nanog47/presentations/Sunday/RAS_Traceroute_N47_Sun.pdf
There's also a presentation here:
http://www.nanog.org/meetings/nanog45/presentations/Interpret_traceroutes.wmv
--- On Sat, 11/3/12, Christopher Morrow wrote:
> From: Christopher Morrow
> Subject: Re: qwest.net dropping packets... wife would like someone to pick
> them up please...
> To: "Randy Bush"
> Cc: "North American Network Operators' Group"
> Date: Saturday, November 3, 2012, 7:04 PM
> On Sat, N
On Sat, Nov 3, 2012 at 3:07 AM, Randy Bush wrote:
>> one router along the path showing loss that does not continue to
>> affect the rest of the path simply means the cpu on that router
>> is a bit too busy to respond to icmp messages
>
> trivial footnote: some folk configure some routers to rate l
On Nov 1, 2012, at 8:20 AM, Masataka Ohta wrote:
> We should better introduce partially decimal format for
> IPv6 addresses or, better, avoid IPv6 entirely.
With respect, it is already possible to use the decimal subset if you wish. For
example, you could write
2001:dba::192:168:2:1
It wo
On 11/1/12 2:01 PM, Owen DeLong wrote:
There are better ways to avoid neighbor exhaustion attacks unless you have
attackers
inside your network.
All of the migrations are compromises of one sort or another. We thought
this one was important enough to include in an informational status
RFC (6
On Nov 3, 2012, at 04:19 , Tore Anderson
wrote:
> * Owen DeLong
>
>> On Nov 2, 2012, at 02:52 , Tore Anderson
>> wrote:
>>
>>> It absolutely does make sense, especially in the case of IPv4/IPv6
>>> translation. For example, when using NAT64, "64:ff9b::192.0.2.33"
>>> is an example of a val
Thank you all who answered. I got a few good leads to follow, and
information on operation gotchas.
***Stefan
* Owen DeLong
> On Nov 2, 2012, at 02:52 , Tore Anderson
> wrote:
>
>> It absolutely does make sense, especially in the case of IPv4/IPv6
>> translation. For example, when using NAT64, "64:ff9b::192.0.2.33"
>> is an example of a valid IPv6 address that maps to 192.0.2.33.
>> Much easier to re
> one router along the path showing loss that does not continue to
> affect the rest of the path simply means the cpu on that router
> is a bit too busy to respond to icmp messages
trivial footnote: some folk configure some routers to rate limit
icmp
randy
9 matches
Mail list logo
