From owner-freebsd-hackers Wed Jan 13 16:06:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24913 for freebsd-hackers-outgoing; Wed, 13 Jan 1999 16:06:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24902 for ; Wed, 13 Jan 1999 16:06:10 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40363>; Thu, 14 Jan 1999 11:04:15 +1100 Date: Thu, 14 Jan 1999 11:04:44 +1100 From: Peter Jeremy Subject: Re: freebsd-hackers-digest V4 #364 To: hackers@FreeBSD.ORG Message-Id: <99Jan14.110415est.40363@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 13 Jan 1999 00:43:18 +0100, sthaug@nethelp.no wrote: >If you ping the IP address associated with the NIC from *the host itself*, >it won't be put on the wire. You have to ping it from another host. Actually, this is an artifact of the 4.4BSD IP stack: If you look at the routing tables, you will see there is an explicit entry routing your hosts own IP address through lo0. In theory, you should be able to route packets to your own IP address via the NIC (in which case they _will_ be seen by tcpdump and will probably appear on the wire), but I can't work out the correct incantation. Other OSs may behave differently: DEC OSF/1 seems to send the packet over the wire, Solaris 2.5 seems not to. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message