From owner-freebsd-net@FreeBSD.ORG Thu May 18 22:41:06 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24E0F16A411 for ; Thu, 18 May 2006 22:41:06 +0000 (UTC) (envelope-from mjeung@cisdata.net) Received: from dagobah.cisdata.net (dagobah.cisdata.net [63.82.223.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACFDA43D46 for ; Thu, 18 May 2006 22:41:05 +0000 (GMT) (envelope-from mjeung@cisdata.net) Received: from adsl-69-237-115-101.dsl.scrm01.pacbell.net ([69.237.115.101] helo=[192.168.45.103]) by dagobah.cisdata.net with esmtp (Exim 4.52 (FreeBSD)) id 1FgrEp-000Bge-9e for freebsd-net@freebsd.org; Thu, 18 May 2006 15:45:00 -0700 Mime-Version: 1.0 (Apple Message framework v750) Content-Transfer-Encoding: 7bit Message-Id: <3D7C7275-432A-448D-82D6-AB551A1CE256@cisdata.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-net@freebsd.org From: Michael Jeung Date: Thu, 18 May 2006 15:42:24 -0700 X-Mailer: Apple Mail (2.750) Subject: Load Balancing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 May 2006 22:41:06 -0000 Hey folks, We currently use DNS round-robin to balance traffic to servers. We've recently run into situations where multiple search engine spiders are crawling our webservers. They appear to be targeting specific webservers by IP address. This defeats DNS round-robin and as a result 1 of our webservers starts responding very slowly since it's full of search engine spiders. I recently looked at the port solution "'balance" and it seems like a great answer for our problems. The difficulty I'm running into now is that if I put all the webservers behind a single balance server, now the webservers are only receiving traffic from the balance server and this messes up our traffic reporting tools since it now looks like all the traffic is coming from a single IP address. I'm sure this is a common problem. Does anyone have a good solution to this? Essentially, I want all the benefits of load-balancing with none of the single-IP-traffic drawbacks. =) Regards, Michael Jeung