Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 18 Feb 2002 15:29:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 18 Feb 2002 15:28:51 -0500 Received: from lightning.swansea.linux.org.uk ([194.168.151.1]:264 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Mon, 18 Feb 2002 15:28:43 -0500 Subject: Re: weird ip sequence number To: xinwenfu@cs.tamu.edu (Xinwen - Fu) Date: Mon, 18 Feb 2002 20:42:36 +0000 (GMT) Cc: root@chaos.analogic.com (Richard B. Johnson), linux-kernel@vger.kernel.org In-Reply-To: from "Xinwen - Fu" at Feb 18, 2002 02:24:50 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > Although there are few chances that our randomly chosen ip_id collides > with the other packet's ip_id generated by kernel, I don't want this > possibility to happen. So pick one at random. However its a pretty strange way to abuse IP. > So is there any method to get a true ip_id from the kernel? > I want this ip_id to do my own fragmentation on a packet. Linux does not generate ip idents on DF frames. You can't fragment a DF frame anyway so the problem does not arrive. Frames without DF get assigned ip ids - 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/