On Sat, Oct 15, 2016 at 01:00:28AM -0400, Matthew Gabeler-Lee wrote:
> On Thu, 13 Oct 2016, Rogier Wolff wrote:
>
> >No! Not a "more reasonable" value! An outrageous value!
> >
> >You have a network where 5 hops-in-a-row don't conform to IP standards. And
> >then you expect mtr to work?
>
>
On Thu, 13 Oct 2016, Rogier Wolff wrote:
No! Not a "more reasonable" value! An outrageous value!
You have a network where 5 hops-in-a-row don't conform to IP standards. And
then you expect mtr to work?
traceroute works fine, ping works fine, tcp connections work fine ...
but mtr is special
On Wed, Oct 12, 2016 at 03:29:41PM -0400, Matthew Gabeler-Lee wrote:
> Package: mtr
> Version: 0.86-1+b1
> Severity: wishlist
>
> A new upstream release 0.87 has a fix (of sorts) for the problem where MTR
> will not trace a successful path that has more than five non-responding
> hops. I say fix
Package: mtr
Version: 0.86-1+b1
Severity: wishlist
A new upstream release 0.87 has a fix (of sorts) for the problem where MTR
will not trace a successful path that has more than five non-responding
hops. I say fix "of sorts" because the default limit for this has not been
changed, but it is now
4 matches
Mail list logo
