Date: Mon, 12 Mar 2001 20:52:53 -0500 (EST) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Ruslan Ermilov <ru@FreeBSD.ORG> Cc: Bill Fumerola <billf@mu.org>, Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, freebsd-bugs@FreeBSD.ORG Subject: Re: bin/25584: arp.c - better printed ether address Message-ID: <200103130152.UAA66526@khavrinen.lcs.mit.edu> In-Reply-To: <20010309114537.A19746@sunbay.com> References: <200103072200.f27M02o56673@freefall.freebsd.org> <20010307195349.H31752@elvis.mu.org> <20010309114537.A19746@sunbay.com>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Fri, 9 Mar 2001 11:45:37 +0200, Ruslan Ermilov <ru@FreeBSD.ORG> said: > comparison, how route(8) and netstat(1) output Ethernet addresses. > (I know that kernel prints Ethernet addresses differently.) route(8) does not output Ethernet addresses; it outputs generic link-layer addresses. A utility which is Ethernet-specific should output an Ethernet address in the appropriate format (i.e., aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff). The output of netstat(8) is inconsistent. `netstat -i' shows: Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll dc0 1500 <Link#1> 00:a0:cc:58:41:30 819592 0 642740 0 19 The corresponding route is shown by `netstat -r' thus: Destination Gateway Flags Refs Use Netif Expire 18.23.11.98 0:a0:cc:58:41:30 UHLW 0 1184 lo0 I don't think either `route' or `netstat' has any business knowing anything more than ``it's a link-layer address, print it appropriately''. `arp' on the other hand knows that it's dealing with Ethernet addresses; I would by mighty pissed if I could not cut and paste the output of `arp -a' into my router's `show fdb' command. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200103130152.UAA66526>