-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
"jlewis" == jlewis <jlewis@lewis.org> writes:
jlewis> On Tue, 16 May 2000, Roeland M.J. Meyer wrote: >> > ww@shadowfax.styx.org: Tuesday, May 16, 2000 10:34 PM >> >> > What is the general feeling about running routing protocols >> on > web/dns/mail servers? [...] jlewis> Running a routing protocol on a unix box doesn't mean jlewis> you're using it as a router. Perhaps he just wants OSPF jlewis> on a few servers so they can send their packets more jlewis> efficiently. Consider a case where you have a few access jlewis> servers and unix servers on the same switch and a router jlewis> connecting that POP to your backbone. Having a routing jlewis> protocol on those unix boxes means they can send packets jlewis> directly to the appropriate access server (or the router) jlewis> rather than everything to the router, just to have it spit jlewis> the packets back out headed for an access server on that jlewis> segment. Correct. It also means that they can inject some routing information - -- i.e. that the ip address configured onto their loopback interface is reachable through the ip address on their ethernet interface subject to a certain cost. The intent is to provide an efficient failover mechanism (one host crashes, a backup host is automatically used since they both have the same address on their loopbacks, but the backup is advertising it with a higher cost), as well as the ability to easily relocate services to different machines and load balance in a way that doesn't break if one host goes away (à la DNS round-robin) or cost a fortune (à la local-director). - -w - -- Will Waites \________ ww@shadowfax.styx.org\____________________________ Idiosyntactix Ministry of Research and Development\ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (OpenBSD) Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard <http://www.gnupg.org/> iQEXAwUBOSQl5g4cK24IcAwYFAOpywP/SjUKo09WCeBW0Wjq+6znsYJ6Eh7+Tirh Ik7To9fFie00kmpc4VSYitKFpQEBNX7qN9y0vtdq0B5hzzUbUeDqip+xM3gdPO5G VV2wSdob84S59eruRl6zqU7+WrcCqW5kq5OG9e3U1sG/5b38jcJbFB8KgvXwthgO I8aZhsEK6YkD/RRZNEtkLbwHvBdMXI4SpxVIY5rjWCIbmgriGHzenJ9NVOXufgqv KeJ8617eFcgSOCZUMtopoT2Q+Iorzm1nVGLHNdI8F/vTutV0RDgSGKjhOqx9yK69 aoVLsuqzr8qVQolzNh3ZPOZh2a2YkvpgtMDVK5fsSxrqNc37/4C4aYBl =6Zzr -----END PGP SIGNATURE-----