From owner-freebsd-current  Fri Jun 25 15: 6:34 1999
Delivered-To: freebsd-current@freebsd.org
Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4])
	by hub.freebsd.org (Postfix) with ESMTP
	id E8B9315153; Fri, 25 Jun 1999 15:06:28 -0700 (PDT)
	(envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
	by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id WAA11861;
	Fri, 25 Jun 1999 22:05:58 GMT
Message-ID: <3773FCA9.2B9408C6@tdx.co.uk>
Date: Fri, 25 Jun 1999 23:03:21 +0100
From: Karl Pielorz <kpielorz@tdx.co.uk>
Organization: TDX - The Digital eXchange
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: John Polstra <jdp@polstra.com>
Cc: archie@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: traceroute breakage in -current
References: <XFMail.990625092228.jdp@polstra.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John Polstra wrote:
> 
> I just noticed that traceroute in -current is starting its probes
> with port 1 instead of 33435 as it is supposed to do:
> 
> tcpdump: listening on fxp0
> 09:05:03.527313 206.213.73.12.38947 > 204.216.27.21.1: udp 12 [ttl 1]
>
> It broke in revision 1.9 of "src/contrib/traceroute/traceroute.c".

Thanks! - I thought I was going mad! - I've been out the office recently, so
I've not had time to chase it up, but I noticed _exacltly_ the same thing...
This results in my -current machine not being able to traceroute through our
firewall, whereas the 2.2.X / 3.X boxes can...

-Kp


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message