Date: Wed, 07 May 2008 05:41:50 +0100 From: "Bruce M. Simpson" <bms@incunabulum.net> To: Julian Elischer <julian@elischer.org> Cc: freebsd-net@freebsd.org, Edwin Groothuis <edwin@mavetju.org> Subject: Re: IPPROTO_DIVERT and PF_INET6 Message-ID: <4821330E.8030101@incunabulum.net> In-Reply-To: <481F95DE.6090201@elischer.org> References: <20080503100043.GA68835@k7.mavetju> <m2od7k7e5z.wl%Jinmei_Tatuya@isc.org> <481F6AE1.5020408@elischer.org> <20080505231009.GX44028@k7.mavetju> <481F95DE.6090201@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer wrote: > you could implement a whole new protocol family of which there > was a single protocol.. divert. That's sheer overkill for what Edwin needs to be able to do. We already have a bunch of apps which use divert sockets in the IPv4 space, why should the existing semantics change? Divert sockets are still tied to the transport you instantiate them with, and they have always been a special case anyway depending on where one wishes to draw the lines. There is no reason per se, that I can see, why the IPPROTO_DIVERT identifier can't just be re-used along with pf_proto_register() for PF_INET6, and I've said this to Edwin off-list. A PROTO_SPACER entry just needs to be added to in6protosw. I was surprised to learn no-one had gone ahead and actually implemented it already as there are a few cases in IPv6 which might warrant it (6to4, Teredo etc.) If I'm missing anything obvious please let me know. cheers BMS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4821330E.8030101>