From owner-freebsd-hackers Mon Nov 13 22:26:48 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA00599 for hackers-outgoing; Mon, 13 Nov 1995 22:26:48 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA00581 for ; Mon, 13 Nov 1995 22:26:43 -0800 Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id WAA27832; Mon, 13 Nov 1995 22:26:41 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id WAA04450; Mon, 13 Nov 1995 22:21:02 -0800 Message-Id: <199511140621.WAA04450@corbin.Root.COM> To: Peter Wemm cc: hackers@freebsd.org Subject: Re: if_mux hack? In-reply-to: Your message of "Tue, 14 Nov 95 05:28:43 +0800." From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 13 Nov 1995 22:21:01 -0800 Sender: owner-hackers@freebsd.org Precedence: bulk >Create a stub if_mux that only accepts packets from IP, and >redistributes them to other interfaces that it's been told about below >it. Ie: it's if_output routine would take the packets and distribute >them to other interface's if_output routines below it. > >Incoming packets from the lower interfaces would still go direct to IP, >but that's no big deal. ... >Sound interesting? Is it a "worthy hack"? (especially since Linux has >something like it.. :-) I thought of doing this exact thing about 3 years ago. It was more work than I was willing to do at the time so I never got around to doing it. The mechanics of the load balancing are trivial; the difficulty comes from the little nits - like writing the utility to manage the list of "multiplexed" interfaces, etc.. I definately think it is worthwhile. -DG