From owner-freebsd-hackers  Mon Apr  1 19:47:06 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA29942
          for hackers-outgoing; Mon, 1 Apr 1996 19:47:06 -0800 (PST)
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA29928
          for <hackers@freebsd.org>; Mon, 1 Apr 1996 19:47:00 -0800 (PST)
Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id RAA05694 for hackers@freebsd.org; Mon, 1 Apr 1996 17:35:58 -0800 (PST)
Date: Mon, 1 Apr 1996 17:35:58 -0800 (PST)
From: Julian Elischer <julian@ref.tfs.com>
Message-Id: <199604020135.RAA05694@ref.tfs.com>
To: hackers@freebsd.org
Subject: Route removal on interface shutdown
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Ok So this is more a political question than a technical one..

when an interface is shut down, certain things should be removed
from the routing tables..
but how much is a judgement call:

1/ Every routing entry that points to that interface?
2/ Only those that were automatically created?
3/ what if the default points out there as well?
4/ only cloned routes?
5/ should all ARP entries be flushed as well?
etc.

I tend to go for the "anything that references that interface" set..

I know how to do it, I just can't convince myself of what the RIGHT
action is