From owner-freebsd-hackers Fri May 3 1:27:50 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id B955937B420; Fri, 3 May 2002 01:27:37 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1098) id 888D1AE1D7; Fri, 3 May 2002 01:27:37 -0700 (PDT) Date: Fri, 3 May 2002 01:27:37 -0700 From: Bill Fumerola To: andrew mejia Cc: freebsd-net@FreeBSD.ORG Subject: Re: network design Message-ID: <20020503082737.GN688@elvis.mu.org> Reply-To: freebsd-net@FreeBSD.org References: <3CD17557.7BC1F7C0@mindspring.com> <20020503073501.67347.qmail@web14802.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020503073501.67347.qmail@web14802.mail.yahoo.com> User-Agent: Mutt/1.3.27i X-Operating-System: FreeBSD 4.5-MUORG-20020423 i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [ this is probably more appropriate for -net, -hackers bcc:'d ] On Fri, May 03, 2002 at 08:35:01AM +0100, andrew mejia wrote: > [andrew]$ exactly what i would suggest. a single > NIC can handle multiple assigments pretty easily, > unless you're expecting mega-traffic. but even then > you could use the native load balancing/caching tech- > nology offered with some other freewares (like > apache web server). finding content in the above post is like a "Where's Waldo?" puzzle. you would suggest exactly what? this has nothing to do with multiple IP addresses (which is what i assume you're talking about when you say, "NIC can handle multiple assignments") neither in the traditional 'secondary address' sense nor as IPs aliased to a loopback interface. this has nothing to do with load balancing or webservers or caching or mega-traffic(?!). this is about representing within the freebsd network stack ethernet cards that support multiple (>1) unicast mac addresses through either multiple perfect filter entries or a multicast filter borrowed to serve such a purpose. until freebsd has a way of supporting this, failover technologies like vrrp (or any where members 'share' a common lladdr) will be impossible to implement properly. i believe the hangup is that adding an interface to network drivers is the easy part relative to teaching the network stack about network cards with more then one lladdr. specifically, which mac address do you use when putting a frame onto the wire that was locally generated? forwarded? -- - bill fumerola / fumerola@yahoo-inc.com / billf@FreeBSD.org / billf@mu.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message