From owner-freebsd-hackers Sat Jan 18 14:51:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA03277 for hackers-outgoing; Sat, 18 Jan 1997 14:51:14 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA03269 for ; Sat, 18 Jan 1997 14:51:09 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14958(1)>; Sat, 18 Jan 1997 14:50:34 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177476>; Sat, 18 Jan 1997 14:50:22 -0800 To: Jaye Mathisen cc: Joerg Wunsch , freebsd-hackers@freebsd.org Subject: Re: Route command breakage In-reply-to: Your message of "Fri, 17 Jan 97 09:32:44 PST." Date: Sat, 18 Jan 1997 14:50:10 PST From: Bill Fenner Message-Id: <97Jan18.145022pst.177476@crevenia.parc.xerox.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message you write: >Well, the point was more that there doesn't seem to be anyway to delete >it easily. Just replaing add with delete and various combinations didn't >remove it. True, there's no way to look that route up in the routing table, so the kernel should not have let you add it in the first place, since there's no way to delete it. (But for the same reason, you don't have to worry about it being used, so you can just leave it in the table and just get annoyed every type you type "netstat -nr") >And the &0x display stuff in the route display is certainly new. It's new as of 4.4BSD, yes. With normal fully contiguous netmasks, it looks like "/NN" where NN is the number of contiguous 1's in the netmask. The "/NN" syntax can't represent a netmask like 204.118.244.252, which is the mask on this route, so it displays it in hex with the "&0x" prefix. Bill