From owner-freebsd-net  Wed Aug  2  3:54:31 2000
Delivered-To: freebsd-net@freebsd.org
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by hub.freebsd.org (Postfix) with ESMTP id 026F137B50D
	for <freebsd-net@freebsd.org>; Wed,  2 Aug 2000 03:54:29 -0700 (PDT)
	(envelope-from itojun@itojun.org)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id TAA20537;
	Wed, 2 Aug 2000 19:54:23 +0900 (JST)
To: Ping Pan <pingpan@research.bell-labs.com>
Cc: freebsd-net@freebsd.org
In-reply-to: pingpan's message of Tue, 01 Aug 2000 21:56:29 -0400.
      <39877FCD.AC968B74@research.bell-labs.com>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: Fwd: A new kernel extension to deal with IP option packets
From: itojun@iijlab.net
Date: Wed, 02 Aug 2000 19:54:23 +0900
Message-ID: <20535.965213663@coconut.itojun.org>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Hello, Itojun,
>
>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.
>
>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.

	you mean router alert option?  you may want to look at ip6_input().
	there's some code in it.  router alert option is standardized
	enough, and i don't think you need additional AF for it.

itojun


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message