Date: Wed, 07 May 2008 11:08:01 -0700 From: Julian Elischer <julian@elischer.org> To: "Bruce M. Simpson" <bms@incunabulum.net> Cc: freebsd-net@freebsd.org, Edwin Groothuis <edwin@mavetju.org> Subject: Re: IPPROTO_DIVERT and PF_INET6 Message-ID: <4821F001.10208@elischer.org> In-Reply-To: <48215D08.5050500@incunabulum.net> References: <20080503100043.GA68835@k7.mavetju> <m2od7k7e5z.wl%Jinmei_Tatuya@isc.org> <481F6AE1.5020408@elischer.org> <20080505231009.GX44028@k7.mavetju> <481F95DE.6090201@elischer.org> <4821330E.8030101@incunabulum.net> <4821535B.8050001@elischer.org> <48215D08.5050500@incunabulum.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce M. Simpson wrote: > Julian Elischer wrote: >> actually the divert sockets should really not be in PF_INET >> they could deliver both inet and inet6 packets. >> the sockaddr that they return (and which needs to be read for divert >> to make sense) could be used to distinguish between them. > > Good point. I'd forgotten that they were abusing the fields in sin_zero. "they" == "me" :-) if we made it its own protocol family we could define our own sockaddr types too and have actual fields for that stuff... > This is not OK for IPv6, although the kludge can still be perpetuated by > looking at sa_len and stashing what divert wants at the end of > sockaddr_in6. > > So there IS a case for making them a separate protocol family if > someone's going to do a clean implementation of divert sockets for IPv6. > > cheers > BMS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4821F001.10208>