From owner-freebsd-questions@FreeBSD.ORG Sun Feb 13 06:56:12 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 950AE16A4CE for ; Sun, 13 Feb 2005 06:56:12 +0000 (GMT) Received: from hosea.tallye.com (joel.tallye.com [216.99.199.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6AB043D1D for ; Sun, 13 Feb 2005 06:56:11 +0000 (GMT) (envelope-from lorenl@alzatex.com) Received: from hosea.tallye.com (hosea.tallye.com [127.0.0.1]) by hosea.tallye.com (8.12.8/8.12.10) with ESMTP id j1D6uBGf002455 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 12 Feb 2005 22:56:11 -0800 Received: (from sttng359@localhost) by hosea.tallye.com (8.12.8/8.12.10/Submit) id j1D6uBOS002453; Sat, 12 Feb 2005 22:56:11 -0800 X-Authentication-Warning: hosea.tallye.com: sttng359 set sender to lorenl@alzatex.com using -f Date: Sat, 12 Feb 2005 22:56:10 -0800 From: "Loren M. Lang" To: ann kok Message-ID: <20050213065610.GX8619@alzatex.com> References: <20050212165032.1637.qmail@web52003.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050212165032.1637.qmail@web52003.mail.yahoo.com> User-Agent: Mutt/1.4.1i X-GPG-Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc X-GPG-Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C cc: freebsd-questions@freebsd.org Subject: Re: ping question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2005 06:56:12 -0000 On Sat, Feb 12, 2005 at 08:50:32AM -0800, ann kok wrote: > Hi all > > I ping from redhat to cisco router and freebsd router > but I don't understand ttl (time to live) > > Cisco router has ttl=251 and freebsd router has 58 > Does it set by the router itself? > Can I change it in freebsd? FreeBSD's default ttl, I believe, is 64, Cisco's is probably 255. As long as the number of hops neccessary to get to a certain computer is never more than 64, there's nothing wrong with it. The highest I've seen is about 30 and the Internet is going to have to grow a bit, I think, before it's an issue. > > Thank you > > 64 bytes from 212.223.x.193: icmp_seq=1151 ttl=251 > time=100 ms > 64 bytes from 212.223.x.193: icmp_seq=1152 ttl=251 > time=103 ms > 64 bytes from 212.223.x.193: icmp_seq=1153 ttl=251 > time=104 ms > 64 bytes from 212.223.x.193: icmp_seq=1154 ttl=251 > time=106 ms > > 64 bytes from 212.x.254.4: icmp_seq=1182 ttl=58 > time=105 ms > 64 bytes from 212.x.254.4: icmp_seq=1183 ttl=58 > time=105 ms > 64 bytes from 212.x.254.4: icmp_seq=1184 ttl=58 > time=104 ms > 64 bytes from 212.x.254.4: icmp_seq=1185 ttl=58 > time=108 ms > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C