From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C0A0C1381F3 for ; Mon, 2 Sep 2013 18:17:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A2BCCE0C4E; Mon, 2 Sep 2013 18:17:11 +0000 (UTC) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 828A1E09DD for ; Mon, 2 Sep 2013 18:17:10 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id hj3so1006638wib.1 for ; Mon, 02 Sep 2013 11:17:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=dnbXjOgn5KCF+YeKr2EJ39jev6dep8b1GeR3QyAH+ag=; b=J09n1dC/Jj5MnhB+j0Kl4LBOyOUQRgx7oWBImV4xmdgYLDpbHgcZbN0b+hWpk5xfZK Ha29j2eXjPhjoiELERedi2daMOqBaaVz65Qe3V4dTdBHwb2qUEDNPZ8O5lYELnYWMCEv EjTz37L2m2QXSlNTKvqv2s8fz0Ah/hMP9Y4ovf9r7nWBi/QmJY4Nhg8OhYOcCcEIWdbG 7v8c/k5qlZIUMBmQAnXxjrq1CAckFxsc1WfOW0ecNLiN9Q0x0jnPwKBZ+LmwFJ5BzPKG FPrRZeb5ItLDearLjpJHjaJtJkuDxGKygzsOoSRhhSFci94B7CXVw2xY/jboyJaynBx7 OFrw== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.194.178.166 with SMTP id cz6mr2520493wjc.53.1378145829037; Mon, 02 Sep 2013 11:17:09 -0700 (PDT) Received: by 10.194.93.199 with HTTP; Mon, 2 Sep 2013 11:17:08 -0700 (PDT) In-Reply-To: <201309012010.22227.michaelkintzios@gmail.com> References: <52238823.9060008@gmail.com> <201309012010.22227.michaelkintzios@gmail.com> Date: Mon, 2 Sep 2013 11:17:08 -0700 Message-ID: Subject: Re: [gentoo-user] Can't ping remote system From: Grant To: Gentoo mailing list Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 1282ca20-3b9b-4f26-a537-a2fcc11ab130 X-Archives-Hash: f7f55a483f706fa07866310ad5d105ba >> >> So the culprit is the first IP that should appear in the list but >> >> doesn't? If so, how is that helpful since it's not displayed? >> > >> > This is where it gets tricky. You identify the last router in the list >> > for which you have an address or name, and contact the NOC team for that >> > organization. Ask them for the next hop in routing for the destination >> > address you are trying to ping and hope that they will be kind enough to >> > help you out. >> >> Oh man that's funny. Really? Let's say they do pass along the info. >> Then I hunt down contact info for the culprit router based on its IP >> and tell them their stuff isn't working and hope they fix it? >> Actually, since the last IP displayed is from AT&T and my server's ISP >> is AT&T, I suppose it's extremely likely that the culprit is either an >> AT&T router somewhere or my own server and I could find out by calling >> AT&T. > > It could well be your router and it is easy to confirm this after you set it > up to respond to ping (or set it to forward all packets with ICMP protocol to > your server while you're troubleshooting this). I called AT&T and they say the Westell 6100 modem/router I have will not respond to pings. They said I could put it into bridged mode and set up PPPoE on the computer connected to it which would cause ICMP packets to pass through to the computer. Would you guys recommend that? For sure I won't attempt this until I'm in the same room as the device. - Grant