From owner-freebsd-hackers Mon Aug 31 18:10:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19892 for freebsd-hackers-outgoing; Mon, 31 Aug 1998 18:10:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19868 for ; Mon, 31 Aug 1998 18:10:39 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-119.camalott.com [208.229.74.119]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id UAA08536; Mon, 31 Aug 1998 20:11:08 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id UAA11696; Mon, 31 Aug 1998 20:09:07 -0500 (CDT) (envelope-from joelh) Date: Mon, 31 Aug 1998 20:09:07 -0500 (CDT) Message-Id: <199809010109.UAA11696@detlev.UUCP> To: freebsd-hackers@FreeBSD.ORG Subject: Use of metric From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do I remember hearing some caveats about the use of ifconfig's metric under FreeBSD? Another question: Is there a reason that the following sequence: ifconfig ep0 inet 192.168.13.3 netmask 255.255.255.0 down ifconfig ed0 inet 192.168.13.1 netmask 255.255.255.0 configures ep0 to be the selected interface? More to the point, would it be useful if I made the changes to cause interfaces configured as down to not go into the routing table at configuration time? Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message