From owner-freebsd-net Mon May 6 9: 6:25 2002 Delivered-To: freebsd-net@freebsd.org Received: from quack.kfu.com (adsl-67-113-12-90.dsl.snfc21.pacbell.net [67.113.12.90]) by hub.freebsd.org (Postfix) with ESMTP id 0444E37B50C for ; Mon, 6 May 2002 09:05:05 -0700 (PDT) Received: from morpheus.kfu.com (morpheus.kfu.com [3ffe:1200:301b:1:2d0:b7ff:fe3f:bdd0]) by quack.kfu.com (8.11.6/8.11.6) with ESMTP id g46G4ts72094 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Mon, 6 May 2002 09:05:00 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from quack.kfu.com (nospam@localhost [::1]) by morpheus.kfu.com (8.11.6/8.11.6) with ESMTP id g46G4sO01361 for ; Mon, 6 May 2002 09:04:54 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Message-ID: <3CD6A9A6.6010205@quack.kfu.com> Date: Mon, 06 May 2002 09:04:54 -0700 From: Nick Sayer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.9) Gecko/20020312 X-Accept-Language: en, en-US, en-GB MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: Re: network design References: <3CD17557.7BC1F7C0@mindspring.com> <20020503073501.67347.qmail@web14802.mail.yahoo.com> <20020503082737.GN688@elvis.mu.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Bill Fumerola wrote: > [ 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? > I believe IPv6 anycasting could be a solution for this sort of thing. The front end could serve as a reverse NATPT mapping to an anycast address. Of course, I've never set up anycasting, so I am mostly talking through my hat. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message