From: Harald Welte <laforge@netfilter.org>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>,
netfilter-devel@lists.netfilter.org
Subject: Re: TTL patch buggy?
Date: Wed, 7 Jan 2004 20:31:35 +0100 [thread overview]
Message-ID: <20040107193135.GE6629@obroa-skai.de.gnumonks.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0401071709030.4717-100000@filer.marasystems.com>
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
On Wed, Jan 07, 2004 at 05:16:51PM +0100, Henrik Nordstrom wrote:
> Harald: What do you think about making the patch civilised and restricting
> the TTL to be set to lower values only eleminating the need of the above
> safeguard match? (simply change "new_ttl != iph->ttl" to "new_ttl <
> iph->ttl")
No. The most common use of the TTL target is to re-increment the ttl to
64 at the gateway. This is for br0ken ISP's that don't allow you to use
a router behind your DSL line. They check if the TTL is one of the
commonly-used values (32,64,128).. .if it is an odd number, they drop
the packet.
Yes, it is dangerous. That's why we didn't put it in the stock kernel.
But still, it has valid uses :(
> Regards
> Henrik
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-07 19:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 15:02 TTL patch buggy? John A. Sullivan III
2004-01-06 18:56 ` Harald Welte
2004-01-06 22:18 ` John A. Sullivan III
2004-01-07 16:16 ` Henrik Nordstrom
2004-01-07 19:04 ` John A. Sullivan III
2004-01-07 19:18 ` Antony Stone
2004-01-07 20:44 ` Ramin Dousti
2004-01-07 19:35 ` Harald Welte
2004-01-07 20:07 ` John A. Sullivan III
2004-01-07 21:38 ` Ramin Dousti
2004-01-08 8:02 ` Cedric Blancher
2004-01-08 16:25 ` Ramin Dousti
2004-01-08 19:17 ` Cedric Blancher
2004-01-07 21:19 ` Ramin Dousti
2004-01-07 20:54 ` Henrik Nordstrom
2004-01-07 20:54 ` Henrik Nordstrom
2004-01-07 22:16 ` Ramin Dousti
2004-01-08 7:14 ` Henrik Nordstrom
2004-01-08 7:14 ` Henrik Nordstrom
2004-01-08 20:56 ` Ramin Dousti
2004-01-07 20:36 ` Ramin Dousti
2004-01-07 19:31 ` Harald Welte [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-08 14:32 bmcdowell
2004-01-02 13:13 John A. Sullivan III
2004-01-02 14:27 ` Antony Stone
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=20040107193135.GE6629@obroa-skai.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=hno@marasystems.com \
--cc=john.sullivan@nexusmgmt.com \
--cc=netfilter-devel@lists.netfilter.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.