From: Ramin Dousti <ramin@cannon.eng.us.uu.net>
To: Harald Welte <laforge@netfilter.org>,
"John A. Sullivan III" <john.sullivan@nexusmgmt.com>,
Henrik Nordstrom <hno@marasystems.com>,
netfilter@lists.netfilter.org,
netfilter-devel@lists.netfilter.org
Subject: Re: TTL patch buggy?
Date: Wed, 7 Jan 2004 16:19:51 -0500 [thread overview]
Message-ID: <20040107211951.GC20346@cannon.eng.us.uu.net> (raw)
In-Reply-To: <20040107193547.GF6629@obroa-skai.de.gnumonks.org>
On Wed, Jan 07, 2004 at 08:35:47PM +0100, Harald Welte wrote:
> The most dangerous cases of incrementing the TTL are:
>
> a) incrementing the TTL of transit traffic (not close to sender or receiver)
> b) incrementing the TTL of multicast traffic
Can you explain (b) a bit more, Harald? Multicast traffic is being
dealt with by the routers in exactly the same way as the unicast
traffic with regards to the TTL (as far as I understand it).
Or did you mean by "multicast traffic", the IGMP messages?
Appreciate the explanation.
Ramin
next prev parent reply other threads:[~2004-01-07 21:19 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 [this message]
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
-- 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=20040107211951.GC20346@cannon.eng.us.uu.net \
--to=ramin@cannon.eng.us.uu.net \
--cc=hno@marasystems.com \
--cc=john.sullivan@nexusmgmt.com \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@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.