From owner-freebsd-net@FreeBSD.ORG Sat Jan 7 03:53:15 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 29C1D16A41F for ; Sat, 7 Jan 2006 03:53:15 +0000 (GMT) (envelope-from ras@overlord.e-gerbil.net) Received: from overlord.e-gerbil.net (e-gerbil.net [69.31.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1A6543D45 for ; Sat, 7 Jan 2006 03:53:14 +0000 (GMT) (envelope-from ras@overlord.e-gerbil.net) Received: from overlord.e-gerbil.net (ras@localhost.e-gerbil.net [127.0.0.1]) by overlord.e-gerbil.net (8.13.3/8.13.3) with ESMTP id k073rAee096735; Fri, 6 Jan 2006 22:53:10 -0500 (EST) (envelope-from ras@overlord.e-gerbil.net) Received: (from ras@localhost) by overlord.e-gerbil.net (8.13.3/8.13.3/Submit) id k073rAmA096734; Fri, 6 Jan 2006 22:53:10 -0500 (EST) (envelope-from ras) Date: Fri, 6 Jan 2006 22:53:10 -0500 From: Richard A Steenbergen To: kamal kc Message-ID: <20060107035310.GB826@overlord.e-gerbil.net> References: <20060106234511.GY826@overlord.e-gerbil.net> <20060107023500.68514.qmail@web30001.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060107023500.68514.qmail@web30001.mail.mud.yahoo.com> User-Agent: Mutt/1.5.6i Cc: freebsd Subject: Re: increasing the ethernet MTU greater than 1500 (1502) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 03:53:15 -0000 On Fri, Jan 06, 2006 at 06:35:00PM -0800, kamal kc wrote: > > thanks for providing the insight. I would try > with GigE next time. > > since it seems a bad option to try MTU larger than > 1500 in 10/100 Mbps ethernet i tried another option to > solve my problem. Also try any number of other $5 10/100 NICs with vlan/mini-jumbo capabilities. > Now i don't add additional header(2 bytes) to > distinguish > the packets that were processed. I rather tried for > protocol mapping. > > This is what i did, > > i mapped the protocol (in the protocol field of the ip > header) > > 0..56 to 138..194 if compressed > 0..56 to 195..251 if uncompressed > > with this simple protocol mapping i could only > compress > 57 protocol data. > > I guess the protocols 138 to 251 will not be used for > couple of years. > OR Is there any slighest possibility ???? If you're sure you're not going to deal with fragments, and you're ok with violating rfc's and hacking the headers to suit your needs, why not steal the id and/or frag offset fields? -- Richard A Steenbergen http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)