From owner-freebsd-hackers Tue Mar 24 17:51:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08076 for freebsd-hackers-outgoing; Tue, 24 Mar 1998 17:51:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08001 for ; Tue, 24 Mar 1998 17:50:26 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id UAA22155; Tue, 24 Mar 1998 20:50:18 -0500 (EST) Date: Tue, 24 Mar 1998 20:50:18 -0500 (EST) From: Snob Art Genre To: Tom cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ARP REQUEST question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Mar 1998, Tom wrote: > > Probably. Also, let's say an ARP frame does get corrupted. Where do > > Ahh.. no. An error check is critical for ARP, as you will be using this > information to locate a particular system. Thankfully, ethernet framing > provides an error-check. You're right, but -- The question was about ARP requests, wasn't it? Let's say I want to talk to you, and my request gets corrupted. My ARP code should retransmit fairly quickly. For ARP replies, yes, corruption would be a Bad Thing. Good thing there's that CRC I forgot about. :-) > Huh? Why would it get retransmitted? Some devices cache ARP entries > for 2 hours, before making another request. Only if the request is completed (in the case of a corrupted ARP reply). If a request gets corrupted enough times to time out, which is pretty unlikely, all I get is an incomplete ARP entry, which lasts three minutes on most systems, if I recall correctly. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message