From phk@critter.tfs.com  Thu Nov 21 23:29:18 1996
Received: from critter.tfs.com ([140.145.230.177])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA00672
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 21 Nov 1996 23:29:16 -0800 (PST)
Received: (from phk@localhost) by critter.tfs.com (8.8.2/8.8.2) id IAA08283; Fri, 22 Nov 1996 08:29:48 +0100 (MET)
Message-Id: <199611220729.IAA08283@critter.tfs.com>
Date: Fri, 22 Nov 1996 08:29:48 +0100 (MET)
From: phk@freebsd.org
Reply-To: phk@freebsd.org
To: FreeBSD-gnats-submit@freebsd.org
Subject: pings clock is troubled
X-Send-Pr-Version: 3.2

>Number:         2081
>Category:       bin
>Synopsis:       pings clock is troubled
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Nov 21 23:30:01 PST 1996
>Closed-Date:    Wed Jan 15 07:03:23 PST 1997
>Last-Modified:  Wed Jan 15 07:04:12 PST 1997
>Originator:     Poul-Henning Kamp
>Release:        FreeBSD 3.0-CURRENT i386
>Organization:
>Environment:

	IP line where ICMP is low priority, swamped by higher
	priority traffic.

>Description:

	this is utterly impossible RTTs.
  64 bytes from 204.216.27.18: icmp_seq=149 ttl=246 time=13073.815 ms
  64 bytes from 204.216.27.18: icmp_seq=150 ttl=246 time=12092.478 ms
  64 bytes from 204.216.27.18: icmp_seq=151 ttl=246 time=11388.356 ms
  64 bytes from 204.216.27.18: icmp_seq=152 ttl=246 time=831870306350.667 ms
  64 bytes from 204.216.27.18: icmp_seq=154 ttl=246 time=831870335424.108 ms
  64 bytes from 204.216.27.18: icmp_seq=155 ttl=246 time=831870335423.959 ms
  64 bytes from 204.216.27.18: icmp_seq=160 ttl=246 time=831870335374.866 ms
  64 bytes from 204.216.27.18: icmp_seq=161 ttl=246 time=831870345245.081 ms
  64 bytes from 204.216.27.18: icmp_seq=162 ttl=246 time=831870345236.793 ms
  64 bytes from 204.216.27.18: icmp_seq=163 ttl=246 time=831870345264.797 ms
  64 bytes from 204.216.27.18: icmp_seq=164 ttl=246 time=831870345256.368 ms
  64 bytes from 204.216.27.18: icmp_seq=165 ttl=246 time=831870345247.212 ms
  64 bytes from 204.216.27.18: icmp_seq=198 ttl=246 time=831870344954.712 ms
  64 bytes from 204.216.27.18: icmp_seq=199 ttl=246 time=831870344974.821 ms
  64 bytes from 204.216.27.18: icmp_seq=210 ttl=246 time=10984.584 ms
  64 bytes from 204.216.27.18: icmp_seq=211 ttl=246 time=10004.628 ms
  64 bytes from 204.216.27.18: icmp_seq=220 ttl=246 time=1507.495 ms
  64 bytes from 204.216.27.18: icmp_seq=221 ttl=246 time=544.629 ms

>How-To-Repeat:

	I can probably repeat it using the same setup.

>Fix:
	
	no idea.

>Release-Note:
>Audit-Trail:

From: Bill Fenner <fenner>
To: phk, freebsd-gnats-submit
Cc:  Subject: Re: bin/2081: pings clock is troubled
Date: Mon, 2 Dec 1996 14:55:28 -0800 (PST)

 Poul,
 
   Can you replicate this and use "tcpdump -w /tmp/foo icmp" to capture
 the actual packets?
 
 Thanks,
   Bill
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Wed Jan 15 07:03:23 PST 1997 
State-Changed-Why:  
I have concluded that this was due to some NAT code problem, and probably 
only sos can explain it.  But since it is not part of FreeBSD, we close. 
>Unformatted:
