Date: Wed, 16 Jun 1999 13:33:17 -0600 From: Warner Losh <imp@harmony.village.org> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: security@FreeBSD.ORG Subject: Re: named timeouts Message-ID: <199906161933.NAA01189@harmony.village.org> In-Reply-To: Your message of "Wed, 16 Jun 1999 13:41:40 %2B0200." <10262.929533300@critter.freebsd.dk> References: <10262.929533300@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906161933.NAA01189>