From owner-freebsd-security Wed Jun 16 12:33:23 1999 Delivered-To: freebsd-security@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E8D0B15286 for ; Wed, 16 Jun 1999 12:33:16 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA51702; Wed, 16 Jun 1999 13:33:15 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA01189; Wed, 16 Jun 1999 13:33:17 -0600 (MDT) Message-Id: <199906161933.NAA01189@harmony.village.org> To: Poul-Henning Kamp Subject: Re: named timeouts Cc: security@FreeBSD.ORG In-reply-to: Your message of "Wed, 16 Jun 1999 13:41:40 +0200." <10262.929533300@critter.freebsd.dk> References: <10262.929533300@critter.freebsd.dk> Date: Wed, 16 Jun 1999 13:33:17 -0600 From: Warner Losh Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <10262.929533300@critter.freebsd.dk> Poul-Henning Kamp writes: : My guess is that the following happens: I don't think it is even that complex. I was able to recreate it just now. First the packet trace: 13:28:45.613210 harmony.4302 > rover.domain: 29085+ A? slow.com. (26) 13:28:45.952766 rover.domain > harmony.4302: 29085* 1/2/2 (117) 13:28:45.952997 harmony > rover: icmp: harmony. udp port 4302 unreachable And in my /var/log/messages (slightly edited) 13:28:45 harmony /k: Connection attempt to UDP 10.0.0.6:4302 from 10.0.0.1:53 And in another X term: % nslookup Default Server: rover Address: 10.0.0.1 > slow.com Server: rover.village.org Address: 10.0.0.1 ^C # Typed quickly > There weren't multiple packets involved, just that the listening socket closed before the answer came back... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message