Date: Fri, 27 Oct 2000 02:21:52 -0400 (EDT) From: "Richard A. Steenbergen" <ras@e-gerbil.net> To: Nick Rogness <nick@rapidnet.com> Cc: Bakul Shah <bakul@torrentnet.com>, Ron 'The InSaNe One' Rosson <insane@lunatic.oneinsane.net>, freebsd-net@FreeBSD.ORG Subject: Re: Multihomed Routing Message-ID: <Pine.BSF.4.21.0010270205210.10623-100000@overlord.e-gerbil.net> In-Reply-To: <Pine.BSF.4.21.0010262335480.89387-100000@rapidnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 26 Oct 2000, Nick Rogness wrote: > You are assuming that the network that machine1 lies on has only 1 > machine on it. What happens when you add 2 more machines to that > network? Now, router1 has to handle redirects for all of those > machines as well. > > 1 machine = 200 redirects > 2 machines = 400 redirects (200 for machine1 & 200 for machine2) > 3 machines = 600 redirects In practice this is beyond silly (and most hosts should probably not be honoring redirects for security reasons). If reliability is that important to you, you should have routers which support a redundancy protocol. This will scale many orders of magnitude further then informing every host of available routes, especially as the number of hosts and the number of routes increase. The only advantages of pushing the routing decision down to the host is A) load balancing, and B) the asthetic value of one less hop if the best exit is not available on the router you ended up hitting. For point A, if you have two NICs and a legitimate need to balance across them at an IP layer, go for it. For point B, I would venture to bet that the local communication between two routers sitting beside each other is far more reliable then trying to push a full routing table down to every host. :P And if you design your network correctly many of these become non-issues. -- Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/humble PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0010270205210.10623-100000>