From owner-freebsd-current  Fri Jun 25 15: 9:12 1999
Delivered-To: freebsd-current@freebsd.org
Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7])
	by hub.freebsd.org (Postfix) with ESMTP id D050015153
	for <current@FreeBSD.ORG>; Fri, 25 Jun 1999 15:09:10 -0700 (PDT)
	(envelope-from archie@whistle.com)
Received: (from archie@localhost)
	by bubba.whistle.com (8.9.2/8.9.2) id PAA46881;
	Fri, 25 Jun 1999 15:08:30 -0700 (PDT)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199906252208.PAA46881@bubba.whistle.com>
Subject: Re: traceroute breakage in -current
In-Reply-To: <3773FCA9.2B9408C6@tdx.co.uk> from Karl Pielorz at "Jun 25, 99 11:03:21 pm"
To: kpielorz@tdx.co.uk (Karl Pielorz)
Date: Fri, 25 Jun 1999 15:08:29 -0700 (PDT)
Cc: jdp@polstra.com, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Karl Pielorz writes:
> > 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...

I just fixed this, so see if it works for you now. Sorry about that.

-Archie

___________________________________________________________________________
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com


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