From: Ralph Spitzner Newsgroups: comp.os.linux.networking Subject: Re: iptables NAT forwarding adding 75-100ms Date: Fri, 04 May 2012 09:22:59 +0200 Organization: Hanswurst & Kaspar Hauser Ltd. Lines: 32 Message-ID: References: NNTP-Posting-Host: RvCFikQlDO31yztxmContQ.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120429 Firefox/12.0 SeaMonkey/2.9.1 X-Notice: Filtered by postfilter v. 0.8.2 Path: csiph.com!usenet.pasdenom.info!bete-des-vosges.org!feed.ac-versailles.fr!gegeweb.org!aioe.org!.POSTED!not-for-mail Xref: csiph.com comp.os.linux.networking:1364 Pascal Hambourg wrote: > >> --- 68.86.118.57 ping statistics --- > > What is that address ? Comcast Cable Communications, Inc. JUMPSTART-2 (NET-68-80-0-0-1) 68.80.0.0 - 68.87.255.255 Comcast Cable Communications, Inc. COMCAST-16 (NET-68-86-64-0-1) 68.86.64.0 - 68.86.127.255 As told by `whois` :-) To the OP: It's always a good idea to ping an address you a) know b) know the distance to c) maybe use `traceroute -n` instead As the ghoul for instance has many IP addresses for the same domai name, so the DNS is not the problem but just by pinging e.g. google.com you're probably pinging a dozen different IP's... No offense, just my 0.02 Drachmen :-P -rasp -- See why I hate Windows users? All pain, no gain. -Howard Chu