From owner-freebsd-hackers Thu Jan 30 10:14:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA23145 for hackers-outgoing; Thu, 30 Jan 1997 10:14:56 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA23135 for ; Thu, 30 Jan 1997 10:14:51 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.5/8.8.3) with UUCP id TAA01757; Thu, 30 Jan 1997 19:13:09 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id TAA13677; Thu, 30 Jan 1997 19:02:13 +0100 (MET) Message-Id: <3.0.32.19970130190212.00b22780@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Thu, 30 Jan 1997 19:02:14 +0100 To: Warner Losh From: Eivind Eklund Subject: Re: ipdivert & masqd Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 08:04 AM 1/30/97 -0700, you wrote: >In message <199701292038.MAA19786@freefall.freebsd.org> Darren Reed writes: >> It is a *much* better idea to redirect IRC to a local TCP port and process >> it using a proxy agent. Same could also be said for FTP. > >Yes. It is. However, you also have to do the same for Talk, Real >Audio and at least one other protocol that encodes either the IP >address or ports of the system. I'm thinking about doing transparent proxying for the protocols, but I want to see how well the packet-patching version run first. As it is, it is (hopefully) right in 99% of the cases, and it scales well. If I get reports of real-life problems I'll make it a priority to make proxies, but not before. (And the packet-patchers will still be an option - for most people, they probably are a better or as good solution.) Eivind Eklund / perhaps@yes.no / http://maybe.yes.no/perhaps/