Path: usenet.ee.pdx.edu!fastrac.llnl.gov!lll-winken.llnl.gov!fnnews.fnal.gov!mp.cs.niu.edu!annex1.niu.edu!not-for-mail From: rickert@cs.niu.edu (Neil Rickert) Newsgroups: comp.sys.sun.admin Subject: Re: /etc/gateways and default routing Date: 16 Aug 1994 09:45:52 -0500 Organization: Northern Illinois University Lines: 25 Message-ID: <32qjf0$17i@ux.cs.niu.edu> References: <32pk94$h1j@cad2.seodu.co.kr> NNTP-Posting-Host: ux.cs.niu.edu jschoi@cad2.seodu.co.kr (Choi Jaeseon) writes: >Is it ok to put a default route in the /etc/gateways file? >I added the following line in the /etc/gateways file along with other >lines. > net 0 gateway 1 passive It is perfectly ok. That is what I use, and it works quite well. >It looks like that the in.routed correctly accepts an default rouing >infomation from this line when the host is booted. But, after a while >the default route entry would disappear somehow. I want to know if >such an entry in the /etc/gateways file is an allowed one. Most likely your gateway is broadcasting a default route, which replaces the passive one. Then, if the gateway fails to send routing packets for a sufficiently long period, the entry times out. If you only access one gateway on your subnet, and if the only route you need to add is a default one, an alternative would be to add it with the 'route' command, and not run 'in.routed' at all. In that case, since you are not running in.routed, it is unlikely to time out the route.