From owner-freebsd-current Mon Mar 29 11:42:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 493CB14CA3 for ; Mon, 29 Mar 1999 11:42:56 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id LAA28510; Mon, 29 Mar 1999 11:40:42 -0800 (PST) From: Archie Cobbs Message-Id: <199903291940.LAA28510@bubba.whistle.com> Subject: Re: Status of 'tee' firewall action In-Reply-To: from Julian Elischer at "Mar 29, 99 09:14:05 am" To: julian@whistle.com (Julian Elischer) Date: Mon, 29 Mar 1999 11:40:42 -0800 (PST) Cc: romanp@wuppy.rcs.ru, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message