From owner-freebsd-net Tue Aug 1 20:29:35 2000 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id A907137BF6A for ; Tue, 1 Aug 2000 20:29:26 -0700 (PDT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from localhost (shuttle.sixyards.wide.toshiba.co.jp [3ffe:501:100f:0:200:f8ff:fe01:61cf]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id MAA24745; Wed, 2 Aug 2000 12:14:35 +0900 (JST) Date: Wed, 02 Aug 2000 12:24:47 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: pingpan@research.bell-labs.com Cc: freebsd-net@FreeBSD.ORG Subject: Re: Fwd: A new kernel extension to deal with IP option packets In-Reply-To: In your message of "Tue, 01 Aug 2000 21:56:29 -0400" <39877FCD.AC968B74@research.bell-labs.com> References: <19654.965020987@coconut.itojun.org> <39877FCD.AC968B74@research.bell-labs.com> User-Agent: Wanderlust/2.3.0 (Roam) Emacs/20.6 Mule/4.0 (HANANOEN) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 31 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> On Tue, 01 Aug 2000 21:56:29 -0400, >>>>> Ping Pan said: >> you want to look at RFC2292, and draft-ietf-ipngwg-2292bis. >> RFC2292 specifies how you can manipulate IPv6 extension headers >> (header chains between IP and TCP/UDP header, has similar role to >> IPv4 options), using ancillary data stream. it gives you much higher >> flexibility and control, without additional address family >> (i think we shouldn't define address family for this). > I could not find you in IETF. So here is my response: after reading > through some of the FrreBSD kernel code on IPv6 and the RFC, it has the > same > problem as in IPv4. That is, the user needs to open a raw socket first > with a protocol family and a protocol type. Only then you may use > setsockopt() to receive the option that you want. This mechanism is > pretty much the same as in IPv4. No. You can get IPv6 extension headers of packets via RFC2292 (or 2292bis), regardless of the transport layer protocols. However, > The problem that we are trying to solve is to intercept the IP packets > *only* base on their IP option types. The protocol type is irrelevant > here. I don't see this is solved in IPv6 RFC and drafts. I'm not sure if 2292 (or 22292bis) can be used to satisfy this goal. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message