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 384661381F3 for ; Sun, 1 Sep 2013 19:10:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 390DEE1072; Sun, 1 Sep 2013 19:10:46 +0000 (UTC) Received: from mail-we0-f169.google.com (mail-we0-f169.google.com [74.125.82.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0BD31E0F81 for ; Sun, 1 Sep 2013 19:10:44 +0000 (UTC) Received: by mail-we0-f169.google.com with SMTP id p60so785106wes.0 for ; Sun, 01 Sep 2013 12:10:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=Hr6SL3NFHFTweMOrLca7EDMXcXOIoe4szzPdVn5Z788=; b=JMvHkVS72nr5iCPVKhwWskFpeq9PiAHDYqdGNUCxHD25Ke6yWAsk+PWqw7zwWGKqf6 Y0tJhedeW51S3ntOv7FswARpNtaa6C/pBC3ihkL0GKTFoWJFMZqqHjoafw9WHdYSZC/b dkAKix0wwT9JaOgaSVPZ2+irJy2vHG9VV+ztQgSugSr5GZy80ii4/t60pFX4V/OmUzUi egB0zv67HIEEaugthbosA9dRI3vfHSy2cGOl9LXTSWZC6kqCIEMAvzqXlUlT4RRg7/kT 1rbDfxVRYm/7DLodERMd2F+KxVZIU5awLZ05jinDJLdHIRWVySJI0fB3GWzXXXbR2Ij/ yJ4A== X-Received: by 10.194.202.230 with SMTP id kl6mr20107939wjc.9.1378062643606; Sun, 01 Sep 2013 12:10:43 -0700 (PDT) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by mx.google.com with ESMTPSA id a8sm12948652wie.6.1969.12.31.16.00.00 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 01 Sep 2013 12:10:42 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Can't ping remote system Date: Sun, 1 Sep 2013 20:10:19 +0100 User-Agent: KMail/1.13.7 (Linux/3.10.7-gentoo; KDE/4.10.5; x86_64; ; ) References: <52238823.9060008@gmail.com> In-Reply-To: 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 Content-Type: multipart/signed; boundary="nextPart65626408.m0PLBP1XFl"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201309012010.22227.michaelkintzios@gmail.com> X-Archives-Salt: 2d4f57ae-a346-4e2d-939b-9acc70624eef X-Archives-Hash: e8c3d8d907950e84b1688644977008bf --nextPart65626408.m0PLBP1XFl Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sunday 01 Sep 2013 19:50:53 Grant wrote: > >> 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? > >=20 > > 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. >=20 > 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 i= t=20 up to respond to ping (or set it to forward all packets with ICMP protocol = to=20 your server while you're troubleshooting this). After you set up your router/server to respond you should be getting a=20 different mtr or traceroute output showing any hops in between you and your= =20 server that are dropping packets. You may have to contact them if they are= =20 running a saturated link which is not allowing you to use the service you a= re=20 paying them for. Here's an example of saturated links: # mtr -r -c 9 -n bbc.co.uk Start: Sun Sep 1 20:03:24 2013 HOST: dell_xps Loss% Snt Last Avg Best Wrst StDev [snip ...] 4.|-- 195.66.224.103 0.0% 9 65.8 41.1 26.0 77.3 19.1 5.|-- ??? 100.0 9 0.0 0.0 0.0 0.0 0.0 6.|-- ??? 100.0 9 0.0 0.0 0.0 0.0 0.0 7.|-- 132.185.254.109 0.0% 9 28.1 32.5 27.0 55.7 9.7 8.|-- 132.185.255.140 0.0% 9 27.0 27.5 26.4 29.0 0.6 9.|-- 212.58.251.195 0.0% 9 27.5 28.0 27.1 28.9 0.4 =2D-=20 Regards, Mick --nextPart65626408.m0PLBP1XFl Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQEcBAABAgAGBQJSI5EeAAoJELAdA+zwE4Ye8HoH/iKvh7XFE4qT+7lXZn/+d+tA 1LLzxxvRN3aG+xEupxQBi43Ok0R1rHkUkRiswg3YlniMWpxrejOEg9rxp5iLFe2R Nv0W2xmZDm/QgtrqkbPqBlM3IMJP/VVNcpl89VgWAPE7SAD94nQkS4roC2bachFf RlyRc9sdINH9NvL3xTQKkj5B4uicMqNn984haQ2UgL/5G+vRN+rD/GFIUuizXvda T2AQ+zMvQqR66od5idv3vc65Q+wUy1ioE/5HyuQSTJgRr1dznIZoHIwUXJG0H9UP 8wbAUgYsVs77yZUnThH54eerZ6ZqG5SdKduBYwgTw61NJSYcDZoYaL4P348scDc= =dD2Q -----END PGP SIGNATURE----- --nextPart65626408.m0PLBP1XFl--