From owner-freebsd-net Mon Sep 10 5:52: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id C440537B401 for ; Mon, 10 Sep 2001 05:52:01 -0700 (PDT) Received: from localhost ([3ffe:501:100f:10c1:200:39ff:fe97:3f1e]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id VAA23503; Mon, 10 Sep 2001 21:52:19 +0900 (JST) Date: Mon, 10 Sep 2001 21:51:49 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Brian Somers Cc: freebsd-net@FreeBSD.ORG Subject: Re: Forward: Re: ping gif0 In-Reply-To: <200109101054.f8AAsnJ57600@hak.lan.Awfulhak.org> References: <200109101054.f8AAsnJ57600@hak.lan.Awfulhak.org> User-Agent: Wanderlust/2.6.0 (Twist And Shout-pre) Emacs/21.0 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 33 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> On Mon, 10 Sep 2001 11:54:49 +0100, >>>>> Brian Somers said: > The local endpoint can't be pinged unless you've got a route for > it... that's just the way the routing code works. > You can ping the local address for an Ethernet interface, but that's > just because the hardware returns such packets. > Adding a loopback route or address alias is the way to handle this. Correct, but in this case, pinging the other end of the link also failed: gif0: flags=8011 mtu 1280 inet 10.0.2.130 --> 10.0.2.2 netmask 0xffffffff physical address inet 209.167.75.123 --> 209.167.75.124 waterloo.heers.on.ca# ping 10.0.2.2 PING 10.0.2.2 (10.0.2.2): 56 data bytes ^C --- 10.0.2.2 ping statistics --- 15 packets transmitted, 0 packets received, 100% packet loss I don't get the reason for this part. This is perhaps due to some IPsec issues? netstat gave us an interesting result: 34 inbound packets violated process security policy JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message