From owner-freebsd-hackers Sat Apr 13 14:15:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA28558 for hackers-outgoing; Sat, 13 Apr 1996 14:15:55 -0700 (PDT) Received: from etinc.com (etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA28553 for ; Sat, 13 Apr 1996 14:15:50 -0700 (PDT) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id RAA08117 for ; Sat, 13 Apr 1996 17:18:59 -0400 Date: Sat, 13 Apr 1996 17:18:59 -0400 Message-Id: <199604132118.RAA08117@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: hackers@freebsd.org From: dennis@etinc.com (dennis) Subject: route with interface names Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk How painful would it be to make the changes to do the following: route add a.b.c.d -interface sl0 the goal is being able to use an interface name rather than an address. (You can do this in Linux). Aside from being easier to use and easier on the eyes, particularly with large static configs, there are situations where interfaces may not have unique addresses (as in an unnumbered serial line scenario). I'm also encountering some cases with virtual interfaces where assigning them addresses is just plain stupid.... except there currently is no choice. Dennis ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous Communications Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD and LINUX