From owner-freebsd-hackers Thu Jan 30 07:08:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA14405 for hackers-outgoing; Thu, 30 Jan 1997 07:08:22 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id HAA14394 for ; Thu, 30 Jan 1997 07:08:13 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vpy4d-0007Oo-00; Thu, 30 Jan 1997 08:06:47 -0700 To: Charles Mott Subject: Re: ipdivert & masqd Cc: Darren Reed , Eivind Eklund , brian@awfulhak.demon.co.uk, archie@whistle.com, hackers@freebsd.org, ari.suutari@ps.carel.fi In-reply-to: Your message of "Wed, 29 Jan 1997 13:58:28 MST." References: Date: Thu, 30 Jan 1997 08:06:47 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Charles Mott writes: : In practice, these situations are not seen, and the packet aliasing : software works for FTP. The system loading is very low, and the software : easily scales to situations where there are large numbers of users. True. : I don't know about IRC, but my guess is that the real situation is simpler : than the theoretical. Whatever Linux does to handle IRC, I am told that : it looks fairly similar to what one does for FTP. Yes. You could also go out and get SLiRP, which would show you all kinds of neat tricks for all the pathological protocols out there. It has to do exactly the same thing. You could look at the TIA sources, if you have them too, but few people do :-) Warner