Bug 35604

Summary: arp(4) page mentions 10Mb/s but not 100Mb/s.
Product: Documentation Reporter: Gary W. Swearingen <swear>
Component: Books & ArticlesAssignee: freebsd-doc (Nobody) <doc>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Gary W. Swearingen 2002-03-06 23:40:01 UTC
The arp(4) man page says it only supports 10Mb/s Ethernet, while it
seems to support 100Mb/s (and maybe gigabit Ethernet, FAIK).  (I'm not
sure why it mentioned 10Mb/s to begin with, and I don't feel
knowledgeable enough about the subject to change it.)

================

Fix: 

?
How-To-Repeat: n/a
================
Comment 1 Mike DeGraw-Bertsch 2002-04-04 17:30:14 UTC
Howdy,

Mark Tinguely tells me that ARP works for all speeds of Ethernet.  The 
patch below reflects that.

   -Mike

--- arp.4.old   Thu Apr  4 11:09:54 2002
+++ arp.4       Thu Apr  4 11:11:05 2002
@@ -42,9 +42,9 @@
  .Cd "pseudo-device ether"
  .Sh DESCRIPTION
  The Address Resolution Protocol (ARP) is a protocol used to dynamically
-map between Internet host addresses and 10Mb/s Ethernet addresses.
-It is used by all the 10Mb/s Ethernet interface drivers.
-It is not specific to Internet protocols or to 10Mb/s Ethernet,
+map between Internet host addresses and Ethernet addresses.
+It is used by all the Ethernet interface drivers.
+It is not specific to Internet protocols or to Ethernet,
  but this implementation currently supports only that combination.
  .Pp
  ARP caches Internet-Ethernet address mappings.
Comment 2 Gary W. Swearingen 2002-04-04 20:29:54 UTC
Mike DeGraw-Bertsch <mbertsch@radioactivedata.org> writes:

> Howdy,
> 
> Mark Tinguely tells me that ARP works for all speeds of Ethernet.  The
> patch below reflects that.

[new version:]
>   The Address Resolution Protocol (ARP) is a protocol used to dynamically
> +map between Internet host addresses and Ethernet addresses.
> +It is used by all the Ethernet interface drivers.
> +It is not specific to Internet protocols or to Ethernet,
>   but this implementation currently supports only that combination.

That last sentence seems wrong in light of the first two.  I'm no
expert, but I thought ARP was precisely specific to Ethernet.
If that's correct, there's no "combination" left, and maybe the whole
sentence is unneeded.  It's not clear what the leftover would be trying
to say.  That ARP doesn't need to use Internet Protocol, but this
implementation does?  ??  It should be cleared up or cleared out.
Comment 3 Mike DeGraw-Bertsch 2002-04-04 21:05:11 UTC
Thanks for the clarification.  I've revised my patch to accurately 
reflect both what the ARP protocol does, and what the FreeBSD 
implementation does.  Let me know how it looks.

   -Mike

--- arp.4.old   Thu Apr  4 11:09:54 2002
+++ arp.4       Thu Apr  4 15:01:34 2002
@@ -41,13 +41,14 @@
  .Sh SYNOPSIS
  .Cd "pseudo-device ether"
  .Sh DESCRIPTION
-The Address Resolution Protocol (ARP) is a protocol used to dynamically
-map between Internet host addresses and 10Mb/s Ethernet addresses.
-It is used by all the 10Mb/s Ethernet interface drivers.
-It is not specific to Internet protocols or to 10Mb/s Ethernet,
-but this implementation currently supports only that combination.
+The Address Resolution Protocol (ARP) is used to dynamically
+map between Protocol Addresses (such as IP addresses) and Local Network
+Addresses (such as Ethernet addresses).
+This implementation maps IP addresses to Ethernet, ARCnet, or Token Ring
+addresses.
+It is used by all the Ethernet interface drivers.
  .Pp
-ARP caches Internet-Ethernet address mappings.
+ARP caches address mappings.
  When an interface requests a mapping for an address not in the cache,
  ARP queues the message which requires the mapping and broadcasts
  a message on the associated network requesting the address mapping.
Comment 4 brooks 2002-04-04 21:15:52 UTC
On Thu, Apr 04, 2002 at 03:05:11PM -0500, Mike DeGraw-Bertsch wrote:
> Thanks for the clarification.  I've revised my patch to accurately 
> reflect both what the ARP protocol does, and what the FreeBSD 
> implementation does.  Let me know how it looks.

This looks fine to me.

-- Brooks
Comment 5 Jeroen Ruigrok van der Werven freebsd_committer freebsd_triage 2002-04-05 22:59:20 UTC
State Changed
From-To: open->closed

Committed, thanks!