From owner-freebsd-net Sun Jul 30 16:57:16 2000 Delivered-To: freebsd-net@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 6DCC837B7EA for ; Sun, 30 Jul 2000 16:57:12 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id TAA74234; Sun, 30 Jul 2000 19:57:10 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200007302357.TAA74234@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jeroen Ruigrok/Asmodai Cc: Garrett Wollman , freebsd-net@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: Fwd: A new kernel extension to deal with IP option packets References: <20000730104427.A28035@daemon.ninth-circle.org> <200007301827.OAA02982@khavrinen.lcs.mit.edu> <20000730212106.D28035@daemon.ninth-circle.org> In-reply-to: Your message of "Sun, 30 Jul 2000 21:21:06 +0200." <20000730212106.D28035@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 30 Jul 2000 19:57:10 -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I saw this too, and I guess what I can't figure out is why socket options to extract IP options on a raw IP socket (or perhaps any datagram socket) are not sufficient. There are no "IP options packets"; the options are already associated with a packet bound to a socket. Or for packets transiting the host. Is this specifically to support an RSVP implementation when the FreeBSD platform is acting as a router? I'm also wondering why perhaps BPF isn't a mechanism which can be used, but perhaps that's much too low a level an interface. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message