Julian Elischer writes: > Unfortunatly the 'tee' option is quite a bit more complicated than it > looks.this is because teh normal way that packets get to divert sockets > and the way it'd have to get there from a 'tee' are kinda incompatible. > > It can be done but it's just not quite as straight forward as it first > appears.. > > On Mon, 29 Mar 1999, Roman V. Palagin wrote: > > > > What the status of 'tee' action? Anybody working on it?
As a workaround, use "divert" instead of "tee" and immediately write any packet you read, using the same struct sockaddr, back to the socket. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message