Date: Fri, 8 Nov 2002 14:30:46 -0600 From: Michael Owens <mike@mikesclutter.com> To: Jonathan Chen <jonc@chen.org.nz> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Unresponsive when default route is down Message-ID: <200211081430.46587.mike@mikesclutter.com> In-Reply-To: <20021108193345.GA42436@grimoire.chen.org.nz> References: <200211081109.23830.mike@mikesclutter.com> <20021108193345.GA42436@grimoire.chen.org.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
Yep that's it. It was resolving LAN IPs via the default route, which when down, caused it to take a long time to time out. I did not properly configure the router to consult the internal DNS server: my IPF rules were blocking it. Once I modified them, it works like a charm, with or without the default gateway. Thanks for your help. Michael Owens On Friday 08 November 2002 01:33 pm, Jonathan Chen wrote: > On Fri, Nov 08, 2002 at 11:09:23AM -0600, Michael Owens wrote: > > I have a 4.4 STABLE machine with a Sangoma WANPipe, configured as a > > router, using IPNAT/IPF. Up until last week, it had a 370+ day uptime, no > > problems whatsoever. Since last week, I have had problems with our > > upstream provider -- the link has gone down several times. > > > > The problem is that when the link goes down, within five or ten minutes > > the router's network services become unreponsive. I can't SSH in, can't > > ping, the DHCP and interal DNS services are non-repsonsive - nothing. Not > > only does is not route, it does not communicate with any hosts on the > > LAN. Is it trying to reverse DNS via the default route and freezing > > there? > > Possibly. Have you set up an internal DNS for your LAN? As a general > rule, every LAN should have internal DNS instead of resolving off the > 'Net directly. > > Cheers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211081430.46587.mike>