From owner-freebsd-hackers Sun Jul 14 02:02:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA07914 for hackers-outgoing; Sun, 14 Jul 1996 02:02:16 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA07904 for ; Sun, 14 Jul 1996 02:02:11 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id JAA01382; Sun, 14 Jul 1996 09:01:56 GMT Date: Sun, 14 Jul 1996 18:01:56 +0900 (JST) From: Michael Hancock To: michael butler cc: Archie Cobbs , freebsd-hackers@freebsd.org Subject: Re: interfaces, routes, etc. In-Reply-To: <199607140623.QAA00562@walkabout.asstdc.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 14 Jul 1996, michael butler wrote: > > - When you bring an EtherNet interface up and ping some addresses > > on that network, you get automatically generated LINK layer routes > > (ie, arp entries). However, when you bring the interface down > > these routes do not automatically go away. > > I must admit that I was puzzled as to why it was necessary to add MAC > addresses into the route table. I thought they belonged in the ARP table and > nowhere else .. use arp -d to remove the entries. The arp table and routes are in a data structure called a radix trie. It's a structure that assumes routes and links don't change very often and it optimizes lookups at the expense of additions and deletions, though these don't seem to be that slow. -mike hancock