From owner-freebsd-net@FreeBSD.ORG Tue Jun 29 18:04:18 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6712116A4CE for ; Tue, 29 Jun 2004 18:04:18 +0000 (GMT) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA57B43D1F for ; Tue, 29 Jun 2004 18:04:17 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 5731 invoked from network); 29 Jun 2004 18:04:06 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 29 Jun 2004 18:04:06 -0000 Message-ID: <40E1AF17.788540DD@freebsd.org> Date: Tue, 29 Jun 2004 20:04:07 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Max Laier References: <200406291413.ab33924@salmon.maths.tcd.ie> <200406291643.39705.max@love2party.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: David Malone cc: freebsd-net@freebsd.org Subject: Re: RANDOM_IP_ID sysctl? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2004 18:04:18 -0000 Max Laier wrote: > > On Tuesday 29 June 2004 15:40, Xin LI wrote: > > On Tue, Jun 29, 2004 at 02:13:38PM +0100, David Malone wrote: > > > It seems to me that RANDOM_IP_ID might be better as a sysctl rather > > > than a kernel option. Would anyone mind if I changed this? > > I personally think that RANDOM_IP_ID is something that should be tweakable on > a per-interface basis (at least). I usually want randomized IDs on my uplink > interface while it could harm my GigE internal network due to faster ID reuse > cycles. ip_id is only an issue when you have packet fragmentation going on. Which I doubt for your internal GigE network. > FYI, pf(4) can set randomized IDs on a per interface (and even on a per > connection) basis. > > David, I'd appreciate to review your patches in order to avoid breakage of pf, > thanks. How could random ip_id break pf? -- Andre