[EMAIL PROTECTED] writes: > > You don't need /etc/gateways for normal operation. You need it if the > > defaults for in.routed (documented in the man page) aren't what you > > want. > > > > This is a good enough answer for my procedure. I assume that most people > want the default operation for in.routed and have no need to further > configure /etc/gateways.
Yes. It's there so that you can do fancy things, such as enable or disable a particular protocol on a particular interface, customize the route summarization, supply authentication keys, or turn on or off special features. Most should not need to use it. In particular, /etc/gateways is _not_ the right way to configure static routes. There are some who try to do this, and the legacy 'net' entries do this as a side effect, but it has never quite worked right. If you want static routes, look at "route -p add ..." instead. -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
