Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 29 Apr 2001 10:46:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 29 Apr 2001 10:46:30 -0400 Received: from barnowl.demon.co.uk ([158.152.23.247]:56070 "EHLO barnowl.demon.co.uk") by vger.kernel.org with ESMTP id ; Sun, 29 Apr 2001 10:46:19 -0400 Mail-Copies-To: nobody To: linux-kernel@vger.kernel.org Subject: Re: traceroute breaks with 2.4.4 In-Reply-To: <3AEBE142.E3CAD85E@konerding.com> <3AEC219C.3B4618AB@haque.net> From: Graham Murray Date: 29 Apr 2001 14:46:11 +0000 In-Reply-To: <3AEC219C.3B4618AB@haque.net> ("Mohammad A. Haque"'s message of "Sun, 29 Apr 2001 10:13:48 -0400") Message-ID: Lines: 7 User-Agent: Gnus/5.090003 (Oort Gnus v0.03) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org "Mohammad A. Haque" writes: > Traceroute is working fine here. You sure you didn't inadvertantly turn > on ECN w/o knowing it? Will ECN have any effect on Traceroute? Does ECN not only affect TCP connections? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/