From owner-freebsd-net Tue Sep 18 7:57:16 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id F207737B40C for ; Tue, 18 Sep 2001 07:57:12 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f8IEutZ50461; Tue, 18 Sep 2001 10:56:55 -0400 (EDT) (envelope-from wollman) Date: Tue, 18 Sep 2001 10:56:55 -0400 (EDT) From: Garrett Wollman Message-Id: <200109181456.f8IEutZ50461@khavrinen.lcs.mit.edu> To: "Matthew Luckie" Cc: Subject: arp X moved from Y to Z messages In-Reply-To: <001501c14017$9c2e73c0$0a00a8c0@neoprene> References: <001501c14017$9c2e73c0$0a00a8c0@neoprene> 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 < said: > The gateway's IP address actually refers to two different machines. > Naturally the gateway is used quite a bit, and the syslog fills up with "arp > X moved from Y to Z on fxp0" messages. That's really not the right way to do it, and probably doesn't balance the load as well as you might think it would. The right way to do it is to advertise a single *multicast* MAC address, allocated out of the local MAC space (i.e., first two bits 11), and have both routers join the group; then both will get all the packets and can decide which ones to forward. This gives you automatic fail-over trivially. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message