From: "George Bonser" <george@gator.com>
To: "Mikael Abrahamsson" <swmike@swm.pp.se>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] Linux default IP ttl
Date: Sun, 15 Jul 2001 03:34:28 -0700 [thread overview]
Message-ID: <CHEKKPICCNOGICGMDODJIEELDKAA.george@gator.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0107151209290.2352-100000@uplift.swm.pp.se>
> What problems could occur from raising it to 128? I'd imagine routing
> loops might mean a bit more traffic, but if other major OSes are at TTL
> 128 and someone is actually having trouble with 64, then why not raise it?
I just did a traceroute to one of the IP addresses that fails with a TTL of
64 ... it is in India but the traceroute ends with a different IP address in
less than 16 hops ... proxy arp ???
Anyway ... with the address in question is able to access my server farm
with a TTL of 128 but not with 64. I have NO IDEA what those people are
doing inside their net ... and really do not care. The bottom line as far as
I am concerned is that if they can reach me, I should be able to reach them
... and with a TTL of 128, it appears that I can.
next prev parent reply other threads:[~2001-07-15 10:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-15 8:58 George Bonser
2001-07-15 10:03 ` David S. Miller
2001-07-15 10:15 ` Mikael Abrahamsson
2001-07-15 10:34 ` George Bonser [this message]
2001-07-15 10:17 ` George Bonser
2001-07-15 10:35 ` acmay
2001-07-15 11:11 ` George Bonser
2001-07-15 11:11 ` David S. Miller
2001-07-15 11:17 ` David S. Miller
2001-07-15 11:28 ` George Bonser
2001-07-15 11:30 ` David S. Miller
2001-07-15 11:42 ` George Bonser
2001-07-15 18:24 ` Steve VanDevender
2001-07-15 19:28 ` Lew Wolfgang
2001-07-15 19:51 ` George Bonser
2001-07-15 19:40 ` George Bonser
2001-07-15 20:10 ` George Bonser
2001-07-15 11:31 ` David S. Miller
2001-07-15 11:32 ` George Bonser
2001-07-15 11:20 ` George Bonser
2001-07-16 16:14 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CHEKKPICCNOGICGMDODJIEELDKAA.george@gator.com \
--to=george@gator.com \
--cc=linux-kernel@vger.kernel.org \
--cc=swmike@swm.pp.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®