On Wed, Mar 01, 2006 at 02:45:21PM -0500, James Carlson wrote: > Darren Reed writes: > > > I have a specific need for the observability part of Clearview. I need > > > to know > > > zone related information to route traffic to only those users that > > > should be > > > allowed to see it. > > > > > > In this case, you should really be looking at the cred_t off the > > dblk_t in order to access the zoneid of the "packet". > > The cred_t means something only when a user process allocated the > message. That's not true for things coming off the wire, so that > might not be very helpful here.
But eventually the packet will be processed and either dropped or "consumed" by a socket with a zoneid (allzones sockets, presumably, have the global zone as their zoneid). By then the packetness of the dblk might be lost, I dunno (check what fireengine/yosemite do), but if not then it could be a useful place for a hook (if there isn't one already). Nico -- _______________________________________________ networking-discuss mailing list [email protected]
