Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.sdsmt.edu!news.mid.net!news.dra.com!news.starnet.net!spool.mu.edu!howland.erols.net!nntp.crl.com!crl.crl.com!not-for-mail From: skimmel@crl.com (Stephen J. Kimmel) Newsgroups: comp.unix.bsd.bsdi.misc Subject: how to increase socket timeout Date: 4 Sep 1996 09:04:15 -0700 Organization: CRL Network Services (415) 705-6060 [Login: guest] Lines: 22 Message-ID: <50k99v$53p@crl.crl.com> NNTP-Posting-Host: crl.com X-Newsreader: TIN [version 1.2 PL2] How can I increase the length of time a socket will wait for response from a remote host before timing out? We are running a Gauntlet firewall on a bsdi 2.1 pentium system and are having a problem with connections timing out after about 1 minute. If the remote host comes back after that timeout the packet filtering code on the firewall says that "host xyz connecting on port 53 - unused port." In other words, the process on the bsdi system is no longer listening (blocking?) on the port expecting a return packet from the remote system, and when the packet finally does come back the system treats it like an unsolicited / invalid packet. I've asked the firewall vendor but they maintain it isn't their code that controls things like whether or not the resolver waits for x amount of time for a DNS query to be answered. Is there a kernel parameter that controls this? Any help would be welcome. Thanks. -- Steve Kimmel skimmel@crl.com Phoenix, Arizona