Date: Wed, 21 Jan 1998 15:08:53 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: Wally Waliany <wally@scv.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: No Route To Host Message-ID: <Pine.BSF.3.96.980121150702.5192Q-100000@gdi.uoregon.edu> In-Reply-To: <3.0.1.32.19980118090718.00b1f1e8@scv.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 18 Jan 1998, Wally Waliany wrote: > Recently I have been having problems with one of my FreeBSD servers(2.1.0) > where the DNS server is not working as the web browsers respond with server > not found message. When this has happened(every 2 hrs or so) I try to do > traceroute to any site and I get the No Route to host message. The other > FreeBSD box does not have this problem, that is I can traceroute to any > sites. I have to reload my router to fix this situation on my server and I > have to do this every 2 hours. I had the same problem at Thanksgiving for a > week and it went away. What can I do to fix this problem. This server was > working for almost a year before I had this problem at Thanksgiving. Are you running routed? If you don't need to, try disabling it; this will insulate your servers from being taken down when the router goes on the fritz. Routed removes any default routes, so if your net route gets busted by a fried router, your computer can't figure out how to talk to the rest of the world. Don't forget to add a default route if you haven't been running one. One of the UOs routers killed my box in my first year here with the same type of problem; routed died a quick and painless death. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980121150702.5192Q-100000>